Command: /usr/local/sbin/syslog-digest.py Time : 0.1397s Status : exited 0 Output : Syslog digest — 2026-10-10 10:05 EDT Processed 5,691 lines, filtered 3,608 (63%). 2,083 unknown (135 distinct) from 14 host(s). == abuse (1 distinct, 346 total) == Oct 10 09: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 10 09:21:22 b0b02.cs.umd.edu rustdesk[2281826]: cannot open display: == idm00 (1 distinct, 1 total) == Oct 10 09:54:44 idm00 named[4166701]: client @0x7f11a4071638 10.73.240.42#62803: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 10 09:39:22 idmp0 named[1598691]: client @0x7f2d2803dc38 10.73.240.43#62436: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 1 total) == Oct 10 09:58:03 itmon02 sshd[805675]: error: beginning MaxStartups throttling == krispykreme.cs.umd.edu (1 distinct, 1 total) == Oct 10 09:09:58 krispykreme.cs.umd.edu sshd-session[11702]: error: send_error: write: Connection reset by peer == newhonors2 (1 distinct, 24 total) == Oct 10 09:13:03 newhonors2 dhcpcd[3827672]: dhcpcd is not running [x24] == ntop00 (93 distinct, 93 total) == Oct 10 09:05:17 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6370, QN: 8836/8836, ET: 16) *** Oct 10 09:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6371) *** Oct 10 09:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6371, QN: 8561/8561, ET: 0) *** Oct 10 09:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6371) *** Oct 10 09:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6371, QN: 74/74, ET: 0) *** Oct 10 09:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6372) *** Oct 10 09:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6372) *** Oct 10 09:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6372, QN: 78/78, ET: 0) *** Oct 10 09:10:17 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6372, QN: 8667/8667, ET: 16) *** Oct 10 09:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6373) *** Oct 10 09:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6373, QN: 9345/9345, ET: 0) *** Oct 10 09:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6373) *** Oct 10 09:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6373, QN: 71/71, ET: 0) *** Oct 10 09:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6374) *** Oct 10 09:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6374) *** Oct 10 09:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6374, QN: 70/70, ET: 0) *** Oct 10 09:15:19 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6374, QN: 9146/9146, ET: 18) *** Oct 10 09:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6375) *** Oct 10 09:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6375, QN: 8637/8637, ET: 0) *** Oct 10 09:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6375) *** Oct 10 09:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6375, QN: 60/60, ET: 0) *** Oct 10 09:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6376) *** Oct 10 09:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6376) *** Oct 10 09:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6376, QN: 48/48, ET: 0) *** Oct 10 09:20:17 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6376, QN: 8821/8821, ET: 16) *** Oct 10 09:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6377) *** Oct 10 09:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6377, QN: 8901/8901, ET: 0) *** Oct 10 09:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6377) *** Oct 10 09:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6377, QN: 60/60, ET: 0) *** Oct 10 09:25:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6378) *** ... 63 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 10 09:09:09 outbound00.cs.umd.edu python3[1236612]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 10 total) == Oct 10 09:06:06 outbound01.cs.umd.edu krb5_child[2709057]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Oct 10 09:13:06 outbound01.cs.umd.edu python3[2710383]: ldapdb [x6] == strawberry (7 distinct, 38 total) == Oct 10 09:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 10 09:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 10 09:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 10 09:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 10 09:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 10 09:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 10 09:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit10-cln25 (5 distinct, 1539 total) == Oct 10 09: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 10 09: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 10 09:25:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_check: Input/output error [x2] Oct 10 09:28:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmie_check: Input/output error [x2] Oct 10 09:30:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_daily: Input/output error == submit26-b9-f3 (9 distinct, 9 total) == Oct 10 09:06:50 submit26-b9-f3 setroubleshoot[2756414]: 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 10 09:06:50 submit26-b9-f3 setroubleshoot[2756414]: 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 10 09:06:50 submit26-b9-f3 setroubleshoot[2756414]: 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 10 09:06:50 submit26-b9-f3 setroubleshoot[2756414]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.GKoFdB/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 10 09:06:50 submit26-b9-f3 setroubleshoot[2756414]: 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 10 09:06:50 submit26-b9-f3 setroubleshoot[2756414]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GKoFdB. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 10 09:06:50 submit26-b9-f3 setroubleshoot[2756414]: 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 10 09:06:50 submit26-b9-f3 setroubleshoot[2756414]: 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 10 09:06:50 submit26-b9-f3 setroubleshoot[2756414]: 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 == submit26-b9-f4 (11 distinct, 13 total) == Oct 10 09:20:09 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL Oct 10 09:24:55 submit26-b9-f4 setroubleshoot[750679]: 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 10 09:24:55 submit26-b9-f4 setroubleshoot[750679]: 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 10 09:24:55 submit26-b9-f4 setroubleshoot[750679]: 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 10 09:24:55 submit26-b9-f4 setroubleshoot[750679]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.XrTF4M/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 10 09:24:55 submit26-b9-f4 setroubleshoot[750679]: 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 [x2] Oct 10 09:24:55 submit26-b9-f4 setroubleshoot[750679]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.XrTF4M. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 10 09:24:55 submit26-b9-f4 setroubleshoot[750679]: 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 10 09:24:55 submit26-b9-f4 setroubleshoot[750679]: 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 [x2] Oct 10 09:24:55 submit26-b9-f4 setroubleshoot[750679]: 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 10 09:24:55 submit26-b9-f4 setroubleshoot[750679]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Yr28UU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0