Command: /usr/local/sbin/syslog-digest.py Time : 0.4648s Status : exited 0 Output : Syslog digest — 2026-08-03 22:05 EDT Processed 3,941 lines, filtered 3,385 (85%). 556 unknown (94 distinct) from 18 host(s). == abuse (1 distinct, 347 total) == Aug 3 21: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 ] [x347] == b0b02.cs.umd.edu (1 distinct, 1 total) == Aug 3 21:44:07 b0b02.cs.umd.edu rustdesk[2625621]: cannot open display: == contest (9 distinct, 43 total) == Aug 3 21:06:47 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') [x33] Aug 3 21:48:18 contest setroubleshoot[582345]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.Vl1m5B. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Aug 3 21:48:18 contest setroubleshoot[582345]: 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 Aug 3 21:48:18 contest setroubleshoot[582345]: 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 Aug 3 21:48:18 contest setroubleshoot[582345]: 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 [x2] Aug 3 21:48:18 contest setroubleshoot[582345]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.Vl1m5B. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Aug 3 21:48:18 contest setroubleshoot[582345]: 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] Aug 3 21:48:18 contest setroubleshoot[582345]: 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 Aug 3 21:48:33 contest setroubleshoot[582408]: SELinux is preventing rhsmcertd-worke from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 22835727-7fef-4cfb-b3b5-881f66888317 == csfw00a (1 distinct, 8 total) == Aug 3 21:15:28 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x8] == hackerman (7 distinct, 12 total) == Aug 3 21: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.UDVZT3”: Permission denied Aug 3 21:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4] Aug 3 21:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding Aug 3 21:20:28 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.TWWJT3”: Permission denied Aug 3 21:20:28 hackerman packagekitd[3587233]: Failed to get cache filename for libreoffice [x2] Aug 3 21:20:28 hackerman packagekitd[3587233]: Failed to get cache filename for kernel [x2] Aug 3 21:20:38 hackerman packagekitd[3587233]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == idm00 (1 distinct, 1 total) == Aug 3 21:51:16 idm00 named[1455]: client @0x7f33103716c8 10.73.240.42#64035: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 3 21:36:01 idmp0 named[5198]: client @0x7f98e88e1668 10.73.240.43#57241: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 28 total) == Aug 3 21:08:01 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x28] == neodontcare.cs.umd.edu (1 distinct, 1 total) == Aug 3 21:26:54 neodontcare.cs.umd.edu tracker-extract[2076084]: tracker_module_manager_load_modules: assertion 'initialized == TRUE' failed == newhonors2 (1 distinct, 24 total) == Aug 3 21:13:02 newhonors2 dhcpcd[696806]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Aug 3 21:09:09 outbound00.cs.umd.edu python3[2604851]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 3 21:13:06 outbound01.cs.umd.edu python3[638658]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Aug 3 21:24:27 sentry-docker00.cs.umd.edu systemd-udevd[1315234]: link_config: could not get ethtool features for veth4c30031 Aug 3 21:24:27 sentry-docker00.cs.umd.edu systemd-udevd[1315234]: Could not set offload features of veth4c30031: No such device Aug 3 21:24:27 sentry-docker00.cs.umd.edu systemd-udevd[1315330]: Could not generate persistent MAC address for veth955fd96: No such file or directory Aug 3 21:24:27 sentry-docker00.cs.umd.edu systemd-udevd[1315329]: Could not generate persistent MAC address for veth66c8a22: No such file or directory Aug 3 21:24:27 sentry-docker00.cs.umd.edu systemd-udevd[1315333]: Could not generate persistent MAC address for veth2cf7614: No such file or directory Aug 3 21:24:27 sentry-docker00.cs.umd.edu systemd-udevd[1315334]: Could not generate persistent MAC address for veth3a82a10: No such file or directory Aug 3 21:24:27 sentry-docker00.cs.umd.edu systemd-udevd[1315356]: Could not generate persistent MAC address for vethd819129: No such file or directory Aug 3 21:24:27 sentry-docker00.cs.umd.edu systemd-udevd[1315333]: Could not generate persistent MAC address for vethcedcb6a: No such file or directory Aug 3 21:24:27 sentry-docker00.cs.umd.edu systemd-udevd[1315339]: Could not generate persistent MAC address for veth92bf0f9: No such file or directory Aug 3 21:24:27 sentry-docker00.cs.umd.edu systemd-udevd[1315356]: Could not generate persistent MAC address for vethe8f174d: No such file or directory Aug 3 21:24:27 sentry-docker00.cs.umd.edu systemd-udevd[1315402]: Could not generate persistent MAC address for veth68c7ef7: No such file or directory Aug 3 21:24:27 sentry-docker00.cs.umd.edu systemd-udevd[1315408]: Could not generate persistent MAC address for veth0b31de2: No such file or directory Aug 3 21:44:35 sentry-docker00.cs.umd.edu systemd-udevd[1324758]: link_config: could not get ethtool features for veth2cf7614 Aug 3 21:44:35 sentry-docker00.cs.umd.edu systemd-udevd[1324758]: Could not set offload features of veth2cf7614: No such device Aug 3 21:44:35 sentry-docker00.cs.umd.edu systemd-udevd[1324786]: Could not generate persistent MAC address for veth2f48db4: No such file or directory Aug 3 21:44:35 sentry-docker00.cs.umd.edu systemd-udevd[1324787]: Could not generate persistent MAC address for vethfac38e6: No such file or directory Aug 3 21:44:35 sentry-docker00.cs.umd.edu systemd-udevd[1324790]: Could not generate persistent MAC address for veth4b22327: No such file or directory Aug 3 21:44:35 sentry-docker00.cs.umd.edu systemd-udevd[1324786]: Could not generate persistent MAC address for veth9354782: No such file or directory Aug 3 21:44:35 sentry-docker00.cs.umd.edu systemd-udevd[1324814]: Could not generate persistent MAC address for vethd6ccb55: No such file or directory Aug 3 21:44:35 sentry-docker00.cs.umd.edu systemd-udevd[1324815]: Could not generate persistent MAC address for veth8faf4ea: No such file or directory Aug 3 21:44:35 sentry-docker00.cs.umd.edu systemd-udevd[1324831]: Could not generate persistent MAC address for vethcb04b77: No such file or directory Aug 3 21:44:35 sentry-docker00.cs.umd.edu systemd-udevd[1324836]: Could not generate persistent MAC address for vethd9b95a9: No such file or directory Aug 3 21:44:35 sentry-docker00.cs.umd.edu systemd-udevd[1324821]: Could not generate persistent MAC address for vethd11c876: No such file or directory Aug 3 21:44:35 sentry-docker00.cs.umd.edu systemd-udevd[1324825]: Could not generate persistent MAC address for vethea70897: No such file or directory Aug 3 22:04:43 sentry-docker00.cs.umd.edu systemd-udevd[1334177]: link_config: could not get ethtool features for vethd9b95a9 Aug 3 22:04:43 sentry-docker00.cs.umd.edu systemd-udevd[1334177]: Could not set offload features of vethd9b95a9: No such device Aug 3 22:04:44 sentry-docker00.cs.umd.edu systemd-udevd[1334214]: Could not generate persistent MAC address for veth77768e8: No such file or directory Aug 3 22:04:44 sentry-docker00.cs.umd.edu systemd-udevd[1334216]: Could not generate persistent MAC address for veth6d7148c: No such file or directory Aug 3 22:04:44 sentry-docker00.cs.umd.edu systemd-udevd[1334233]: Could not generate persistent MAC address for veth8a1e233: No such file or directory Aug 3 22:04:44 sentry-docker00.cs.umd.edu systemd-udevd[1334218]: Could not generate persistent MAC address for vethd68b34f: No such file or directory ... 6 more distinct messages not shown == strawberry (2 distinct, 8 total) == Aug 3 21: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] Aug 3 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (10 distinct, 10 total) == Aug 3 21:12:52 submit26-b9-2 setroubleshoot[972771]: 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 Aug 3 21:12:52 submit26-b9-2 setroubleshoot[972771]: 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 Aug 3 21:12:52 submit26-b9-2 setroubleshoot[972771]: 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 Aug 3 21:12:52 submit26-b9-2 setroubleshoot[972771]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.em6Y0F/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Aug 3 21:12:52 submit26-b9-2 setroubleshoot[972771]: 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 Aug 3 21:12:52 submit26-b9-2 setroubleshoot[972771]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.em6Y0F. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Aug 3 21:12:52 submit26-b9-2 setroubleshoot[972771]: 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 Aug 3 21:12:52 submit26-b9-2 setroubleshoot[972771]: 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 Aug 3 21:12:52 submit26-b9-2 setroubleshoot[972771]: 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 Aug 3 22:03:06 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-3 (10 distinct, 13 total) == Aug 3 21:20:38 submit26-b9-3 setroubleshoot[814248]: 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 Aug 3 21:20:38 submit26-b9-3 setroubleshoot[814248]: 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 Aug 3 21:20:38 submit26-b9-3 setroubleshoot[814248]: 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] Aug 3 21:20:38 submit26-b9-3 setroubleshoot[814248]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.pNKrBh/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Aug 3 21:20:38 submit26-b9-3 setroubleshoot[814248]: 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] Aug 3 21:20:38 submit26-b9-3 setroubleshoot[814248]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.pNKrBh. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Aug 3 21:20:38 submit26-b9-3 setroubleshoot[814248]: 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 Aug 3 21:20:39 submit26-b9-3 setroubleshoot[814248]: 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] Aug 3 21:20:39 submit26-b9-3 setroubleshoot[814248]: 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 Aug 3 21:20:39 submit26-b9-3 setroubleshoot[814248]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.zhF75f/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 == submit26-b9-4 (1 distinct, 2 total) == Aug 3 21:21:35 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-clnb9 (9 distinct, 9 total) == Aug 3 21:31:57 submit26-clnb9 setroubleshoot[1753272]: 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 Aug 3 21:31:57 submit26-clnb9 setroubleshoot[1753272]: 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 Aug 3 21:31:57 submit26-clnb9 setroubleshoot[1753272]: 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 Aug 3 21:31:57 submit26-clnb9 setroubleshoot[1753272]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.bzeRwt/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Aug 3 21:31:57 submit26-clnb9 setroubleshoot[1753272]: 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 Aug 3 21:31:57 submit26-clnb9 setroubleshoot[1753272]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.bzeRwt. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Aug 3 21:31:57 submit26-clnb9 setroubleshoot[1753272]: 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 Aug 3 21:31:57 submit26-clnb9 setroubleshoot[1753272]: 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 Aug 3 21:31:57 submit26-clnb9 setroubleshoot[1753272]: 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