Command: /usr/local/sbin/syslog-digest.py Time : 0.5196s Status : exited 0 Output : Syslog digest — 2026-07-23 06:05 EDT Processed 4,592 lines, filtered 3,717 (80%). 875 unknown (100 distinct) from 23 host(s). == abuse (1 distinct, 347 total) == Jul 23 05: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 23 05:05:32 alec.cs.umd.edu setroubleshoot[2103866]: failed to retrieve rpm info for path '/run/netns/netns-a2b2cc2d-7532-4db7-6a36-b1dd3d5f51db': [x12] Jul 23 05:05:32 alec.cs.umd.edu sedispatch[1526]: AVC Message regarding setroubleshoot, ignoring message [x24] Jul 23 05:05:32 alec.cs.umd.edu setroubleshoot[2103866]: SELinux is preventing /usr/bin/df from getattr access on the file /run/netns/netns-a2b2cc2d-7532-4db7-6a36-b1dd3d5f51db. For complete SELinux messages run: sealert -l 23f93208-3063-4aac-b78a-bb0fcb40740c [x23] == b0b02.cs.umd.edu (4 distinct, 4 total) == Jul 23 05:07:59 b0b02.cs.umd.edu setroubleshoot[1935623]: 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 Jul 23 05:08:01 b0b02.cs.umd.edu setroubleshoot[1935623]: 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 Jul 23 05:08:04 b0b02.cs.umd.edu setroubleshoot[1935623]: 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 Jul 23 05:11:54 b0b02.cs.umd.edu rustdesk[1936921]: cannot open display: == bachata (10 distinct, 10 total) == Jul 23 05:53:01 bachata smbd[1760309]: [2026/07/23 05:53:01.047694, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jul 23 05:53:01 bachata smbd[1760309]: chdir_current_service: vfs_ChDir(/fs/junkfood/mount) failed: Permission denied. Current token: uid=11255, gid=11255, 12 groups: 11255 319000009 25038 15294 15229 755 25030 25025 30880 25029 770 15026 Jul 23 05:53:01 bachata smbd[1760309]: [2026/07/23 05:53:01.049763, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect) Jul 23 05:53:01 bachata smbd[1760309]: smbXsrv_tcon_disconnect: disconnect(0xabc3cb9d, 'mount'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR Jul 23 05:53:01 bachata smbd[1760309]: [2026/07/23 05:53:01.050274, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all) Jul 23 05:53:01 bachata smbd[1760309]: smbXsrv_tcon_disconnect_all: count[2] errors[1] first[NT_STATUS_INTERNAL_ERROR] Jul 23 05:53:01 bachata smbd[1760309]: [2026/07/23 05:53:01.050353, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff) Jul 23 05:53:01 bachata smbd[1760309]: smbXsrv_session_logoff: smbXsrv_session_logoff(0xbd773cd0): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR Jul 23 05:53:01 bachata smbd[1760309]: [2026/07/23 05:53:01.050422, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done) Jul 23 05:53:01 bachata smbd[1760309]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(3178708176) failed: NT_STATUS_INTERNAL_ERROR == contest (1 distinct, 33 total) == Jul 23 05:06:29 contest goferd[994]: [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] == csfw00a (1 distinct, 252 total) == Jul 23 05:04:46 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x252] == grades01.cs.umd.edu (1 distinct, 1 total) == Jul 23 05:48:52 grades01.cs.umd.edu puppet-agent[27164]: 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) == Jul 23 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.BRGDT3”: Permission denied == idm00 (1 distinct, 1 total) == Jul 23 05:51:04 idm00 named[1455]: client @0x7f3314ae3878 10.73.240.42#59849: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Jul 23 05:34:57 idmp0 named[5198]: client @0x7f992002bc08 10.73.240.43#64000: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 45 total) == Jul 23 05:07:50 itmon02 sshd[1904]: error: beginning MaxStartups throttling [x45] == matrix (9 distinct, 10 total) == Jul 23 05:37:59 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 60975, but reception only permitted for main PID 720 Jul 23 05:37:59 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 60983, but reception only permitted for main PID 720 Jul 23 05:38:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 61087, but reception only permitted for main PID 720 Jul 23 05:38:07 matrix networkctl[61098]: Interface "veth7141cf4" not found. Jul 23 05:38:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 61180, but reception only permitted for main PID 720 Jul 23 05:38:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 61191, but reception only permitted for main PID 720 Jul 23 05:38:17 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 61289, but reception only permitted for main PID 720 Jul 23 05:38:17 matrix networkctl[61299]: Interface "veth881bc35" not found. Jul 23 05:38:17 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 61299, but reception only permitted for main PID 720 [x2] == neo-gizmonic (1 distinct, 1 total) == Jul 23 06:03:17 neo-gizmonic xinetd[807]: Exiting... == newhonors2 (1 distinct, 24 total) == Jul 23 05:13:02 newhonors2 dhcpcd[158944]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 23 05:09:09 outbound00.cs.umd.edu python3[2867020]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Jul 23 05:08:18 outbound01.cs.umd.edu python3[893602]: ldapdb [x7] Jul 23 05:09:26 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, 2 total) == Jul 23 05:32:09 peach.cs.umd.edu setroubleshoot[253976]: 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 Jul 23 05:32:09 peach.cs.umd.edu setroubleshoot[253976]: 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 == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Jul 23 05:09:00 sentry-docker00.cs.umd.edu systemd-udevd[1677226]: link_config: could not get ethtool features for veth9281973 Jul 23 05:09:00 sentry-docker00.cs.umd.edu systemd-udevd[1677226]: Could not set offload features of veth9281973: No such device Jul 23 05:09:00 sentry-docker00.cs.umd.edu systemd-udevd[1677249]: Could not generate persistent MAC address for veth3559fe7: No such file or directory Jul 23 05:09:00 sentry-docker00.cs.umd.edu systemd-udevd[1677250]: Could not generate persistent MAC address for vethbd5bc78: No such file or directory Jul 23 05:09:00 sentry-docker00.cs.umd.edu systemd-udevd[1677253]: Could not generate persistent MAC address for veth9029783: No such file or directory Jul 23 05:09:00 sentry-docker00.cs.umd.edu systemd-udevd[1677254]: Could not generate persistent MAC address for vethcd8998c: No such file or directory Jul 23 05:09:00 sentry-docker00.cs.umd.edu systemd-udevd[1677277]: Could not generate persistent MAC address for veth48b5d1e: No such file or directory Jul 23 05:09:00 sentry-docker00.cs.umd.edu systemd-udevd[1677278]: Could not generate persistent MAC address for veth31894ad: No such file or directory Jul 23 05:09:00 sentry-docker00.cs.umd.edu systemd-udevd[1677297]: Could not generate persistent MAC address for vethe873578: No such file or directory Jul 23 05:09:00 sentry-docker00.cs.umd.edu systemd-udevd[1677283]: Could not generate persistent MAC address for veth59796a7: No such file or directory Jul 23 05:24:50 sentry-docker00.cs.umd.edu systemd-udevd[1683943]: Could not generate persistent MAC address for vethe9718c6: No such file or directory Jul 23 05:24:50 sentry-docker00.cs.umd.edu systemd-udevd[1683944]: Could not generate persistent MAC address for vetha59e8db: No such file or directory Jul 23 05:29:08 sentry-docker00.cs.umd.edu systemd-udevd[1686629]: link_config: could not get ethtool features for veth48b5d1e Jul 23 05:29:08 sentry-docker00.cs.umd.edu systemd-udevd[1686629]: Could not set offload features of veth48b5d1e: No such device Jul 23 05:29:08 sentry-docker00.cs.umd.edu systemd-udevd[1686655]: Could not generate persistent MAC address for veth8ae98ba: No such file or directory Jul 23 05:29:08 sentry-docker00.cs.umd.edu systemd-udevd[1686656]: Could not generate persistent MAC address for vethba4c144: No such file or directory Jul 23 05:29:08 sentry-docker00.cs.umd.edu systemd-udevd[1686659]: Could not generate persistent MAC address for vethfc2ccd4: No such file or directory Jul 23 05:29:08 sentry-docker00.cs.umd.edu systemd-udevd[1686660]: Could not generate persistent MAC address for veth76edab6: No such file or directory Jul 23 05:29:08 sentry-docker00.cs.umd.edu systemd-udevd[1686680]: Could not generate persistent MAC address for veth3d75533: No such file or directory Jul 23 05:29:08 sentry-docker00.cs.umd.edu systemd-udevd[1686678]: Could not generate persistent MAC address for veth8b06846: No such file or directory Jul 23 05:29:08 sentry-docker00.cs.umd.edu systemd-udevd[1686678]: Could not generate persistent MAC address for vethf0e1948: No such file or directory Jul 23 05:29:08 sentry-docker00.cs.umd.edu systemd-udevd[1686680]: Could not generate persistent MAC address for veth1e613a5: No such file or directory Jul 23 05:44:59 sentry-docker00.cs.umd.edu systemd-udevd[1693402]: Could not generate persistent MAC address for veth1c6892f: No such file or directory Jul 23 05:44:59 sentry-docker00.cs.umd.edu systemd-udevd[1693403]: Could not generate persistent MAC address for vethd8112c5: No such file or directory Jul 23 05:49:17 sentry-docker00.cs.umd.edu systemd-udevd[1696080]: link_config: could not get ethtool features for veth3d75533 Jul 23 05:49:17 sentry-docker00.cs.umd.edu systemd-udevd[1696080]: Could not set offload features of veth3d75533: No such device Jul 23 05:49:17 sentry-docker00.cs.umd.edu systemd-udevd[1696108]: Could not generate persistent MAC address for veth7526fc4: No such file or directory Jul 23 05:49:17 sentry-docker00.cs.umd.edu systemd-udevd[1696109]: Could not generate persistent MAC address for vetheaef890: No such file or directory Jul 23 05:49:17 sentry-docker00.cs.umd.edu systemd-udevd[1696112]: Could not generate persistent MAC address for veth363fbe5: No such file or directory Jul 23 05:49:17 sentry-docker00.cs.umd.edu systemd-udevd[1696113]: Could not generate persistent MAC address for vethf57b157: No such file or directory ... 4 more distinct messages not shown == strawberry (2 distinct, 8 total) == Jul 23 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] Jul 23 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (1 distinct, 2 total) == Jul 23 05:37:14 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-3 (9 distinct, 9 total) == Jul 23 05:20:34 submit26-b9-3 setroubleshoot[526997]: 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 23 05:20:34 submit26-b9-3 setroubleshoot[526997]: 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 23 05:20:34 submit26-b9-3 setroubleshoot[526997]: 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 23 05:20:34 submit26-b9-3 setroubleshoot[526997]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.bzrB5j/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Jul 23 05:20:34 submit26-b9-3 setroubleshoot[526997]: 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 23 05:20:34 submit26-b9-3 setroubleshoot[526997]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.bzrB5j. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 23 05:20:34 submit26-b9-3 setroubleshoot[526997]: 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 23 05:20:34 submit26-b9-3 setroubleshoot[526997]: 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 23 05:20:34 submit26-b9-3 setroubleshoot[526997]: 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) == Jul 23 05:31:52 submit26-clnb9 setroubleshoot[1180991]: 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 23 05:31:52 submit26-clnb9 setroubleshoot[1180991]: 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 23 05:31:52 submit26-clnb9 setroubleshoot[1180991]: 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 23 05:31:52 submit26-clnb9 setroubleshoot[1180991]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.6JcYsF/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Jul 23 05:31:52 submit26-clnb9 setroubleshoot[1180991]: 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 23 05:31:52 submit26-clnb9 setroubleshoot[1180991]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.6JcYsF. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 23 05:31:52 submit26-clnb9 setroubleshoot[1180991]: 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 23 05:31:52 submit26-clnb9 setroubleshoot[1180991]: 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 23 05:31:52 submit26-clnb9 setroubleshoot[1180991]: 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 23 05:31:52 submit26-clnb9 setroubleshoot[1180991]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GznMQ1. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c == updates00.cs.umd.edu (3 distinct, 3 total) == Jul 23 05:18:27 updates00.cs.umd.edu puppet-agent[10367]: 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 Jul 23 05:18:27 updates00.cs.umd.edu puppet-agent[10367]: Not using cache on failed catalog Jul 23 05:18:27 updates00.cs.umd.edu puppet-agent[10367]: Could not retrieve catalog; skipping run