Command: /usr/local/sbin/syslog-digest.py Time : 0.1428s Status : exited 0 Output : Syslog digest — 2026-10-09 14:05 EDT Processed 5,391 lines, filtered 3,186 (59%). 2,205 unknown (174 distinct) from 22 host(s). == abuse (1 distinct, 347 total) == Oct 9 13: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 ] [x347] == atif01.cs.umd.edu (1 distinct, 1 total) == Oct 9 13:16:55 atif01.cs.umd.edu kernel: net_ratelimit: 13 callbacks suppressed == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 9 13:20:09 b0b02.cs.umd.edu rustdesk[1976753]: cannot open display: == frozone (9 distinct, 10 total) == Oct 9 14:00:29 frozone goa-identity-se[251959]: GoaKerberosIdentityManager: Using polling for change notification for credential cache type 'KCM' Oct 9 14:00:30 frozone vmware-user.desktop[252140]: vmware-user: could not open /proc/fs/vmblock/dev Oct 9 14:00:30 frozone remmina-applet.desktop[252135]: error: app/org.remmina.Remmina/x86_64/master not installed Oct 9 14:00:30 frozone gsd-usb-protect[252134]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable Oct 9 14:00:34 frozone gnome-software[252109]: Only 0 apps for recent list, hiding [x2] Oct 9 14:00:42 frozone packagekitd[252060]: Failed to get cache filename for vault Oct 9 14:00:54 frozone evolution-calen[252030]: failed to commit changes to dconf: Timeout was reached Oct 9 14:00:54 frozone evolution-addre[252043]: failed to commit changes to dconf: Timeout was reached Oct 9 14:01:07 frozone packagekitd[252060]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == grosh (1 distinct, 1 total) == Oct 9 13:29:35 grosh setroubleshoot[2436004]: failed to retrieve rpm info for path '/etc/resolv.conf': == hazfs.cs.umd.edu (11 distinct, 66 total) == Oct 9 13:30:54 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Oct 9 13:30:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Oct 9 13:30:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Oct 9 13:30:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Oct 9 13:30:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Oct 9 13:30:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Oct 9 13:30:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Oct 9 13:30:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Oct 9 13:30:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Oct 9 13:30:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Oct 9 13:30:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Oct 9 13:54:44 idm00 named[4166701]: client @0x7f11980511b8 10.73.240.42#54968: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 9 13:39:21 idmp0 named[1598691]: client @0x7f2d3001d0e8 10.73.240.43#64775: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Oct 9 13:48:32 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 12 total) == Oct 9 13:28:06 munin sudo[2346585]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Oct 9 13:28:06 munin sudo[2346585]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == newhonors2 (1 distinct, 24 total) == Oct 9 13:13:03 newhonors2 dhcpcd[3789666]: dhcpcd is not running [x24] == ntop00 (100 distinct, 100 total) == Oct 9 13:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5890, QN: 81/81, ET: 0) *** Oct 9 13:05:45 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5890, QN: 11944/11944, ET: 44) *** Oct 9 13:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 5891) *** Oct 9 13:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 5891, QN: 13036/13036, ET: 0) *** Oct 9 13:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 5891) *** Oct 9 13:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 5891, QN: 90/90, ET: 0) *** Oct 9 13:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5892) *** Oct 9 13:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5892) *** Oct 9 13:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5892, QN: 88/88, ET: 0) *** Oct 9 13:10:52 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5892, QN: 13184/13184, ET: 51) *** Oct 9 13:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 5893) *** Oct 9 13:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 5893, QN: 12394/12394, ET: 0) *** Oct 9 13:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 5893) *** Oct 9 13:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 5893, QN: 100/100, ET: 0) *** Oct 9 13:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5894) *** Oct 9 13:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5894) *** Oct 9 13:15:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5894, QN: 84/84, ET: 1) *** Oct 9 13:15:47 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5894, QN: 11842/11842, ET: 46) *** Oct 9 13:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 5895) *** Oct 9 13:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 5895, QN: 13606/13606, ET: 0) *** Oct 9 13:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 5895) *** Oct 9 13:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 5895, QN: 74/74, ET: 0) *** Oct 9 13:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5896) *** Oct 9 13:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5896) *** Oct 9 13:20:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5896, QN: 81/81, ET: 1) *** Oct 9 13:20:44 ntop00 pmacct-mariadb[775683]: 2026-10-09 17:20:44 6775 [Warning] Aborted connection 6775 to db: 'pmacct' user: 'grafana_reader' host: '10.73.246.25' (Got an error reading communication packets) Oct 9 13:20:44 ntop00 pmacct-mariadb[775683]: 2026-10-09 17:20:44 6782 [Warning] Aborted connection 6782 to db: 'pmacct' user: 'grafana_reader' host: '10.73.246.25' (Got an error reading communication packets) Oct 9 13:20:44 ntop00 pmacct-mariadb[775683]: 2026-10-09 17:20:44 6784 [Warning] Aborted connection 6784 to db: 'pmacct' user: 'grafana_reader' host: '10.73.246.25' (Got an error reading communication packets) Oct 9 13:20:44 ntop00 pmacct-mariadb[775683]: 2026-10-09 17:20:44 6778 [Warning] Aborted connection 6778 to db: 'pmacct' user: 'grafana_reader' host: '10.73.246.25' (Got an error reading communication packets) Oct 9 13:20:44 ntop00 pmacct-mariadb[775683]: 2026-10-09 17:20:44 6776 [Warning] Aborted connection 6776 to db: 'pmacct' user: 'grafana_reader' host: '10.73.246.25' (Got an error reading communication packets) ... 70 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 9 13:09:09 outbound00.cs.umd.edu python3[958175]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 9 13:13:06 outbound01.cs.umd.edu python3[2427850]: ldapdb [x6] == quiss (5 distinct, 17 total) == Oct 9 13:07:40 quiss systemd-coredump[884038]: Process 884023 (chrome) of user 14533 dumped core.#012#012Stack trace of thread 86069:#012#0 0x00005577a91839d8 n/a (/app/extra/chrome + 0x5efb9d8)#012#1 0x00005577a917cac5 n/a (/app/extra/chrome + 0x5ef4ac5)#012#2 0x00005577a91d2e9c n/a (/app/extra/chrome + 0x5f4ae9c)#012#3 0x00005577a786391d n/a (/app/extra/chrome + 0x45db91d)#012#4 0x00007fdf7bae5975 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2b975)#012#5 0x00007fdf7bae5a28 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2ba28)#012#6 0x00005577a9eb7e9a n/a (/app/extra/chrome + 0x6c2fe9a)#012ELF object binary architecture: AMD x86-64 Oct 9 13:08:35 quiss systemd-coredump[886608]: Process 1843863 (chrome) of user 14533 dumped core.#012#012Stack trace of thread 50:#012#0 0x00007fbdc4d66599 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Oct 9 13:59:30 quiss kernel: NFS: nfs4_handle_delegation_recall_error: unhandled error -13. [x4] Oct 9 14:01:09 quiss kernel: NFSv4: state recovery failed for open file dconf/user, error = -13 [x9] Oct 9 14:03:41 quiss kernel: NFSv4: state recovery failed for open file tags/meta.db, error = -13 [x2] == strawberry (7 distinct, 38 total) == Oct 9 13: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 13: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 13:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 9 13: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 13: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 13:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 9 13:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit10-cln25 (5 distinct, 1539 total) == Oct 9 13:05:11 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 13: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 13:25:01 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_check: Input/output error [x2] Oct 9 13:28:01 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmie_check: Input/output error [x2] Oct 9 13:30:01 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_daily: Input/output error == submit26-b9-3 (3 distinct, 8 total) == Sep 11 15:58:15 submit26-b9-3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Sep 11 16:17:09 submit26-b9-3 systemd-coredump[2631181]: Process 2631178 (release02) of user 1001 dumped core.#012#012Stack trace of thread 2631178:#012#0 0x00000000004021b7 highlight_text (release02 + 0x21b7)#012#1 0x0000000000401593 main (release02 + 0x1593)#012#2 0x00007f7c2ca2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f7c2ca2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x00000000004010c5 _start (release02 + 0x10c5)#012ELF object binary architecture: AMD x86-64 Sep 11 16:40:08 submit26-b9-3 systemd-coredump[2633255]: Process 2633252 (release02) of user 1001 dumped core.#012#012Stack trace of thread 2633252:#012#0 0x00007f2bdb766625 __strcpy_avx2_rtm (libc.so.6 + 0x166625)#012#1 0x000000000040222a highlight_text (release02 + 0x222a)#012#2 0x0000000000401593 main (release02 + 0x1593)#012#3 0x00007f2bdb62a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f2bdb62a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010c5 _start (release02 + 0x10c5)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f1 (1 distinct, 2 total) == Oct 9 13:25:43 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f2 (1 distinct, 1 total) == Oct 9 13:35:55 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (10 distinct, 10 total) == Oct 9 13:06:50 submit26-b9-f3 setroubleshoot[2407896]: 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 9 13:06:50 submit26-b9-f3 setroubleshoot[2407896]: 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 9 13:06:50 submit26-b9-f3 setroubleshoot[2407896]: 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 13:06:50 submit26-b9-f3 setroubleshoot[2407896]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.91cWhZ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 9 13:06:50 submit26-b9-f3 setroubleshoot[2407896]: 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 13:06:50 submit26-b9-f3 setroubleshoot[2407896]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.91cWhZ. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 9 13:06:50 submit26-b9-f3 setroubleshoot[2407896]: 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 9 13:06:50 submit26-b9-f3 setroubleshoot[2407896]: 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 13:06:50 submit26-b9-f3 setroubleshoot[2407896]: 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 9 13:48:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f4 (10 distinct, 10 total) == Oct 9 13:24:53 submit26-b9-f4 setroubleshoot[526961]: 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 9 13:24:54 submit26-b9-f4 setroubleshoot[526961]: 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 9 13:24:54 submit26-b9-f4 setroubleshoot[526961]: 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 13:24:54 submit26-b9-f4 setroubleshoot[526961]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.o2fSps/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 9 13:24:54 submit26-b9-f4 setroubleshoot[526961]: 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 13:24:54 submit26-b9-f4 setroubleshoot[526961]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.o2fSps. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 9 13:24:54 submit26-b9-f4 setroubleshoot[526961]: 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 9 13:24:54 submit26-b9-f4 setroubleshoot[526961]: 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 13:24:54 submit26-b9-f4 setroubleshoot[526961]: 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 9 13:43:08 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL