Command: /usr/local/sbin/syslog-digest.py Time : 0.0478s Status : exited 0 Output : Syslog digest — 2026-10-14 06:05 EDT Processed 1,370 lines, filtered 794 (57%). 576 unknown (169 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 14 05:27:15 b0b02.cs.umd.edu rustdesk[3684378]: cannot open display: == grades01.cs.umd.edu (1 distinct, 1 total) == Oct 14 05:47:53 grades01.cs.umd.edu puppet-agent[21363]: 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 14 05:54:48 idm00 named[1014]: client @0x7fcbc93a91a8 10.73.240.42#64539: update '73.10.in-addr.arpa/IN' denied == idmh1 (13 distinct, 156 total) == Oct 14 05:07:04 idmh1 check-named-alive[595668]: zone cs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 14 05:07:04 idmh1 check-named-alive[595729]: zone csdlabs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 05:07:04 idmh1 check-named-alive[595790]: zone csic.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 05:07:05 idmh1 check-named-alive[595851]: zone 72.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 05:07:05 idmh1 check-named-alive[595912]: zone 73.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 05:07:05 idmh1 check-named-alive[595973]: zone 88.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 05:07:05 idmh1 check-named-alive[596034]: zone 125.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 05:07:05 idmh1 check-named-alive[596095]: zone 126.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 05:07:06 idmh1 check-named-alive[596156]: zone 127.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 14 05:07:06 idmh1 check-named-alive[596217]: zone 128.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 14 05:07:06 idmh1 check-named-alive[596278]: zone 129.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 14 05:07:06 idmh1 check-named-alive[596339]: zone 130.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 14 05:07:07 idmh1 check-named-alive[596400]: 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 14 05:39:45 idmp0 named[1180]: client @0x7fe03c0223e8 10.73.240.43#64295: update '73.10.in-addr.arpa/IN' denied == idmv0 (13 distinct, 156 total) == Oct 14 05:07:25 idmv0 check-named-alive[657300]: zone cs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 14 05:07:26 idmv0 check-named-alive[657361]: zone csdlabs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 05:07:26 idmv0 check-named-alive[657422]: zone csic.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 05:07:26 idmv0 check-named-alive[657483]: zone 72.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 05:07:26 idmv0 check-named-alive[657544]: zone 73.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 05:07:26 idmv0 check-named-alive[657605]: zone 88.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 05:07:26 idmv0 check-named-alive[657666]: zone 125.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 05:07:27 idmv0 check-named-alive[657727]: zone 126.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 05:07:27 idmv0 check-named-alive[657788]: zone 127.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 14 05:07:27 idmv0 check-named-alive[657849]: zone 128.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 14 05:07:27 idmv0 check-named-alive[657910]: zone 129.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 14 05:07:27 idmv0 check-named-alive[657971]: zone 130.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 14 05:07:27 idmv0 check-named-alive[658032]: zone 131.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] == inbound00.cs.umd.edu (1 distinct, 1 total) == Oct 14 05:43:24 inbound00.cs.umd.edu krb5_child[1946317]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 2 total) == Oct 14 05:58:34 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x2] == matrix (2 distinct, 2 total) == Oct 14 05:05:10 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 1961224, but reception only permitted for main PID 720 Oct 14 05:05:10 matrix networkctl[1961240]: Interface "veth19cb1d3" not found. == mcstic (1 distinct, 2 total) == Oct 14 05:55:56 mcstic krb5_child[1978569]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == munin (2 distinct, 26 total) == Oct 14 05:13:30 munin sudo[575355]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x13] Oct 14 05:13:30 munin sudo[575355]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x13] == netman.cs.umd.edu (4 distinct, 34 total) == Oct 14 05:06:08 netman.cs.umd.edu krb5_child[3037439]: Client 'admin@UMD.EDU' not found in Kerberos database [x28] Oct 14 05:07:50 netman.cs.umd.edu krb5_child[3037937]: Client 'guest1@UMD.EDU' not found in Kerberos database [x2] Oct 14 05:11:07 netman.cs.umd.edu krb5_child[3038939]: Client 'anton@UMD.EDU' not found in Kerberos database [x2] Oct 14 05:12:57 netman.cs.umd.edu krb5_child[3039105]: Client 'george@UMD.EDU' not found in Kerberos database [x2] == newhonors2 (1 distinct, 24 total) == Oct 14 05:13:02 newhonors2 dhcpcd[4001258]: dhcpcd is not running [x24] == ntop00 (99 distinct, 99 total) == Oct 14 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8578) *** Oct 14 05:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8578) *** Oct 14 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8578, QN: 64/64, ET: 0) *** Oct 14 05:05:12 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8578, QN: 4740/4740, ET: 11) *** Oct 14 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8579) *** Oct 14 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8579, QN: 4749/4749, ET: 0) *** Oct 14 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8579) *** Oct 14 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8579, QN: 56/56, ET: 0) *** Oct 14 05:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8580) *** Oct 14 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8580) *** Oct 14 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8580, QN: 52/52, ET: 0) *** Oct 14 05:10:13 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8580, QN: 4877/4877, ET: 12) *** Oct 14 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8581) *** Oct 14 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8581, QN: 5116/5116, ET: 0) *** Oct 14 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8581) *** Oct 14 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8581, QN: 51/51, ET: 0) *** Oct 14 05:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8582) *** Oct 14 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8582) *** Oct 14 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8582, QN: 53/53, ET: 0) *** Oct 14 05:15:13 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8582, QN: 4883/4883, ET: 12) *** Oct 14 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8583) *** Oct 14 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8583, QN: 4513/4513, ET: 0) *** Oct 14 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8583) *** Oct 14 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8583, QN: 59/59, ET: 0) *** Oct 14 05:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8584) *** Oct 14 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8584) *** Oct 14 05:20:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8584, QN: 51/51, ET: 1) *** Oct 14 05:20:10 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8584, QN: 4507/4507, ET: 9) *** Oct 14 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8585) *** Oct 14 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8585, QN: 4694/4694, ET: 0) *** ... 69 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 14 05:09:08 outbound00.cs.umd.edu python3[2516668]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Oct 14 05:08:23 outbound01.cs.umd.edu python3[4004866]: ldapdb [x7] Oct 14 05:10:04 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 14 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 14 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 14 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 14 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 14 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 14 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 14 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 14 05:06:51 submit26-b9-f3 setroubleshoot[3309270]: 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 14 05:06:51 submit26-b9-f3 setroubleshoot[3309270]: 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 14 05:06:51 submit26-b9-f3 setroubleshoot[3309270]: 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 14 05:06:51 submit26-b9-f3 setroubleshoot[3309270]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.mTxVxB/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 14 05:06:51 submit26-b9-f3 setroubleshoot[3309270]: 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 14 05:06:51 submit26-b9-f3 setroubleshoot[3309270]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.mTxVxB. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 14 05:06:52 submit26-b9-f3 setroubleshoot[3309270]: 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 14 05:06:52 submit26-b9-f3 setroubleshoot[3309270]: 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 14 05:06:52 submit26-b9-f3 setroubleshoot[3309270]: 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 14 05:24:55 submit26-b9-f4 setroubleshoot[1145230]: 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 14 05:24:55 submit26-b9-f4 setroubleshoot[1145230]: 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 14 05:24:55 submit26-b9-f4 setroubleshoot[1145230]: 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 14 05:24:55 submit26-b9-f4 setroubleshoot[1145230]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.FgDF0J/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 14 05:24:55 submit26-b9-f4 setroubleshoot[1145230]: 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 14 05:24:55 submit26-b9-f4 setroubleshoot[1145230]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.FgDF0J. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 14 05:24:55 submit26-b9-f4 setroubleshoot[1145230]: 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 14 05:24:55 submit26-b9-f4 setroubleshoot[1145230]: 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 14 05:24:55 submit26-b9-f4 setroubleshoot[1145230]: 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