Command: /usr/local/sbin/syslog-digest.py Time : 0.5089s Status : exited 0 Output : Syslog digest — 2026-08-03 03:05 EDT Processed 4,688 lines, filtered 3,900 (83%). 788 unknown (74 distinct) from 19 host(s). == abuse (1 distinct, 347 total) == Aug 3 02: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 (1 distinct, 1 total) == Aug 3 02:42:55 b0b02.cs.umd.edu rustdesk[2337047]: cannot open display: == biggulp.cs.umd.edu (5 distinct, 5 total) == Aug 3 02:42:51 biggulp.cs.umd.edu sshd-session[2500438]: error: maximum authentication attempts exceeded for root from 109.63.133.236 port 37974 ssh2 [preauth] Aug 3 02:42:57 biggulp.cs.umd.edu sshd-session[2500473]: error: maximum authentication attempts exceeded for root from 109.63.133.236 port 38264 ssh2 [preauth] Aug 3 02:43:03 biggulp.cs.umd.edu sshd-session[2500506]: error: maximum authentication attempts exceeded for root from 109.63.133.236 port 38546 ssh2 [preauth] Aug 3 02:43:16 biggulp.cs.umd.edu sshd-session[2500515]: error: maximum authentication attempts exceeded for admin from 109.63.133.236 port 39198 ssh2 [preauth] Aug 3 02:43:22 biggulp.cs.umd.edu sshd-session[2500523]: error: maximum authentication attempts exceeded for admin from 109.63.133.236 port 39530 ssh2 [preauth] == cheezit.cs.umd.edu (11 distinct, 13 total) == Aug 3 02:36:50 cheezit.cs.umd.edu setroubleshoot[494006]: failed to retrieve rpm info for path '/var/log/falconctl.log': Aug 3 02:36:51 cheezit.cs.umd.edu setroubleshoot[494006]: SELinux is preventing /opt/CrowdStrike/falconctl18708 from append access on the file /var/log/falconctl.log. For complete SELinux messages run: sealert -l 63f66d53-fcfc-44da-a79e-c789b1ce2ce8 Aug 3 02:36:53 cheezit.cs.umd.edu setroubleshoot[494006]: SELinux is preventing /opt/CrowdStrike/falconctl18708 from write access on the file falconstore. For complete SELinux messages run: sealert -l 386506af-597f-4357-89de-bc382f369a6e Aug 3 02:37:04 cheezit.cs.umd.edu setroubleshoot[494408]: failed to retrieve rpm info for path '/var/lib/sss/pipes/nss': [x2] Aug 3 02:37:05 cheezit.cs.umd.edu setroubleshoot[494408]: SELinux is preventing /usr/bin/lsof from write access on the sock_file /var/lib/sss/pipes/nss. For complete SELinux messages run: sealert -l f570494d-54d2-4dac-97e2-28395659abf1 [x2] Aug 3 02:37:05 cheezit.cs.umd.edu setroubleshoot[494408]: SELinux is preventing /usr/bin/lsof from write access on the sock_file socket. For complete SELinux messages run: sealert -l 9ff2383b-9e1d-44ff-b8ae-af91637450ae Aug 3 02:37:45 cheezit.cs.umd.edu setroubleshoot[494832]: SELinux is preventing /usr/bin/python3.9 from read access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs_dist. For complete SELinux messages run: sealert -l 679eb260-cf5d-4783-99f4-ce308edb3295 Aug 3 02:37:45 cheezit.cs.umd.edu setroubleshoot[494832]: SELinux is preventing /usr/bin/python3.9 from open access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs_dist. For complete SELinux messages run: sealert -l 77caba8a-5cd0-4e18-b188-6e35c461772d Aug 3 02:37:45 cheezit.cs.umd.edu setroubleshoot[494832]: SELinux is preventing /usr/bin/python3.9 from read access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs. For complete SELinux messages run: sealert -l d9c6dd0d-0a34-4430-a5ff-e985c55cb064 Aug 3 02:37:45 cheezit.cs.umd.edu setroubleshoot[494832]: SELinux is preventing /usr/bin/python3.9 from open access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs. For complete SELinux messages run: sealert -l 8edbce57-8212-4ac8-af50-3fe403231eda Aug 3 02:37:45 cheezit.cs.umd.edu setroubleshoot[494832]: SELinux is preventing /usr/bin/python3.9 from map access on the file /etc/selinux/targeted/contexts/files/file_contexts.bin. For complete SELinux messages run: sealert -l 4a0cbe3b-6f49-4c7e-95c6-380f7aef806e == cmsc436-0101-redis (2 distinct, 2 total) == Aug 3 02:07:26 cmsc436-0101-redis krb5_child[726385]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 3 02:07:28 cmsc436-0101-redis sshd-session[726381]: error: PAM: Authentication failure for admin from 34.140.33.144 == contest (1 distinct, 34 total) == Aug 3 02: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, 246 total) == Aug 3 02:04:24 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x246] == idm00 (1 distinct, 1 total) == Aug 3 02:51:15 idm00 named[1455]: client @0x7f330ca369a8 10.73.240.42#64227: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 3 02:36:01 idmp0 named[5198]: client @0x7f992400e068 10.73.240.43#56928: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 35 total) == Aug 3 02:08:04 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x35] == krispykreme.cs.umd.edu (3 distinct, 3 total) == Aug 3 03:00:05 krispykreme.cs.umd.edu sshd-session[2651416]: pam_access(sshd:auth): access denied for user `admin' from `34.22.121.160' Aug 3 03:00:06 krispykreme.cs.umd.edu krb5_child[2651418]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 3 03:00:06 krispykreme.cs.umd.edu sshd-session[2651414]: error: PAM: System error for admin from 34.22.121.160 == munin (2 distinct, 4 total) == Aug 3 02:52:53 munin sudo[924533]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Aug 3 02:52:53 munin sudo[924533]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == newhonors2 (1 distinct, 24 total) == Aug 3 02:13:02 newhonors2 dhcpcd[660521]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (2 distinct, 7 total) == Aug 3 02:09:09 outbound00.cs.umd.edu python3[2338043]: ldapdb [x6] Aug 3 02:49:45 outbound00.cs.umd.edu krb5_child[2347405]: Client 'admin@UMD.EDU' not found in Kerberos database == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 3 02:13:06 outbound01.cs.umd.edu python3[370885]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Aug 3 02:16:32 sentry-docker00.cs.umd.edu systemd-udevd[772410]: link_config: could not get ethtool features for veth8033bb8 Aug 3 02:16:32 sentry-docker00.cs.umd.edu systemd-udevd[772410]: Could not set offload features of veth8033bb8: No such device Aug 3 02:16:32 sentry-docker00.cs.umd.edu systemd-udevd[772435]: Could not generate persistent MAC address for veth087465b: No such file or directory Aug 3 02:16:32 sentry-docker00.cs.umd.edu systemd-udevd[772436]: Could not generate persistent MAC address for veth56faf7d: No such file or directory Aug 3 02:16:33 sentry-docker00.cs.umd.edu systemd-udevd[772439]: Could not generate persistent MAC address for veth49d24fb: No such file or directory Aug 3 02:16:33 sentry-docker00.cs.umd.edu systemd-udevd[772440]: Could not generate persistent MAC address for veth8477eda: No such file or directory Aug 3 02:16:33 sentry-docker00.cs.umd.edu systemd-udevd[772463]: Could not generate persistent MAC address for veth7167671: No such file or directory Aug 3 02:16:33 sentry-docker00.cs.umd.edu systemd-udevd[772464]: Could not generate persistent MAC address for veth927cbb4: No such file or directory Aug 3 02:16:33 sentry-docker00.cs.umd.edu systemd-udevd[772482]: Could not generate persistent MAC address for veth3711874: No such file or directory Aug 3 02:16:33 sentry-docker00.cs.umd.edu systemd-udevd[772463]: Could not generate persistent MAC address for veth7b34f73: No such file or directory Aug 3 02:17:54 sentry-docker00.cs.umd.edu systemd-udevd[773231]: Could not generate persistent MAC address for veth08ad5e4: No such file or directory Aug 3 02:17:54 sentry-docker00.cs.umd.edu systemd-udevd[773232]: Could not generate persistent MAC address for vethab1f1f7: No such file or directory Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782171]: link_config: could not set ethtool features for veth7167671 Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782171]: Could not set offload features of veth7167671: Operation not permitted Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782193]: Could not generate persistent MAC address for veth6ba931f: No such file or directory Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782194]: Could not generate persistent MAC address for vethe6714b1: No such file or directory Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782197]: Could not generate persistent MAC address for vethd73de87: No such file or directory Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782198]: Could not generate persistent MAC address for vethcd9c6ba: No such file or directory Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782221]: Could not generate persistent MAC address for veth87e6598: No such file or directory Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782222]: Could not generate persistent MAC address for vethb98579a: No such file or directory Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782246]: Could not generate persistent MAC address for veth347b6f1: No such file or directory Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782248]: Could not generate persistent MAC address for veth813d17a: No such file or directory Aug 3 02:37:59 sentry-docker00.cs.umd.edu systemd-udevd[782928]: Could not generate persistent MAC address for vethda8feb5: No such file or directory Aug 3 02:37:59 sentry-docker00.cs.umd.edu systemd-udevd[782929]: Could not generate persistent MAC address for veth58b6d43: No such file or directory Aug 3 02:56:49 sentry-docker00.cs.umd.edu systemd-udevd[791842]: link_config: could not get ethtool features for veth347b6f1 Aug 3 02:56:49 sentry-docker00.cs.umd.edu systemd-udevd[791842]: Could not set offload features of veth347b6f1: No such device Aug 3 02:56:49 sentry-docker00.cs.umd.edu systemd-udevd[791865]: Could not generate persistent MAC address for vethd1b6719: No such file or directory Aug 3 02:56:49 sentry-docker00.cs.umd.edu systemd-udevd[791866]: Could not generate persistent MAC address for veth2132ee7: No such file or directory Aug 3 02:56:49 sentry-docker00.cs.umd.edu systemd-udevd[791869]: Could not generate persistent MAC address for vethe49b80f: No such file or directory Aug 3 02:56:49 sentry-docker00.cs.umd.edu systemd-udevd[791887]: Could not generate persistent MAC address for vethd9660ac: No such file or directory ... 6 more distinct messages not shown == strawberry (2 distinct, 8 total) == Aug 3 02: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 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (1 distinct, 8 total) == Aug 3 02:05:05 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] == submit26-b9-4 (1 distinct, 7 total) == Aug 3 02:05:05 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x7]