Command: /usr/local/sbin/syslog-digest.py Time : 0.1451s Status : exited 0 Output : Syslog digest — 2026-10-09 02:05 EDT Processed 5,227 lines, filtered 3,051 (58%). 2,176 unknown (158 distinct) from 18 host(s). == abuse (1 distinct, 346 total) == Oct 9 01:05:25 abuse rsyslogd[1033]: 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 (1 distinct, 1 total) == Oct 9 01:19:33 b0b02.cs.umd.edu rustdesk[1793913]: cannot open display: == cheezit.cs.umd.edu (1 distinct, 1 total) == Oct 9 01:54:30 cheezit.cs.umd.edu sshd-session[864139]: pam_access(sshd:auth): access denied for user `lin' from `74.96.151.253' == hazfs.cs.umd.edu (11 distinct, 66 total) == Oct 9 01:28:16 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Oct 9 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Oct 9 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Oct 9 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Oct 9 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Oct 9 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Oct 9 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Oct 9 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Oct 9 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Oct 9 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Oct 9 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Oct 9 01:54:42 idm00 named[4166701]: client @0x7f11a0064678 10.73.240.42#61088: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 9 01:39:22 idmp0 named[1598691]: client @0x7f2d4c02e298 10.73.240.43#64398: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Oct 9 01:17:57 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x4] == krispykreme.cs.umd.edu (3 distinct, 8 total) == Oct 9 01:19:41 krispykreme.cs.umd.edu sshd[705415]: error: beginning MaxStartups throttling Oct 9 01:19:43 krispykreme.cs.umd.edu sshd-session[3686574]: error: Protocol major versions differ: 2 vs. 1 [x2] Oct 9 01:21:54 krispykreme.cs.umd.edu sshd-session[3687329]: error: send_error: write: Connection reset by peer [x5] == mcstic (2 distinct, 5 total) == Oct 9 01:23:27 mcstic krb5_child[1729493]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Oct 9 01:23:31 mcstic sshd[1729488]: error: PAM: Authentication failure for admin from 35.241.197.164 == newhonors2 (1 distinct, 24 total) == Oct 9 01:13:02 newhonors2 dhcpcd[3759560]: dhcpcd is not running [x24] == ntop00 (94 distinct, 94 total) == Oct 9 01:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5602, QN: 67/67, ET: 0) *** Oct 9 01:05:09 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5602, QN: 4481/4481, ET: 8) *** Oct 9 01:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 5603) *** Oct 9 01:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 5603, QN: 5053/5053, ET: 0) *** Oct 9 01:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 5603) *** Oct 9 01:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 5603, QN: 40/40, ET: 0) *** Oct 9 01:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5604) *** Oct 9 01:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5604) *** Oct 9 01:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5604, QN: 43/43, ET: 0) *** Oct 9 01:10:12 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5604, QN: 6139/6139, ET: 11) *** Oct 9 01:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 5605) *** Oct 9 01:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 5605, QN: 6857/6857, ET: 0) *** Oct 9 01:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 5605) *** Oct 9 01:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 5605, QN: 50/50, ET: 0) *** Oct 9 01:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5606) *** Oct 9 01:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5606) *** Oct 9 01:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5606, QN: 67/67, ET: 0) *** Oct 9 01:15:13 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5606, QN: 6743/6743, ET: 12) *** Oct 9 01:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 5607) *** Oct 9 01:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 5607, QN: 6900/6900, ET: 0) *** Oct 9 01:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 5607) *** Oct 9 01:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 5607, QN: 55/55, ET: 0) *** Oct 9 01:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5608) *** Oct 9 01:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5608) *** Oct 9 01:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5608, QN: 54/54, ET: 0) *** Oct 9 01:20:14 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5608, QN: 6921/6921, ET: 13) *** Oct 9 01:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 5609) *** Oct 9 01:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 5609, QN: 7364/7364, ET: 0) *** Oct 9 01:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 5609) *** Oct 9 01:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 5609, QN: 55/55, ET: 0) *** ... 64 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 7 total) == Oct 9 01:09:08 outbound00.cs.umd.edu python3[791714]: ldapdb [x6] Oct 9 01:28:11 outbound00.cs.umd.edu krb5_child[796146]: Client 'admin@UMD.EDU' not found in Kerberos database == outbound01.cs.umd.edu (3 distinct, 8 total) == Oct 9 01:05:18 outbound01.cs.umd.edu krb5_child[2257753]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 9 01:05:37 outbound01.cs.umd.edu sshd-session[2257832]: error: Protocol major versions differ: 2 vs. 1 Oct 9 01:13:06 outbound01.cs.umd.edu python3[2259138]: ldapdb [x6] == strawberry (7 distinct, 38 total) == Oct 9 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 9 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 9 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 9 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 9 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 9 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 9 01:34:43 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit10-cln25 (5 distinct, 1539 total) == Oct 9 01:05:22 submit10-cln25 rsyslogd: file '/var/log/messages': open error: Input/output error [v8.24.0-57.el7_9.3 try http://www.rsyslog.com/e/2433 ] [x1200] Oct 9 01:05:22 submit10-cln25 rsyslogd: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.24.0-57.el7_9.3 try http://www.rsyslog.com/e/2013 ] [x334] Oct 9 01:25:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_check: Input/output error [x2] Oct 9 01:28:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmie_check: Input/output error [x2] Oct 9 01:30:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_daily: Input/output error == submit26-b9-3 (2 distinct, 3 total) == Sep 11 03:43:22 submit26-b9-3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Sep 11 03:43:24 submit26-b9-3 systemd-coredump[2598931]: Process 2598928 (secret02) of user 1001 dumped core.#012#012Stack trace of thread 2598928:#012#0 0x00007fc71748d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fc71743fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fc717429873 abort (libc.so.6 + 0x29873)#012#3 0x00007fc71742a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fc71751d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fc71751e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401231 main (secret02 + 0x1231)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f3 (12 distinct, 16 total) == Oct 9 01:06:50 submit26-b9-f3 setroubleshoot[2361905]: 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 [x2] Oct 9 01:06:50 submit26-b9-f3 setroubleshoot[2361905]: 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 [x2] Oct 9 01:06:50 submit26-b9-f3 setroubleshoot[2361905]: 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 Oct 9 01:06:50 submit26-b9-f3 setroubleshoot[2361905]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.c4BWKl/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 9 01:06:50 submit26-b9-f3 setroubleshoot[2361905]: 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 Oct 9 01:06:50 submit26-b9-f3 setroubleshoot[2361905]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.c4BWKl. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 9 01:06:50 submit26-b9-f3 setroubleshoot[2361905]: 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 [x2] Oct 9 01:06:50 submit26-b9-f3 setroubleshoot[2361905]: 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 9 01:06:50 submit26-b9-f3 setroubleshoot[2361905]: 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 [x2] Oct 9 01:06:50 submit26-b9-f3 setroubleshoot[2361905]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.YAhEjH. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 9 01:32:13 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL Oct 9 01:32:15 submit26-b9-f3 systemd-coredump[2364441]: Process 2364438 (secret02) of user 1001 dumped core.#012#012Stack trace of thread 2364438:#012#0 0x00007f43e408d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f43e403fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f43e4029873 abort (libc.so.6 + 0x29873)#012#3 0x00007f43e402a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f43e411d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f43e411e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401231 main (secret02 + 0x1231)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f4 (10 distinct, 14 total) == Oct 9 01:24:53 submit26-b9-f4 setroubleshoot[491892]: 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 [x2] Oct 9 01:24:53 submit26-b9-f4 setroubleshoot[491892]: 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 [x2] Oct 9 01:24:53 submit26-b9-f4 setroubleshoot[491892]: 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 9 01:24:53 submit26-b9-f4 setroubleshoot[491892]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.k9VKTB/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 9 01:24:53 submit26-b9-f4 setroubleshoot[491892]: 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 9 01:24:53 submit26-b9-f4 setroubleshoot[491892]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.k9VKTB. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 9 01:24:53 submit26-b9-f4 setroubleshoot[491892]: 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 [x2] Oct 9 01:24:53 submit26-b9-f4 setroubleshoot[491892]: 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 9 01:24:53 submit26-b9-f4 setroubleshoot[491892]: 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 [x2] Oct 9 01:24:53 submit26-b9-f4 setroubleshoot[491892]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.SeFIxG. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
participants (1)
-
cron/syslog01.cs.umd.edu