Command: /usr/local/sbin/syslog-digest.py Time : 0.4814s Status : exited 0 Output : Syslog digest — 2026-08-01 05:05 EDT Processed 4,108 lines, filtered 3,342 (81%). 766 unknown (91 distinct) from 21 host(s). == abadi-computer (2 distinct, 2 total) == Aug 1 04:15:00 abadi-computer nologin[536079]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN Aug 1 04:15:00 abadi-computer pipewire[536077]: 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 1 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] == b0b02.cs.umd.edu (4 distinct, 4 total) == Aug 1 04:28:33 b0b02.cs.umd.edu setroubleshoot[1635297]: 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 1 04:28:35 b0b02.cs.umd.edu setroubleshoot[1635297]: 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 1 04:28:38 b0b02.cs.umd.edu setroubleshoot[1635297]: 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 1 04:40:09 b0b02.cs.umd.edu rustdesk[1638241]: cannot open display: == contest (1 distinct, 34 total) == Aug 1 04:05:59 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, 224 total) == Aug 1 04:04:54 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x224] == dojo (1 distinct, 1 total) == Aug 1 04:15:00 dojo nologin[791366]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN == forge00 (1 distinct, 1 total) == Aug 1 04:09:02 forge00 (httpd)[1339995]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS == idm00 (1 distinct, 1 total) == Aug 1 04:51:14 idm00 named[1455]: client @0x7f3310201ff8 10.73.240.42#61247: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 1 04:36:02 idmp0 named[5198]: client @0x7f99040313a8 10.73.240.43#50570: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 31 total) == Aug 1 04:08:13 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x31] == matrix (11 distinct, 13 total) == Aug 1 04:16:58 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3301215, but reception only permitted for main PID 720 Aug 1 04:16:58 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3301225, but reception only permitted for main PID 720 Aug 1 04:17:05 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3301338, but reception only permitted for main PID 720 Aug 1 04:17:05 matrix networkctl[3301355]: Interface "veth561eb29" not found. Aug 1 04:17:05 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3301355, but reception only permitted for main PID 720 [x2] Aug 1 04:17:06 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3301416, but reception only permitted for main PID 720 Aug 1 04:17:06 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3301428, but reception only permitted for main PID 720 Aug 1 04:17:15 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3301532, but reception only permitted for main PID 720 Aug 1 04:17:15 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3301538, but reception only permitted for main PID 720 Aug 1 04:17:15 matrix networkctl[3301549]: Interface "veth5d07beb" not found. Aug 1 04:17:15 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3301549, but reception only permitted for main PID 720 [x2] == mcstic (3 distinct, 6 total) == Aug 1 04:29:29 mcstic krb5_child[1951573]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Aug 1 04:29:35 mcstic sshd[1951568]: error: PAM: Authentication failure for admin from 34.77.36.89 Aug 1 04:29:47 mcstic sshd[1951582]: error: Protocol major versions differ: 2 vs. 1 == nagios-worker-admin-avw00.cs.umd.edu (1 distinct, 1 total) == Aug 1 04:26:26 nagios-worker-admin-avw00.cs.umd.edu kernel: hrtimer: interrupt took 316151 ns == netman.cs.umd.edu (3 distinct, 3 total) == Aug 1 04:29:58 netman.cs.umd.edu setroubleshoot[3570328]: 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 1 04:29:59 netman.cs.umd.edu setroubleshoot[3570328]: 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 1 04:30:02 netman.cs.umd.edu setroubleshoot[3570328]: 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 1 04:13:03 newhonors2 dhcpcd[572401]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Aug 1 04:09:09 outbound00.cs.umd.edu python3[1692182]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 1 04:13:06 outbound01.cs.umd.edu python3[3918573]: ldapdb [x6] == sentry-docker00.cs.umd.edu (42 distinct, 42 total) == Aug 1 04:17:33 sentry-docker00.cs.umd.edu systemd-udevd[3661041]: link_config: could not get ethtool features for veth333ba1e Aug 1 04:17:33 sentry-docker00.cs.umd.edu systemd-udevd[3661041]: Could not set offload features of veth333ba1e: No such device Aug 1 04:17:33 sentry-docker00.cs.umd.edu systemd-udevd[3661070]: Could not generate persistent MAC address for veth5c01a2f: No such file or directory Aug 1 04:17:33 sentry-docker00.cs.umd.edu systemd-udevd[3661071]: Could not generate persistent MAC address for veth354a01b: No such file or directory Aug 1 04:17:33 sentry-docker00.cs.umd.edu systemd-udevd[3661074]: Could not generate persistent MAC address for vetha8bc216: No such file or directory Aug 1 04:17:33 sentry-docker00.cs.umd.edu systemd-udevd[3661075]: Could not generate persistent MAC address for veth103d50a: No such file or directory Aug 1 04:17:33 sentry-docker00.cs.umd.edu systemd-udevd[3661090]: Could not generate persistent MAC address for veth4e3ce81: No such file or directory Aug 1 04:17:33 sentry-docker00.cs.umd.edu systemd-udevd[3661083]: Could not generate persistent MAC address for vethf6cbbd0: No such file or directory Aug 1 04:17:33 sentry-docker00.cs.umd.edu systemd-udevd[3661148]: Could not generate persistent MAC address for veth44835a0: No such file or directory Aug 1 04:17:33 sentry-docker00.cs.umd.edu systemd-udevd[3661152]: Could not generate persistent MAC address for vethba7b037: No such file or directory Aug 1 04:20:57 sentry-docker00.cs.umd.edu systemd-udevd[3663707]: link_config: could not get ethtool features for vethaff66ab Aug 1 04:20:57 sentry-docker00.cs.umd.edu systemd-udevd[3663707]: Could not set offload features of vethaff66ab: No such device Aug 1 04:20:57 sentry-docker00.cs.umd.edu systemd-udevd[3663725]: Could not generate persistent MAC address for veth07b7204: No such file or directory Aug 1 04:20:57 sentry-docker00.cs.umd.edu systemd-udevd[3663726]: Could not generate persistent MAC address for veth6f4bcbf: No such file or directory Aug 1 04:37:41 sentry-docker00.cs.umd.edu systemd-udevd[3670423]: link_config: could not get ethtool features for veth44835a0 Aug 1 04:37:41 sentry-docker00.cs.umd.edu systemd-udevd[3670423]: Could not set offload features of veth44835a0: No such device Aug 1 04:37:41 sentry-docker00.cs.umd.edu systemd-udevd[3670489]: Could not generate persistent MAC address for veth83a6bcd: No such file or directory Aug 1 04:37:41 sentry-docker00.cs.umd.edu systemd-udevd[3670490]: Could not generate persistent MAC address for veth41844e5: No such file or directory Aug 1 04:37:41 sentry-docker00.cs.umd.edu systemd-udevd[3670501]: Could not generate persistent MAC address for vethdbb77da: No such file or directory Aug 1 04:37:41 sentry-docker00.cs.umd.edu systemd-udevd[3670497]: Could not generate persistent MAC address for veth6871498: No such file or directory Aug 1 04:37:41 sentry-docker00.cs.umd.edu systemd-udevd[3670514]: Could not generate persistent MAC address for veth940ac23: No such file or directory Aug 1 04:37:41 sentry-docker00.cs.umd.edu systemd-udevd[3670494]: Could not generate persistent MAC address for veth72f5ff2: No such file or directory Aug 1 04:37:41 sentry-docker00.cs.umd.edu systemd-udevd[3670497]: Could not generate persistent MAC address for veth014facd: No such file or directory Aug 1 04:37:41 sentry-docker00.cs.umd.edu systemd-udevd[3670502]: Could not generate persistent MAC address for veth54ad1bb: No such file or directory Aug 1 04:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3673084]: link_config: could not get ethtool features for veth07b7204 Aug 1 04:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3673084]: Could not set offload features of veth07b7204: No such device Aug 1 04:41:02 sentry-docker00.cs.umd.edu systemd-udevd[3673101]: Could not generate persistent MAC address for veth968e894: No such file or directory Aug 1 04:41:02 sentry-docker00.cs.umd.edu systemd-udevd[3673102]: Could not generate persistent MAC address for veth7b73a45: No such file or directory Aug 1 04:57:49 sentry-docker00.cs.umd.edu systemd-udevd[3679798]: link_config: could not get ethtool features for veth6871498 Aug 1 04:57:49 sentry-docker00.cs.umd.edu systemd-udevd[3679798]: Could not set offload features of veth6871498: No such device ... 12 more distinct messages not shown == smokeping-slave (1 distinct, 1 total) == Aug 1 04:15:31 smokeping-slave nologin[397754]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN == strawberry (4 distinct, 10 total) == Aug 1 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 1 04:15:04 strawberry nologin[3293847]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN Aug 1 04:15:04 strawberry pipewire[3293846]: 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 1 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 1 04:16:12 submit26-b9-4 setroubleshoot[760975]: 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 1 04:16:12 submit26-b9-4 setroubleshoot[760975]: 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 1 04:16:12 submit26-b9-4 setroubleshoot[760975]: 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 1 04:16:12 submit26-b9-4 setroubleshoot[760975]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.WkNPEE/repodata/repomd.xml. For complete SELinux messages run: sealert -l a8ec5e1b-49f9-4fbc-a8ae-22e800f7abf2 Aug 1 04:16:12 submit26-b9-4 setroubleshoot[760975]: 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 1 04:16:12 submit26-b9-4 setroubleshoot[760975]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.WkNPEE. For complete SELinux messages run: sealert -l 463998a0-fb0d-463c-82b1-471135710a14 Aug 1 04:16:12 submit26-b9-4 setroubleshoot[760975]: 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 1 04:16:12 submit26-b9-4 setroubleshoot[760975]: 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 1 04:16:12 submit26-b9-4 setroubleshoot[760975]: 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