Command: /usr/local/sbin/syslog-digest.py Time : 0.9912s Status : exited 0 Output : Syslog digest — 2026-08-07 03:05 EDT Processed 7,938 lines, filtered 5,218 (65%). 2,720 unknown (81 distinct) from 22 host(s). == abuse (3 distinct, 2255 total) == Aug 7 02:05:03 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 ] [x879] Aug 7 02:05:03 abuse systemd[1]: Failed to load environment files: Input/output error [x688] Aug 7 02:05:03 abuse systemd[1]: choria-server.service failed to run 'start' task: Input/output error [x688] == b0b02.cs.umd.edu (1 distinct, 1 total) == Aug 7 02:48:38 b0b02.cs.umd.edu rustdesk[3800680]: cannot open display: == biggulp.cs.umd.edu (5 distinct, 5 total) == Aug 7 03:02:51 biggulp.cs.umd.edu sshd-session[3650254]: pam_access(sshd:auth): access denied for user `admin' from `171.243.150.99' Aug 7 03:02:51 biggulp.cs.umd.edu krb5_child[3650271]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 7 03:02:51 biggulp.cs.umd.edu sshd-session[3650236]: error: PAM: System error for admin from 171.243.150.99 Aug 7 03:04:24 biggulp.cs.umd.edu sshd-session[3650401]: pam_access(sshd:auth): access denied for user `root' from `116.99.168.223' Aug 7 03:04:26 biggulp.cs.umd.edu sshd-session[3650396]: error: PAM: Authentication failure for root from 116.99.168.223 == cheezit.cs.umd.edu (3 distinct, 3 total) == Aug 7 03:04:08 cheezit.cs.umd.edu sshd-session[1998045]: pam_access(sshd:auth): access denied for user `admin' from `171.243.150.99' Aug 7 03:04:18 cheezit.cs.umd.edu krb5_child[1998064]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 7 03:04:18 cheezit.cs.umd.edu sshd-session[1998043]: error: PAM: System error for admin from 171.243.150.99 == contest (1 distinct, 34 total) == Aug 7 02:05:19 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, 272 total) == Aug 7 02:04:51 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x244] Aug 7 02:08:12 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x28] == dojo (1 distinct, 1 total) == Aug 7 03:03:58 dojo sshd[1319538]: error: Protocol major versions differ: 2 vs. 1 == idm00 (1 distinct, 1 total) == Aug 7 02:51:19 idm00 named[1455]: client @0x7f33046c1f38 10.73.240.42#54239: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 7 02:36:02 idmp0 named[5198]: client @0x7f98e88d1c18 10.73.240.43#63040: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (1 distinct, 1 total) == Aug 7 02:57:17 inbound01.cs.umd.edu krb5_child[1794053]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 39 total) == Aug 7 02:08:08 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x39] == krispykreme.cs.umd.edu (3 distinct, 3 total) == Aug 7 03:04:43 krispykreme.cs.umd.edu sshd-session[151482]: pam_access(sshd:auth): access denied for user `admin' from `116.99.168.223' Aug 7 03:04:43 krispykreme.cs.umd.edu krb5_child[151485]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 7 03:04:43 krispykreme.cs.umd.edu sshd-session[151480]: error: PAM: System error for admin from 116.99.168.223 == munin (2 distinct, 4 total) == Aug 7 02:37:50 munin sudo[2964870]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Aug 7 02:37:50 munin sudo[2964870]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == netman.cs.umd.edu (1 distinct, 2 total) == Aug 7 03:04:47 netman.cs.umd.edu krb5_child[1890914]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == networkvm01.cs.umd.edu (10 distinct, 12 total) == Aug 7 02:15:54 networkvm01.cs.umd.edu setroubleshoot[1919724]: SELinux is preventing /usr/bin/gpg from write access on the directory /(null). For complete SELinux messages run: sealert -l 8ead1354-ae8a-4a17-bb3f-146ebf6c892c Aug 7 02:15:54 networkvm01.cs.umd.edu setroubleshoot[1919724]: SELinux is preventing /usr/bin/gpg from add_name access on the directory /(null). For complete SELinux messages run: sealert -l f9b51e91-5dbc-455f-88c2-f0746a2f0f4c Aug 7 02:15:54 networkvm01.cs.umd.edu setroubleshoot[1919724]: SELinux is preventing /usr/bin/gpg from create access on the file /(null). For complete SELinux messages run: sealert -l af0a60e6-c449-4bdd-bfb8-c69b58472884 [x2] Aug 7 02:15:54 networkvm01.cs.umd.edu setroubleshoot[1919724]: SELinux is preventing /usr/bin/gpg from link access on the file /(null). For complete SELinux messages run: sealert -l 3df452f6-4d9e-4e38-946b-ea8e1edd356c [x2] Aug 7 02:15:54 networkvm01.cs.umd.edu setroubleshoot[1919724]: SELinux is preventing /usr/bin/gpg from remove_name access on the directory .#lk0x0000561ea9a7aed0.networkvm01.cs.umd.edu.1919723x. For complete SELinux messages run: sealert -l fcac71c9-c7c0-45a9-9dc2-a8dcbeccfc75 Aug 7 02:15:54 networkvm01.cs.umd.edu setroubleshoot[1919724]: SELinux is preventing /usr/bin/gpg from unlink access on the file .#lk0x0000561ea9a7aed0.networkvm01.cs.umd.edu.1919723x. For complete SELinux messages run: sealert -l a672ebb7-fa69-419c-b1f0-fb386b8b48a6 Aug 7 02:15:54 networkvm01.cs.umd.edu setroubleshoot[1919724]: SELinux is preventing /usr/bin/gpg from write access on the directory /(null). For complete SELinux messages run: sealert -l fec9104e-d27a-4fd4-9872-6b17088c2951 Aug 7 02:15:55 networkvm01.cs.umd.edu setroubleshoot[1919724]: SELinux is preventing /usr/bin/gpg from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 26718b2a-493d-457d-818c-244bd8d4ec9d Aug 7 02:15:55 networkvm01.cs.umd.edu setroubleshoot[1919724]: SELinux is preventing /usr/bin/gpg from remove_name access on the directory .#lk0x000056399344bee0.networkvm01.cs.umd.edu.1919741x. For complete SELinux messages run: sealert -l 80e6efe4-93f3-4219-8132-b2b52db1f517 Aug 7 02:15:55 networkvm01.cs.umd.edu setroubleshoot[1919724]: SELinux is preventing /usr/bin/gpg from unlink access on the file .#lk0x000056399344bee0.networkvm01.cs.umd.edu.1919741x. For complete SELinux messages run: sealert -l a672ebb7-fa69-419c-b1f0-fb386b8b48a6 == newhonors2 (1 distinct, 24 total) == Aug 7 02:13:03 newhonors2 dhcpcd[851576]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (2 distinct, 7 total) == Aug 7 02:09:09 outbound00.cs.umd.edu python3[3716458]: ldapdb [x6] Aug 7 03:03:36 outbound00.cs.umd.edu krb5_child[3729357]: Client 'admin@UMD.EDU' not found in Kerberos database == outbound01.cs.umd.edu (2 distinct, 8 total) == Aug 7 02:13:07 outbound01.cs.umd.edu python3[1752940]: ldapdb [x6] Aug 7 02:26:33 outbound01.cs.umd.edu krb5_child[1756474]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Aug 7 02:16:12 sentry-docker00.cs.umd.edu systemd-udevd[3494572]: link_config: could not get ethtool features for vethc0fa054 Aug 7 02:16:12 sentry-docker00.cs.umd.edu systemd-udevd[3494572]: Could not set offload features of vethc0fa054: No such device Aug 7 02:16:12 sentry-docker00.cs.umd.edu systemd-udevd[3494635]: Could not generate persistent MAC address for veth3a2acc6: No such file or directory Aug 7 02:16:12 sentry-docker00.cs.umd.edu systemd-udevd[3494636]: Could not generate persistent MAC address for veth41dcd10: No such file or directory Aug 7 02:16:12 sentry-docker00.cs.umd.edu systemd-udevd[3494639]: Could not generate persistent MAC address for veth4adccae: No such file or directory Aug 7 02:16:12 sentry-docker00.cs.umd.edu systemd-udevd[3494636]: Could not generate persistent MAC address for vethb106aa5: No such file or directory Aug 7 02:16:12 sentry-docker00.cs.umd.edu systemd-udevd[3494635]: Could not generate persistent MAC address for vethfa4e584: No such file or directory Aug 7 02:16:12 sentry-docker00.cs.umd.edu systemd-udevd[3494650]: Could not generate persistent MAC address for vethad1f595: No such file or directory Aug 7 02:16:12 sentry-docker00.cs.umd.edu systemd-udevd[3494636]: Could not generate persistent MAC address for vethe465961: No such file or directory Aug 7 02:16:12 sentry-docker00.cs.umd.edu systemd-udevd[3494635]: Could not generate persistent MAC address for veth409b40e: No such file or directory Aug 7 02:16:12 sentry-docker00.cs.umd.edu systemd-udevd[3494636]: Could not generate persistent MAC address for veth4af3a53: No such file or directory Aug 7 02:16:12 sentry-docker00.cs.umd.edu systemd-udevd[3494635]: Could not generate persistent MAC address for vethbd34ce2: No such file or directory Aug 7 02:36:20 sentry-docker00.cs.umd.edu systemd-udevd[3504355]: link_config: could not get ethtool features for vethb106aa5 Aug 7 02:36:20 sentry-docker00.cs.umd.edu systemd-udevd[3504355]: Could not set offload features of vethb106aa5: No such device Aug 7 02:36:20 sentry-docker00.cs.umd.edu systemd-udevd[3504423]: Could not generate persistent MAC address for vethc5ee798: No such file or directory Aug 7 02:36:20 sentry-docker00.cs.umd.edu systemd-udevd[3504424]: Could not generate persistent MAC address for veth279ef25: No such file or directory Aug 7 02:36:20 sentry-docker00.cs.umd.edu systemd-udevd[3504427]: Could not generate persistent MAC address for veth6fc5db9: No such file or directory Aug 7 02:36:20 sentry-docker00.cs.umd.edu systemd-udevd[3504435]: Could not generate persistent MAC address for veth6664036: No such file or directory Aug 7 02:36:20 sentry-docker00.cs.umd.edu systemd-udevd[3504438]: Could not generate persistent MAC address for veth5db0b61: No such file or directory Aug 7 02:36:20 sentry-docker00.cs.umd.edu systemd-udevd[3504441]: Could not generate persistent MAC address for vetha53bb25: No such file or directory Aug 7 02:36:20 sentry-docker00.cs.umd.edu systemd-udevd[3504466]: Could not generate persistent MAC address for vethc75d38e: No such file or directory Aug 7 02:36:20 sentry-docker00.cs.umd.edu systemd-udevd[3504470]: Could not generate persistent MAC address for veth83af6fe: No such file or directory Aug 7 02:36:21 sentry-docker00.cs.umd.edu systemd-udevd[3504498]: Could not generate persistent MAC address for veth6f48636: No such file or directory Aug 7 02:36:21 sentry-docker00.cs.umd.edu systemd-udevd[3504479]: Could not generate persistent MAC address for vethba3315c: No such file or directory Aug 7 02:56:29 sentry-docker00.cs.umd.edu systemd-udevd[3513884]: link_config: could not get ethtool features for veth6f48636 Aug 7 02:56:29 sentry-docker00.cs.umd.edu systemd-udevd[3513884]: Could not set offload features of veth6f48636: No such device Aug 7 02:56:29 sentry-docker00.cs.umd.edu systemd-udevd[3513908]: Could not generate persistent MAC address for veth5fa74cc: No such file or directory Aug 7 02:56:29 sentry-docker00.cs.umd.edu systemd-udevd[3513909]: Could not generate persistent MAC address for veth226a84c: No such file or directory Aug 7 02:56:29 sentry-docker00.cs.umd.edu systemd-udevd[3513912]: Could not generate persistent MAC address for veth7db82f4: No such file or directory Aug 7 02:56:29 sentry-docker00.cs.umd.edu systemd-udevd[3513918]: Could not generate persistent MAC address for vethdff0a5b: No such file or directory ... 6 more distinct messages not shown == strawberry (2 distinct, 8 total) == Aug 7 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 7 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-4 (1 distinct, 2 total) == Aug 7 02:40:01 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == teaching-awards (1 distinct, 1 total) == Aug 7 03:02:34 teaching-awards krb5_child[2048817]: Client 'admin@UMD.EDU' not found in Kerberos database