Command: /usr/local/sbin/syslog-digest.py Time : 0.0528s Status : exited 0 Output : Syslog digest — 2026-09-17 18:05 EDT Processed 2,924 lines, filtered 2,503 (85%). 421 unknown (135 distinct) from 18 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 17 17:48:19 b0b02.cs.umd.edu rustdesk[2232289]: cannot open display: == biggulp.cs.umd.edu (1 distinct, 1 total) == Sep 17 17:37:05 biggulp.cs.umd.edu sshd-session[2098631]: pam_access(sshd:auth): access denied for user `conniehg' from `73.133.150.131' == csfw00a (1 distinct, 118 total) == Sep 17 17:03:44 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x118] == frozone (1 distinct, 1 total) == Sep 17 17:35:36 frozone systemd-tmpfiles[1908926]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted == idm00 (1 distinct, 1 total) == Sep 17 17:53:57 idm00 named[4166701]: client @0x7f11a0045838 10.73.240.42#59727: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 17 17:37:57 idmp0 named[1598691]: client @0x7f2d2402e528 10.73.240.43#54771: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 17 17:07:58 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 4 total) == Sep 17 17:23:04 munin sudo[3524440]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 17 17:23:04 munin sudo[3524440]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == networkvm02 (1 distinct, 2 total) == Sep 17 17:46:25 networkvm02 systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive. [x2] == newhonors2 (1 distinct, 24 total) == Sep 17 17:13:02 newhonors2 dhcpcd[2777576]: dhcpcd is not running [x24] == ntop00 (57 distinct, 156 total) == Sep 17 17:06:01 ntop00 sfacctd[199410]: INFO ( default_print/print ): *** Purging cache - START (PID: 85) *** Sep 17 17:06:01 ntop00 sfacctd[199410]: INFO ( default_print/print ): *** Purging cache - END (PID: 85, QN: 4866/4866, ET: 0) *** Sep 17 17:06:02 ntop00 setroubleshoot[284450]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 539d53cf-5c9e-4ce3-8be1-3107489dd267 [x12] Sep 17 17:06:02 ntop00 setroubleshoot[284450]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 4a31fdf6-45fc-4da3-a3a4-03f8ff60af3d [x12] Sep 17 17:06:02 ntop00 setroubleshoot[284450]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 17 17:06:02 ntop00 setroubleshoot[284450]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l a19c0db5-f585-4fb9-a34e-811b7321a145 [x12] Sep 17 17:07:01 ntop00 nfacctd[199535]: INFO ( default_print/print ): *** Purging cache - START (PID: 85) *** Sep 17 17:07:01 ntop00 nfacctd[199535]: INFO ( default_print/print ): *** Purging cache - END (PID: 85, QN: 65/65, ET: 0) *** Sep 17 17:07:04 ntop00 setroubleshoot[284498]: SELinux is preventing /usr/local/sbin/nfacctd from append access on the file netflow.json. For complete SELinux messages run: sealert -l 41a326dc-aacd-478a-8da5-fdde097995a3 [x12] Sep 17 17:07:04 ntop00 setroubleshoot[284498]: failed to retrieve rpm info for path '/srv/pmacct/netflow.json': [x12] Sep 17 17:07:06 ntop00 setroubleshoot[284498]: SELinux is preventing /usr/local/sbin/nfacctd from open access on the file /srv/pmacct/netflow.json. For complete SELinux messages run: sealert -l c28a02e8-a028-434b-8b14-c5770a528750 [x12] Sep 17 17:07:08 ntop00 setroubleshoot[284498]: SELinux is preventing /usr/local/sbin/nfacctd from write access on the file netflow.json. For complete SELinux messages run: sealert -l 6ee8ccb3-78cd-4317-9099-2cda6c9e7195 [x12] Sep 17 17:07:10 ntop00 setroubleshoot[284498]: SELinux is preventing /usr/local/sbin/nfacctd from lock access on the file /srv/pmacct/netflow.json. For complete SELinux messages run: sealert -l 978c927f-8b4c-4fa4-8245-d7dd7f676027 [x12] Sep 17 17:11:01 ntop00 sfacctd[199410]: INFO ( default_print/print ): *** Purging cache - START (PID: 86) *** Sep 17 17:11:01 ntop00 sfacctd[199410]: INFO ( default_print/print ): *** Purging cache - END (PID: 86, QN: 4759/4759, ET: 0) *** Sep 17 17:12:01 ntop00 nfacctd[199535]: INFO ( default_print/print ): *** Purging cache - START (PID: 86) *** Sep 17 17:12:01 ntop00 nfacctd[199535]: INFO ( default_print/print ): *** Purging cache - END (PID: 86, QN: 44/44, ET: 0) *** Sep 17 17:16:01 ntop00 sfacctd[199410]: INFO ( default_print/print ): *** Purging cache - START (PID: 87) *** Sep 17 17:16:01 ntop00 sfacctd[199410]: INFO ( default_print/print ): *** Purging cache - END (PID: 87, QN: 5049/5049, ET: 0) *** Sep 17 17:17:01 ntop00 nfacctd[199535]: INFO ( default_print/print ): *** Purging cache - START (PID: 87) *** Sep 17 17:17:01 ntop00 nfacctd[199535]: INFO ( default_print/print ): *** Purging cache - END (PID: 87, QN: 66/66, ET: 0) *** Sep 17 17:21:01 ntop00 sfacctd[199410]: INFO ( default_print/print ): *** Purging cache - START (PID: 88) *** Sep 17 17:21:01 ntop00 sfacctd[199410]: INFO ( default_print/print ): *** Purging cache - END (PID: 88, QN: 4675/4675, ET: 0) *** Sep 17 17:22:01 ntop00 nfacctd[199535]: INFO ( default_print/print ): *** Purging cache - START (PID: 88) *** Sep 17 17:22:01 ntop00 nfacctd[199535]: INFO ( default_print/print ): *** Purging cache - END (PID: 88, QN: 51/51, ET: 0) *** Sep 17 17:26:01 ntop00 sfacctd[199410]: INFO ( default_print/print ): *** Purging cache - START (PID: 89) *** Sep 17 17:26:01 ntop00 sfacctd[199410]: INFO ( default_print/print ): *** Purging cache - END (PID: 89, QN: 4874/4874, ET: 0) *** Sep 17 17:27:01 ntop00 nfacctd[199535]: INFO ( default_print/print ): *** Purging cache - START (PID: 89) *** Sep 17 17:27:01 ntop00 nfacctd[199535]: INFO ( default_print/print ): *** Purging cache - END (PID: 89, QN: 54/54, ET: 0) *** Sep 17 17:31:01 ntop00 sfacctd[199410]: INFO ( default_print/print ): *** Purging cache - START (PID: 90) *** ... 27 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 17 17:09:08 outbound00.cs.umd.edu python3[1083528]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 17 17:13:07 outbound01.cs.umd.edu python3[3343085]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 17 17:09:33 sentry-docker00.cs.umd.edu systemd-udevd[2409365]: link_config: could not get ethtool features for veth9a695d4 Sep 17 17:09:33 sentry-docker00.cs.umd.edu systemd-udevd[2409365]: Could not set offload features of veth9a695d4: No such device Sep 17 17:09:33 sentry-docker00.cs.umd.edu systemd-udevd[2409367]: link_config: could not get ethtool features for veth7e75bff Sep 17 17:09:33 sentry-docker00.cs.umd.edu systemd-udevd[2409367]: Could not set offload features of veth7e75bff: No such device Sep 17 17:09:33 sentry-docker00.cs.umd.edu systemd-udevd[2409403]: Could not generate persistent MAC address for veth93d7df8: No such file or directory Sep 17 17:09:33 sentry-docker00.cs.umd.edu systemd-udevd[2409404]: Could not generate persistent MAC address for veth94bd482: No such file or directory Sep 17 17:09:34 sentry-docker00.cs.umd.edu systemd-udevd[2409422]: Could not generate persistent MAC address for vetha1a6306: No such file or directory Sep 17 17:09:34 sentry-docker00.cs.umd.edu systemd-udevd[2409407]: Could not generate persistent MAC address for vethbbeaae4: No such file or directory Sep 17 17:09:34 sentry-docker00.cs.umd.edu systemd-udevd[2409410]: Could not generate persistent MAC address for vethd1b2c99: No such file or directory Sep 17 17:09:34 sentry-docker00.cs.umd.edu systemd-udevd[2409421]: Could not generate persistent MAC address for veth3047637: No such file or directory Sep 17 17:09:34 sentry-docker00.cs.umd.edu systemd-udevd[2409414]: Could not generate persistent MAC address for veth285242b: No such file or directory Sep 17 17:09:34 sentry-docker00.cs.umd.edu systemd-udevd[2409418]: Could not generate persistent MAC address for veth02ab4d1: No such file or directory Sep 17 17:09:34 sentry-docker00.cs.umd.edu systemd-udevd[2409476]: Could not generate persistent MAC address for veth0f55bd9: No such file or directory Sep 17 17:09:34 sentry-docker00.cs.umd.edu systemd-udevd[2409478]: Could not generate persistent MAC address for veth24ecfac: No such file or directory Sep 17 17:29:41 sentry-docker00.cs.umd.edu systemd-udevd[2419032]: link_config: could not get ethtool features for veth285242b Sep 17 17:29:41 sentry-docker00.cs.umd.edu systemd-udevd[2419032]: Could not set offload features of veth285242b: No such device Sep 17 17:29:42 sentry-docker00.cs.umd.edu systemd-udevd[2419063]: Could not generate persistent MAC address for vethcea99bf: No such file or directory Sep 17 17:29:42 sentry-docker00.cs.umd.edu systemd-udevd[2419064]: Could not generate persistent MAC address for veth35273f7: No such file or directory Sep 17 17:29:42 sentry-docker00.cs.umd.edu systemd-udevd[2419067]: Could not generate persistent MAC address for vethf3c9f7d: No such file or directory Sep 17 17:29:42 sentry-docker00.cs.umd.edu systemd-udevd[2419075]: Could not generate persistent MAC address for veth39986a6: No such file or directory Sep 17 17:29:42 sentry-docker00.cs.umd.edu systemd-udevd[2419082]: Could not generate persistent MAC address for vethcc0db56: No such file or directory Sep 17 17:29:42 sentry-docker00.cs.umd.edu systemd-udevd[2419068]: Could not generate persistent MAC address for veth5ae1fcb: No such file or directory Sep 17 17:29:42 sentry-docker00.cs.umd.edu systemd-udevd[2419093]: Could not generate persistent MAC address for veth6116b8d: No such file or directory Sep 17 17:29:42 sentry-docker00.cs.umd.edu systemd-udevd[2419094]: Could not generate persistent MAC address for vethe84b6ba: No such file or directory Sep 17 17:29:42 sentry-docker00.cs.umd.edu systemd-udevd[2419119]: Could not generate persistent MAC address for vethb6d5ea1: No such file or directory Sep 17 17:29:42 sentry-docker00.cs.umd.edu systemd-udevd[2419120]: Could not generate persistent MAC address for veth1096be6: No such file or directory Sep 17 17:49:50 sentry-docker00.cs.umd.edu systemd-udevd[2428453]: link_config: could not get ethtool features for vethcc0db56 Sep 17 17:49:50 sentry-docker00.cs.umd.edu systemd-udevd[2428453]: Could not set offload features of vethcc0db56: No such device Sep 17 17:49:50 sentry-docker00.cs.umd.edu systemd-udevd[2428488]: Could not generate persistent MAC address for veth83fd905: No such file or directory Sep 17 17:49:50 sentry-docker00.cs.umd.edu systemd-udevd[2428489]: Could not generate persistent MAC address for vetha61a79e: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 17 17:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 17 17:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 17 17:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 17 17:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 17 17:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 17 17:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 17 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Sep 17 17:27:05 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (9 distinct, 9 total) == Sep 17 17:06:42 submit26-b9-f3 setroubleshoot[1634055]: 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 17 17:06:42 submit26-b9-f3 setroubleshoot[1634055]: 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 17 17:06:42 submit26-b9-f3 setroubleshoot[1634055]: 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 17 17:06:42 submit26-b9-f3 setroubleshoot[1634055]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.0GZCqw/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 17 17:06:42 submit26-b9-f3 setroubleshoot[1634055]: 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 17 17:06:42 submit26-b9-f3 setroubleshoot[1634055]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.0GZCqw. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 17 17:06:42 submit26-b9-f3 setroubleshoot[1634055]: 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 17 17:06:42 submit26-b9-f3 setroubleshoot[1634055]: 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 17 17:06:42 submit26-b9-f3 setroubleshoot[1634055]: 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 (10 distinct, 10 total) == Sep 17 17:24:46 submit26-b9-f4 setroubleshoot[1204130]: 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 17 17:24:46 submit26-b9-f4 setroubleshoot[1204130]: 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 17 17:24:46 submit26-b9-f4 setroubleshoot[1204130]: 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 17 17:24:46 submit26-b9-f4 setroubleshoot[1204130]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.qEeg5Z/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 17 17:24:46 submit26-b9-f4 setroubleshoot[1204130]: 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 17 17:24:46 submit26-b9-f4 setroubleshoot[1204130]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.qEeg5Z. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 17 17:24:46 submit26-b9-f4 setroubleshoot[1204130]: 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 17 17:24:46 submit26-b9-f4 setroubleshoot[1204130]: 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 17 17:24:46 submit26-b9-f4 setroubleshoot[1204130]: 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 Sep 17 17:48:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL