Command: /usr/local/sbin/syslog-digest.py Time : 0.0462s Status : exited 0 Output : Syslog digest — 2026-10-15 06:05 EDT Processed 1,256 lines, filtered 697 (55%). 559 unknown (168 distinct) from 17 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 15 05:28:45 b0b02.cs.umd.edu rustdesk[4050294]: cannot open display: == biggulp.cs.umd.edu (1 distinct, 1 total) == Oct 15 05:53:18 biggulp.cs.umd.edu sshd-session[2248983]: error: send_error: write: Connection reset by peer == grades01.cs.umd.edu (1 distinct, 1 total) == Oct 15 05:48:05 grades01.cs.umd.edu puppet-agent[18901]: 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 15 05:54:49 idm00 named[1014]: client @0x7fcbc9382988 10.73.240.42#57401: update '73.10.in-addr.arpa/IN' denied == idmh1 (12 distinct, 144 total) == Oct 15 05:08:38 idmh1 check-named-alive[922126]: zone cs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 15 05:08:38 idmh1 check-named-alive[922187]: zone csdlabs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 05:08:38 idmh1 check-named-alive[922248]: zone csic.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 05:08:38 idmh1 check-named-alive[922309]: zone 72.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 05:08:39 idmh1 check-named-alive[922430]: zone 88.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 05:08:39 idmh1 check-named-alive[922491]: zone 125.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 05:08:39 idmh1 check-named-alive[922552]: zone 126.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 05:08:39 idmh1 check-named-alive[922613]: zone 127.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 15 05:08:40 idmh1 check-named-alive[922674]: zone 128.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 15 05:08:40 idmh1 check-named-alive[922735]: zone 129.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 15 05:08:40 idmh1 check-named-alive[922796]: zone 130.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 05:08:40 idmh1 check-named-alive[922857]: 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 15 05:40:03 idmp0 named[1180]: client @0x7fe03402b1b8 10.73.240.43#61094: update '73.10.in-addr.arpa/IN' denied == idmv0 (12 distinct, 144 total) == Oct 15 05:09:14 idmv0 check-named-alive[1029726]: zone cs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 15 05:09:14 idmv0 check-named-alive[1029787]: zone csdlabs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 05:09:14 idmv0 check-named-alive[1029848]: zone csic.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 05:09:15 idmv0 check-named-alive[1029909]: zone 72.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 05:09:15 idmv0 check-named-alive[1030030]: zone 88.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 05:09:15 idmv0 check-named-alive[1030091]: zone 125.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 05:09:15 idmv0 check-named-alive[1030152]: zone 126.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 05:09:15 idmv0 check-named-alive[1030213]: zone 127.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 15 05:09:16 idmv0 check-named-alive[1030274]: zone 128.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 15 05:09:16 idmv0 check-named-alive[1030335]: zone 129.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 15 05:09:16 idmv0 check-named-alive[1030396]: zone 130.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 05:09:16 idmv0 check-named-alive[1030457]: 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, 3 total) == Oct 15 05:08:14 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x3] == matrix (11 distinct, 13 total) == Oct 15 05:27:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2811197, but reception only permitted for main PID 720 Oct 15 05:27:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2811205, but reception only permitted for main PID 720 Oct 15 05:27:14 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2811333, but reception only permitted for main PID 720 Oct 15 05:27:14 matrix networkctl[2811343]: Interface "veth47a43bb" not found. Oct 15 05:27:14 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2811343, but reception only permitted for main PID 720 [x2] Oct 15 05:27:15 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2811408, but reception only permitted for main PID 720 Oct 15 05:27:15 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2811417, but reception only permitted for main PID 720 Oct 15 05:30:36 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2813501, but reception only permitted for main PID 720 Oct 15 05:30:36 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2813507, but reception only permitted for main PID 720 Oct 15 05:30:36 matrix networkctl[2813518]: Interface "veth60dd80e" not found. Oct 15 05:30:36 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2813518, but reception only permitted for main PID 720 [x2] == munin (2 distinct, 60 total) == Oct 15 05:14:03 munin sudo[1096159]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x30] Oct 15 05:14:03 munin sudo[1096159]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x30] == newhonors2 (1 distinct, 24 total) == Oct 15 05:13:03 newhonors2 dhcpcd[4046575]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Oct 15 05:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9154) *** Oct 15 05:05:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9154) *** Oct 15 05:05:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9154, QN: 70/70, ET: 0) *** Oct 15 05:05:12 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9154, QN: 5003/5003, ET: 11) *** Oct 15 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 9155) *** Oct 15 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 9155, QN: 60/60, ET: 0) *** Oct 15 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 9155) *** Oct 15 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 9155, QN: 5218/5218, ET: 0) *** Oct 15 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9156) *** Oct 15 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9156, QN: 57/57, ET: 0) *** Oct 15 05:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9156) *** Oct 15 05:10:12 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9156, QN: 5148/5148, ET: 11) *** Oct 15 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 9157) *** Oct 15 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 9157, QN: 5187/5187, ET: 0) *** Oct 15 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 9157) *** Oct 15 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 9157, QN: 50/50, ET: 0) *** Oct 15 05:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9158) *** Oct 15 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9158) *** Oct 15 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9158, QN: 49/49, ET: 0) *** Oct 15 05:15:14 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9158, QN: 5292/5292, ET: 13) *** Oct 15 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 9159) *** Oct 15 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 9159, QN: 5181/5181, ET: 0) *** Oct 15 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 9159) *** Oct 15 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 9159, QN: 66/66, ET: 0) *** Oct 15 05:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9160) *** Oct 15 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9160) *** Oct 15 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9160, QN: 61/61, ET: 0) *** Oct 15 05:20:14 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9160, QN: 5306/5306, ET: 13) *** Oct 15 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 9161) *** Oct 15 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 9161, QN: 4751/4751, ET: 0) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 15 05:09:09 outbound00.cs.umd.edu python3[2850086]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Oct 15 05:08:11 outbound01.cs.umd.edu python3[148748]: ldapdb [x7] Oct 15 05:10:23 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 15 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 15 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 15 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 15 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 15 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 15 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 15 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 9 total) == Oct 15 05:06:52 submit26-b9-f3 setroubleshoot[3514372]: 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 15 05:06:52 submit26-b9-f3 setroubleshoot[3514372]: 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 15 05:06:52 submit26-b9-f3 setroubleshoot[3514372]: 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 15 05:06:52 submit26-b9-f3 setroubleshoot[3514372]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.qTFXt1/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 15 05:06:52 submit26-b9-f3 setroubleshoot[3514372]: 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 15 05:06:52 submit26-b9-f3 setroubleshoot[3514372]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.qTFXt1. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 15 05:06:52 submit26-b9-f3 setroubleshoot[3514372]: 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 15 05:06:52 submit26-b9-f3 setroubleshoot[3514372]: 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 15 05:06:52 submit26-b9-f3 setroubleshoot[3514372]: 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 15 05:24:58 submit26-b9-f4 setroubleshoot[1285236]: 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 15 05:24:58 submit26-b9-f4 setroubleshoot[1285236]: 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 15 05:24:58 submit26-b9-f4 setroubleshoot[1285236]: 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 15 05:24:58 submit26-b9-f4 setroubleshoot[1285236]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.vlSpVD/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 15 05:24:58 submit26-b9-f4 setroubleshoot[1285236]: 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 15 05:24:58 submit26-b9-f4 setroubleshoot[1285236]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.vlSpVD. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 15 05:24:58 submit26-b9-f4 setroubleshoot[1285236]: 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 15 05:24:58 submit26-b9-f4 setroubleshoot[1285236]: 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 15 05:24:58 submit26-b9-f4 setroubleshoot[1285236]: 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