Command: /usr/local/sbin/syslog-digest.py Time : 0.0491s Status : exited 0 Output : Syslog digest — 2026-10-14 02:05 EDT Processed 1,655 lines, filtered 1,052 (63%). 603 unknown (178 distinct) from 21 host(s). == atif01.cs.umd.edu (1 distinct, 1 total) == Oct 14 01:18:13 atif01.cs.umd.edu sshd[14725]: fatal: ssh_packet_get_string: incomplete message [preauth] == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 14 01:26:59 b0b02.cs.umd.edu rustdesk[3623692]: cannot open display: == gle-omnibus00.cs.umd.edu (2 distinct, 2 total) == Oct 14 01:26:12 gle-omnibus00.cs.umd.edu systemctl[39079]: Warning: Stopping amanda_udp.service, but it can still be activated by: Oct 14 01:26:12 gle-omnibus00.cs.umd.edu systemctl[39079]: amanda_udp.socket == hazfs.cs.umd.edu (11 distinct, 66 total) == Oct 14 01:35:22 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Oct 14 01:35:22 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Oct 14 01:35:22 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Oct 14 01:35:22 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Oct 14 01:35:22 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Oct 14 01:35:22 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Oct 14 01:35:22 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Oct 14 01:35:22 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Oct 14 01:35:22 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Oct 14 01:35:22 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Oct 14 01:35:22 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Oct 14 01:54:48 idm00 named[1014]: client @0x7fcbc0065c38 10.73.240.42#60038: update '73.10.in-addr.arpa/IN' denied == idmh1 (13 distinct, 156 total) == Oct 14 01:06:48 idmh1 check-named-alive[541016]: zone cs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 14 01:06:49 idmh1 check-named-alive[541077]: zone csdlabs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 01:06:49 idmh1 check-named-alive[541138]: zone csic.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 01:06:49 idmh1 check-named-alive[541199]: zone 72.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 01:06:49 idmh1 check-named-alive[541260]: zone 73.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 01:06:49 idmh1 check-named-alive[541321]: zone 88.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 01:06:50 idmh1 check-named-alive[541382]: zone 125.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 01:06:50 idmh1 check-named-alive[541443]: zone 126.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 01:06:50 idmh1 check-named-alive[541504]: zone 127.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 14 01:06:50 idmh1 check-named-alive[541565]: zone 128.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 14 01:06:50 idmh1 check-named-alive[541626]: zone 129.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 14 01:06:51 idmh1 check-named-alive[541687]: zone 130.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 01:06:51 idmh1 check-named-alive[541748]: zone 131.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] == idmp0 (1 distinct, 1 total) == Oct 14 01:39:45 idmp0 named[1180]: client @0x7fe058007d58 10.73.240.43#57701: update '73.10.in-addr.arpa/IN' denied == idmv0 (13 distinct, 156 total) == Oct 14 01:07:10 idmv0 check-named-alive[595021]: zone cs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 14 01:07:10 idmv0 check-named-alive[595082]: zone csdlabs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 01:07:10 idmv0 check-named-alive[595143]: zone csic.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 01:07:11 idmv0 check-named-alive[595204]: zone 72.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 01:07:11 idmv0 check-named-alive[595265]: zone 73.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 01:07:11 idmv0 check-named-alive[595326]: zone 88.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 01:07:11 idmv0 check-named-alive[595387]: zone 125.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 01:07:11 idmv0 check-named-alive[595448]: zone 126.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 01:07:11 idmv0 check-named-alive[595509]: zone 127.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 14 01:07:12 idmv0 check-named-alive[595570]: zone 128.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 14 01:07:12 idmv0 check-named-alive[595631]: zone 129.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 14 01:07:12 idmv0 check-named-alive[595692]: zone 130.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 01:07:12 idmv0 check-named-alive[595753]: zone 131.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] == itmon02 (1 distinct, 3 total) == Oct 14 01:17:58 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x3] == munin (2 distinct, 10 total) == Oct 14 01:13:34 munin sudo[489931]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x5] Oct 14 01:13:34 munin sudo[489931]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x5] == netman.cs.umd.edu (3 distinct, 6 total) == Oct 14 01:40:05 netman.cs.umd.edu krb5_child[2979076]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Oct 14 01:40:09 netman.cs.umd.edu sshd[2979073]: error: PAM: Authentication failure for admin from 34.140.234.253 Oct 14 01:40:15 netman.cs.umd.edu sshd[2979152]: error: Protocol major versions differ: 2 vs. 1 == newhonors2 (1 distinct, 24 total) == Oct 14 01:13:03 newhonors2 dhcpcd[3993820]: dhcpcd is not running [x24] == ntop00 (93 distinct, 93 total) == Oct 14 01:05:13 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8482, QN: 4627/4627, ET: 12) *** Oct 14 01:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8483) *** Oct 14 01:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8483, QN: 4062/4062, ET: 0) *** Oct 14 01:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8483) *** Oct 14 01:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8483, QN: 69/69, ET: 0) *** Oct 14 01:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8484) *** Oct 14 01:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8484) *** Oct 14 01:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8484, QN: 64/64, ET: 0) *** Oct 14 01:10:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8484, QN: 3952/3952, ET: 10) *** Oct 14 01:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8485) *** Oct 14 01:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8485, QN: 3976/3976, ET: 0) *** Oct 14 01:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8485) *** Oct 14 01:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8485, QN: 48/48, ET: 0) *** Oct 14 01:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8486) *** Oct 14 01:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8486) *** Oct 14 01:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8486, QN: 51/51, ET: 0) *** Oct 14 01:15:10 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8486, QN: 3880/3880, ET: 9) *** Oct 14 01:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8487) *** Oct 14 01:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8487, QN: 3623/3623, ET: 0) *** Oct 14 01:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8487) *** Oct 14 01:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8487, QN: 54/54, ET: 0) *** Oct 14 01:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8488) *** Oct 14 01:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8488) *** Oct 14 01:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8488, QN: 61/61, ET: 0) *** Oct 14 01:20:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8488, QN: 3698/3698, ET: 10) *** Oct 14 01:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8489) *** Oct 14 01:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8489, QN: 3838/3838, ET: 0) *** Oct 14 01:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8489) *** Oct 14 01:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8489, QN: 68/68, ET: 0) *** Oct 14 01:25:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8490) *** ... 63 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 14 01:09:09 outbound00.cs.umd.edu python3[2460890]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 14 01:13:05 outbound01.cs.umd.edu python3[3950031]: ldapdb [x6] == strawberry (7 distinct, 38 total) == Oct 14 01:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 14 01:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 14 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 14 01:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 14 01:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 14 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 14 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-3 (1 distinct, 3 total) == Sep 16 13:10:06 submit26-b9-3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f1 (2 distinct, 4 total) == Oct 14 01:10:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Oct 14 01:38:13 submit26-b9-f1 systemd-coredump[2691587]: Process 2691584 (secret02) of user 1001 dumped core.#012#012Stack trace of thread 2691584:#012#0 0x00007f0f4ae8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f0f4ae3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f0f4ae29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f0f4ae2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f0f4af1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f0f4af1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401261 main (secret02 + 0x1261)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f2 (1 distinct, 1 total) == Oct 14 01:18:10 submit26-b9-f2 systemd-coredump[1803934]: Process 1803931 (secret02) of user 1001 dumped core. == submit26-b9-f3 (11 distinct, 14 total) == Oct 14 01:06:51 submit26-b9-f3 setroubleshoot[3293293]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b Oct 14 01:06:51 submit26-b9-f3 setroubleshoot[3293293]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859 Oct 14 01:06:51 submit26-b9-f3 setroubleshoot[3293293]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033 [x2] Oct 14 01:06:51 submit26-b9-f3 setroubleshoot[3293293]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.4RvIvI/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f [x2] Oct 14 01:06:51 submit26-b9-f3 setroubleshoot[3293293]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba [x2] Oct 14 01:06:51 submit26-b9-f3 setroubleshoot[3293293]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.4RvIvI. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 14 01:06:51 submit26-b9-f3 setroubleshoot[3293293]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407 Oct 14 01:06:51 submit26-b9-f3 setroubleshoot[3293293]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65 Oct 14 01:06:51 submit26-b9-f3 setroubleshoot[3293293]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68 Oct 14 01:08:09 submit26-b9-f3 systemd-coredump[3293482]: Process 3293479 (secret02) of user 1001 dumped core. Oct 14 01:18:09 submit26-b9-f3 systemd-coredump[3294068]: Process 3294065 (secret02) of user 1001 dumped core. == submit26-b9-f4 (11 distinct, 11 total) == Oct 14 01:24:55 submit26-b9-f4 setroubleshoot[1134664]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb Oct 14 01:24:55 submit26-b9-f4 setroubleshoot[1134664]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4 Oct 14 01:24:55 submit26-b9-f4 setroubleshoot[1134664]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d Oct 14 01:24:55 submit26-b9-f4 setroubleshoot[1134664]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.9ZBPEs/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 14 01:24:56 submit26-b9-f4 setroubleshoot[1134664]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e Oct 14 01:24:56 submit26-b9-f4 setroubleshoot[1134664]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.9ZBPEs. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 14 01:24:56 submit26-b9-f4 setroubleshoot[1134664]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d Oct 14 01:24:56 submit26-b9-f4 setroubleshoot[1134664]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74 Oct 14 01:24:56 submit26-b9-f4 setroubleshoot[1134664]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915 Oct 14 01:28:13 submit26-b9-f4 systemd-coredump[1134908]: Process 1134905 (secret02) of user 1001 dumped core. Oct 14 01:38:16 submit26-b9-f4 systemd-coredump[1135664]: Process 1135662 (secret02) of user 1001 dumped core.