Command: /usr/local/sbin/syslog-digest.py Time : 0.4880s Status : exited 0 Output : Syslog digest — 2026-08-03 05:05 EDT Processed 4,107 lines, filtered 3,328 (81%). 779 unknown (94 distinct) from 22 host(s). == abadi-computer (2 distinct, 2 total) == Aug 3 04:15:00 abadi-computer nologin[788154]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN Aug 3 04:15:00 abadi-computer pipewire[788153]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files == abuse (1 distinct, 347 total) == Aug 3 04: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 (4 distinct, 4 total) == Aug 3 04:43:02 b0b02.cs.umd.edu rustdesk[2367541]: cannot open display: Aug 3 04:47:30 b0b02.cs.umd.edu setroubleshoot[2368407]: 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 3 04:47:32 b0b02.cs.umd.edu setroubleshoot[2368407]: 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 3 04:47:35 b0b02.cs.umd.edu setroubleshoot[2368407]: 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 == contest (1 distinct, 34 total) == Aug 3 04:05:37 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] == csfw00a (1 distinct, 218 total) == Aug 3 04:04:48 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x218] == dojo (1 distinct, 1 total) == Aug 3 04:15:10 dojo nologin[967471]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN == forge00 (1 distinct, 1 total) == Aug 3 04:09:02 forge00 (httpd)[1613922]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS == idm00 (1 distinct, 1 total) == Aug 3 04:51:15 idm00 named[1455]: client @0x7f3310552688 10.73.240.42#64153: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 3 04:36:01 idmp0 named[5198]: client @0x7f992407d618 10.73.240.43#54495: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 40 total) == Aug 3 04:07:59 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x40] == matrix (11 distinct, 13 total) == Aug 3 04:53:59 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 789135, but reception only permitted for main PID 720 Aug 3 04:53:59 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 789144, but reception only permitted for main PID 720 Aug 3 04:54:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 789237, but reception only permitted for main PID 720 Aug 3 04:54:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 789243, but reception only permitted for main PID 720 Aug 3 04:54:07 matrix networkctl[789257]: Interface "vethedc7728" not found. Aug 3 04:54:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 789257, but reception only permitted for main PID 720 [x2] Aug 3 04:54:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 789314, but reception only permitted for main PID 720 Aug 3 04:54:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 789326, but reception only permitted for main PID 720 Aug 3 04:54:17 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 789457, but reception only permitted for main PID 720 Aug 3 04:54:17 matrix networkctl[789469]: Interface "veth4258f27" not found. Aug 3 04:54:17 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 789469, but reception only permitted for main PID 720 [x2] == munin (2 distinct, 4 total) == Aug 3 04:28:02 munin sudo[959292]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Aug 3 04:28:02 munin sudo[959292]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == netman.cs.umd.edu (3 distinct, 3 total) == Aug 3 04:30:00 netman.cs.umd.edu setroubleshoot[176461]: SELinux is preventing /usr/bin/gpg from read access on the file gpg.conf. For complete SELinux messages run: sealert -l 019ad1da-a874-4814-8037-3b3e5f413ad2 Aug 3 04:30:01 netman.cs.umd.edu setroubleshoot[176461]: SELinux is preventing /usr/bin/gpg from open access on the file /root/.gnupg/gpg.conf. For complete SELinux messages run: sealert -l cb54177e-d44c-46a1-b246-5c0bbb8343be Aug 3 04:30:08 netman.cs.umd.edu setroubleshoot[176461]: SELinux is preventing /usr/bin/gpg from getattr access on the file /root/.gnupg/gpg.conf. For complete SELinux messages run: sealert -l fbba2e30-b7ab-491c-9ec6-f553e9ef72af == newhonors2 (1 distinct, 24 total) == Aug 3 04:13:03 newhonors2 dhcpcd[664196]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Aug 3 04:09:09 outbound00.cs.umd.edu python3[2366723]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 3 04:13:06 outbound01.cs.umd.edu python3[398575]: ldapdb [x6] == peach.cs.umd.edu (2 distinct, 2 total) == Aug 3 04:52:08 peach.cs.umd.edu setroubleshoot[696175]: 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 007f2494-1b82-4ff6-bd59-5f449ab9de99 Aug 3 04:52:08 peach.cs.umd.edu setroubleshoot[696175]: 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 a801d9aa-5cee-4f5c-b9a9-bd22e572596b == sentry-docker00.cs.umd.edu (42 distinct, 42 total) == Aug 3 04:17:22 sentry-docker00.cs.umd.edu systemd-udevd[829697]: link_config: could not get ethtool features for veth4354b2d Aug 3 04:17:22 sentry-docker00.cs.umd.edu systemd-udevd[829697]: Could not set offload features of veth4354b2d: No such device Aug 3 04:17:24 sentry-docker00.cs.umd.edu systemd-udevd[829735]: Could not generate persistent MAC address for veth6e03461: No such file or directory Aug 3 04:17:24 sentry-docker00.cs.umd.edu systemd-udevd[829736]: Could not generate persistent MAC address for vethaabf4eb: No such file or directory Aug 3 04:17:24 sentry-docker00.cs.umd.edu systemd-udevd[829740]: Could not generate persistent MAC address for vethe201042: No such file or directory Aug 3 04:17:24 sentry-docker00.cs.umd.edu systemd-udevd[829739]: Could not generate persistent MAC address for veth43f2fcd: No such file or directory Aug 3 04:17:24 sentry-docker00.cs.umd.edu systemd-udevd[829756]: Could not generate persistent MAC address for vethdc68836: No such file or directory Aug 3 04:17:24 sentry-docker00.cs.umd.edu systemd-udevd[829761]: Could not generate persistent MAC address for veth6e0552a: No such file or directory Aug 3 04:17:24 sentry-docker00.cs.umd.edu systemd-udevd[829765]: Could not generate persistent MAC address for veth89fd46f: No such file or directory Aug 3 04:17:24 sentry-docker00.cs.umd.edu systemd-udevd[829766]: Could not generate persistent MAC address for veth9c1bbc3: No such file or directory Aug 3 04:18:40 sentry-docker00.cs.umd.edu systemd-udevd[831542]: link_config: could not get ethtool features for vethbff2086 Aug 3 04:18:40 sentry-docker00.cs.umd.edu systemd-udevd[831542]: Could not set offload features of vethbff2086: No such device Aug 3 04:18:40 sentry-docker00.cs.umd.edu systemd-udevd[831574]: Could not generate persistent MAC address for veth978aac9: No such file or directory Aug 3 04:18:40 sentry-docker00.cs.umd.edu systemd-udevd[831575]: Could not generate persistent MAC address for veth11183cf: No such file or directory Aug 3 04:37:31 sentry-docker00.cs.umd.edu systemd-udevd[839119]: link_config: could not get ethtool features for veth89fd46f Aug 3 04:37:31 sentry-docker00.cs.umd.edu systemd-udevd[839119]: Could not set offload features of veth89fd46f: No such device Aug 3 04:37:31 sentry-docker00.cs.umd.edu systemd-udevd[839181]: Could not generate persistent MAC address for vetha5a02d8: No such file or directory Aug 3 04:37:31 sentry-docker00.cs.umd.edu systemd-udevd[839182]: Could not generate persistent MAC address for vethcf38fa0: No such file or directory Aug 3 04:37:31 sentry-docker00.cs.umd.edu systemd-udevd[839185]: Could not generate persistent MAC address for veth274fd83: No such file or directory Aug 3 04:37:31 sentry-docker00.cs.umd.edu systemd-udevd[839186]: Could not generate persistent MAC address for veth01377f9: No such file or directory Aug 3 04:37:31 sentry-docker00.cs.umd.edu systemd-udevd[839209]: Could not generate persistent MAC address for veth530c2f1: No such file or directory Aug 3 04:37:31 sentry-docker00.cs.umd.edu systemd-udevd[839210]: Could not generate persistent MAC address for veth6c54b33: No such file or directory Aug 3 04:37:31 sentry-docker00.cs.umd.edu systemd-udevd[839228]: Could not generate persistent MAC address for veth20c911a: No such file or directory Aug 3 04:37:31 sentry-docker00.cs.umd.edu systemd-udevd[839210]: Could not generate persistent MAC address for vethf127b6e: No such file or directory Aug 3 04:38:49 sentry-docker00.cs.umd.edu systemd-udevd[841005]: Could not generate persistent MAC address for veth480ad69: No such file or directory Aug 3 04:38:49 sentry-docker00.cs.umd.edu systemd-udevd[841006]: Could not generate persistent MAC address for veth5f10a50: No such file or directory Aug 3 04:57:39 sentry-docker00.cs.umd.edu systemd-udevd[848582]: link_config: could not get ethtool features for veth20c911a Aug 3 04:57:39 sentry-docker00.cs.umd.edu systemd-udevd[848582]: Could not set offload features of veth20c911a: No such device Aug 3 04:57:39 sentry-docker00.cs.umd.edu systemd-udevd[848583]: link_config: could not get ethtool features for vetha5a02d8 Aug 3 04:57:39 sentry-docker00.cs.umd.edu systemd-udevd[848583]: Could not set offload features of vetha5a02d8: No such device ... 12 more distinct messages not shown == smokeping-slave (1 distinct, 1 total) == Aug 3 04:15:31 smokeping-slave nologin[627822]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN == strawberry (4 distinct, 10 total) == Aug 3 04: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 04:15:04 strawberry nologin[3453213]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN Aug 3 04:15:04 strawberry pipewire[3453212]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files Aug 3 04:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (1 distinct, 2 total) == Aug 3 04:05:18 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-4 (11 distinct, 17 total) == Aug 3 04:16:12 submit26-b9-4 setroubleshoot[928084]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a4e66030-8621-4da9-bd27-5988bb1bf8ad [x2] Aug 3 04:16:12 submit26-b9-4 setroubleshoot[928084]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l c055e37d-bbf5-4800-9083-d606f792c8c1 [x2] Aug 3 04:16:12 submit26-b9-4 setroubleshoot[928084]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l e5bc3a56-6d6f-4776-954f-ddde1579648f Aug 3 04:16:12 submit26-b9-4 setroubleshoot[928084]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3w4m7b/repodata/repomd.xml. For complete SELinux messages run: sealert -l a8ec5e1b-49f9-4fbc-a8ae-22e800f7abf2 Aug 3 04:16:12 submit26-b9-4 setroubleshoot[928084]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 945db714-d0c0-4402-911e-932978b8b036 Aug 3 04:16:12 submit26-b9-4 setroubleshoot[928084]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3w4m7b. For complete SELinux messages run: sealert -l 463998a0-fb0d-463c-82b1-471135710a14 Aug 3 04:16:12 submit26-b9-4 setroubleshoot[928084]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 473d2e21-15d8-407a-a9ee-2b842607fa00 [x2] Aug 3 04:16:12 submit26-b9-4 setroubleshoot[928084]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 80c54d4f-bf4b-4501-addb-1627383587d0 Aug 3 04:16:12 submit26-b9-4 setroubleshoot[928084]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l c63d3890-151e-49a0-83f0-3dfb69d051e5 [x2] Aug 3 04:16:12 submit26-b9-4 setroubleshoot[928084]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.hWqpuf. For complete SELinux messages run: sealert -l 463998a0-fb0d-463c-82b1-471135710a14 Aug 3 04:42:50 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3]