Command: /usr/local/sbin/syslog-digest.py Time : 0.5272s Status : exited 0 Output : Syslog digest — 2026-07-30 22:05 EDT Processed 5,090 lines, filtered 4,263 (83%). 827 unknown (88 distinct) from 20 host(s). == abuse (1 distinct, 347 total) == Jul 30 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] == alec.cs.umd.edu (3 distinct, 59 total) == Jul 30 21:05:23 alec.cs.umd.edu setroubleshoot[654131]: failed to retrieve rpm info for path '/run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3': [x12] Jul 30 21:05:24 alec.cs.umd.edu sedispatch[1526]: AVC Message regarding setroubleshoot, ignoring message [x22] Jul 30 21:05:24 alec.cs.umd.edu setroubleshoot[654131]: 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 [x25] == b0b02.cs.umd.edu (1 distinct, 1 total) == Jul 30 21:38:17 b0b02.cs.umd.edu rustdesk[1166338]: cannot open display: == bachata (1 distinct, 1 total) == Jul 30 21:35:52 bachata setroubleshoot[2191772]: SELinux is preventing /usr/sbin/smbd from name_bind access on the udp_socket port 931. For complete SELinux messages run: sealert -l 8f7247f1-69a5-4a62-a4f0-88a324bfd75c == contest (9 distinct, 42 total) == Jul 30 21:05:46 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 30 21:48:16 contest setroubleshoot[360864]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.jhXUWX. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Jul 30 21:48:16 contest setroubleshoot[360864]: 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 30 21:48:16 contest setroubleshoot[360864]: 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 30 21:48:16 contest setroubleshoot[360864]: 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 30 21:48:16 contest setroubleshoot[360864]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.jhXUWX. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Jul 30 21:48:20 contest setroubleshoot[360864]: 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 Jul 30 21:48:24 contest setroubleshoot[360864]: 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 Jul 30 21:48:36 contest setroubleshoot[360918]: 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 == csfw00a (2 distinct, 214 total) == Jul 30 21:04:41 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x210] Jul 30 21:34:30 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x4] == hackerman (7 distinct, 12 total) == Jul 30 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.3HT2S3”: Permission denied Jul 30 21:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4] Jul 30 21:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding Jul 30 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.ESWET3”: Permission denied Jul 30 21:20:28 hackerman packagekitd[2281573]: Failed to get cache filename for libreoffice [x2] Jul 30 21:20:28 hackerman packagekitd[2281573]: Failed to get cache filename for kernel [x2] Jul 30 21:20:38 hackerman packagekitd[2281573]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == idm00 (1 distinct, 1 total) == Jul 30 21:51:12 idm00 named[1455]: client @0x7f330c44b1c8 10.73.240.42#54037: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Jul 30 21:36:02 idmp0 named[5198]: client @0x7f98fc03bf48 10.73.240.43#53356: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (1 distinct, 2 total) == Jul 30 21:06:20 inbound01.cs.umd.edu krb5_child[3497989]: Preauthentication failed [x2] == itmon02 (1 distinct, 37 total) == Jul 30 21:08:14 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x37] == newhonors2 (1 distinct, 24 total) == Jul 30 21:13:02 newhonors2 dhcpcd[513086]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 30 21:09:09 outbound00.cs.umd.edu python3[1255864]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Jul 30 21:13:06 outbound01.cs.umd.edu python3[3482181]: ldapdb [x6] == sentry-docker00.cs.umd.edu (26 distinct, 26 total) == Jul 30 21:09:42 sentry-docker00.cs.umd.edu systemd-udevd[2778757]: Could not generate persistent MAC address for vethdd9fa23: No such file or directory Jul 30 21:09:42 sentry-docker00.cs.umd.edu systemd-udevd[2778758]: Could not generate persistent MAC address for vethc84d38c: No such file or directory Jul 30 21:24:47 sentry-docker00.cs.umd.edu systemd-udevd[2785243]: link_config: could not get ethtool features for vetha2d5a16 Jul 30 21:24:47 sentry-docker00.cs.umd.edu systemd-udevd[2785243]: Could not set offload features of vetha2d5a16: No such device Jul 30 21:24:47 sentry-docker00.cs.umd.edu systemd-udevd[2785268]: Could not generate persistent MAC address for veth8579395: No such file or directory Jul 30 21:24:47 sentry-docker00.cs.umd.edu systemd-udevd[2785269]: Could not generate persistent MAC address for veth359b034: No such file or directory Jul 30 21:24:47 sentry-docker00.cs.umd.edu systemd-udevd[2785272]: Could not generate persistent MAC address for vethcbde455: No such file or directory Jul 30 21:24:47 sentry-docker00.cs.umd.edu systemd-udevd[2785273]: Could not generate persistent MAC address for veth0a47e73: No such file or directory Jul 30 21:24:47 sentry-docker00.cs.umd.edu systemd-udevd[2785277]: Could not generate persistent MAC address for veth8ae6be1: No such file or directory Jul 30 21:24:47 sentry-docker00.cs.umd.edu systemd-udevd[2785279]: Could not generate persistent MAC address for vethc5d4889: No such file or directory Jul 30 21:24:47 sentry-docker00.cs.umd.edu systemd-udevd[2785292]: Could not generate persistent MAC address for veth758dbdd: No such file or directory Jul 30 21:24:47 sentry-docker00.cs.umd.edu systemd-udevd[2785273]: Could not generate persistent MAC address for veth33f0038: No such file or directory Jul 30 21:29:46 sentry-docker00.cs.umd.edu systemd-udevd[2788371]: Could not generate persistent MAC address for vethba88aa0: No such file or directory Jul 30 21:29:46 sentry-docker00.cs.umd.edu systemd-udevd[2788372]: Could not generate persistent MAC address for veth01b1602: No such file or directory Jul 30 21:44:55 sentry-docker00.cs.umd.edu systemd-udevd[2794643]: link_config: could not get ethtool features for veth8ae6be1 Jul 30 21:44:55 sentry-docker00.cs.umd.edu systemd-udevd[2794643]: Could not set offload features of veth8ae6be1: No such device Jul 30 21:44:55 sentry-docker00.cs.umd.edu systemd-udevd[2794739]: Could not generate persistent MAC address for vethcb65f4e: No such file or directory Jul 30 21:44:55 sentry-docker00.cs.umd.edu systemd-udevd[2794738]: Could not generate persistent MAC address for veth1eaa106: No such file or directory Jul 30 21:44:55 sentry-docker00.cs.umd.edu systemd-udevd[2794757]: Could not generate persistent MAC address for veth777a0a4: No such file or directory Jul 30 21:44:56 sentry-docker00.cs.umd.edu systemd-udevd[2794746]: Could not generate persistent MAC address for vethb82cb88: No such file or directory Jul 30 21:44:56 sentry-docker00.cs.umd.edu systemd-udevd[2794766]: Could not generate persistent MAC address for vetha798aac: No such file or directory Jul 30 21:44:56 sentry-docker00.cs.umd.edu systemd-udevd[2794767]: Could not generate persistent MAC address for vethf308b54: No such file or directory Jul 30 21:44:56 sentry-docker00.cs.umd.edu systemd-udevd[2794785]: Could not generate persistent MAC address for veth1d89a41: No such file or directory Jul 30 21:44:56 sentry-docker00.cs.umd.edu systemd-udevd[2794792]: Could not generate persistent MAC address for veth6d5df45: No such file or directory Jul 30 21:49:50 sentry-docker00.cs.umd.edu systemd-udevd[2797820]: Could not generate persistent MAC address for veth76bf89b: No such file or directory Jul 30 21:49:50 sentry-docker00.cs.umd.edu systemd-udevd[2797821]: Could not generate persistent MAC address for veth79e61d8: No such file or directory == strawberry (2 distinct, 8 total) == Jul 30 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] Jul 30 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (10 distinct, 16 total) == Jul 30 21:08:06 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] Jul 30 21:12:50 submit26-b9-2 setroubleshoot[667121]: 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 30 21:12:50 submit26-b9-2 setroubleshoot[667121]: 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 30 21:12:50 submit26-b9-2 setroubleshoot[667121]: 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 30 21:12:50 submit26-b9-2 setroubleshoot[667121]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ETxCcO/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Jul 30 21:12:50 submit26-b9-2 setroubleshoot[667121]: 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 30 21:12:50 submit26-b9-2 setroubleshoot[667121]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ETxCcO. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Jul 30 21:12:50 submit26-b9-2 setroubleshoot[667121]: 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 Jul 30 21:12:50 submit26-b9-2 setroubleshoot[667121]: 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 30 21:12:50 submit26-b9-2 setroubleshoot[667121]: 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 == submit26-b9-3 (9 distinct, 9 total) == Jul 30 21:20:37 submit26-b9-3 setroubleshoot[715754]: 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 30 21:20:37 submit26-b9-3 setroubleshoot[715754]: 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 30 21:20:37 submit26-b9-3 setroubleshoot[715754]: 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 Jul 30 21:20:37 submit26-b9-3 setroubleshoot[715754]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.SOQbyu/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Jul 30 21:20:37 submit26-b9-3 setroubleshoot[715754]: 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 Jul 30 21:20:37 submit26-b9-3 setroubleshoot[715754]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.SOQbyu. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 30 21:20:37 submit26-b9-3 setroubleshoot[715754]: 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 30 21:20:37 submit26-b9-3 setroubleshoot[715754]: 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 Jul 30 21:20:37 submit26-b9-3 setroubleshoot[715754]: 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 == submit26-b9-4 (1 distinct, 6 total) == Jul 30 21:08:05 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] == submit26-clnb9 (9 distinct, 9 total) == Jul 30 21:31:54 submit26-clnb9 setroubleshoot[1557238]: 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 Jul 30 21:31:54 submit26-clnb9 setroubleshoot[1557238]: 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 Jul 30 21:31:55 submit26-clnb9 setroubleshoot[1557238]: 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 30 21:31:55 submit26-clnb9 setroubleshoot[1557238]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.S95u1N/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Jul 30 21:31:55 submit26-clnb9 setroubleshoot[1557238]: 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 30 21:31:55 submit26-clnb9 setroubleshoot[1557238]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.S95u1N. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 30 21:31:55 submit26-clnb9 setroubleshoot[1557238]: 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 Jul 30 21:31:55 submit26-clnb9 setroubleshoot[1557238]: 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 30 21:31:55 submit26-clnb9 setroubleshoot[1557238]: 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