Command: /usr/local/sbin/syslog-digest.py Time : 0.0604s Status : exited 0 Output : Syslog digest — 2026-09-09 06:05 EDT Processed 2,877 lines, filtered 2,189 (76%). 688 unknown (107 distinct) from 17 host(s). == atif01.cs.umd.edu (2 distinct, 2 total) == Sep 9 05:25:17 atif01.cs.umd.edu kernel: net_ratelimit: 13 callbacks suppressed Sep 9 05:25:17 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)! == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 9 05:35:44 b0b02.cs.umd.edu rustdesk[3304892]: cannot open display: == csfw00a (2 distinct, 147 total) == Sep 9 05:04:02 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x139] Sep 9 05:07:58 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x8] == grades01.cs.umd.edu (1 distinct, 1 total) == Sep 9 05:48:09 grades01.cs.umd.edu puppet-agent[26106]: 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 == hazfs.cs.umd.edu (1 distinct, 2 total) == Sep 9 05:25:02 hazfs.cs.umd.edu pcp[3625325]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2] == idm00 (15 distinct, 169 total) == Sep 9 05:05:04 idm00 check-named-alive[5110]: zone cs.umd.edu: local SOA serial 1788938974 lags newest peer 1788943211 by 4237 (threshold 3600); not acting [x12] Sep 9 05:05:04 idm00 check-named-alive[5171]: zone csdlabs.umd.edu: local SOA serial 1788938974 lags newest peer 1788943212 by 4238 (threshold 3600); not acting [x12] Sep 9 05:05:04 idm00 check-named-alive[5232]: zone csic.umd.edu: local SOA serial 1788938974 lags newest peer 1788943211 by 4237 (threshold 3600); not acting [x12] Sep 9 05:05:04 idm00 check-named-alive[5293]: zone 72.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788943211 by 4237 (threshold 3600); not acting [x12] Sep 9 05:05:05 idm00 check-named-alive[5354]: zone 73.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788943211 by 4237 (threshold 3600); not acting [x12] Sep 9 05:05:05 idm00 check-named-alive[5415]: zone 88.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788943211 by 4237 (threshold 3600); not acting [x12] Sep 9 05:05:05 idm00 check-named-alive[5476]: zone 28.172.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788943211 by 4237 (threshold 3600); not acting [x12] Sep 9 05:05:05 idm00 check-named-alive[5537]: zone 125.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788943211 by 4237 (threshold 3600); not acting [x12] Sep 9 05:05:05 idm00 check-named-alive[5618]: zone 126.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788943211 by 4237 (threshold 3600); not acting [x12] Sep 9 05:05:05 idm00 check-named-alive[5719]: zone 127.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788943211 by 4237 (threshold 3600); not acting [x12] Sep 9 05:05:06 idm00 check-named-alive[5780]: zone 128.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788943211 by 4237 (threshold 3600); not acting [x12] Sep 9 05:05:06 idm00 check-named-alive[5841]: zone 129.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788943211 by 4237 (threshold 3600); not acting [x12] Sep 9 05:05:06 idm00 check-named-alive[5902]: zone 130.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788943211 by 4237 (threshold 3600); not acting [x12] Sep 9 05:05:06 idm00 check-named-alive[5963]: zone 131.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788943211 by 4237 (threshold 3600); not acting [x12] Sep 9 05:53:47 idm00 named[4166701]: client @0x7f11a93d09c8 10.73.240.42#65319: update '73.10.in-addr.arpa/IN' denied == idmh1 (14 distinct, 168 total) == Sep 9 05:08:32 idmh1 check-named-alive[3619729]: zone cs.umd.edu: local SOA serial 1788939166 lags newest peer 1788943211 by 4045 (threshold 3600); not acting [x12] Sep 9 05:08:32 idmh1 check-named-alive[3619790]: zone csdlabs.umd.edu: local SOA serial 1788939166 lags newest peer 1788943212 by 4046 (threshold 3600); not acting [x12] Sep 9 05:08:32 idmh1 check-named-alive[3619851]: zone csic.umd.edu: local SOA serial 1788939166 lags newest peer 1788943211 by 4045 (threshold 3600); not acting [x12] Sep 9 05:08:32 idmh1 check-named-alive[3619912]: zone 72.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788943211 by 4045 (threshold 3600); not acting [x12] Sep 9 05:08:32 idmh1 check-named-alive[3619973]: zone 73.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788943211 by 4045 (threshold 3600); not acting [x12] Sep 9 05:08:33 idmh1 check-named-alive[3620036]: zone 88.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788943211 by 4045 (threshold 3600); not acting [x12] Sep 9 05:08:33 idmh1 check-named-alive[3620097]: zone 28.172.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788943211 by 4045 (threshold 3600); not acting [x12] Sep 9 05:08:33 idmh1 check-named-alive[3620158]: zone 125.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788943211 by 4045 (threshold 3600); not acting [x12] Sep 9 05:08:33 idmh1 check-named-alive[3620221]: zone 126.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788943211 by 4045 (threshold 3600); not acting [x12] Sep 9 05:08:33 idmh1 check-named-alive[3620282]: zone 127.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788943211 by 4045 (threshold 3600); not acting [x12] Sep 9 05:08:34 idmh1 check-named-alive[3620346]: zone 128.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788943211 by 4045 (threshold 3600); not acting [x12] Sep 9 05:08:34 idmh1 check-named-alive[3620407]: zone 129.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788943211 by 4045 (threshold 3600); not acting [x12] Sep 9 05:08:34 idmh1 check-named-alive[3620468]: zone 130.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788943211 by 4045 (threshold 3600); not acting [x12] Sep 9 05:08:34 idmh1 check-named-alive[3620536]: zone 131.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788943211 by 4045 (threshold 3600); not acting [x12] == idmp0 (1 distinct, 1 total) == Sep 9 05:37:42 idmp0 named[1598691]: client @0x7f2d3400d5c8 10.73.240.43#56477: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 53 total) == Sep 9 05:08:04 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x53] == newhonors2 (1 distinct, 24 total) == Sep 9 05:13:03 newhonors2 dhcpcd[2389204]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 9 05:09:08 outbound00.cs.umd.edu python3[2382747]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Sep 9 05:08:22 outbound01.cs.umd.edu python3[442276]: ldapdb [x7] Sep 9 05:09:58 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. == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Sep 9 05:46:48 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 9 05:05:02 sentry-docker00.cs.umd.edu systemd-udevd[828119]: link_config: could not get ethtool features for vethda95f54 Sep 9 05:05:02 sentry-docker00.cs.umd.edu systemd-udevd[828119]: Could not set offload features of vethda95f54: No such device Sep 9 05:05:03 sentry-docker00.cs.umd.edu systemd-udevd[828188]: Could not generate persistent MAC address for vethc5bafe3: No such file or directory Sep 9 05:05:03 sentry-docker00.cs.umd.edu systemd-udevd[828189]: Could not generate persistent MAC address for veth06370a2: No such file or directory Sep 9 05:05:03 sentry-docker00.cs.umd.edu systemd-udevd[828192]: Could not generate persistent MAC address for veth991193c: No such file or directory Sep 9 05:05:03 sentry-docker00.cs.umd.edu systemd-udevd[828193]: Could not generate persistent MAC address for vethfc9beea: No such file or directory Sep 9 05:05:03 sentry-docker00.cs.umd.edu systemd-udevd[828216]: Could not generate persistent MAC address for veth7027e21: No such file or directory Sep 9 05:05:03 sentry-docker00.cs.umd.edu systemd-udevd[828217]: Could not generate persistent MAC address for vethd29eab6: No such file or directory Sep 9 05:05:03 sentry-docker00.cs.umd.edu systemd-udevd[828235]: Could not generate persistent MAC address for veth685512a: No such file or directory Sep 9 05:05:03 sentry-docker00.cs.umd.edu systemd-udevd[828242]: Could not generate persistent MAC address for vethf15bf05: No such file or directory Sep 9 05:05:03 sentry-docker00.cs.umd.edu systemd-udevd[828252]: Could not generate persistent MAC address for vethffe7e31: No such file or directory Sep 9 05:05:03 sentry-docker00.cs.umd.edu systemd-udevd[828249]: Could not generate persistent MAC address for vetha96822c: No such file or directory Sep 9 05:25:11 sentry-docker00.cs.umd.edu systemd-udevd[837822]: link_config: could not get ethtool features for vethc5bafe3 Sep 9 05:25:11 sentry-docker00.cs.umd.edu systemd-udevd[837822]: Could not set offload features of vethc5bafe3: No such device Sep 9 05:25:11 sentry-docker00.cs.umd.edu systemd-udevd[837851]: Could not generate persistent MAC address for veth2a01c18: No such file or directory Sep 9 05:25:11 sentry-docker00.cs.umd.edu systemd-udevd[837852]: Could not generate persistent MAC address for veth0554806: No such file or directory Sep 9 05:25:11 sentry-docker00.cs.umd.edu systemd-udevd[837870]: Could not generate persistent MAC address for vethf79477a: No such file or directory Sep 9 05:25:11 sentry-docker00.cs.umd.edu systemd-udevd[837859]: Could not generate persistent MAC address for veth8ce70aa: No such file or directory Sep 9 05:25:11 sentry-docker00.cs.umd.edu systemd-udevd[837879]: Could not generate persistent MAC address for vethc970115: No such file or directory Sep 9 05:25:11 sentry-docker00.cs.umd.edu systemd-udevd[837880]: Could not generate persistent MAC address for veth05be458: No such file or directory Sep 9 05:25:11 sentry-docker00.cs.umd.edu systemd-udevd[837898]: Could not generate persistent MAC address for vethba4044b: No such file or directory Sep 9 05:25:11 sentry-docker00.cs.umd.edu systemd-udevd[837905]: Could not generate persistent MAC address for veth3576fc7: No such file or directory Sep 9 05:25:11 sentry-docker00.cs.umd.edu systemd-udevd[837938]: Could not generate persistent MAC address for vethfd51570: No such file or directory Sep 9 05:25:11 sentry-docker00.cs.umd.edu systemd-udevd[837940]: Could not generate persistent MAC address for vethf594ed4: No such file or directory Sep 9 05:45:19 sentry-docker00.cs.umd.edu systemd-udevd[847477]: link_config: could not get ethtool features for vethfd51570 Sep 9 05:45:19 sentry-docker00.cs.umd.edu systemd-udevd[847477]: Could not set offload features of vethfd51570: No such device Sep 9 05:45:19 sentry-docker00.cs.umd.edu systemd-udevd[847572]: Could not generate persistent MAC address for veth7c6211c: No such file or directory Sep 9 05:45:19 sentry-docker00.cs.umd.edu systemd-udevd[847573]: Could not generate persistent MAC address for veth911ebda: No such file or directory Sep 9 05:45:19 sentry-docker00.cs.umd.edu systemd-udevd[847576]: Could not generate persistent MAC address for veth2b55833: No such file or directory Sep 9 05:45:19 sentry-docker00.cs.umd.edu systemd-udevd[847577]: Could not generate persistent MAC address for veth537b5e7: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 9 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 9 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 9 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 9 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 9 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 9 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 9 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (10 distinct, 13 total) == Sep 9 05:06:38 submit26-b9-f3 setroubleshoot[36289]: 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 Sep 9 05:06:39 submit26-b9-f3 setroubleshoot[36289]: 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 Sep 9 05:06:39 submit26-b9-f3 setroubleshoot[36289]: 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 [x2] Sep 9 05:06:39 submit26-b9-f3 setroubleshoot[36289]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.V6jGOx/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 9 05:06:39 submit26-b9-f3 setroubleshoot[36289]: 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 [x2] Sep 9 05:06:39 submit26-b9-f3 setroubleshoot[36289]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.V6jGOx. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 9 05:06:39 submit26-b9-f3 setroubleshoot[36289]: 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 Sep 9 05:06:39 submit26-b9-f3 setroubleshoot[36289]: 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 [x2] Sep 9 05:06:39 submit26-b9-f3 setroubleshoot[36289]: 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 Sep 9 05:07:08 submit26-b9-f3 setroubleshoot[36324]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.GeNSZ1/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f == submit26-b9-f4 (11 distinct, 18 total) == Sep 9 05:24:42 submit26-b9-f4 setroubleshoot[27043]: 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 [x2] Sep 9 05:24:42 submit26-b9-f4 setroubleshoot[27043]: 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 [x2] Sep 9 05:24:42 submit26-b9-f4 setroubleshoot[27043]: 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] Sep 9 05:24:42 submit26-b9-f4 setroubleshoot[27043]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.5lWByx/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 9 05:24:43 submit26-b9-f4 setroubleshoot[27043]: 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] Sep 9 05:24:43 submit26-b9-f4 setroubleshoot[27043]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.5lWByx. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 9 05:24:43 submit26-b9-f4 setroubleshoot[27043]: 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 [x2] Sep 9 05:24:43 submit26-b9-f4 setroubleshoot[27043]: 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 [x2] Sep 9 05:24:43 submit26-b9-f4 setroubleshoot[27043]: 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 [x2] Sep 9 05:25:12 submit26-b9-f4 setroubleshoot[27098]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.B6RhWg/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 9 05:25:12 submit26-b9-f4 setroubleshoot[27098]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.B6RhWg. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c