Command: /usr/local/sbin/syslog-digest.py Time : 0.5852s Status : exited 0 Output : Syslog digest — 2026-07-31 21:05 EDT Processed 4,814 lines, filtered 3,634 (75%). 1,180 unknown (287 distinct) from 18 host(s). == abuse (1 distinct, 349 total) == Jul 31 20: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 ] [x349] == atif01.cs.umd.edu (213 distinct, 426 total) == Jul 31 20:08:08 atif01.cs.umd.edu sshd[10126]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 57863 ssh2 [preauth] Jul 31 20:08:08 atif01.cs.umd.edu sshd[10126]: PAM service(sshd) ignoring max retries; 6 > 3 [x213] Jul 31 20:08:24 atif01.cs.umd.edu sshd[10134]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 60495 ssh2 [preauth] Jul 31 20:08:40 atif01.cs.umd.edu sshd[10152]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 62834 ssh2 [preauth] Jul 31 20:08:54 atif01.cs.umd.edu sshd[10162]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 65363 ssh2 [preauth] Jul 31 20:09:10 atif01.cs.umd.edu sshd[10170]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 51199 ssh2 [preauth] Jul 31 20:09:26 atif01.cs.umd.edu sshd[10180]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 53559 ssh2 [preauth] Jul 31 20:09:43 atif01.cs.umd.edu sshd[10196]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 56096 ssh2 [preauth] Jul 31 20:09:59 atif01.cs.umd.edu sshd[10207]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 58504 ssh2 [preauth] Jul 31 20:10:16 atif01.cs.umd.edu sshd[10217]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 61034 ssh2 [preauth] Jul 31 20:10:33 atif01.cs.umd.edu sshd[10242]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 63452 ssh2 [preauth] Jul 31 20:10:49 atif01.cs.umd.edu sshd[10254]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 49633 ssh2 [preauth] Jul 31 20:11:06 atif01.cs.umd.edu sshd[10264]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 52091 ssh2 [preauth] Jul 31 20:11:21 atif01.cs.umd.edu sshd[10272]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 54577 ssh2 [preauth] Jul 31 20:11:37 atif01.cs.umd.edu sshd[10290]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 56906 ssh2 [preauth] Jul 31 20:11:53 atif01.cs.umd.edu sshd[10300]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 59293 ssh2 [preauth] Jul 31 20:12:09 atif01.cs.umd.edu sshd[10316]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 61745 ssh2 [preauth] Jul 31 20:12:26 atif01.cs.umd.edu sshd[10326]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 64228 ssh2 [preauth] Jul 31 20:12:41 atif01.cs.umd.edu sshd[10342]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 50364 ssh2 [preauth] Jul 31 20:12:56 atif01.cs.umd.edu sshd[10352]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 52757 ssh2 [preauth] [x2] Jul 31 20:13:13 atif01.cs.umd.edu sshd[10362]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 55108 ssh2 [preauth] Jul 31 20:13:29 atif01.cs.umd.edu sshd[10370]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 57654 ssh2 [preauth] Jul 31 20:13:44 atif01.cs.umd.edu sshd[10388]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 60227 ssh2 [preauth] Jul 31 20:13:59 atif01.cs.umd.edu sshd[10396]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 62681 ssh2 [preauth] Jul 31 20:14:15 atif01.cs.umd.edu sshd[10406]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 65091 ssh2 [preauth] Jul 31 20:14:30 atif01.cs.umd.edu sshd[10424]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 51263 ssh2 [preauth] Jul 31 20:14:46 atif01.cs.umd.edu sshd[10432]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 53592 ssh2 [preauth] Jul 31 20:15:01 atif01.cs.umd.edu sshd[10442]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 56017 ssh2 [preauth] Jul 31 20:15:16 atif01.cs.umd.edu sshd[10451]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 58355 ssh2 [preauth] Jul 31 20:15:31 atif01.cs.umd.edu sshd[10469]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 60739 ssh2 [preauth] ... 183 more distinct messages not shown == b0b02.cs.umd.edu (1 distinct, 1 total) == Jul 31 20:39:40 b0b02.cs.umd.edu rustdesk[1516440]: cannot open display: == contest (1 distinct, 34 total) == Jul 31 20:05:46 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 (2 distinct, 232 total) == Jul 31 20:04:34 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x228] Jul 31 20:16:34 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x4] == hackerman (6 distinct, 11 total) == Jul 31 20:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4] Jul 31 20:20:13 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding Jul 31 20:20:27 hackerman packagekitd[2585478]: Failed to get cache filename for libreoffice [x2] Jul 31 20:20:27 hackerman packagekitd[2585478]: Failed to get cache filename for kernel [x2] Jul 31 20:20:30 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.9LRVS3”: Permission denied Jul 31 20:20:38 hackerman packagekitd[2585478]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == idm00 (1 distinct, 1 total) == Jul 31 20:51:13 idm00 named[1455]: client @0x7f330c5f7628 10.73.240.42#52642: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Jul 31 20:36:02 idmp0 named[5198]: client @0x7f992801b8a8 10.73.240.43#64974: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 21 total) == Jul 31 20:07:57 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x21] == munin (2 distinct, 2 total) == Jul 31 20:07:57 munin sudo[3954247]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory Jul 31 20:07:57 munin sudo[3954247]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. == netman.cs.umd.edu (3 distinct, 3 total) == Jul 31 20:29:59 netman.cs.umd.edu setroubleshoot[3435269]: 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 Jul 31 20:30:00 netman.cs.umd.edu setroubleshoot[3435269]: 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 Jul 31 20:30:02 netman.cs.umd.edu setroubleshoot[3435269]: 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) == Jul 31 20:13:03 newhonors2 dhcpcd[557372]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 31 20:09:09 outbound00.cs.umd.edu python3[1579470]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Jul 31 20:13:06 outbound01.cs.umd.edu python3[3806519]: ldapdb [x6] == peach.cs.umd.edu (2 distinct, 2 total) == Jul 31 20:32:09 peach.cs.umd.edu setroubleshoot[1930281]: 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 31 20:32:09 peach.cs.umd.edu setroubleshoot[1930281]: 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 (38 distinct, 38 total) == Jul 31 20:14:13 sentry-docker00.cs.umd.edu systemd-udevd[3432906]: Could not generate persistent MAC address for veth1c1279c: No such file or directory Jul 31 20:14:13 sentry-docker00.cs.umd.edu systemd-udevd[3432907]: Could not generate persistent MAC address for veth79ab242: No such file or directory Jul 31 20:14:13 sentry-docker00.cs.umd.edu systemd-udevd[3432910]: Could not generate persistent MAC address for veth968ed51: No such file or directory Jul 31 20:14:13 sentry-docker00.cs.umd.edu systemd-udevd[3432911]: Could not generate persistent MAC address for vetha58917d: No such file or directory Jul 31 20:14:13 sentry-docker00.cs.umd.edu systemd-udevd[3432910]: Could not generate persistent MAC address for veth7b677d5: No such file or directory Jul 31 20:14:13 sentry-docker00.cs.umd.edu systemd-udevd[3432927]: Could not generate persistent MAC address for vethbc4fc0a: No such file or directory Jul 31 20:14:13 sentry-docker00.cs.umd.edu systemd-udevd[3432927]: Could not generate persistent MAC address for veth87b98c8: No such file or directory Jul 31 20:14:13 sentry-docker00.cs.umd.edu systemd-udevd[3432930]: Could not generate persistent MAC address for veth271fd73: No such file or directory Jul 31 20:18:10 sentry-docker00.cs.umd.edu systemd-udevd[3435673]: Could not generate persistent MAC address for veth432371c: No such file or directory Jul 31 20:18:10 sentry-docker00.cs.umd.edu systemd-udevd[3435674]: Could not generate persistent MAC address for vethb361b8e: No such file or directory Jul 31 20:34:21 sentry-docker00.cs.umd.edu systemd-udevd[3442283]: link_config: could not get ethtool features for veth7b677d5 Jul 31 20:34:21 sentry-docker00.cs.umd.edu systemd-udevd[3442283]: Could not set offload features of veth7b677d5: No such device Jul 31 20:34:21 sentry-docker00.cs.umd.edu systemd-udevd[3442347]: Could not generate persistent MAC address for veth723b4fd: No such file or directory Jul 31 20:34:21 sentry-docker00.cs.umd.edu systemd-udevd[3442348]: Could not generate persistent MAC address for veth2db074f: No such file or directory Jul 31 20:34:21 sentry-docker00.cs.umd.edu systemd-udevd[3442351]: Could not generate persistent MAC address for veth134bdb9: No such file or directory Jul 31 20:34:21 sentry-docker00.cs.umd.edu systemd-udevd[3442352]: Could not generate persistent MAC address for veth72d0d7c: No such file or directory Jul 31 20:34:21 sentry-docker00.cs.umd.edu systemd-udevd[3442375]: Could not generate persistent MAC address for veth649a314: No such file or directory Jul 31 20:34:21 sentry-docker00.cs.umd.edu systemd-udevd[3442376]: Could not generate persistent MAC address for veth6f84ae0: No such file or directory Jul 31 20:34:21 sentry-docker00.cs.umd.edu systemd-udevd[3442394]: Could not generate persistent MAC address for vethb441ee6: No such file or directory Jul 31 20:34:21 sentry-docker00.cs.umd.edu systemd-udevd[3442395]: Could not generate persistent MAC address for vethdc6cee7: No such file or directory Jul 31 20:38:15 sentry-docker00.cs.umd.edu systemd-udevd[3445073]: link_config: could not get ethtool features for veth432371c Jul 31 20:38:15 sentry-docker00.cs.umd.edu systemd-udevd[3445073]: Could not set offload features of veth432371c: No such device Jul 31 20:38:15 sentry-docker00.cs.umd.edu systemd-udevd[3445089]: Could not generate persistent MAC address for vethfc4cba3: No such file or directory Jul 31 20:38:15 sentry-docker00.cs.umd.edu systemd-udevd[3445090]: Could not generate persistent MAC address for veth5cd3b73: No such file or directory Jul 31 20:54:29 sentry-docker00.cs.umd.edu systemd-udevd[3451791]: link_config: could not get ethtool features for vethb441ee6 Jul 31 20:54:29 sentry-docker00.cs.umd.edu systemd-udevd[3451791]: Could not set offload features of vethb441ee6: No such device Jul 31 20:54:30 sentry-docker00.cs.umd.edu systemd-udevd[3451828]: Could not generate persistent MAC address for vetheb11e68: No such file or directory Jul 31 20:54:30 sentry-docker00.cs.umd.edu systemd-udevd[3451829]: Could not generate persistent MAC address for vethcfd5b9c: No such file or directory Jul 31 20:54:30 sentry-docker00.cs.umd.edu systemd-udevd[3451854]: Could not generate persistent MAC address for veth878bcd5: No such file or directory Jul 31 20:54:30 sentry-docker00.cs.umd.edu systemd-udevd[3451855]: Could not generate persistent MAC address for vethdb31bf0: No such file or directory ... 8 more distinct messages not shown == strawberry (2 distinct, 8 total) == Jul 31 20: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 31 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-4 (10 distinct, 15 total) == Jul 31 20:08:05 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Jul 31 20:15:28 submit26-b9-4 setroubleshoot[737799]: 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 Jul 31 20:15:28 submit26-b9-4 setroubleshoot[737799]: 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 Jul 31 20:15:28 submit26-b9-4 setroubleshoot[737799]: 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 [x2] Jul 31 20:15:28 submit26-b9-4 setroubleshoot[737799]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.votyI6/repodata/repomd.xml. For complete SELinux messages run: sealert -l a8ec5e1b-49f9-4fbc-a8ae-22e800f7abf2 [x2] Jul 31 20:15:28 submit26-b9-4 setroubleshoot[737799]: 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 [x2] Jul 31 20:15:28 submit26-b9-4 setroubleshoot[737799]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.votyI6. For complete SELinux messages run: sealert -l 463998a0-fb0d-463c-82b1-471135710a14 Jul 31 20:15:28 submit26-b9-4 setroubleshoot[737799]: 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 Jul 31 20:15:28 submit26-b9-4 setroubleshoot[737799]: 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 Jul 31 20:15:28 submit26-b9-4 setroubleshoot[737799]: 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