Command: /usr/local/sbin/syslog-digest.py Time : 0.9772s Status : exited 0 Output : Syslog digest — 2026-08-09 06:05 EDT Processed 7,611 lines, filtered 4,845 (63%). 2,766 unknown (108 distinct) from 23 host(s). == abuse (3 distinct, 2243 total) == Aug 9 05:05:06 abuse systemd[1]: Failed to load environment files: Input/output error [x687] Aug 9 05:05:06 abuse systemd[1]: choria-server.service failed to run 'start' task: Input/output error [x687] Aug 9 05:05:11 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 ] [x869] == b0b02.cs.umd.edu (4 distinct, 4 total) == Aug 9 05:22:35 b0b02.cs.umd.edu setroubleshoot[375632]: SELinux is preventing /usr/bin/python3.9 from getattr access on the file /etc/authselect/nsswitch.conf. For complete SELinux messages run: sealert -l 9a1e2952-3fde-4937-a8ab-f7f59791a458 Aug 9 05:22:37 b0b02.cs.umd.edu setroubleshoot[375632]: SELinux is preventing /usr/bin/python3.9 from read access on the file /etc/authselect/nsswitch.conf. For complete SELinux messages run: sealert -l 97d74423-e027-4cd6-8810-ad80944900b5 Aug 9 05:22:40 b0b02.cs.umd.edu setroubleshoot[375632]: SELinux is preventing /usr/bin/python3.9 from open access on the file /etc/authselect/nsswitch.conf. For complete SELinux messages run: sealert -l 4f253f6a-62d6-46dd-8eaf-0b4d29df41c6 Aug 9 05:51:19 b0b02.cs.umd.edu rustdesk[383046]: cannot open display: == cheezit.cs.umd.edu (1 distinct, 1 total) == Aug 9 05:53:06 cheezit.cs.umd.edu sshd[1813730]: error: beginning MaxStartups throttling == contest (9 distinct, 45 total) == Aug 9 05:05:14 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 9 05:48:20 contest setroubleshoot[877337]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.eqKC9z. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Aug 9 05:48:20 contest setroubleshoot[877337]: 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 9 05:48:20 contest setroubleshoot[877337]: 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 9 05:48:20 contest setroubleshoot[877337]: 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 Aug 9 05:48:20 contest setroubleshoot[877337]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.eqKC9z. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Aug 9 05:48:20 contest setroubleshoot[877337]: 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 [x3] Aug 9 05:48:20 contest setroubleshoot[877337]: 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 [x2] Aug 9 05:48:22 contest setroubleshoot[877337]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.NtAPPm. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 == csfw00a (2 distinct, 298 total) == Aug 9 05:04:58 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x294] Aug 9 05:40:43 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x4] == grades01.cs.umd.edu (1 distinct, 1 total) == Aug 9 05:48:33 grades01.cs.umd.edu puppet-agent[30045]: The directory '/srv/grades' contains 2471 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees == hackerman (1 distinct, 1 total) == Aug 9 05: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.5J3NT3”: Permission denied == idm00 (1 distinct, 1 total) == Aug 9 05:51:22 idm00 named[243294]: client @0x7f5f140180f8 10.73.240.42#65361: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 9 05:36:01 idmp0 named[1540302]: client @0x7ff7e4001b68 10.73.240.43#49659: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 36 total) == Aug 9 05:08:13 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x36] == matrix (9 distinct, 11 total) == Aug 9 05:44:59 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 1606719, but reception only permitted for main PID 720 Aug 9 05:45:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 1606844, but reception only permitted for main PID 720 Aug 9 05:45:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 1606850, but reception only permitted for main PID 720 Aug 9 05:45:08 matrix networkctl[1606861]: Interface "veth4d6e858" not found. Aug 9 05:45:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 1606861, but reception only permitted for main PID 720 [x2] Aug 9 05:45:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 1606924, but reception only permitted for main PID 720 Aug 9 05:45:18 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 1607036, but reception only permitted for main PID 720 Aug 9 05:45:18 matrix networkctl[1607054]: Interface "veth0638158" not found. Aug 9 05:45:18 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 1607054, but reception only permitted for main PID 720 [x2] == newhonors2 (1 distinct, 24 total) == Aug 9 05:13:03 newhonors2 dhcpcd[948759]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Aug 9 05:09:09 outbound00.cs.umd.edu python3[241238]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Aug 9 05:08:13 outbound01.cs.umd.edu python3[2471437]: ldapdb [x7] Aug 9 05:09:21 outbound01.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway. == peach.cs.umd.edu (2 distinct, 4 total) == Aug 9 05:12:09 peach.cs.umd.edu setroubleshoot[3468964]: 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 [x2] Aug 9 05:12:09 peach.cs.umd.edu setroubleshoot[3468964]: 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 [x2] == quiss (1 distinct, 1 total) == Aug 9 05:46:34 quiss gnome-software[879803]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/josephao/.config/dconf/user.8GLHT3”: Permission denied == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Aug 9 05:17:21 sentry-docker00.cs.umd.edu systemd-udevd[744580]: link_config: could not get ethtool features for veth045a794 Aug 9 05:17:21 sentry-docker00.cs.umd.edu systemd-udevd[744580]: Could not set offload features of veth045a794: No such device Aug 9 05:17:21 sentry-docker00.cs.umd.edu systemd-udevd[744627]: Could not generate persistent MAC address for veth940dd68: No such file or directory Aug 9 05:17:21 sentry-docker00.cs.umd.edu systemd-udevd[744628]: Could not generate persistent MAC address for vethff9cb9c: No such file or directory Aug 9 05:17:21 sentry-docker00.cs.umd.edu systemd-udevd[744646]: Could not generate persistent MAC address for veth5d57185: No such file or directory Aug 9 05:17:21 sentry-docker00.cs.umd.edu systemd-udevd[744651]: Could not generate persistent MAC address for veth4d7b96a: No such file or directory Aug 9 05:17:21 sentry-docker00.cs.umd.edu systemd-udevd[744655]: Could not generate persistent MAC address for veth92727f5: No such file or directory Aug 9 05:17:21 sentry-docker00.cs.umd.edu systemd-udevd[744656]: Could not generate persistent MAC address for veth5ab8cc2: No such file or directory Aug 9 05:17:21 sentry-docker00.cs.umd.edu systemd-udevd[744709]: Could not generate persistent MAC address for veth0491bc3: No such file or directory Aug 9 05:17:21 sentry-docker00.cs.umd.edu systemd-udevd[744711]: Could not generate persistent MAC address for veth9dc0ac1: No such file or directory Aug 9 05:17:21 sentry-docker00.cs.umd.edu systemd-udevd[744799]: Could not generate persistent MAC address for veth1a74953: No such file or directory Aug 9 05:17:21 sentry-docker00.cs.umd.edu systemd-udevd[744802]: Could not generate persistent MAC address for vetha1d738e: No such file or directory Aug 9 05:37:29 sentry-docker00.cs.umd.edu systemd-udevd[754276]: link_config: could not get ethtool features for veth0491bc3 Aug 9 05:37:29 sentry-docker00.cs.umd.edu systemd-udevd[754276]: Could not set offload features of veth0491bc3: No such device Aug 9 05:37:29 sentry-docker00.cs.umd.edu systemd-udevd[754310]: Could not generate persistent MAC address for veth4fed72a: No such file or directory Aug 9 05:37:29 sentry-docker00.cs.umd.edu systemd-udevd[754311]: Could not generate persistent MAC address for veth991acfb: No such file or directory Aug 9 05:37:29 sentry-docker00.cs.umd.edu systemd-udevd[754315]: Could not generate persistent MAC address for veth79ddc51: No such file or directory Aug 9 05:37:29 sentry-docker00.cs.umd.edu systemd-udevd[754314]: Could not generate persistent MAC address for vethbb07f9f: No such file or directory Aug 9 05:37:29 sentry-docker00.cs.umd.edu systemd-udevd[754336]: Could not generate persistent MAC address for vethd023d2a: No such file or directory Aug 9 05:37:29 sentry-docker00.cs.umd.edu systemd-udevd[754325]: Could not generate persistent MAC address for veth006f50a: No such file or directory Aug 9 05:37:29 sentry-docker00.cs.umd.edu systemd-udevd[754367]: Could not generate persistent MAC address for veth71bcbfb: No such file or directory Aug 9 05:37:29 sentry-docker00.cs.umd.edu systemd-udevd[754368]: Could not generate persistent MAC address for veth6a15ab3: No such file or directory Aug 9 05:37:29 sentry-docker00.cs.umd.edu systemd-udevd[754393]: Could not generate persistent MAC address for veth49ad523: No such file or directory Aug 9 05:37:29 sentry-docker00.cs.umd.edu systemd-udevd[754399]: Could not generate persistent MAC address for veth901f519: No such file or directory Aug 9 05:57:38 sentry-docker00.cs.umd.edu systemd-udevd[763714]: Could not generate persistent MAC address for veth1887af6: No such file or directory Aug 9 05:57:38 sentry-docker00.cs.umd.edu systemd-udevd[763715]: Could not generate persistent MAC address for vethebc6795: No such file or directory Aug 9 05:57:38 sentry-docker00.cs.umd.edu systemd-udevd[763718]: Could not generate persistent MAC address for veth7301066: No such file or directory Aug 9 05:57:38 sentry-docker00.cs.umd.edu systemd-udevd[763719]: Could not generate persistent MAC address for vethfe80514: No such file or directory Aug 9 05:57:38 sentry-docker00.cs.umd.edu systemd-udevd[763718]: Could not generate persistent MAC address for veth88078b5: No such file or directory Aug 9 05:57:38 sentry-docker00.cs.umd.edu systemd-udevd[763730]: Could not generate persistent MAC address for veth53b050e: No such file or directory ... 4 more distinct messages not shown == strawberry (2 distinct, 8 total) == Aug 9 05: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 9 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (9 distinct, 11 total) == Aug 9 05:12:54 submit26-b9-2 setroubleshoot[1432118]: 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 9 05:12:54 submit26-b9-2 setroubleshoot[1432118]: 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 9 05:12:54 submit26-b9-2 setroubleshoot[1432118]: 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 9 05:12:54 submit26-b9-2 setroubleshoot[1432118]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.WWarT2/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Aug 9 05:12:54 submit26-b9-2 setroubleshoot[1432118]: 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 9 05:12:54 submit26-b9-2 setroubleshoot[1432118]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.WWarT2. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Aug 9 05:12:54 submit26-b9-2 setroubleshoot[1432118]: 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 9 05:12:54 submit26-b9-2 setroubleshoot[1432118]: 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 9 05:12:54 submit26-b9-2 setroubleshoot[1432118]: 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) == Aug 9 05:20:40 submit26-b9-3 setroubleshoot[945728]: 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 9 05:20:40 submit26-b9-3 setroubleshoot[945728]: 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 9 05:20:40 submit26-b9-3 setroubleshoot[945728]: 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 9 05:20:40 submit26-b9-3 setroubleshoot[945728]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.s9EzDo/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Aug 9 05:20:40 submit26-b9-3 setroubleshoot[945728]: 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 9 05:20:40 submit26-b9-3 setroubleshoot[945728]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.s9EzDo. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Aug 9 05:20:40 submit26-b9-3 setroubleshoot[945728]: 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 9 05:20:40 submit26-b9-3 setroubleshoot[945728]: 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 9 05:20:40 submit26-b9-3 setroubleshoot[945728]: 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 9 05:32:00 submit26-clnb9 setroubleshoot[2014943]: 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 9 05:32:00 submit26-clnb9 setroubleshoot[2014943]: 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 9 05:32:00 submit26-clnb9 setroubleshoot[2014943]: 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 9 05:32:00 submit26-clnb9 setroubleshoot[2014943]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.nlB33q/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Aug 9 05:32:00 submit26-clnb9 setroubleshoot[2014943]: 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 9 05:32:00 submit26-clnb9 setroubleshoot[2014943]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.nlB33q. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Aug 9 05:32:00 submit26-clnb9 setroubleshoot[2014943]: 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 9 05:32:00 submit26-clnb9 setroubleshoot[2014943]: 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 9 05:32:00 submit26-clnb9 setroubleshoot[2014943]: 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 9 05:32:00 submit26-clnb9 setroubleshoot[2014943]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.sNSKvc. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c == talkhosts9 (1 distinct, 2 total) == Aug 9 05:11:31 talkhosts9 setroubleshoot[2266858]: 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] == updates00.cs.umd.edu (3 distinct, 3 total) == Aug 9 05:18:35 updates00.cs.umd.edu puppet-agent[23128]: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Function lookup() did not find a value for the name 'vault::kerberos' on node updates00.cs.umd.edu Aug 9 05:18:35 updates00.cs.umd.edu puppet-agent[23128]: Not using cache on failed catalog Aug 9 05:18:35 updates00.cs.umd.edu puppet-agent[23128]: Could not retrieve catalog; skipping run