Command: /usr/local/sbin/syslog-digest.py Time : 0.4990s Status : exited 0 Output : Syslog digest — 2026-08-06 05:05 EDT Processed 4,562 lines, filtered 3,799 (83%). 763 unknown (89 distinct) from 22 host(s). == abadi-computer (2 distinct, 2 total) == Aug 6 04:15:01 abadi-computer nologin[1794714]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN Aug 6 04:15:01 abadi-computer pipewire[1794711]: 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, 346 total) == Aug 6 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 ] [x346] == atif01.cs.umd.edu (1 distinct, 1 total) == Aug 6 05:04:04 atif01.cs.umd.edu kernel: net_ratelimit: 12 callbacks suppressed == b0b02.cs.umd.edu (4 distinct, 4 total) == Aug 6 04:41:51 b0b02.cs.umd.edu setroubleshoot[3461408]: 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 6 04:41:54 b0b02.cs.umd.edu setroubleshoot[3461408]: 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 6 04:41:57 b0b02.cs.umd.edu setroubleshoot[3461408]: 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 6 04:47:25 b0b02.cs.umd.edu rustdesk[3462385]: cannot open display: == biggulp.cs.umd.edu (3 distinct, 3 total) == Aug 6 04:23:28 biggulp.cs.umd.edu sshd-session[3307866]: pam_access(sshd:auth): access denied for user `admin' from `94.183.187.22' Aug 6 04:23:28 biggulp.cs.umd.edu krb5_child[3307868]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 6 04:23:28 biggulp.cs.umd.edu sshd-session[3307864]: error: PAM: System error for admin from 94.183.187.22 == contest (1 distinct, 34 total) == Aug 6 04:06:00 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, 226 total) == Aug 6 04:04:38 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x226] == dojo (1 distinct, 1 total) == Aug 6 04:15:24 dojo nologin[1228254]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN == forge00 (1 distinct, 1 total) == Aug 6 04:09:02 forge00 (httpd)[2027577]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS == idm00 (1 distinct, 1 total) == Aug 6 04:51:18 idm00 named[1455]: client @0x7f33103836b8 10.73.240.42#55385: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 6 04:36:07 idmp0 named[5198]: client @0x7f9908000cc8 10.73.240.43#57630: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 1 total) == Aug 6 04:09:21 inbound00.cs.umd.edu krb5_child[3425801]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 32 total) == Aug 6 04:08:05 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x32] == matrix (11 distinct, 12 total) == Aug 6 04:23:59 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3260559, but reception only permitted for main PID 720 Aug 6 04:23:59 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3260572, but reception only permitted for main PID 720 Aug 6 04:24:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3260704, but reception only permitted for main PID 720 Aug 6 04:24:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3260710, but reception only permitted for main PID 720 Aug 6 04:24:07 matrix networkctl[3260723]: Interface "vethbb30bf9" not found. Aug 6 04:24:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3260779, but reception only permitted for main PID 720 Aug 6 04:24:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3260792, but reception only permitted for main PID 720 Aug 6 04:24:17 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3260895, but reception only permitted for main PID 720 Aug 6 04:24:17 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3260901, but reception only permitted for main PID 720 Aug 6 04:24:17 matrix networkctl[3260913]: Interface "vethe5f6624" not found. Aug 6 04:24:17 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3260913, but reception only permitted for main PID 720 [x2] == netman.cs.umd.edu (4 distinct, 4 total) == Aug 6 04:30:01 netman.cs.umd.edu setroubleshoot[1376608]: 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 6 04:30:02 netman.cs.umd.edu setroubleshoot[1376608]: 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 6 04:30:02 netman.cs.umd.edu setroubleshoot[1376608]: 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 Aug 6 04:41:30 netman.cs.umd.edu sshd[1379868]: error: PAM: Authentication failure for sshd from 122.187.227.152 == newhonors2 (1 distinct, 24 total) == Aug 6 04:13:03 newhonors2 dhcpcd[801319]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Aug 6 04:09:09 outbound00.cs.umd.edu python3[3377652]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 6 04:13:06 outbound01.cs.umd.edu python3[1411519]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Aug 6 04:07:03 sentry-docker00.cs.umd.edu systemd-udevd[2862407]: link_config: could not get ethtool features for veth15d9cbf Aug 6 04:07:03 sentry-docker00.cs.umd.edu systemd-udevd[2862407]: Could not set offload features of veth15d9cbf: No such device Aug 6 04:07:03 sentry-docker00.cs.umd.edu systemd-udevd[2862435]: Could not generate persistent MAC address for veth087a328: No such file or directory Aug 6 04:07:03 sentry-docker00.cs.umd.edu systemd-udevd[2862436]: Could not generate persistent MAC address for vetha028ad4: No such file or directory Aug 6 04:07:03 sentry-docker00.cs.umd.edu systemd-udevd[2862461]: Could not generate persistent MAC address for veth117a660: No such file or directory Aug 6 04:07:03 sentry-docker00.cs.umd.edu systemd-udevd[2862462]: Could not generate persistent MAC address for veth7902f0e: No such file or directory Aug 6 04:07:03 sentry-docker00.cs.umd.edu systemd-udevd[2862487]: Could not generate persistent MAC address for veth741a7dc: No such file or directory Aug 6 04:07:03 sentry-docker00.cs.umd.edu systemd-udevd[2862488]: Could not generate persistent MAC address for vethf2bb0e2: No such file or directory Aug 6 04:07:03 sentry-docker00.cs.umd.edu systemd-udevd[2862487]: Could not generate persistent MAC address for vetha1af088: No such file or directory Aug 6 04:07:03 sentry-docker00.cs.umd.edu systemd-udevd[2862510]: Could not generate persistent MAC address for veth48d952c: No such file or directory Aug 6 04:07:03 sentry-docker00.cs.umd.edu systemd-udevd[2862499]: Could not generate persistent MAC address for veth15fe071: No such file or directory Aug 6 04:07:03 sentry-docker00.cs.umd.edu systemd-udevd[2862510]: Could not generate persistent MAC address for vethff07072: No such file or directory Aug 6 04:27:11 sentry-docker00.cs.umd.edu systemd-udevd[2871910]: link_config: could not get ethtool features for veth087a328 Aug 6 04:27:11 sentry-docker00.cs.umd.edu systemd-udevd[2871910]: Could not set offload features of veth087a328: No such device Aug 6 04:27:11 sentry-docker00.cs.umd.edu systemd-udevd[2871945]: Could not generate persistent MAC address for veth288d6a8: No such file or directory Aug 6 04:27:11 sentry-docker00.cs.umd.edu systemd-udevd[2871946]: Could not generate persistent MAC address for veth71d4f47: No such file or directory Aug 6 04:27:11 sentry-docker00.cs.umd.edu systemd-udevd[2871949]: Could not generate persistent MAC address for veth34bb73b: No such file or directory Aug 6 04:27:11 sentry-docker00.cs.umd.edu systemd-udevd[2871950]: Could not generate persistent MAC address for vetha107dae: No such file or directory Aug 6 04:27:11 sentry-docker00.cs.umd.edu systemd-udevd[2871967]: Could not generate persistent MAC address for veth868dec5: No such file or directory Aug 6 04:27:11 sentry-docker00.cs.umd.edu systemd-udevd[2871945]: Could not generate persistent MAC address for vethaba402b: No such file or directory Aug 6 04:27:11 sentry-docker00.cs.umd.edu systemd-udevd[2871967]: Could not generate persistent MAC address for vetha367946: No such file or directory Aug 6 04:27:11 sentry-docker00.cs.umd.edu systemd-udevd[2871950]: Could not generate persistent MAC address for vethfd39c39: No such file or directory Aug 6 04:27:11 sentry-docker00.cs.umd.edu systemd-udevd[2871984]: Could not generate persistent MAC address for vethc74d234: No such file or directory Aug 6 04:27:11 sentry-docker00.cs.umd.edu systemd-udevd[2871988]: Could not generate persistent MAC address for veth3d4311e: No such file or directory Aug 6 04:47:19 sentry-docker00.cs.umd.edu systemd-udevd[2881232]: link_config: could not get ethtool features for vethfd39c39 Aug 6 04:47:19 sentry-docker00.cs.umd.edu systemd-udevd[2881232]: Could not set offload features of vethfd39c39: No such device Aug 6 04:47:19 sentry-docker00.cs.umd.edu systemd-udevd[2881282]: link_config: could not get ethtool features for vethc74d234 Aug 6 04:47:19 sentry-docker00.cs.umd.edu systemd-udevd[2881282]: Could not set offload features of vethc74d234: No such device Aug 6 04:47:20 sentry-docker00.cs.umd.edu systemd-udevd[2881341]: Could not generate persistent MAC address for vethe25195e: No such file or directory Aug 6 04:47:20 sentry-docker00.cs.umd.edu systemd-udevd[2881339]: Could not generate persistent MAC address for veth5984efe: No such file or directory ... 8 more distinct messages not shown == smokeping-slave (1 distinct, 1 total) == Aug 6 04:15:01 smokeping-slave nologin[973036]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN == strawberry (4 distinct, 10 total) == Aug 6 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 6 04:15:00 strawberry nologin[3663192]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN Aug 6 04:15:00 strawberry pipewire[3663191]: 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 6 04:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-4 (9 distinct, 9 total) == Aug 6 04:16:25 submit26-b9-4 setroubleshoot[1163498]: 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 Aug 6 04:16:25 submit26-b9-4 setroubleshoot[1163498]: 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 Aug 6 04:16:25 submit26-b9-4 setroubleshoot[1163498]: 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 6 04:16:25 submit26-b9-4 setroubleshoot[1163498]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.g8nveZ/repodata/repomd.xml. For complete SELinux messages run: sealert -l a8ec5e1b-49f9-4fbc-a8ae-22e800f7abf2 Aug 6 04:16:25 submit26-b9-4 setroubleshoot[1163498]: 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 6 04:16:25 submit26-b9-4 setroubleshoot[1163498]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.g8nveZ. For complete SELinux messages run: sealert -l 463998a0-fb0d-463c-82b1-471135710a14 Aug 6 04:16:25 submit26-b9-4 setroubleshoot[1163498]: 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 Aug 6 04:16:25 submit26-b9-4 setroubleshoot[1163498]: 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 6 04:16:25 submit26-b9-4 setroubleshoot[1163498]: 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