Command: /usr/local/sbin/syslog-digest.py Time : 0.1594s Status : exited 0 Output : Syslog digest — 2026-10-11 10:05 EDT Processed 5,576 lines, filtered 2,961 (53%). 2,615 unknown (189 distinct) from 17 host(s). == abuse (1 distinct, 347 total) == Oct 11 09:05:09 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] == b0b02.cs.umd.edu (2 distinct, 2 total) == Oct 11 09:17:11 b0b02.cs.umd.edu systemd[1]: insights-client.service: Start request repeated too quickly. Oct 11 09:22:51 b0b02.cs.umd.edu rustdesk[2646394]: cannot open display: == idm00 (1 distinct, 1 total) == Oct 11 09:54:46 idm00 named[2816192]: client @0x7fd0f4025428 10.73.240.42#59168: update '73.10.in-addr.arpa/IN' denied == idmh1 (14 distinct, 168 total) == Oct 11 09:07:30 idmh1 check-named-alive[443171]: zone cs.umd.edu: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 09:07:30 idmh1 check-named-alive[443232]: zone csdlabs.umd.edu: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 09:07:30 idmh1 check-named-alive[443293]: zone csic.umd.edu: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 09:07:31 idmh1 check-named-alive[443354]: zone 72.10.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 09:07:31 idmh1 check-named-alive[443415]: zone 73.10.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 09:07:31 idmh1 check-named-alive[443476]: zone 88.10.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 09:07:31 idmh1 check-named-alive[443539]: zone 28.172.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 09:07:31 idmh1 check-named-alive[443600]: zone 125.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 09:07:32 idmh1 check-named-alive[443661]: zone 126.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 09:07:32 idmh1 check-named-alive[443723]: zone 127.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 09:07:32 idmh1 check-named-alive[443785]: zone 128.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 09:07:32 idmh1 check-named-alive[443849]: zone 129.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 09:07:32 idmh1 check-named-alive[443912]: zone 130.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 09:07:33 idmh1 check-named-alive[443973]: zone 131.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] == idmp0 (15 distinct, 169 total) == Oct 11 09:08:00 idmp0 check-named-alive[231398]: zone cs.umd.edu: local SOA serial 1791691939 lags newest peer 1791695702 by 3763 (threshold 3600); not acting [x12] Oct 11 09:08:01 idmp0 check-named-alive[231459]: zone csdlabs.umd.edu: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 09:08:01 idmp0 check-named-alive[231520]: zone csic.umd.edu: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 09:08:01 idmp0 check-named-alive[231581]: zone 72.10.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 09:08:02 idmp0 check-named-alive[231642]: zone 73.10.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 09:08:02 idmp0 check-named-alive[231703]: zone 88.10.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 09:08:02 idmp0 check-named-alive[231764]: zone 28.172.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 09:08:02 idmp0 check-named-alive[231825]: zone 125.8.128.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 09:08:03 idmp0 check-named-alive[231886]: zone 126.8.128.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 09:08:03 idmp0 check-named-alive[231947]: zone 127.8.128.in-addr.arpa: local SOA serial 1791691939 lags newest peer 1791695702 by 3763 (threshold 3600); not acting [x12] Oct 11 09:08:03 idmp0 check-named-alive[232010]: zone 128.8.128.in-addr.arpa: local SOA serial 1791691939 lags newest peer 1791695702 by 3763 (threshold 3600); not acting [x12] Oct 11 09:08:04 idmp0 check-named-alive[232071]: zone 129.8.128.in-addr.arpa: local SOA serial 1791691939 lags newest peer 1791695702 by 3763 (threshold 3600); not acting [x12] Oct 11 09:08:04 idmp0 check-named-alive[232132]: zone 130.8.128.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 09:08:04 idmp0 check-named-alive[232193]: zone 131.8.128.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 09:39:23 idmp0 named[61110]: client @0x7fd7d80165f8 10.73.240.43#64444: update '73.10.in-addr.arpa/IN' denied == idmv0 (14 distinct, 168 total) == Oct 11 09:05:50 idmv0 check-named-alive[3543818]: zone cs.umd.edu: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 09:05:50 idmv0 check-named-alive[3543879]: zone csdlabs.umd.edu: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 09:05:50 idmv0 check-named-alive[3543940]: zone csic.umd.edu: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 09:05:50 idmv0 check-named-alive[3544001]: zone 72.10.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 09:05:51 idmv0 check-named-alive[3544062]: zone 73.10.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 09:05:51 idmv0 check-named-alive[3544123]: zone 88.10.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 09:05:51 idmv0 check-named-alive[3544184]: zone 28.172.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 09:05:51 idmv0 check-named-alive[3544245]: zone 125.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 09:05:51 idmv0 check-named-alive[3544306]: zone 126.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 09:05:51 idmv0 check-named-alive[3544367]: zone 127.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 09:05:52 idmv0 check-named-alive[3544428]: zone 128.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 09:05:52 idmv0 check-named-alive[3544489]: zone 129.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 09:05:52 idmv0 check-named-alive[3544550]: zone 130.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 09:05:52 idmv0 check-named-alive[3544611]: zone 131.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] == itmon02 (1 distinct, 4 total) == Oct 11 09:13:03 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 12 total) == Oct 11 09:08:41 munin sudo[3291920]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Oct 11 09:08:41 munin sudo[3291920]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == newhonors2 (1 distinct, 24 total) == Oct 11 09:13:03 newhonors2 dhcpcd[3872505]: dhcpcd is not running [x24] == ntop00 (98 distinct, 98 total) == Oct 11 09:05:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6946, QN: 4699/4699, ET: 10) *** Oct 11 09:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6947) *** Oct 11 09:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6947, QN: 4844/4844, ET: 0) *** Oct 11 09:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6947) *** Oct 11 09:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6947, QN: 57/57, ET: 0) *** Oct 11 09:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6948) *** Oct 11 09:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6948) *** Oct 11 09:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6948, QN: 60/60, ET: 0) *** Oct 11 09:10:10 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6948, QN: 4900/4900, ET: 9) *** Oct 11 09:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6949) *** Oct 11 09:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6949, QN: 4778/4778, ET: 0) *** Oct 11 09:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6949) *** Oct 11 09:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6949, QN: 59/59, ET: 0) *** Oct 11 09:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6950) *** Oct 11 09:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6950) *** Oct 11 09:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6950, QN: 57/57, ET: 0) *** Oct 11 09:15:10 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6950, QN: 4909/4909, ET: 9) *** Oct 11 09:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6951) *** Oct 11 09:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6951, QN: 4868/4868, ET: 0) *** Oct 11 09:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6951) *** Oct 11 09:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6951, QN: 56/56, ET: 0) *** Oct 11 09:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6952) *** Oct 11 09:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6952) *** Oct 11 09:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6952, QN: 54/54, ET: 0) *** Oct 11 09:20:12 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6952, QN: 4913/4913, ET: 11) *** Oct 11 09:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6953) *** Oct 11 09:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6953, QN: 5004/5004, ET: 0) *** Oct 11 09:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6953) *** Oct 11 09:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6953, QN: 52/52, ET: 0) *** Oct 11 09:25:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6954) *** ... 68 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 11 09:09:09 outbound00.cs.umd.edu python3[1570401]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 11 09:13:06 outbound01.cs.umd.edu python3[3048184]: ldapdb [x6] == quiss (8 distinct, 14 total) == Oct 11 09:08:37 quiss gnome-software[191719]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/josephao/.config/dconf/user.S1GMW3”: Permission denied Oct 11 09:08:40 quiss gnome-software[191719]: failed to get featured apps: no apps to show Oct 11 09:08:40 quiss gnome-software[191719]: Only 0 apps for curated list, hiding Oct 11 09:08:40 quiss gnome-software[191719]: Only 0 apps for recent list, hiding Oct 11 09:08:43 quiss packagekitd[676840]: Failed to get cache filename for gnome-control-center-filesystem [x3] Oct 11 09:08:43 quiss packagekitd[676840]: Failed to get cache filename for perl [x3] Oct 11 09:08:43 quiss packagekitd[676840]: Failed to get cache filename for kernel [x3] Oct 11 09:09:00 quiss gnome-software[191719]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/josephao/.config/dconf/user.NNPVW3”: Permission denied == strawberry (7 distinct, 38 total) == Oct 11 09:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 11 09:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 11 09:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 11 09:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 11 09:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 11 09:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 11 09:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit10-cln25 (5 distinct, 1540 total) == Oct 11 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 ] [x335] Oct 11 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 11 09:25:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_check: Input/output error [x2] Oct 11 09:28:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmie_check: Input/output error [x2] Oct 11 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 11 09:06:50 submit26-b9-f3 setroubleshoot[2868035]: 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 11 09:06:50 submit26-b9-f3 setroubleshoot[2868035]: 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 11 09:06:50 submit26-b9-f3 setroubleshoot[2868035]: 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 11 09:06:50 submit26-b9-f3 setroubleshoot[2868035]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.JLwbNC/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 11 09:06:50 submit26-b9-f3 setroubleshoot[2868035]: 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 11 09:06:50 submit26-b9-f3 setroubleshoot[2868035]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.JLwbNC. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 11 09:06:50 submit26-b9-f3 setroubleshoot[2868035]: 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 11 09:06:50 submit26-b9-f3 setroubleshoot[2868035]: 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 11 09:06:50 submit26-b9-f3 setroubleshoot[2868035]: 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 (9 distinct, 9 total) == Oct 11 09:24:55 submit26-b9-f4 setroubleshoot[831912]: 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 11 09:24:55 submit26-b9-f4 setroubleshoot[831912]: 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 11 09:24:55 submit26-b9-f4 setroubleshoot[831912]: 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 11 09:24:55 submit26-b9-f4 setroubleshoot[831912]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.DUQJuv/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 11 09:24:55 submit26-b9-f4 setroubleshoot[831912]: 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 11 09:24:55 submit26-b9-f4 setroubleshoot[831912]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.DUQJuv. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 11 09:24:55 submit26-b9-f4 setroubleshoot[831912]: 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 11 09:24:55 submit26-b9-f4 setroubleshoot[831912]: 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 11 09:24:55 submit26-b9-f4 setroubleshoot[831912]: 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
participants (1)
-
cron/syslog01.cs.umd.edu