Command: /usr/local/sbin/syslog-digest.py Time : 0.0565s Status : exited 0 Output : Syslog digest — 2026-09-18 14:05 EDT Processed 2,911 lines, filtered 2,330 (80%). 581 unknown (189 distinct) from 18 host(s). == atif01.cs.umd.edu (1 distinct, 1 total) == Sep 18 13:33:59 atif01.cs.umd.edu kernel: net_ratelimit: 12 callbacks suppressed == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 18 13:49:36 b0b02.cs.umd.edu rustdesk[2540352]: cannot open display: == bale (5 distinct, 86 total) == Sep 18 13:05:59 bale setroubleshoot[562692]: failed to retrieve rpm info for /dev/nvme0 [x37] Sep 18 13:05:59 bale setroubleshoot[562692]: 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 [x12] Sep 18 13:06:02 bale setroubleshoot[562692]: 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 18 13:06:05 bale setroubleshoot[562692]: 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 18 13:06:17 bale setroubleshoot[563307]: 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 [x13] == csfw00a (1 distinct, 146 total) == Sep 18 13:04:14 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x146] == hazfs.cs.umd.edu (11 distinct, 66 total) == Sep 18 13:41:42 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Sep 18 13:41:42 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Sep 18 13:41:42 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Sep 18 13:41:42 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Sep 18 13:41:42 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Sep 18 13:41:42 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Sep 18 13:41:42 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Sep 18 13:41:42 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Sep 18 13:41:42 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Sep 18 13:41:42 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Sep 18 13:41:42 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Sep 18 13:54:09 idm00 named[4166701]: client @0x7f11a00618f8 10.73.240.42#54877: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 18 13:37:56 idmp0 named[1598691]: client @0x7f2d5002e408 10.73.240.43#56872: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (3 distinct, 3 total) == Sep 18 13:17:39 inbound01.cs.umd.edu krb5_child[3717430]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 18 13:20:41 inbound01.cs.umd.edu krb5_child[3717793]: Client 'test1@UMD.EDU' not found in Kerberos database Sep 18 13:26:38 inbound01.cs.umd.edu krb5_child[3720049]: Preauthentication failed == itmon02 (1 distinct, 3 total) == Sep 18 13:43:10 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3] == newhonors2 (1 distinct, 24 total) == Sep 18 13:13:03 newhonors2 dhcpcd[2815569]: dhcpcd is not running [x24] == ntop00 (100 distinct, 144 total) == Sep 18 13:05:18 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 130, QN: 7649/7649, ET: 17) *** Sep 18 13:05:18 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 130, QN: 72/72, ET: 17) *** Sep 18 13:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 131) *** Sep 18 13:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 131, QN: 7847/7847, ET: 0) *** Sep 18 13:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 131) *** Sep 18 13:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 131, QN: 72/72, ET: 0) *** Sep 18 13:08:02 ntop00 setroubleshoot[451912]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12] Sep 18 13:08:02 ntop00 setroubleshoot[451912]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12] Sep 18 13:08:02 ntop00 setroubleshoot[451912]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 18 13:08:02 ntop00 setroubleshoot[451912]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12] Sep 18 13:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 132) *** Sep 18 13:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 132) *** Sep 18 13:10:18 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 132, QN: 7703/7703, ET: 17) *** Sep 18 13:10:18 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 132, QN: 67/67, ET: 17) *** Sep 18 13:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 133) *** Sep 18 13:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 133, QN: 7849/7849, ET: 0) *** Sep 18 13:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 133) *** Sep 18 13:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 133, QN: 52/52, ET: 0) *** Sep 18 13:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 134) *** Sep 18 13:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 134) *** Sep 18 13:15:18 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 134, QN: 7621/7621, ET: 17) *** Sep 18 13:15:18 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 134, QN: 56/56, ET: 17) *** Sep 18 13:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 135) *** Sep 18 13:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 135, QN: 71/71, ET: 0) *** Sep 18 13:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 135) *** Sep 18 13:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 135, QN: 6877/6877, ET: 0) *** Sep 18 13:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 136) *** Sep 18 13:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 136) *** Sep 18 13:20:17 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 136, QN: 6958/6958, ET: 16) *** Sep 18 13:20:17 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 136, QN: 61/61, ET: 16) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 18 13:09:08 outbound00.cs.umd.edu python3[1369147]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 18 13:13:07 outbound01.cs.umd.edu python3[3627144]: ldapdb [x6] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 18 13:17:52 sentry-docker00.cs.umd.edu systemd-udevd[2978830]: link_config: could not get ethtool features for veth39db042 Sep 18 13:17:52 sentry-docker00.cs.umd.edu systemd-udevd[2978830]: Could not set offload features of veth39db042: No such device Sep 18 13:17:52 sentry-docker00.cs.umd.edu systemd-udevd[2978948]: Could not generate persistent MAC address for veth1912733: No such file or directory Sep 18 13:17:52 sentry-docker00.cs.umd.edu systemd-udevd[2978949]: Could not generate persistent MAC address for veth21b275a: No such file or directory Sep 18 13:17:52 sentry-docker00.cs.umd.edu systemd-udevd[2978974]: Could not generate persistent MAC address for vethbc7f165: No such file or directory Sep 18 13:17:52 sentry-docker00.cs.umd.edu systemd-udevd[2978975]: Could not generate persistent MAC address for veth9996bb6: No such file or directory Sep 18 13:17:53 sentry-docker00.cs.umd.edu systemd-udevd[2978993]: Could not generate persistent MAC address for veth68b398c: No such file or directory Sep 18 13:17:53 sentry-docker00.cs.umd.edu systemd-udevd[2978996]: Could not generate persistent MAC address for vethce33144: No such file or directory Sep 18 13:17:53 sentry-docker00.cs.umd.edu systemd-udevd[2978991]: Could not generate persistent MAC address for veth0f6a68c: No such file or directory Sep 18 13:17:53 sentry-docker00.cs.umd.edu systemd-udevd[2978994]: Could not generate persistent MAC address for vethc9fda74: No such file or directory Sep 18 13:17:53 sentry-docker00.cs.umd.edu systemd-udevd[2979066]: Could not generate persistent MAC address for vetha1cfac3: No such file or directory Sep 18 13:17:53 sentry-docker00.cs.umd.edu systemd-udevd[2979067]: Could not generate persistent MAC address for vethc3fd9b0: No such file or directory Sep 18 13:38:01 sentry-docker00.cs.umd.edu systemd-udevd[2988576]: link_config: could not get ethtool features for vethbc7f165 Sep 18 13:38:01 sentry-docker00.cs.umd.edu systemd-udevd[2988576]: Could not set offload features of vethbc7f165: No such device Sep 18 13:38:01 sentry-docker00.cs.umd.edu systemd-udevd[2988612]: Could not generate persistent MAC address for veth6f9beda: No such file or directory Sep 18 13:38:01 sentry-docker00.cs.umd.edu systemd-udevd[2988614]: Could not generate persistent MAC address for vethf6849f9: No such file or directory Sep 18 13:38:01 sentry-docker00.cs.umd.edu systemd-udevd[2988642]: Could not generate persistent MAC address for veth95f21fa: No such file or directory Sep 18 13:38:01 sentry-docker00.cs.umd.edu systemd-udevd[2988643]: Could not generate persistent MAC address for vetha770d6a: No such file or directory Sep 18 13:38:01 sentry-docker00.cs.umd.edu systemd-udevd[2988656]: Could not generate persistent MAC address for veth0d4bdcc: No such file or directory Sep 18 13:38:01 sentry-docker00.cs.umd.edu systemd-udevd[2988660]: Could not generate persistent MAC address for vethad34f16: No such file or directory Sep 18 13:38:01 sentry-docker00.cs.umd.edu systemd-udevd[2988670]: Could not generate persistent MAC address for vethedd46f5: No such file or directory Sep 18 13:38:01 sentry-docker00.cs.umd.edu systemd-udevd[2988671]: Could not generate persistent MAC address for vethd78635a: No such file or directory Sep 18 13:38:01 sentry-docker00.cs.umd.edu systemd-udevd[2988708]: Could not generate persistent MAC address for veth0636bed: No such file or directory Sep 18 13:38:01 sentry-docker00.cs.umd.edu systemd-udevd[2988671]: Could not generate persistent MAC address for veth2b01036: No such file or directory Sep 18 13:58:09 sentry-docker00.cs.umd.edu systemd-udevd[2998940]: Could not generate persistent MAC address for veth7fae770: No such file or directory Sep 18 13:58:09 sentry-docker00.cs.umd.edu systemd-udevd[2998941]: Could not generate persistent MAC address for vethf57ef6a: No such file or directory Sep 18 13:58:09 sentry-docker00.cs.umd.edu systemd-udevd[2998966]: Could not generate persistent MAC address for veth719c6b4: No such file or directory Sep 18 13:58:09 sentry-docker00.cs.umd.edu systemd-udevd[2998967]: Could not generate persistent MAC address for veth97a9172: No such file or directory Sep 18 13:58:09 sentry-docker00.cs.umd.edu systemd-udevd[2998985]: Could not generate persistent MAC address for veth15a1b79: No such file or directory Sep 18 13:58:09 sentry-docker00.cs.umd.edu systemd-udevd[2998986]: Could not generate persistent MAC address for veth3c1a9ec: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 18 13:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 18 13:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 18 13:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 18 13:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 18 13:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 18 13:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 18 13:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Sep 18 13:42:52 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (10 distinct, 11 total) == Sep 18 13:06:42 submit26-b9-f3 setroubleshoot[1793960]: 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 18 13:06:42 submit26-b9-f3 setroubleshoot[1793960]: 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 18 13:06:42 submit26-b9-f3 setroubleshoot[1793960]: 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 18 13:06:42 submit26-b9-f3 setroubleshoot[1793960]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.JkGfHg/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 18 13:06:42 submit26-b9-f3 setroubleshoot[1793960]: 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 18 13:06:42 submit26-b9-f3 setroubleshoot[1793960]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.JkGfHg. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 18 13:06:42 submit26-b9-f3 setroubleshoot[1793960]: 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 18 13:06:42 submit26-b9-f3 setroubleshoot[1793960]: 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 18 13:06:42 submit26-b9-f3 setroubleshoot[1793960]: 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 18 13:41:00 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 18 13:24:46 submit26-b9-f4 setroubleshoot[1306397]: 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 18 13:24:46 submit26-b9-f4 setroubleshoot[1306397]: 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 18 13:24:46 submit26-b9-f4 setroubleshoot[1306397]: 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 18 13:24:46 submit26-b9-f4 setroubleshoot[1306397]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.4sY8dv/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 18 13:24:46 submit26-b9-f4 setroubleshoot[1306397]: 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 18 13:24:46 submit26-b9-f4 setroubleshoot[1306397]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.4sY8dv. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 18 13:24:46 submit26-b9-f4 setroubleshoot[1306397]: 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 18 13:24:46 submit26-b9-f4 setroubleshoot[1306397]: 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 18 13:24:46 submit26-b9-f4 setroubleshoot[1306397]: 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