Command: /usr/local/sbin/syslog-digest.py Time : 0.1396s Status : exited 0 Output : Syslog digest — 2026-10-08 22:05 EDT Processed 5,199 lines, filtered 3,089 (59%). 2,110 unknown (146 distinct) from 20 host(s). == abuse (1 distinct, 346 total) == Oct 8 21: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 8 21:19:22 b0b02.cs.umd.edu rustdesk[1732566]: cannot open display: == biggulp.cs.umd.edu (1 distinct, 1 total) == Oct 8 21:58:38 biggulp.cs.umd.edu sshd-session[639016]: error: send_error: write: Connection reset by peer == cheezit.cs.umd.edu (1 distinct, 1 total) == Oct 8 21:25:57 cheezit.cs.umd.edu sshd-session[803925]: pam_access(sshd:auth): access denied for user `lin' from `74.96.151.253' == gle-dind02.cs.umd.edu (6 distinct, 6 total) == Oct 8 22:04:47 gle-dind02.cs.umd.edu systemd-udevd[2142080]: Could not generate persistent MAC address for veth610c65e: No such file or directory Oct 8 22:04:47 gle-dind02.cs.umd.edu systemd-udevd[2142081]: Could not generate persistent MAC address for veth69c1498: No such file or directory Oct 8 22:04:48 gle-dind02.cs.umd.edu systemd-udevd[2142181]: Could not generate persistent MAC address for veth3d6416c: No such file or directory Oct 8 22:04:48 gle-dind02.cs.umd.edu systemd-udevd[2142183]: Could not generate persistent MAC address for vethec04b00: No such file or directory Oct 8 22:04:49 gle-dind02.cs.umd.edu systemd-udevd[2142283]: Could not generate persistent MAC address for veth563a8f0: No such file or directory Oct 8 22:04:49 gle-dind02.cs.umd.edu systemd-udevd[2142284]: Could not generate persistent MAC address for veth79c512c: No such file or directory == idm00 (1 distinct, 1 total) == Oct 8 21:54:42 idm00 named[4166701]: client @0x7f11a9468268 10.73.240.42#61294: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 8 21:39:21 idmp0 named[1598691]: client @0x7f2d4c039bf8 10.73.240.43#51822: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Oct 8 21:28:17 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 8 total) == Oct 8 21:08:33 munin sudo[1991582]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Oct 8 21:08:33 munin sudo[1991582]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Oct 8 21:13:02 newhonors2 dhcpcd[3751997]: dhcpcd is not running [x24] == ntop00 (93 distinct, 93 total) == Oct 8 21:05:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5506, QN: 5992/5992, ET: 10) *** Oct 8 21:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 5507) *** Oct 8 21:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 5507, QN: 7427/7427, ET: 0) *** Oct 8 21:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 5507) *** Oct 8 21:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 5507, QN: 60/60, ET: 0) *** Oct 8 21:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5508) *** Oct 8 21:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5508) *** Oct 8 21:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5508, QN: 44/44, ET: 0) *** Oct 8 21:10:16 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5508, QN: 8303/8303, ET: 15) *** Oct 8 21:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 5509) *** Oct 8 21:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 5509, QN: 6848/6848, ET: 0) *** Oct 8 21:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 5509) *** Oct 8 21:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 5509, QN: 58/58, ET: 0) *** Oct 8 21:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5510) *** Oct 8 21:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5510) *** Oct 8 21:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5510, QN: 56/56, ET: 0) *** Oct 8 21:15:14 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5510, QN: 6674/6674, ET: 13) *** Oct 8 21:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 5511) *** Oct 8 21:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 5511, QN: 6221/6221, ET: 0) *** Oct 8 21:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 5511) *** Oct 8 21:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 5511, QN: 67/67, ET: 0) *** Oct 8 21:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5512) *** Oct 8 21:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5512) *** Oct 8 21:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5512, QN: 52/52, ET: 0) *** Oct 8 21:20:15 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5512, QN: 7478/7478, ET: 14) *** Oct 8 21:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 5513) *** Oct 8 21:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 5513, QN: 8757/8757, ET: 0) *** Oct 8 21:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 5513) *** Oct 8 21:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 5513, QN: 47/47, ET: 0) *** Oct 8 21:25:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5514) *** ... 63 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 8 21:09:09 outbound00.cs.umd.edu python3[735905]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 8 21:13:06 outbound01.cs.umd.edu python3[2202626]: ldapdb [x6] == strawberry (7 distinct, 38 total) == Oct 8 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 8 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 8 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 8 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 8 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 8 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 8 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit10-cln25 (5 distinct, 1539 total) == Oct 8 21: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 8 21: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 8 21:25:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_check: Input/output error [x2] Oct 8 21:28:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmie_check: Input/output error [x2] Oct 8 21:30:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_daily: Input/output error == submit26-b9-3 (1 distinct, 6 total) == Sep 10 22:40:29 submit26-b9-3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] == submit26-b9-f1 (1 distinct, 3 total) == Oct 8 21:22:32 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f2 (1 distinct, 4 total) == Oct 8 21:12:31 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f3 (10 distinct, 12 total) == Oct 8 21:06:49 submit26-b9-f3 setroubleshoot[2334994]: 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 8 21:06:49 submit26-b9-f3 setroubleshoot[2334994]: 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 8 21:06:49 submit26-b9-f3 setroubleshoot[2334994]: 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 8 21:06:49 submit26-b9-f3 setroubleshoot[2334994]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.4pfPK8/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 8 21:06:49 submit26-b9-f3 setroubleshoot[2334994]: 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 8 21:06:49 submit26-b9-f3 setroubleshoot[2334994]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.4pfPK8. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 8 21:06:49 submit26-b9-f3 setroubleshoot[2334994]: 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 8 21:06:49 submit26-b9-f3 setroubleshoot[2334994]: 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 8 21:06:49 submit26-b9-f3 setroubleshoot[2334994]: 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 8 21:10:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f4 (10 distinct, 10 total) == Oct 8 21:13:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL Oct 8 21:24:55 submit26-b9-f4 setroubleshoot[476273]: 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 8 21:24:55 submit26-b9-f4 setroubleshoot[476273]: 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 8 21:24:55 submit26-b9-f4 setroubleshoot[476273]: 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 8 21:24:55 submit26-b9-f4 setroubleshoot[476273]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.AX5NYE/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 8 21:24:55 submit26-b9-f4 setroubleshoot[476273]: 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 8 21:24:55 submit26-b9-f4 setroubleshoot[476273]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.AX5NYE. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 8 21:24:55 submit26-b9-f4 setroubleshoot[476273]: 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 8 21:24:55 submit26-b9-f4 setroubleshoot[476273]: 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 8 21:24:55 submit26-b9-f4 setroubleshoot[476273]: 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