Command: /usr/local/sbin/syslog-digest.py Time : 0.5070s Status : exited 0 Output : Syslog digest — 2026-07-26 10:05 EDT Processed 4,646 lines, filtered 4,003 (86%). 643 unknown (105 distinct) from 19 host(s). == abuse (1 distinct, 346 total) == Jul 26 09:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x346] == alec.cs.umd.edu (3 distinct, 60 total) == Jul 26 09:05:05 alec.cs.umd.edu setroubleshoot[3234261]: failed to retrieve rpm info for path '/run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3': [x12] Jul 26 09:05:06 alec.cs.umd.edu sedispatch[1526]: AVC Message regarding setroubleshoot, ignoring message [x24] Jul 26 09:05:06 alec.cs.umd.edu setroubleshoot[3234261]: SELinux is preventing /usr/bin/df from getattr access on the file /run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3. For complete SELinux messages run: sealert -l 23f93208-3063-4aac-b78a-bb0fcb40740c [x24] == b0b02.cs.umd.edu (1 distinct, 1 total) == Jul 26 09:55:39 b0b02.cs.umd.edu rustdesk[736959]: cannot open display: == contest (10 distinct, 44 total) == Jul 26 09:05:19 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x34] Jul 26 09:48:13 contest setroubleshoot[112314]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.rpBamc. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Jul 26 09:48:13 contest setroubleshoot[112314]: SELinux is preventing /usr/bin/gpgconf from add_name access on the directory repodata. For complete SELinux messages run: sealert -l 41cf7b1b-0f34-4609-98f2-b66e7825fef7 Jul 26 09:48:13 contest setroubleshoot[112314]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file mirrorlist. For complete SELinux messages run: sealert -l fc20ff92-ea83-4f38-a24b-ddfd737a3141 Jul 26 09:48:13 contest setroubleshoot[112314]: SELinux is preventing /usr/libexec/platform-python3.6 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l ac675631-fa35-4e93-adc9-b692b18e53e5 Jul 26 09:48:13 contest setroubleshoot[112314]: SELinux is preventing /usr/libexec/platform-python3.6 from setattr access on the file repomd.xml.asc. For complete SELinux messages run: sealert -l ac675631-fa35-4e93-adc9-b692b18e53e5 Jul 26 09:48:13 contest setroubleshoot[112314]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.rpBamc. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Jul 26 09:48:13 contest setroubleshoot[112314]: SELinux is preventing /usr/libexec/platform-python3.6 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 7e499113-2fd7-4f67-bec6-3521efbe3637 [x2] Jul 26 09:48:14 contest setroubleshoot[112314]: SELinux is preventing /usr/libexec/platform-python3.6 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3928930b-a1ed-448d-950b-0665ac2adef8 Jul 26 09:48:16 contest setroubleshoot[112314]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file repomd.xml. For complete SELinux messages run: sealert -l fc20ff92-ea83-4f38-a24b-ddfd737a3141 == csfw00a (1 distinct, 4 total) == Jul 26 09:06:18 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x4] == emaar (1 distinct, 1 total) == Jul 26 09:42:37 emaar systemd[1]: insights-client.service: Start request repeated too quickly. == hackerman (7 distinct, 12 total) == Jul 26 09:19:01 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.OI98S3”: Permission denied Jul 26 09:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4] Jul 26 09:20:13 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding Jul 26 09:20:29 hackerman packagekitd[775620]: Failed to get cache filename for libreoffice [x2] Jul 26 09:20:29 hackerman packagekitd[775620]: Failed to get cache filename for kernel [x2] Jul 26 09:20:29 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.BZDGT3”: Permission denied Jul 26 09:20:38 hackerman packagekitd[775620]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == idm00 (1 distinct, 1 total) == Jul 26 09:51:08 idm00 named[1455]: client @0x7f330ca460c8 10.73.240.42#59812: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Jul 26 09:34:57 idmp0 named[5198]: client @0x7f990801f168 10.73.240.43#58903: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 45 total) == Jul 26 09:07:47 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x45] == newhonors2 (1 distinct, 24 total) == Jul 26 09:13:03 newhonors2 dhcpcd[306193]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 26 09:09:09 outbound00.cs.umd.edu python3[3931837]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Jul 26 09:13:06 outbound01.cs.umd.edu python3[1961135]: ldapdb [x6] == sentry-docker00.cs.umd.edu (42 distinct, 42 total) == Jul 26 09:10:39 sentry-docker00.cs.umd.edu systemd-udevd[3909773]: link_config: could not get ethtool features for veth6c5bf5f Jul 26 09:10:39 sentry-docker00.cs.umd.edu systemd-udevd[3909773]: Could not set offload features of veth6c5bf5f: No such device Jul 26 09:10:39 sentry-docker00.cs.umd.edu systemd-udevd[3909791]: Could not generate persistent MAC address for vethb5f4099: No such file or directory Jul 26 09:10:39 sentry-docker00.cs.umd.edu systemd-udevd[3909792]: Could not generate persistent MAC address for vethec30992: No such file or directory Jul 26 09:20:28 sentry-docker00.cs.umd.edu systemd-udevd[3914285]: link_config: could not get ethtool features for veth8bc8bcf Jul 26 09:20:28 sentry-docker00.cs.umd.edu systemd-udevd[3914285]: Could not set offload features of veth8bc8bcf: No such device Jul 26 09:20:29 sentry-docker00.cs.umd.edu systemd-udevd[3914335]: link_config: could not get ethtool features for veth78f79bc Jul 26 09:20:29 sentry-docker00.cs.umd.edu systemd-udevd[3914335]: Could not set offload features of veth78f79bc: No such device Jul 26 09:20:29 sentry-docker00.cs.umd.edu systemd-udevd[3914346]: Could not generate persistent MAC address for vethae7a82d: No such file or directory Jul 26 09:20:29 sentry-docker00.cs.umd.edu systemd-udevd[3914347]: Could not generate persistent MAC address for veth4188187: No such file or directory Jul 26 09:20:29 sentry-docker00.cs.umd.edu systemd-udevd[3914350]: Could not generate persistent MAC address for vethb13abc6: No such file or directory Jul 26 09:20:29 sentry-docker00.cs.umd.edu systemd-udevd[3914363]: Could not generate persistent MAC address for veth99128e6: No such file or directory Jul 26 09:20:29 sentry-docker00.cs.umd.edu systemd-udevd[3914374]: Could not generate persistent MAC address for veth001dbba: No such file or directory Jul 26 09:20:29 sentry-docker00.cs.umd.edu systemd-udevd[3914375]: Could not generate persistent MAC address for veth4064e76: No such file or directory Jul 26 09:20:29 sentry-docker00.cs.umd.edu systemd-udevd[3914393]: Could not generate persistent MAC address for veth1b35639: No such file or directory Jul 26 09:20:29 sentry-docker00.cs.umd.edu systemd-udevd[3914390]: Could not generate persistent MAC address for vethcfdcd47: No such file or directory Jul 26 09:30:47 sentry-docker00.cs.umd.edu systemd-udevd[3919425]: Could not generate persistent MAC address for veth5270173: No such file or directory Jul 26 09:30:47 sentry-docker00.cs.umd.edu systemd-udevd[3919426]: Could not generate persistent MAC address for veth84314b2: No such file or directory Jul 26 09:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3923938]: link_config: could not get ethtool features for veth001dbba Jul 26 09:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3923938]: Could not set offload features of veth001dbba: No such device Jul 26 09:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3924017]: link_config: could not get ethtool features for veth1b35639 Jul 26 09:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3924017]: Could not set offload features of veth1b35639: No such device Jul 26 09:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3924018]: Could not generate persistent MAC address for veth8691f41: No such file or directory Jul 26 09:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3924019]: Could not generate persistent MAC address for vethfd47acf: No such file or directory Jul 26 09:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3924090]: Could not generate persistent MAC address for vethad9d68e: No such file or directory Jul 26 09:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3924091]: Could not generate persistent MAC address for veth71fd3ae: No such file or directory Jul 26 09:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3924098]: Could not generate persistent MAC address for veth3136cc0: No such file or directory Jul 26 09:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3924102]: Could not generate persistent MAC address for veth269c58a: No such file or directory Jul 26 09:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3924121]: Could not generate persistent MAC address for veth7acfba5: No such file or directory Jul 26 09:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3924102]: Could not generate persistent MAC address for veth7c4a46d: No such file or directory ... 12 more distinct messages not shown == strawberry (2 distinct, 8 total) == Jul 26 09:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6] Jul 26 09:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (10 distinct, 14 total) == Jul 26 09:12:49 submit26-b9-2 setroubleshoot[229431]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l d506243c-d61e-48f3-b42a-4592c913deb0 [x2] Jul 26 09:12:49 submit26-b9-2 setroubleshoot[229431]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3b4752ac-1b9a-4af9-a05b-32e4c2eb13ab [x2] Jul 26 09:12:49 submit26-b9-2 setroubleshoot[229431]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 29e5adbd-4381-4467-b40d-a2219101e096 Jul 26 09:12:49 submit26-b9-2 setroubleshoot[229431]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.mWXX9m/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Jul 26 09:12:49 submit26-b9-2 setroubleshoot[229431]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e5f9af40-1f63-4924-b012-27ab2a7b2266 Jul 26 09:12:49 submit26-b9-2 setroubleshoot[229431]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.mWXX9m. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Jul 26 09:12:49 submit26-b9-2 setroubleshoot[229431]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 63cd60e1-1e61-4276-afea-dd8526ffe8b2 [x2] Jul 26 09:12:49 submit26-b9-2 setroubleshoot[229431]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 81c7e9ec-e023-4c6d-b1ad-c02a242e655e Jul 26 09:12:49 submit26-b9-2 setroubleshoot[229431]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 6ae9a597-e123-4d74-8eec-a8ebe0f5e4d0 [x2] Jul 26 09:12:49 submit26-b9-2 setroubleshoot[229431]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.TodktP. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 == submit26-b9-3 (10 distinct, 13 total) == Jul 26 09:20:35 submit26-b9-3 setroubleshoot[604956]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 5b912a44-22fd-4560-b201-2a4e289b73f5 Jul 26 09:20:35 submit26-b9-3 setroubleshoot[604956]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 7f1df1e4-725e-4953-98eb-1079f908f543 Jul 26 09:20:35 submit26-b9-3 setroubleshoot[604956]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 40b8852a-f77b-44b4-affe-5f11fa33de43 [x2] Jul 26 09:20:35 submit26-b9-3 setroubleshoot[604956]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Bmrx52/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Jul 26 09:20:35 submit26-b9-3 setroubleshoot[604956]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e9f0bfff-7784-4126-baa4-2bb06da56591 [x2] Jul 26 09:20:35 submit26-b9-3 setroubleshoot[604956]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Bmrx52. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 26 09:20:35 submit26-b9-3 setroubleshoot[604956]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 10e38c64-b65f-4cdd-901e-4375652d9a42 Jul 26 09:20:35 submit26-b9-3 setroubleshoot[604956]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 7fd9cf72-ef38-48e1-b6aa-b571b26a7b22 [x2] Jul 26 09:20:35 submit26-b9-3 setroubleshoot[604956]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l b9b11116-89bd-4a3c-980c-1d422c5dcee4 Jul 26 09:20:35 submit26-b9-3 setroubleshoot[604956]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.pAdmkn/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 == submit26-clnb9 (10 distinct, 14 total) == Jul 26 09:31:53 submit26-clnb9 setroubleshoot[1336967]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 6783ed2b-5ae4-42b5-975a-4bf50eec4658 [x2] Jul 26 09:31:53 submit26-clnb9 setroubleshoot[1336967]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 9e7fa955-cc30-4804-ac8c-e1779e85946c [x2] Jul 26 09:31:53 submit26-clnb9 setroubleshoot[1336967]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 69bfa6e3-089c-40ff-9563-fd30787d0774 Jul 26 09:31:53 submit26-clnb9 setroubleshoot[1336967]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.aXawU0/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Jul 26 09:31:53 submit26-clnb9 setroubleshoot[1336967]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l edacddcf-16ed-4dc3-8d82-7c597d5dee23 Jul 26 09:31:53 submit26-clnb9 setroubleshoot[1336967]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.aXawU0. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 26 09:31:53 submit26-clnb9 setroubleshoot[1336967]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 81cb3698-78f8-440a-8e3c-e5d1041e6b78 [x2] Jul 26 09:31:53 submit26-clnb9 setroubleshoot[1336967]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 792b472a-115c-4799-9805-fc7436f916b9 Jul 26 09:31:53 submit26-clnb9 setroubleshoot[1336967]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 15c83a86-837b-41e2-b662-b39cd4e361cb [x2] Jul 26 09:31:53 submit26-clnb9 setroubleshoot[1336967]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.sEcIAh. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c == zfs00.cs.umd.edu (1 distinct, 1 total) == Jul 26 09:37:20 zfs00.cs.umd.edu rsyslogd: imrelp[2514]: error 'server closed relp session, session broken', object 'lstn 2514: conn to clt 10.227.96.13/irb2156.csdips.umd.edu' - input may not work as intended [v8.2604.0 try https://www.rsyslog.com/e/2353 ]
participants (1)
-
cron/zfs00.cs.umd.edu