Command: /usr/local/sbin/syslog-digest.py Time : 0.0526s Status : exited 0 Output : Syslog digest — 2026-09-22 06:05 EDT Processed 2,604 lines, filtered 2,088 (80%). 516 unknown (186 distinct) from 23 host(s). == atif01.cs.umd.edu (2 distinct, 2 total) == Sep 22 05:13:29 atif01.cs.umd.edu kernel: net_ratelimit: 9 callbacks suppressed Sep 22 05:13:29 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)! == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 22 05:54:57 b0b02.cs.umd.edu rustdesk[3887743]: cannot open display: == bale (5 distinct, 90 total) == Sep 22 05:05:15 bale setroubleshoot[1719940]: failed to retrieve rpm info for /dev/nvme0 [x39] Sep 22 05:05:15 bale setroubleshoot[1719940]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x13] Sep 22 05:05:18 bale setroubleshoot[1719940]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12] Sep 22 05:05:21 bale setroubleshoot[1719940]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12] Sep 22 05:05:33 bale setroubleshoot[1720555]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x14] == csfw00a (1 distinct, 121 total) == Sep 22 05:03:57 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x121] == gle-dind02.cs.umd.edu (1 distinct, 1 total) == Sep 22 05:37:40 gle-dind02.cs.umd.edu systemd[1]: cgroup compatibility translation between legacy and unified hierarchy settings activated. See cgroup-compat debug messages for details. == grades01.cs.umd.edu (1 distinct, 1 total) == Sep 22 05:48:23 grades01.cs.umd.edu puppet-agent[5647]: 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) == Sep 22 05:54:03 idm00 named[4166701]: client @0x7f119804aea8 10.73.240.42#56650: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 22 05:37:55 idmp0 named[1598691]: client @0x7f2d2402e528 10.73.240.43#58002: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 2 total) == Sep 22 05:20:12 inbound00.cs.umd.edu cockpit-ws[2751225]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2] == inbound01.cs.umd.edu (1 distinct, 3 total) == Sep 22 05:20:17 inbound01.cs.umd.edu cockpit-ws[774803]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x3] == itmon02 (1 distinct, 3 total) == Sep 22 05:23:12 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == munin (2 distinct, 6 total) == Sep 22 05:08:08 munin sudo[1681959]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x3] Sep 22 05:08:08 munin sudo[1681959]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x3] == neodontcare.cs.umd.edu (1 distinct, 1 total) == Sep 22 06:04:48 neodontcare.cs.umd.edu packagekitd[1501563]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == newhonors2 (1 distinct, 24 total) == Sep 22 05:13:02 newhonors2 dhcpcd[2981503]: dhcpcd is not running [x24] == ntop00 (97 distinct, 141 total) == Sep 22 05:05:28 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 5349/5349, ET: 27) *** Sep 22 05:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 22 05:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 5463/5463, ET: 0) *** Sep 22 05:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 22 05:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 48/48, ET: 0) *** Sep 22 05:08:02 ntop00 setroubleshoot[1151933]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12] Sep 22 05:08:02 ntop00 setroubleshoot[1151933]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12] Sep 22 05:08:02 ntop00 setroubleshoot[1151933]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 22 05:08:02 ntop00 setroubleshoot[1151933]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12] Sep 22 05:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 22 05:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 22 05:10:28 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 5065/5065, ET: 27) *** Sep 22 05:10:28 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 48/48, ET: 27) *** Sep 22 05:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 517) *** Sep 22 05:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 4806/4806, ET: 0) *** Sep 22 05:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 517) *** Sep 22 05:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 55/55, ET: 0) *** Sep 22 05:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 22 05:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 22 05:15:27 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 4845/4845, ET: 26) *** Sep 22 05:15:27 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 61/61, ET: 26) *** Sep 22 05:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 22 05:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 4652/4652, ET: 0) *** Sep 22 05:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 22 05:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 59/59, ET: 0) *** Sep 22 05:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) *** Sep 22 05:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) *** Sep 22 05:20:25 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 4444/4444, ET: 24) *** Sep 22 05:20:25 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 63/63, ET: 24) *** Sep 22 05:23:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 521) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 9 total) == Sep 22 05:09:09 outbound00.cs.umd.edu python3[2613212]: ldapdb [x6] Sep 22 05:17:05 outbound00.cs.umd.edu cockpit-ws[2614794]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x3] == outbound01.cs.umd.edu (3 distinct, 11 total) == Sep 22 05:08:33 outbound01.cs.umd.edu python3[678605]: ldapdb [x7] Sep 22 05:09:40 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. [x2] Sep 22 05:46:29 outbound01.cs.umd.edu cockpit-ws[716537]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273106]: link_config: could not get ethtool features for veth092efca Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273106]: Could not set offload features of veth092efca: No such device Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273140]: Could not generate persistent MAC address for veth3c53bc3: No such file or directory Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273141]: Could not generate persistent MAC address for vetha2a5d78: No such file or directory Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273144]: Could not generate persistent MAC address for veth06ae805: No such file or directory Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273145]: Could not generate persistent MAC address for vethbfd1bd3: No such file or directory Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273154]: Could not generate persistent MAC address for veth9004c64: No such file or directory Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273144]: Could not generate persistent MAC address for veth87eb3c1: No such file or directory Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273145]: Could not generate persistent MAC address for vethd3e513c: No such file or directory Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273154]: Could not generate persistent MAC address for vetha8fefcd: No such file or directory Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273183]: Could not generate persistent MAC address for veth3097d57: No such file or directory Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273192]: Could not generate persistent MAC address for vethd6b0791: No such file or directory Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282697]: link_config: could not get ethtool features for veth3097d57 Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282697]: Could not set offload features of veth3097d57: No such device Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282778]: Could not generate persistent MAC address for vetha399796: No such file or directory Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282779]: Could not generate persistent MAC address for vethb2778ec: No such file or directory Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282782]: Could not generate persistent MAC address for vetha76752e: No such file or directory Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282783]: Could not generate persistent MAC address for veth04e8cf3: No such file or directory Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282798]: Could not generate persistent MAC address for vethc6f3b1f: No such file or directory Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282788]: Could not generate persistent MAC address for veth3a0c6e1: No such file or directory Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282809]: Could not generate persistent MAC address for veth2613524: No such file or directory Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282808]: Could not generate persistent MAC address for veth9b82d81: No such file or directory Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282834]: Could not generate persistent MAC address for veth61443ac: No such file or directory Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282835]: Could not generate persistent MAC address for vetha49593e: No such file or directory Sep 22 05:54:29 sentry-docker00.cs.umd.edu systemd-udevd[1292241]: link_config: could not get ethtool features for veth9b82d81 Sep 22 05:54:29 sentry-docker00.cs.umd.edu systemd-udevd[1292241]: Could not set offload features of veth9b82d81: No such device Sep 22 05:54:29 sentry-docker00.cs.umd.edu systemd-udevd[1292280]: Could not generate persistent MAC address for veth445e0a2: No such file or directory Sep 22 05:54:29 sentry-docker00.cs.umd.edu systemd-udevd[1292281]: Could not generate persistent MAC address for veth885dc41: No such file or directory Sep 22 05:54:29 sentry-docker00.cs.umd.edu systemd-udevd[1292284]: Could not generate persistent MAC address for veth8fd5dd1: No such file or directory Sep 22 05:54:29 sentry-docker00.cs.umd.edu systemd-udevd[1292285]: Could not generate persistent MAC address for vethb21f138: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 22 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 22 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 22 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 22 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 22 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 22 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 22 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Sep 22 05:10:05 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (1 distinct, 1 total) == Sep 22 05:33:09 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (10 distinct, 13 total) == Sep 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 [x2] Sep 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 [x2] Sep 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 Sep 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Aov9YK/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 Sep 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Aov9YK. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 Sep 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 22 05:13:07 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f4 (9 distinct, 9 total) == Sep 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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 Sep 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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 Sep 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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 Sep 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.msu9Es/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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 Sep 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.msu9Es. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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 Sep 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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 Sep 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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