Command: /usr/local/sbin/syslog-digest.py Time : 0.0507s Status : exited 0 Output : Syslog digest — 2026-10-13 06:05 EDT Processed 2,068 lines, filtered 1,483 (71%). 585 unknown (166 distinct) from 19 host(s). == atif01.cs.umd.edu (3 distinct, 5 total) == Oct 13 05:06:42 atif01.cs.umd.edu kernel: net_ratelimit: 14 callbacks suppressed [x2] Oct 13 05:06:42 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)! [x2] Oct 13 05:40:04 atif01.cs.umd.edu kernel: net_ratelimit: 10 callbacks suppressed == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 13 05:25:42 b0b02.cs.umd.edu rustdesk[3319064]: cannot open display: == grades01.cs.umd.edu (1 distinct, 1 total) == Oct 13 05:48:11 grades01.cs.umd.edu puppet-agent[23940]: The directory '/srv/grades' contains 2471 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees == idm00 (1 distinct, 1 total) == Oct 13 05:54:46 idm00 named[1014]: client @0x7fcbc4080348 10.73.240.42#63529: update '73.10.in-addr.arpa/IN' denied == idmh1 (13 distinct, 156 total) == Oct 13 05:05:30 idmh1 check-named-alive[269805]: zone cs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 05:05:30 idmh1 check-named-alive[269866]: zone csdlabs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 05:05:31 idmh1 check-named-alive[269927]: zone csic.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 05:05:31 idmh1 check-named-alive[269988]: zone 72.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 05:05:31 idmh1 check-named-alive[270049]: zone 73.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 05:05:31 idmh1 check-named-alive[270110]: zone 88.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 05:05:31 idmh1 check-named-alive[270171]: zone 125.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 05:05:32 idmh1 check-named-alive[270232]: zone 126.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 05:05:32 idmh1 check-named-alive[270293]: zone 127.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 05:05:32 idmh1 check-named-alive[270354]: zone 128.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 05:05:32 idmh1 check-named-alive[270415]: zone 129.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 05:05:32 idmh1 check-named-alive[270476]: zone 130.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 05:05:33 idmh1 check-named-alive[270537]: zone 131.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] == idmp0 (1 distinct, 1 total) == Oct 13 05:39:20 idmp0 named[1180]: client @0x7fe05c00f858 10.73.240.43#62785: update '73.10.in-addr.arpa/IN' denied == idmv0 (13 distinct, 156 total) == Oct 13 05:05:55 idmv0 check-named-alive[282364]: zone cs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 05:05:55 idmv0 check-named-alive[282425]: zone csdlabs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 05:05:55 idmv0 check-named-alive[282486]: zone csic.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 05:05:55 idmv0 check-named-alive[282547]: zone 72.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 05:05:56 idmv0 check-named-alive[282608]: zone 73.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 05:05:56 idmv0 check-named-alive[282669]: zone 88.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 05:05:56 idmv0 check-named-alive[282730]: zone 125.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 05:05:56 idmv0 check-named-alive[282791]: zone 126.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 05:05:56 idmv0 check-named-alive[282852]: zone 127.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 05:05:56 idmv0 check-named-alive[282913]: zone 128.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 05:05:57 idmv0 check-named-alive[282974]: zone 129.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 05:05:57 idmv0 check-named-alive[283035]: zone 130.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 05:05:57 idmv0 check-named-alive[283096]: zone 131.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] == itmon02 (1 distinct, 2 total) == Oct 13 05:18:28 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x2] == krispykreme.cs.umd.edu (1 distinct, 1 total) == Oct 13 05:25:48 krispykreme.cs.umd.edu sshd-session[1141539]: error: send_error: write: Connection reset by peer == misty.cs.umd.edu (1 distinct, 1 total) == Oct 13 05:31:02 misty.cs.umd.edu kernel: perf: interrupt took too long (12668 > 12282), lowering kernel.perf_event_max_sample_rate to 15000 == munin (2 distinct, 64 total) == Oct 13 05:08:54 munin sudo[53443]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x32] Oct 13 05:08:54 munin sudo[53443]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x32] == newhonors2 (1 distinct, 24 total) == Oct 13 05:13:03 newhonors2 dhcpcd[3956162]: dhcpcd is not running [x24] == ntop00 (98 distinct, 98 total) == Oct 13 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8002) *** Oct 13 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8002, QN: 80/80, ET: 0) *** Oct 13 05:05:10 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8002, QN: 4621/4621, ET: 9) *** Oct 13 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8003) *** Oct 13 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8003, QN: 4412/4412, ET: 0) *** Oct 13 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8003) *** Oct 13 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8003, QN: 95/95, ET: 0) *** Oct 13 05:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8004) *** Oct 13 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8004) *** Oct 13 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8004, QN: 88/88, ET: 0) *** Oct 13 05:10:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8004, QN: 4668/4668, ET: 10) *** Oct 13 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8005) *** Oct 13 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8005, QN: 5109/5109, ET: 0) *** Oct 13 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8005) *** Oct 13 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8005, QN: 79/79, ET: 0) *** Oct 13 05:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8006) *** Oct 13 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8006) *** Oct 13 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8006, QN: 70/70, ET: 0) *** Oct 13 05:15:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8006, QN: 4857/4857, ET: 10) *** Oct 13 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8007) *** Oct 13 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8007, QN: 4433/4433, ET: 0) *** Oct 13 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8007) *** Oct 13 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8007, QN: 62/62, ET: 0) *** Oct 13 05:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8008) *** Oct 13 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8008) *** Oct 13 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8008, QN: 56/56, ET: 0) *** Oct 13 05:20:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8008, QN: 4837/4837, ET: 10) *** Oct 13 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8009) *** Oct 13 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8009, QN: 5240/5240, ET: 0) *** Oct 13 05:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8009) *** ... 68 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 13 05:09:09 outbound00.cs.umd.edu python3[2183667]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Oct 13 05:08:17 outbound01.cs.umd.edu python3[3667950]: ldapdb [x7] Oct 13 05:10:29 outbound01.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway. == strawberry (7 distinct, 38 total) == Oct 13 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 13 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 13 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 13 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 13 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 13 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 13 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-3 (1 distinct, 1 total) == Sep 15 16:07:34 submit26-b9-3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (9 distinct, 9 total) == Oct 13 05:06:51 submit26-b9-f3 setroubleshoot[3210621]: 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 13 05:06:51 submit26-b9-f3 setroubleshoot[3210621]: 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 13 05:06:51 submit26-b9-f3 setroubleshoot[3210621]: 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 13 05:06:51 submit26-b9-f3 setroubleshoot[3210621]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Ky3U76/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 13 05:06:51 submit26-b9-f3 setroubleshoot[3210621]: 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 13 05:06:51 submit26-b9-f3 setroubleshoot[3210621]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Ky3U76. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 13 05:06:51 submit26-b9-f3 setroubleshoot[3210621]: 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 13 05:06:51 submit26-b9-f3 setroubleshoot[3210621]: 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 13 05:06:51 submit26-b9-f3 setroubleshoot[3210621]: 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, 12 total) == Oct 13 05:24:56 submit26-b9-f4 setroubleshoot[1072722]: 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 13 05:24:56 submit26-b9-f4 setroubleshoot[1072722]: 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 13 05:24:56 submit26-b9-f4 setroubleshoot[1072722]: 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 [x2] Oct 13 05:24:56 submit26-b9-f4 setroubleshoot[1072722]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.TR4teh/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2] Oct 13 05:24:56 submit26-b9-f4 setroubleshoot[1072722]: 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 13 05:24:56 submit26-b9-f4 setroubleshoot[1072722]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.TR4teh. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 13 05:24:56 submit26-b9-f4 setroubleshoot[1072722]: 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 13 05:24:56 submit26-b9-f4 setroubleshoot[1072722]: 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 13 05:24:56 submit26-b9-f4 setroubleshoot[1072722]: 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