Command: /usr/local/sbin/syslog-digest.py Time : 0.9739s Status : exited 0 Output : Syslog digest — 2026-08-08 18:05 EDT Processed 7,452 lines, filtered 4,664 (62%). 2,788 unknown (115 distinct) from 25 host(s). == abuse (3 distinct, 2250 total) == Aug 8 17:05:04 abuse systemd[1]: Failed to load environment files: Input/output error [x687] Aug 8 17:05:04 abuse systemd[1]: choria-server.service failed to run 'start' task: Input/output error [x687] Aug 8 17:05:04 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 ] [x876] == b0b02.cs.umd.edu (1 distinct, 1 total) == Aug 8 17:50:37 b0b02.cs.umd.edu rustdesk[200683]: cannot open display: == cheezit.cs.umd.edu (2 distinct, 2 total) == Aug 8 17:35:49 cheezit.cs.umd.edu krb5_child[2541590]: Preauthentication failed Aug 8 17:35:49 cheezit.cs.umd.edu sshd-session[2541582]: error: PAM: Authentication failure for larry from 10.206.97.73 == contest (10 distinct, 45 total) == Aug 8 17:05: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') [x34] Aug 8 17:48:20 contest setroubleshoot[849721]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.G9wFPH. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Aug 8 17:48:20 contest setroubleshoot[849721]: 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 8 17:48:20 contest setroubleshoot[849721]: 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 8 17:48:20 contest setroubleshoot[849721]: 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 8 17:48:20 contest setroubleshoot[849721]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.G9wFPH. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Aug 8 17:48:21 contest setroubleshoot[849721]: 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 8 17:48:21 contest setroubleshoot[849721]: 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 8 17:48:22 contest setroubleshoot[849721]: 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 Aug 8 17:48:35 contest setroubleshoot[849781]: 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, 266 total) == Aug 8 17:04:32 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x266] == frozone (1 distinct, 1 total) == Aug 8 17:34:53 frozone systemd-tmpfiles[1893857]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted == hackerman (7 distinct, 12 total) == Aug 8 17: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.I7RWT3”: Permission denied Aug 8 17:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4] Aug 8 17:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding Aug 8 17: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.EBRNT3”: Permission denied Aug 8 17:20:28 hackerman packagekitd[989077]: Failed to get cache filename for libreoffice [x2] Aug 8 17:20:28 hackerman packagekitd[989077]: Failed to get cache filename for kernel [x2] Aug 8 17:20:37 hackerman packagekitd[989077]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == idm00 (1 distinct, 1 total) == Aug 8 17:51:20 idm00 named[1455]: client @0x7f33041b37e8 10.73.240.42#64005: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 8 17:36:00 idmp0 named[5198]: client @0x7f9904008048 10.73.240.43#63183: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 47 total) == Aug 8 17:08:13 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x47] == itmon03 (1 distinct, 1 total) == Aug 8 17:50:02 itmon03 systemd-timedated[855954]: /dev/rtc is busy. Is somebody keeping it open continuously? That's not a good idea... Returning a bogus RTC timestamp. == neodontcare.cs.umd.edu (2 distinct, 16 total) == Aug 8 17:32:15 neodontcare.cs.umd.edu tracker-extract[3667527]: tracker_module_manager_load_modules: assertion 'initialized == TRUE' failed [x14] Aug 8 18:03:05 neodontcare.cs.umd.edu tracker-miner-f[2945379]: g_hash_table_contains: assertion 'hash_table != NULL' failed [x2] == netman.cs.umd.edu (1 distinct, 2 total) == Aug 8 17:43:40 netman.cs.umd.edu krb5_child[2533596]: Preauthentication failed [x2] == newhonors2 (1 distinct, 24 total) == Aug 8 17:13:02 newhonors2 dhcpcd[925844]: dhcpcd is not running [x24] == orchids (7 distinct, 13 total) == Aug 8 17:11:25 orchids gnome-software[1516991]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4] Aug 8 17:11:31 orchids gnome-software[1516991]: Only 0 apps for recent list, hiding Aug 8 17:11:35 orchids packagekitd[35262]: Failed to get cache filename for libreoffice [x2] Aug 8 17:11:35 orchids packagekitd[35262]: Failed to get cache filename for cups-filesystem [x2] Aug 8 17:11:35 orchids packagekitd[35262]: Failed to get cache filename for kernel [x2] Aug 8 17:11:35 orchids gnome-software[1516991]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/jworden/.config/dconf/user.IKT0T3”: Permission denied Aug 8 17:11:36 orchids packagekitd[35262]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == outbound00.cs.umd.edu (1 distinct, 6 total) == Aug 8 17:09:09 outbound00.cs.umd.edu python3[71290]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 8 17:13:06 outbound01.cs.umd.edu python3[2302878]: ldapdb [x6] == peach.cs.umd.edu (2 distinct, 6 total) == Aug 8 17:12:08 peach.cs.umd.edu setroubleshoot[3394693]: SELinux is preventing /usr/bin/qemu-ga from search access on the directory /var/lib/containers/storage/overlay. For complete SELinux messages run: sealert -l ba415951-a2c6-424e-b17d-305c5300b9f3 [x3] Aug 8 17:12:08 peach.cs.umd.edu setroubleshoot[3394693]: SELinux is preventing /usr/bin/qemu-ga from search access on the directory /var/lib/containers/storage/overlay. For complete SELinux messages run: sealert -l 6aeb0956-fcf2-462a-ae4d-439b912c16d0 [x3] == sebatinsky.cs.umd.edu (3 distinct, 5 total) == Aug 8 17:50:28 sebatinsky.cs.umd.edu setroubleshoot[2418330]: failed to retrieve rpm info for /var/lib/rpm/.dbenv.lock [x2] Aug 8 17:50:32 sebatinsky.cs.umd.edu setroubleshoot[2418330]: SELinux is preventing /usr/libexec/platform-python3.6 from add_name access on the directory /var/lib/rpm/.dbenv.lock. For complete SELinux messages run: sealert -l 26d5bc02-bfff-4827-a9f2-b991fef962b5 [x2] Aug 8 17:50:38 sebatinsky.cs.umd.edu setroubleshoot[2418330]: SELinux is preventing rhsmcertd-worke from create access on the file __db.003. For complete SELinux messages run: sealert -l c2202c24-dc18-413b-8198-09e05919353b == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Aug 8 17:12:21 sentry-docker00.cs.umd.edu systemd-udevd[403384]: link_config: could not get ethtool features for veth0092066 Aug 8 17:12:21 sentry-docker00.cs.umd.edu systemd-udevd[403384]: Could not set offload features of veth0092066: No such device Aug 8 17:12:21 sentry-docker00.cs.umd.edu systemd-udevd[403420]: Could not generate persistent MAC address for veth781b3cf: No such file or directory Aug 8 17:12:21 sentry-docker00.cs.umd.edu systemd-udevd[403421]: Could not generate persistent MAC address for vethf9c38c2: No such file or directory Aug 8 17:12:21 sentry-docker00.cs.umd.edu systemd-udevd[403424]: Could not generate persistent MAC address for vetha62d753: No such file or directory Aug 8 17:12:21 sentry-docker00.cs.umd.edu systemd-udevd[403427]: Could not generate persistent MAC address for vethd961af2: No such file or directory Aug 8 17:12:21 sentry-docker00.cs.umd.edu systemd-udevd[403429]: Could not generate persistent MAC address for veth6d89dca: No such file or directory Aug 8 17:12:21 sentry-docker00.cs.umd.edu systemd-udevd[403426]: Could not generate persistent MAC address for vethf514860: No such file or directory Aug 8 17:12:21 sentry-docker00.cs.umd.edu systemd-udevd[403426]: Could not generate persistent MAC address for veth59c662e: No such file or directory Aug 8 17:12:21 sentry-docker00.cs.umd.edu systemd-udevd[403434]: Could not generate persistent MAC address for veth62290f8: No such file or directory Aug 8 17:12:21 sentry-docker00.cs.umd.edu systemd-udevd[403452]: Could not generate persistent MAC address for veth992e815: No such file or directory Aug 8 17:12:21 sentry-docker00.cs.umd.edu systemd-udevd[403453]: Could not generate persistent MAC address for veth963f3a3: No such file or directory Aug 8 17:32:29 sentry-docker00.cs.umd.edu systemd-udevd[412993]: link_config: could not get ethtool features for veth992e815 Aug 8 17:32:29 sentry-docker00.cs.umd.edu systemd-udevd[412993]: Could not set offload features of veth992e815: No such device Aug 8 17:32:30 sentry-docker00.cs.umd.edu systemd-udevd[413045]: Could not generate persistent MAC address for veth9d173ed: No such file or directory Aug 8 17:32:30 sentry-docker00.cs.umd.edu systemd-udevd[413046]: Could not generate persistent MAC address for veth4c02e13: No such file or directory Aug 8 17:32:30 sentry-docker00.cs.umd.edu systemd-udevd[413048]: Could not generate persistent MAC address for vethbe730da: No such file or directory Aug 8 17:32:30 sentry-docker00.cs.umd.edu systemd-udevd[413049]: Could not generate persistent MAC address for vethba28adf: No such file or directory Aug 8 17:32:30 sentry-docker00.cs.umd.edu systemd-udevd[413086]: Could not generate persistent MAC address for vethc8ae401: No such file or directory Aug 8 17:32:30 sentry-docker00.cs.umd.edu systemd-udevd[413087]: Could not generate persistent MAC address for veth9d4732b: No such file or directory Aug 8 17:32:30 sentry-docker00.cs.umd.edu systemd-udevd[413091]: Could not generate persistent MAC address for vethbb53c43: No such file or directory Aug 8 17:32:30 sentry-docker00.cs.umd.edu systemd-udevd[413094]: Could not generate persistent MAC address for vethe3e55e1: No such file or directory Aug 8 17:32:30 sentry-docker00.cs.umd.edu systemd-udevd[413087]: Could not generate persistent MAC address for veth5dab64b: No such file or directory Aug 8 17:32:30 sentry-docker00.cs.umd.edu systemd-udevd[413092]: Could not generate persistent MAC address for veth1d9a7ee: No such file or directory Aug 8 17:52:38 sentry-docker00.cs.umd.edu systemd-udevd[422344]: link_config: could not get ethtool features for vethbe730da Aug 8 17:52:38 sentry-docker00.cs.umd.edu systemd-udevd[422344]: Could not set offload features of vethbe730da: No such device Aug 8 17:52:38 sentry-docker00.cs.umd.edu systemd-udevd[422448]: Could not generate persistent MAC address for vethe7f4aa8: No such file or directory Aug 8 17:52:38 sentry-docker00.cs.umd.edu systemd-udevd[422449]: Could not generate persistent MAC address for veth633a448: No such file or directory Aug 8 17:52:38 sentry-docker00.cs.umd.edu systemd-udevd[422478]: Could not generate persistent MAC address for vethafb7280: No such file or directory Aug 8 17:52:38 sentry-docker00.cs.umd.edu systemd-udevd[422479]: Could not generate persistent MAC address for veth520f670: No such file or directory ... 6 more distinct messages not shown == strawberry (2 distinct, 8 total) == Aug 8 17: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 8 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (10 distinct, 14 total) == Aug 8 17:12:54 submit26-b9-2 setroubleshoot[1402780]: 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] Aug 8 17:12:54 submit26-b9-2 setroubleshoot[1402780]: 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] Aug 8 17:12:54 submit26-b9-2 setroubleshoot[1402780]: 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 8 17:12:54 submit26-b9-2 setroubleshoot[1402780]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.8h2msx/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Aug 8 17:12:54 submit26-b9-2 setroubleshoot[1402780]: 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 8 17:12:54 submit26-b9-2 setroubleshoot[1402780]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.8h2msx. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Aug 8 17:12:54 submit26-b9-2 setroubleshoot[1402780]: 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] Aug 8 17:12:54 submit26-b9-2 setroubleshoot[1402780]: 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 8 17:12:54 submit26-b9-2 setroubleshoot[1402780]: 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] Aug 8 17:12:54 submit26-b9-2 setroubleshoot[1402780]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.wUFXeF. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 == submit26-b9-3 (9 distinct, 9 total) == Aug 8 17:20:40 submit26-b9-3 setroubleshoot[933333]: 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 8 17:20:40 submit26-b9-3 setroubleshoot[933333]: 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 8 17:20:40 submit26-b9-3 setroubleshoot[933333]: 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 Aug 8 17:20:40 submit26-b9-3 setroubleshoot[933333]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3V9TI9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Aug 8 17:20:40 submit26-b9-3 setroubleshoot[933333]: 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 Aug 8 17:20:40 submit26-b9-3 setroubleshoot[933333]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3V9TI9. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Aug 8 17:20:40 submit26-b9-3 setroubleshoot[933333]: 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 8 17:20:40 submit26-b9-3 setroubleshoot[933333]: 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 Aug 8 17:20:40 submit26-b9-3 setroubleshoot[933333]: 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-clnb9 (10 distinct, 14 total) == Aug 8 17:31:59 submit26-clnb9 setroubleshoot[1990304]: 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] Aug 8 17:31:59 submit26-clnb9 setroubleshoot[1990304]: 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] Aug 8 17:31:59 submit26-clnb9 setroubleshoot[1990304]: 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 8 17:31:59 submit26-clnb9 setroubleshoot[1990304]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.EI3E86/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Aug 8 17:31:59 submit26-clnb9 setroubleshoot[1990304]: 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 8 17:31:59 submit26-clnb9 setroubleshoot[1990304]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.EI3E86. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Aug 8 17:31:59 submit26-clnb9 setroubleshoot[1990304]: 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] Aug 8 17:31:59 submit26-clnb9 setroubleshoot[1990304]: 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 8 17:31:59 submit26-clnb9 setroubleshoot[1990304]: 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] Aug 8 17:31:59 submit26-clnb9 setroubleshoot[1990304]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xi3FZI. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c == talkhosts9 (1 distinct, 2 total) == Aug 8 17:11:27 talkhosts9 setroubleshoot[2162074]: SELinux is preventing /usr/bin/lsof from getattr access on the unix_stream_socket unix_stream_socket. For complete SELinux messages run: sealert -l a6df89b3-c497-469c-8232-c4fde0508abf [x2]