Command: /usr/local/sbin/syslog-digest.py
Time : 0.0522s
Status : exited 0
Output :
Syslog digest — 2026-09-19 21:05 EDT
Processed 2,716 lines, filtered 2,213 (81%). 503 unknown (176 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 20:51:23 b0b02.cs.umd.edu rustdesk[3014699]: cannot open display:
== bale (5 distinct, 92 total) ==
Sep 19 20:05:34 bale setroubleshoot[959961]: failed to retrieve rpm info for /dev/nvme0 [x40]
Sep 19 20:05:35 bale setroubleshoot[959961]: 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 19 20:05:37 bale setroubleshoot[959961]: 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 19 20:05:40 bale setroubleshoot[959961]: 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 19 20:05:52 bale setroubleshoot[960575]: 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 [x16]
== csfw00a (1 distinct, 125 total) ==
Sep 19 20:03:44 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x125]
== idm00 (1 distinct, 1 total) ==
Sep 19 20:53:59 idm00 named[4166701]: client @0x7f11a9407128 10.73.240.42#55237: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 20:37:57 idmp0 named[1598691]: client @0x7f2d28029f68 10.73.240.43#64411: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 5 total) ==
Sep 19 20:08:26 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x5]
== matrix (10 distinct, 14 total) ==
Sep 19 20:13:49 matrix sshd[2625570]: error: Refused by certificate options [x4]
Sep 19 20:45:28 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2644723, but reception only permitted for main PID 720
Sep 19 20:45:28 matrix networkctl[2644887]: Interface "veth3fcb00b" not found.
Sep 19 20:45:28 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2644887, but reception only permitted for main PID 720 [x2]
Sep 19 20:45:29 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2644967, but reception only permitted for main PID 720
Sep 19 20:45:29 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2644972, but reception only permitted for main PID 720
Sep 19 20:45:29 matrix networkctl[2644984]: Interface "vethf9567cd" not found.
Sep 19 20:45:29 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2645101, but reception only permitted for main PID 720
Sep 19 20:45:29 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2645280, but reception only permitted for main PID 720
Sep 19 20:45:44 matrix kernel: kauditd_printk_skb: 8 callbacks suppressed
== newhonors2 (1 distinct, 24 total) ==
Sep 19 20:13:03 newhonors2 dhcpcd[2873832]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 19 20:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 298) ***
Sep 19 20:05:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 6533/6533, ET: 22) ***
Sep 19 20:05:23 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 48/48, ET: 22) ***
Sep 19 20:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 299) ***
Sep 19 20:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 5692/5692, ET: 0) ***
Sep 19 20:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 299) ***
Sep 19 20:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 54/54, ET: 0) ***
Sep 19 20:08:03 ntop00 setroubleshoot[698381]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 20:08:03 ntop00 setroubleshoot[698381]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 20:08:03 ntop00 setroubleshoot[698381]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 20:08:03 ntop00 setroubleshoot[698381]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 20:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) ***
Sep 19 20:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) ***
Sep 19 20:10:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 5732/5732, ET: 20) ***
Sep 19 20:10:21 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 50/50, ET: 20) ***
Sep 19 20:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 301) ***
Sep 19 20:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 6174/6174, ET: 0) ***
Sep 19 20:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 301) ***
Sep 19 20:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 54/54, ET: 0) ***
Sep 19 20:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) ***
Sep 19 20:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) ***
Sep 19 20:15:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 5971/5971, ET: 22) ***
Sep 19 20:15:23 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 53/53, ET: 22) ***
Sep 19 20:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 303) ***
Sep 19 20:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 5645/5645, ET: 0) ***
Sep 19 20:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 303) ***
Sep 19 20:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 39/39, ET: 0) ***
Sep 19 20:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) ***
Sep 19 20:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) ***
Sep 19 20:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 304, QN: 41/41, ET: 0) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 20:09:09 outbound00.cs.umd.edu python3[1806558]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 20:13:06 outbound01.cs.umd.edu python3[4065542]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852951]: link_config: could not get ethtool features for vetha660928
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852951]: Could not set offload features of vetha660928: No such device
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852985]: Could not generate persistent MAC address for veth1ef7a26: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852986]: Could not generate persistent MAC address for veth0531380: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852989]: Could not generate persistent MAC address for vethabe7f2c: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852997]: Could not generate persistent MAC address for vethf512cf0: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852998]: Could not generate persistent MAC address for vethcaeb6e9: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853009]: Could not generate persistent MAC address for veth2a74ba5: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853015]: Could not generate persistent MAC address for vethee1e149: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853016]: Could not generate persistent MAC address for vethcc2b2cf: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853034]: Could not generate persistent MAC address for vethefe56f4: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853029]: Could not generate persistent MAC address for veth52eca01: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862351]: link_config: could not get ethtool features for vethabe7f2c
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862351]: Could not set offload features of vethabe7f2c: No such device
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862401]: Could not generate persistent MAC address for veth50818d2: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862402]: Could not generate persistent MAC address for vethc951973: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862405]: Could not generate persistent MAC address for veth64b2976: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862406]: Could not generate persistent MAC address for veth8ba369b: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862416]: Could not generate persistent MAC address for vethf07cf1f: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862411]: Could not generate persistent MAC address for vethfe9221a: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862424]: Could not generate persistent MAC address for veth832e528: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862410]: Could not generate persistent MAC address for veth021e78d: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862487]: Could not generate persistent MAC address for vethc6622c9: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862490]: Could not generate persistent MAC address for veth9c6631c: No such file or directory
Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871824]: link_config: could not get ethtool features for vethc6622c9
Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871824]: Could not set offload features of vethc6622c9: No such device
Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871846]: Could not generate persistent MAC address for vetha964c49: No such file or directory
Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871847]: Could not generate persistent MAC address for veth622f661: No such file or directory
Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871865]: Could not generate persistent MAC address for veth26f7273: No such file or directory
Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871852]: Could not generate persistent MAC address for vethd627946: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 20:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 20:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 20:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 20:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (1 distinct, 1 total) ==
Sep 19 20:44:38 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.tVmNgA/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.tVmNgA. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c
Sep 19 20:21:58 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0534s
Status : exited 0
Output :
Syslog digest — 2026-09-19 20:05 EDT
Processed 2,695 lines, filtered 2,146 (79%). 549 unknown (172 distinct) from 14 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 19:51:19 b0b02.cs.umd.edu rustdesk[2999309]: cannot open display:
== bale (5 distinct, 88 total) ==
Sep 19 19:05:15 bale setroubleshoot[947192]: failed to retrieve rpm info for /dev/nvme0 [x38]
Sep 19 19:05:16 bale setroubleshoot[947192]: 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 19 19:05:18 bale setroubleshoot[947192]: 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 19 19:05:21 bale setroubleshoot[947192]: 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 19 19:05:33 bale setroubleshoot[947818]: 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, 130 total) ==
Sep 19 19:03:40 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x130]
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 19 19:53:59 idm00 named[4166701]: client @0x7f11a93e2ef8 10.73.240.42#49765: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 19:37:56 idmp0 named[1598691]: client @0x7f2d4802a308 10.73.240.43#60602: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 19 19:23:08 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3]
== newhonors2 (1 distinct, 24 total) ==
Sep 19 19:13:02 newhonors2 dhcpcd[2871958]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 19 19:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 274) ***
Sep 19 19:05:39 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 274, QN: 10366/10366, ET: 38) ***
Sep 19 19:05:39 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 274, QN: 45/45, ET: 38) ***
Sep 19 19:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 275) ***
Sep 19 19:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 275, QN: 9224/9224, ET: 0) ***
Sep 19 19:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 275) ***
Sep 19 19:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 275, QN: 55/55, ET: 0) ***
Sep 19 19:08:02 ntop00 setroubleshoot[690486]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 19:08:02 ntop00 setroubleshoot[690486]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 19:08:03 ntop00 setroubleshoot[690486]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 19:08:03 ntop00 setroubleshoot[690486]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 19:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 276) ***
Sep 19 19:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 276) ***
Sep 19 19:10:31 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 276, QN: 7892/7892, ET: 30) ***
Sep 19 19:10:31 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 276, QN: 67/67, ET: 30) ***
Sep 19 19:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 277) ***
Sep 19 19:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 277, QN: 12029/12029, ET: 0) ***
Sep 19 19:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 277) ***
Sep 19 19:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 277, QN: 65/65, ET: 0) ***
Sep 19 19:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 278) ***
Sep 19 19:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 278) ***
Sep 19 19:15:50 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 278, QN: 13432/13432, ET: 49) ***
Sep 19 19:15:50 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 278, QN: 64/64, ET: 49) ***
Sep 19 19:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 279) ***
Sep 19 19:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 279, QN: 10955/10955, ET: 0) ***
Sep 19 19:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 279) ***
Sep 19 19:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 279, QN: 59/59, ET: 0) ***
Sep 19 19:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 280) ***
Sep 19 19:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 280) ***
Sep 19 19:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 280, QN: 60/60, ET: 0) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 19:09:09 outbound00.cs.umd.edu python3[1792633]: ldapdb [x6]
== outbound01.cs.umd.edu (3 distinct, 8 total) ==
Sep 19 19:13:06 outbound01.cs.umd.edu python3[4051555]: ldapdb [x6]
Sep 19 19:25:50 outbound01.cs.umd.edu krb5_child[4055017]: Preauthentication failed
Sep 19 19:29:14 outbound01.cs.umd.edu krb5_child[4055583]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824649]: link_config: could not get ethtool features for veth2469b9d
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824649]: Could not set offload features of veth2469b9d: No such device
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824685]: Could not generate persistent MAC address for vethfc5f999: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824686]: Could not generate persistent MAC address for vethed6ebbd: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824689]: Could not generate persistent MAC address for vethddac317: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824690]: Could not generate persistent MAC address for veth684ad41: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824709]: Could not generate persistent MAC address for veth5a8e00e: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824686]: Could not generate persistent MAC address for veth0b92870: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824715]: Could not generate persistent MAC address for veth388cad8: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824716]: Could not generate persistent MAC address for vethf1fca53: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824734]: Could not generate persistent MAC address for veth61f1a52: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824726]: Could not generate persistent MAC address for vethc00aaae: No such file or directory
Sep 19 19:30:21 sentry-docker00.cs.umd.edu systemd-udevd[3834064]: link_config: could not get ethtool features for vethfc5f999
Sep 19 19:30:21 sentry-docker00.cs.umd.edu systemd-udevd[3834064]: Could not set offload features of vethfc5f999: No such device
Sep 19 19:30:21 sentry-docker00.cs.umd.edu systemd-udevd[3834099]: Could not generate persistent MAC address for vethf88d4e7: No such file or directory
Sep 19 19:30:21 sentry-docker00.cs.umd.edu systemd-udevd[3834100]: Could not generate persistent MAC address for veth4f7910b: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834103]: Could not generate persistent MAC address for vethcae1808: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834104]: Could not generate persistent MAC address for veth2d80353: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834115]: Could not generate persistent MAC address for veth2bc5cc2: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834113]: Could not generate persistent MAC address for veth05dd065: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834129]: Could not generate persistent MAC address for veth5b9d016: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834130]: Could not generate persistent MAC address for veth78560f3: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834148]: Could not generate persistent MAC address for veth0af52bb: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834136]: Could not generate persistent MAC address for veth6ee54cc: No such file or directory
Sep 19 19:50:29 sentry-docker00.cs.umd.edu systemd-udevd[3843111]: link_config: could not get ethtool features for veth05dd065
Sep 19 19:50:29 sentry-docker00.cs.umd.edu systemd-udevd[3843111]: Could not set offload features of veth05dd065: No such device
Sep 19 19:50:30 sentry-docker00.cs.umd.edu systemd-udevd[3843118]: link_config: could not get ethtool features for vethf88d4e7
Sep 19 19:50:30 sentry-docker00.cs.umd.edu systemd-udevd[3843118]: Could not set offload features of vethf88d4e7: No such device
Sep 19 19:50:30 sentry-docker00.cs.umd.edu systemd-udevd[3843233]: Could not generate persistent MAC address for veth08e65f2: No such file or directory
Sep 19 19:50:30 sentry-docker00.cs.umd.edu systemd-udevd[3843234]: Could not generate persistent MAC address for veth4628bdc: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 19:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 19:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 19:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 19:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 19:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 19:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 19:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== teaching-awards (1 distinct, 1 total) ==
Sep 19 19:46:28 teaching-awards krb5_child[1118941]: Client 'admin(a)UMD.EDU' not found in Kerberos database
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0526s
Status : exited 0
Output :
Syslog digest — 2026-09-19 19:05 EDT
Processed 2,553 lines, filtered 2,043 (80%). 510 unknown (184 distinct) from 19 host(s).
== b0b02.cs.umd.edu (4 distinct, 4 total) ==
Sep 19 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-19T22:10:59.426919828Z" level=info msg="PurgeUploads starting: olderThan=2026-09-12 22:10:59.426842535 +0000 UTC m=+4063020.186770847, actuallyDelete=true"
Sep 19 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-19T22:10:59.427410979Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1"
Sep 19 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-19T22:10:59.427430854Z" level=info msg="Starting upload purge in 24h0m0s" go.version=go1.11.2 instance.id=68469aa4-7857-4a69-bf12-c2190b4f96d8 service=registry version=v2.7.1
Sep 19 18:51:16 b0b02.cs.umd.edu rustdesk[2984122]: cannot open display:
== bale (5 distinct, 87 total) ==
Sep 19 18:06:04 bale setroubleshoot[934499]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 19 18:06:05 bale setroubleshoot[934499]: 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 19 18:06:07 bale setroubleshoot[934499]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13]
Sep 19 18:06:10 bale setroubleshoot[934499]: 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 [x11]
Sep 19 18:06:22 bale setroubleshoot[935113]: 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, 128 total) ==
Sep 19 18:04:09 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x128]
== idm00 (1 distinct, 1 total) ==
Sep 19 18:53:59 idm00 named[4166701]: client @0x7f11980184a8 10.73.240.42#64044: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 18:37:56 idmp0 named[1598691]: client @0x7f2d3c076558 10.73.240.43#63053: update '73.10.in-addr.arpa/IN' denied
== irb2156 (1 distinct, 1 total) ==
Sep 19 18:08:41 irb2156 systemd-tmpfiles[572914]: Opening file "/tmp/org.chromium.Chromium.pnSOAt/SingletonSocket" failed, proceeding without lock: No such device or address
== itmon02 (1 distinct, 2 total) ==
Sep 19 18:18:25 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2]
== munin (2 distinct, 4 total) ==
Sep 19 18:28:59 munin sudo[405059]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 19 18:28:59 munin sudo[405059]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== neoavion (1 distinct, 1 total) ==
Sep 19 18:32:35 neoavion krb5_child[3630822]: No credentials cache found
== newhonors2 (1 distinct, 24 total) ==
Sep 19 18:13:03 newhonors2 dhcpcd[2870113]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 19 18:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 250) ***
Sep 19 18:05:29 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 250, QN: 7481/7481, ET: 28) ***
Sep 19 18:05:29 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 250, QN: 45/45, ET: 28) ***
Sep 19 18:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 251) ***
Sep 19 18:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 251, QN: 9416/9416, ET: 0) ***
Sep 19 18:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 251) ***
Sep 19 18:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 251, QN: 58/58, ET: 0) ***
Sep 19 18:08:02 ntop00 setroubleshoot[682597]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 18:08:02 ntop00 setroubleshoot[682597]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 18:08:03 ntop00 setroubleshoot[682597]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 18:08:03 ntop00 setroubleshoot[682597]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 18:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 252) ***
Sep 19 18:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 252) ***
Sep 19 18:10:29 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 252, QN: 8306/8306, ET: 28) ***
Sep 19 18:10:29 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 252, QN: 71/71, ET: 28) ***
Sep 19 18:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 253) ***
Sep 19 18:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 253, QN: 14544/14544, ET: 0) ***
Sep 19 18:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 253) ***
Sep 19 18:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 253, QN: 82/82, ET: 0) ***
Sep 19 18:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 254) ***
Sep 19 18:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 254) ***
Sep 19 18:16:07 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 254, QN: 19635/19635, ET: 66) ***
Sep 19 18:16:08 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 254, QN: 78/78, ET: 67) ***
Sep 19 18:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 255) ***
Sep 19 18:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 255, QN: 24509/24509, ET: 0) ***
Sep 19 18:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 255) ***
Sep 19 18:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 255, QN: 68/68, ET: 1) ***
Sep 19 18:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 256) ***
Sep 19 18:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 256) ***
Sep 19 18:21:33 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 256, QN: 26844/26844, ET: 92) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 18:09:09 outbound00.cs.umd.edu python3[1778552]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 18:13:06 outbound01.cs.umd.edu python3[4037632]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796075]: link_config: could not get ethtool features for veth69ad032
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796075]: Could not set offload features of veth69ad032: No such device
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796106]: Could not generate persistent MAC address for veth99cdb86: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796107]: Could not generate persistent MAC address for veth97ebd42: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796110]: Could not generate persistent MAC address for vethe7f36d9: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796111]: Could not generate persistent MAC address for veth1c82051: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796111]: Could not generate persistent MAC address for veth20702d5: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796121]: Could not generate persistent MAC address for veth63f8e31: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796122]: Could not generate persistent MAC address for vethcb15d1a: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796129]: Could not generate persistent MAC address for vetha53d8f6: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796152]: Could not generate persistent MAC address for veth5fd93ec: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796151]: Could not generate persistent MAC address for veth4c6561c: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805464]: link_config: could not get ethtool features for vethe7f36d9
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805464]: Could not set offload features of vethe7f36d9: No such device
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805537]: Could not generate persistent MAC address for vethc5f68d5: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805538]: Could not generate persistent MAC address for vethd3bc0eb: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805541]: Could not generate persistent MAC address for veth875e42f: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805542]: Could not generate persistent MAC address for veth3acfc7d: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805565]: Could not generate persistent MAC address for vethf2f220c: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805566]: Could not generate persistent MAC address for vethae3f43a: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805611]: Could not generate persistent MAC address for veth2be16b5: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805622]: Could not generate persistent MAC address for vetha339108: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805639]: Could not generate persistent MAC address for veth4674d73: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805662]: Could not generate persistent MAC address for vethb8400f8: No such file or directory
Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814913]: link_config: could not get ethtool features for veth875e42f
Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814913]: Could not set offload features of veth875e42f: No such device
Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814982]: Could not generate persistent MAC address for vethfbbb2b4: No such file or directory
Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814983]: Could not generate persistent MAC address for veth96a93c2: No such file or directory
Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814986]: Could not generate persistent MAC address for vethb85b833: No such file or directory
Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814995]: Could not generate persistent MAC address for veth21c3f98: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 18:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 18:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 18:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 18:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (9 distinct, 12 total) ==
Sep 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c
Sep 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36
Sep 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6 [x2]
Sep 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.R33FVJ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d [x2]
Sep 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee [x2]
Sep 19 18:25:54 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.R33FVJ. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 19 18:25:54 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d
Sep 19 18:25:54 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9
Sep 19 18:25:54 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848
== submit26-b9-f2 (10 distinct, 13 total) ==
Sep 19 18:06:48 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6
Sep 19 18:06:48 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a
Sep 19 18:06:48 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 [x2]
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Cd0ZAk/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 [x2]
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Cd0ZAk. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af [x2]
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.F0sZXe/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
== submit26-b9-f3 (1 distinct, 1 total) ==
Sep 19 18:08:07 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 19 18:23:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0535s
Status : exited 0
Output :
Syslog digest — 2026-09-19 18:05 EDT
Processed 2,788 lines, filtered 2,268 (81%). 520 unknown (179 distinct) from 17 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 17:51:14 b0b02.cs.umd.edu rustdesk[2968958]: cannot open display:
== bale (5 distinct, 89 total) ==
Sep 19 17:06:07 bale setroubleshoot[921607]: failed to retrieve rpm info for /dev/nvme0 [x38]
Sep 19 17:06:07 bale setroubleshoot[921607]: 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 19 17:06:10 bale setroubleshoot[921607]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13]
Sep 19 17:06:13 bale setroubleshoot[921607]: 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 [x11]
Sep 19 17:06:25 bale setroubleshoot[922223]: 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, 133 total) ==
Sep 19 17:04:08 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x133]
== frozone (1 distinct, 1 total) ==
Sep 19 17:35:38 frozone systemd-tmpfiles[2107225]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted
== idm00 (1 distinct, 1 total) ==
Sep 19 17:53:58 idm00 named[4166701]: client @0x7f11a93cbc38 10.73.240.42#65160: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 17:37:56 idmp0 named[1598691]: client @0x7f2d24019b88 10.73.240.43#53179: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 19 17:38:08 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3]
== newhonors2 (1 distinct, 24 total) ==
Sep 19 17:13:03 newhonors2 dhcpcd[2868272]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 19 17:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 226) ***
Sep 19 17:05:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 226, QN: 6001/6001, ET: 20) ***
Sep 19 17:05:21 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 226, QN: 73/73, ET: 20) ***
Sep 19 17:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 227) ***
Sep 19 17:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 227, QN: 6109/6109, ET: 0) ***
Sep 19 17:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 227) ***
Sep 19 17:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 227, QN: 67/67, ET: 0) ***
Sep 19 17:08:02 ntop00 setroubleshoot[674562]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 17:08:02 ntop00 setroubleshoot[674562]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 17:08:02 ntop00 setroubleshoot[674562]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 17:08:02 ntop00 setroubleshoot[674562]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 17:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 228) ***
Sep 19 17:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 228) ***
Sep 19 17:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 228, QN: 65/65, ET: 0) ***
Sep 19 17:10:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 228, QN: 5973/5973, ET: 20) ***
Sep 19 17:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 229) ***
Sep 19 17:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 229, QN: 6089/6089, ET: 0) ***
Sep 19 17:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 229) ***
Sep 19 17:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 229, QN: 60/60, ET: 0) ***
Sep 19 17:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 230) ***
Sep 19 17:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 230) ***
Sep 19 17:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 230, QN: 49/49, ET: 0) ***
Sep 19 17:15:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 230, QN: 6390/6390, ET: 22) ***
Sep 19 17:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 231) ***
Sep 19 17:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 231) ***
Sep 19 17:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 231, QN: 57/57, ET: 0) ***
Sep 19 17:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 231, QN: 6228/6228, ET: 0) ***
Sep 19 17:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 232) ***
Sep 19 17:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 232) ***
Sep 19 17:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 232, QN: 51/51, ET: 0) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 17:09:09 outbound00.cs.umd.edu python3[1764603]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 17:13:07 outbound01.cs.umd.edu python3[4023465]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767523]: link_config: could not get ethtool features for vethbdd6d47
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767523]: Could not set offload features of vethbdd6d47: No such device
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767569]: Could not generate persistent MAC address for veth7edc101: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767570]: Could not generate persistent MAC address for vethe43aa76: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767573]: Could not generate persistent MAC address for veth93a15e1: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767574]: Could not generate persistent MAC address for veth930beff: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767597]: Could not generate persistent MAC address for veth704f1a2: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767598]: Could not generate persistent MAC address for vethde2c127: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767623]: Could not generate persistent MAC address for vethf756fc7: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767624]: Could not generate persistent MAC address for veth92101ae: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767642]: Could not generate persistent MAC address for veth46ab34f: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767627]: Could not generate persistent MAC address for veth2413952: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777207]: link_config: could not set ethtool features for veth93a15e1
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777207]: Could not set offload features of veth93a15e1: Operation not permitted
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777236]: Could not generate persistent MAC address for veth882bb97: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777237]: Could not generate persistent MAC address for veth9324a28: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777240]: Could not generate persistent MAC address for veth3ea44f0: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777241]: Could not generate persistent MAC address for vethd2e57e4: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777264]: Could not generate persistent MAC address for vethaaae73e: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777265]: Could not generate persistent MAC address for vethe096ac7: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777274]: Could not generate persistent MAC address for veth55cbef3: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777280]: Could not generate persistent MAC address for veth7014535: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777274]: Could not generate persistent MAC address for vethd3f3f7d: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777280]: Could not generate persistent MAC address for veth00e543d: No such file or directory
Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786632]: link_config: could not get ethtool features for vethd3f3f7d
Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786632]: Could not set offload features of vethd3f3f7d: No such device
Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786669]: Could not generate persistent MAC address for vethed42401: No such file or directory
Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786670]: Could not generate persistent MAC address for vethc20fa18: No such file or directory
Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786695]: Could not generate persistent MAC address for vethf5b5d57: No such file or directory
Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786696]: Could not generate persistent MAC address for veth9404756: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 17:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 17:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 17:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 17:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 17:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 17:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 4 total) ==
Sep 19 17:06:54 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f2 (1 distinct, 5 total) ==
Sep 19 17:18:07 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f3 (10 distinct, 14 total) ==
Sep 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.NmGr6G/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.NmGr6G. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 19 17:06:43 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:06:43 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:06:43 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:14:33 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f4 (10 distinct, 14 total) ==
Sep 19 17:11:00 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.GE5aXs/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GE5aXs. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0563s
Status : exited 0
Output :
Syslog digest — 2026-09-19 17:05 EDT
Processed 2,777 lines, filtered 2,272 (81%). 505 unknown (178 distinct) from 21 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 16:51:11 b0b02.cs.umd.edu rustdesk[2953796]: cannot open display:
== bale (5 distinct, 84 total) ==
Sep 19 16:06:06 bale setroubleshoot[908886]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 19 16:06:07 bale setroubleshoot[908886]: 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 19 16:06:09 bale setroubleshoot[908886]: 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 19 16:06:12 bale setroubleshoot[908886]: 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 19 16:06:24 bale setroubleshoot[909501]: 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 [x12]
== csfw00a (1 distinct, 133 total) ==
Sep 19 16:03:44 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x133]
== gle-dind04 (2 distinct, 2 total) ==
Sep 19 16:09:31 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 19 16:09:31 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== idm00 (1 distinct, 1 total) ==
Sep 19 16:53:58 idm00 named[4166701]: client @0x7f11a9462a18 10.73.240.42#57075: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 16:37:56 idmp0 named[1598691]: client @0x7f2d2401e448 10.73.240.43#50318: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 19 16:18:58 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3]
== jaws.cs.umd.edu (3 distinct, 3 total) ==
Sep 19 17:01:33 jaws.cs.umd.edu systemd-coredump[2432034]: Process 2432019 (podman) of user 0 dumped core.#012#012Stack trace of thread 2432019:#012#0 0x00005652d38fc46e internal/runtime/syscall/linux.Syscall6 (podman + 0x48c46e)#012#1 0x00005652d39dc326 syscall.Syscall (podman + 0x56c326)#012#2 0x00005652d39dced0 syscall.Syscall.abi0 (podman + 0x56ced0)#012#3 0x00005652d3b4736e github.com/containers/podman/vendor/golang.org/x/sys/unix.OpenTree (podman + 0x6d736e)#012#4 0x00005652d41a444b github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd3444b)#012#5 0x00005652d41a4354 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34354)#012#6 0x00005652d398ff8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#7 0x00005652d398feb9 sync.(*Once).Do (podman + 0x51feb9)#012#8 0x00005652d41a42c5
github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd342c5)#012#9 0x00005652d41a58e2 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd358e2)#012#10 0x00005652d41a5cf3 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd35cf3)#012#11 0x00005652d41a4e1c github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34e1c)#012#12 0x00005652d41a4858 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34858)#012#13 0x00005652d398ff8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#14 0x00005652d398feb9 sync.(*Once).Do
(podman + 0x51feb9)#012#15 0x00005652d41a47c5 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd347c5)#012#16 0x00005652d41a5c9a github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd35c9a)#012#17 0x00005652d41ac84e github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3c84e)#012#18 0x00005652d41acd38 github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3cd38)#012#19 0x00005652d41abadf github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3badf)#012#20 0x00005652d41abd73 github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3bd73)#012#21 0x00005
652d43a56cb github.com/containers/podman/vendor/go.podman.io/common/pkg/config.defaultC… (podman + 0xf356cb)#012#22 0x00005652d43a90b2 github.com/containers/podman/vendor/go.podman.io/common/pkg/config.newLocked (podman + 0xf390b2)#012#23 0x00005652d43a8da5 github.com/containers/podman/vendor/go.podman.io/common/pkg/config.New (podman + 0xf38da5)#012#24 0x00005652d4b257d3 github.com/containers/podman/cmd/podman/registry.newPodmanConfig (podman + 0x16b57d3)#012#25 0x00005652d398ff8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#26 0x00005652d4b46550 github.com/containers/podman/cmd/podman/common.init (podman + 0x16d6550)#012#27 0x00005652d3955af7 runtime.doInit1 (podman + 0x4e5af7)#012#28 0x00005652d3946030 runtime.main (podman + 0x4d6030)#012#29 0x00005652d3986061 runtime.goexit.abi0 (podman + 0x516061)#012ELF object binary architecture: AMD x86-64
Sep 19 17:01:35 jaws.cs.umd.edu systemd-coredump[2432056]: Process 2432041 (podman) of user 0 dumped core.#012#012Stack trace of thread 2432041:#012#0 0x0000559f60ecd46e internal/runtime/syscall/linux.Syscall6 (podman + 0x48c46e)#012#1 0x0000559f60fad326 syscall.Syscall (podman + 0x56c326)#012#2 0x0000559f60faded0 syscall.Syscall.abi0 (podman + 0x56ced0)#012#3 0x0000559f6111836e github.com/containers/podman/vendor/golang.org/x/sys/unix.OpenTree (podman + 0x6d736e)#012#4 0x0000559f6177544b github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd3444b)#012#5 0x0000559f61775354 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34354)#012#6 0x0000559f60f60f8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#7 0x0000559f60f60eb9 sync.(*Once).Do (podman + 0x51feb9)#012#8 0x0000559f617752c5
github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd342c5)#012#9 0x0000559f617768e2 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd358e2)#012#10 0x0000559f61776cf3 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd35cf3)#012#11 0x0000559f61775e1c github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34e1c)#012#12 0x0000559f61775858 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34858)#012#13 0x0000559f60f60f8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#14 0x0000559f60f60eb9 sync.(*Once).Do
(podman + 0x51feb9)#012#15 0x0000559f617757c5 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd347c5)#012#16 0x0000559f61776c9a github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd35c9a)#012#17 0x0000559f6177d84e github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3c84e)#012#18 0x0000559f6177dd38 github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3cd38)#012#19 0x0000559f6177cadf github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3badf)#012#20 0x0000559f6177cd73 github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3bd73)#012#21 0x00005
59f619766cb github.com/containers/podman/vendor/go.podman.io/common/pkg/config.defaultC… (podman + 0xf356cb)#012#22 0x0000559f6197a0b2 github.com/containers/podman/vendor/go.podman.io/common/pkg/config.newLocked (podman + 0xf390b2)#012#23 0x0000559f61979da5 github.com/containers/podman/vendor/go.podman.io/common/pkg/config.New (podman + 0xf38da5)#012#24 0x0000559f620f67d3 github.com/containers/podman/cmd/podman/registry.newPodmanConfig (podman + 0x16b57d3)#012#25 0x0000559f60f60f8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#26 0x0000559f62117550 github.com/containers/podman/cmd/podman/common.init (podman + 0x16d6550)#012#27 0x0000559f60f26af7 runtime.doInit1 (podman + 0x4e5af7)#012#28 0x0000559f60f17030 runtime.main (podman + 0x4d6030)#012#29 0x0000559f60f57061 runtime.goexit.abi0 (podman + 0x516061)#012ELF object binary architecture: AMD x86-64
Sep 19 17:01:36 jaws.cs.umd.edu systemd-coredump[2432079]: Process 2432062 (podman) of user 0 dumped core.#012#012Stack trace of thread 2432062:#012#0 0x00005626f83a346e internal/runtime/syscall/linux.Syscall6 (podman + 0x48c46e)#012#1 0x00005626f8483326 syscall.Syscall (podman + 0x56c326)#012#2 0x00005626f8483ed0 syscall.Syscall.abi0 (podman + 0x56ced0)#012#3 0x00005626f85ee36e github.com/containers/podman/vendor/golang.org/x/sys/unix.OpenTree (podman + 0x6d736e)#012#4 0x00005626f8c4b44b github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd3444b)#012#5 0x00005626f8c4b354 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34354)#012#6 0x00005626f8436f8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#7 0x00005626f8436eb9 sync.(*Once).Do (podman + 0x51feb9)#012#8 0x00005626f8c4b2c5
github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd342c5)#012#9 0x00005626f8c4c8e2 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd358e2)#012#10 0x00005626f8c4ccf3 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd35cf3)#012#11 0x00005626f8c4be1c github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34e1c)#012#12 0x00005626f8c4b858 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34858)#012#13 0x00005626f8436f8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#14 0x00005626f8436eb9 sync.(*Once).Do
(podman + 0x51feb9)#012#15 0x00005626f8c4b7c5 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd347c5)#012#16 0x00005626f8c4cc9a github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd35c9a)#012#17 0x00005626f8c5384e github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3c84e)#012#18 0x00005626f8c53d38 github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3cd38)#012#19 0x00005626f8c52adf github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3badf)#012#20 0x00005626f8c52d73 github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3bd73)#012#21 0x00005
626f8e4c6cb github.com/containers/podman/vendor/go.podman.io/common/pkg/config.defaultC… (podman + 0xf356cb)#012#22 0x00005626f8e500b2 github.com/containers/podman/vendor/go.podman.io/common/pkg/config.newLocked (podman + 0xf390b2)#012#23 0x00005626f8e4fda5 github.com/containers/podman/vendor/go.podman.io/common/pkg/config.New (podman + 0xf38da5)#012#24 0x00005626f95cc7d3 github.com/containers/podman/cmd/podman/registry.newPodmanConfig (podman + 0x16b57d3)#012#25 0x00005626f8436f8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#26 0x00005626f95ed550 github.com/containers/podman/cmd/podman/common.init (podman + 0x16d6550)#012#27 0x00005626f83fcaf7 runtime.doInit1 (podman + 0x4e5af7)#012#28 0x00005626f83ed030 runtime.main (podman + 0x4d6030)#012#29 0x00005626f842d061 runtime.goexit.abi0 (podman + 0x516061)#012ELF object binary architecture: AMD x86-64
== netman.cs.umd.edu (1 distinct, 2 total) ==
Sep 19 17:03:52 netman.cs.umd.edu krb5_child[2475018]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 19 16:13:02 newhonors2 dhcpcd[2866432]: dhcpcd is not running [x24]
== ntop00 (101 distinct, 145 total) ==
Sep 19 16:05:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 202) ***
Sep 19 16:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 202) ***
Sep 19 16:05:34 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 202, QN: 10149/10149, ET: 33) ***
Sep 19 16:05:34 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 202, QN: 62/62, ET: 33) ***
Sep 19 16:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 203) ***
Sep 19 16:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 203, QN: 9947/9947, ET: 0) ***
Sep 19 16:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 203) ***
Sep 19 16:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 203, QN: 49/49, ET: 0) ***
Sep 19 16:08:02 ntop00 setroubleshoot[666696]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 16:08:02 ntop00 setroubleshoot[666696]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 16:08:02 ntop00 setroubleshoot[666696]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 16:08:02 ntop00 setroubleshoot[666696]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 16:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 204) ***
Sep 19 16:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 204) ***
Sep 19 16:10:34 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 204, QN: 10015/10015, ET: 33) ***
Sep 19 16:10:34 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 204, QN: 52/52, ET: 33) ***
Sep 19 16:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 205) ***
Sep 19 16:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 205, QN: 63/63, ET: 0) ***
Sep 19 16:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 205) ***
Sep 19 16:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 205, QN: 10046/10046, ET: 0) ***
Sep 19 16:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 206) ***
Sep 19 16:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 206) ***
Sep 19 16:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 206, QN: 58/58, ET: 0) ***
Sep 19 16:15:35 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 206, QN: 10093/10093, ET: 34) ***
Sep 19 16:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 207) ***
Sep 19 16:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 207, QN: 10621/10621, ET: 0) ***
Sep 19 16:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 207) ***
Sep 19 16:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 207, QN: 55/55, ET: 0) ***
Sep 19 16:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 208) ***
Sep 19 16:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 208) ***
... 71 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 16:09:08 outbound00.cs.umd.edu python3[1750697]: ldapdb [x6]
== outbound01.cs.umd.edu (2 distinct, 7 total) ==
Sep 19 16:13:06 outbound01.cs.umd.edu python3[4009377]: ldapdb [x6]
Sep 19 17:03:52 outbound01.cs.umd.edu krb5_child[4021615]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 19 16:08:58 sentry-docker00.cs.umd.edu systemd-udevd[3739245]: link_config: could not get ethtool features for veth2cba6b3
Sep 19 16:08:58 sentry-docker00.cs.umd.edu systemd-udevd[3739245]: Could not set offload features of veth2cba6b3: No such device
Sep 19 16:08:58 sentry-docker00.cs.umd.edu systemd-udevd[3739281]: Could not generate persistent MAC address for vethdf41944: No such file or directory
Sep 19 16:08:58 sentry-docker00.cs.umd.edu systemd-udevd[3739282]: Could not generate persistent MAC address for vethd2ab657: No such file or directory
Sep 19 16:08:58 sentry-docker00.cs.umd.edu systemd-udevd[3739285]: Could not generate persistent MAC address for veth755e9fc: No such file or directory
Sep 19 16:08:58 sentry-docker00.cs.umd.edu systemd-udevd[3739286]: Could not generate persistent MAC address for veth9539bcd: No such file or directory
Sep 19 16:08:58 sentry-docker00.cs.umd.edu systemd-udevd[3739292]: Could not generate persistent MAC address for veth26e77a1: No such file or directory
Sep 19 16:08:58 sentry-docker00.cs.umd.edu systemd-udevd[3739297]: Could not generate persistent MAC address for vetha59bdd7: No such file or directory
Sep 19 16:08:58 sentry-docker00.cs.umd.edu systemd-udevd[3739292]: Could not generate persistent MAC address for vethb242e55: No such file or directory
Sep 19 16:08:58 sentry-docker00.cs.umd.edu systemd-udevd[3739297]: Could not generate persistent MAC address for veth4047ac3: No such file or directory
Sep 19 16:08:58 sentry-docker00.cs.umd.edu systemd-udevd[3739362]: Could not generate persistent MAC address for veth8027c18: No such file or directory
Sep 19 16:08:58 sentry-docker00.cs.umd.edu systemd-udevd[3739360]: Could not generate persistent MAC address for vethfb39c2f: No such file or directory
Sep 19 16:29:06 sentry-docker00.cs.umd.edu systemd-udevd[3748620]: link_config: could not get ethtool features for vethdf41944
Sep 19 16:29:06 sentry-docker00.cs.umd.edu systemd-udevd[3748620]: Could not set offload features of vethdf41944: No such device
Sep 19 16:29:06 sentry-docker00.cs.umd.edu systemd-udevd[3748654]: Could not generate persistent MAC address for veth9785a93: No such file or directory
Sep 19 16:29:06 sentry-docker00.cs.umd.edu systemd-udevd[3748655]: Could not generate persistent MAC address for vethe1d3d4a: No such file or directory
Sep 19 16:29:06 sentry-docker00.cs.umd.edu systemd-udevd[3748658]: Could not generate persistent MAC address for vethf734789: No such file or directory
Sep 19 16:29:06 sentry-docker00.cs.umd.edu systemd-udevd[3748659]: Could not generate persistent MAC address for vethcd7c9b5: No such file or directory
Sep 19 16:29:06 sentry-docker00.cs.umd.edu systemd-udevd[3748682]: Could not generate persistent MAC address for veth3210718: No such file or directory
Sep 19 16:29:06 sentry-docker00.cs.umd.edu systemd-udevd[3748683]: Could not generate persistent MAC address for veth7442cbb: No such file or directory
Sep 19 16:29:07 sentry-docker00.cs.umd.edu systemd-udevd[3748701]: Could not generate persistent MAC address for veth1492afb: No such file or directory
Sep 19 16:29:07 sentry-docker00.cs.umd.edu systemd-udevd[3748686]: Could not generate persistent MAC address for vethc0891e6: No such file or directory
Sep 19 16:29:07 sentry-docker00.cs.umd.edu systemd-udevd[3748778]: Could not generate persistent MAC address for vethd9be15e: No such file or directory
Sep 19 16:29:07 sentry-docker00.cs.umd.edu systemd-udevd[3748779]: Could not generate persistent MAC address for veth9a30c0d: No such file or directory
Sep 19 16:49:15 sentry-docker00.cs.umd.edu systemd-udevd[3758093]: link_config: could not set ethtool features for vethf734789
Sep 19 16:49:15 sentry-docker00.cs.umd.edu systemd-udevd[3758093]: Could not set offload features of vethf734789: Operation not permitted
Sep 19 16:49:15 sentry-docker00.cs.umd.edu systemd-udevd[3758128]: Could not generate persistent MAC address for vethbcdf515: No such file or directory
Sep 19 16:49:15 sentry-docker00.cs.umd.edu systemd-udevd[3758129]: Could not generate persistent MAC address for veth788494d: No such file or directory
Sep 19 16:49:15 sentry-docker00.cs.umd.edu systemd-udevd[3758132]: Could not generate persistent MAC address for veth310b8eb: No such file or directory
Sep 19 16:49:15 sentry-docker00.cs.umd.edu systemd-udevd[3758133]: Could not generate persistent MAC address for veth7663702: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 16:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 16:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 16:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 16:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 16:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 16:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 16:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 2 total) ==
Sep 19 16:15:05 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f2 (1 distinct, 5 total) ==
Sep 19 16:18:45 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f3 (1 distinct, 1 total) ==
Sep 19 17:02:45 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 19 16:20:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 19 16:21:57 submit26-b9-fclone setroubleshoot[129536]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff
Sep 19 16:21:57 submit26-b9-fclone setroubleshoot[129536]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f
Sep 19 16:21:57 submit26-b9-fclone setroubleshoot[129536]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8
Sep 19 16:21:57 submit26-b9-fclone setroubleshoot[129536]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.4rosNL/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 19 16:21:57 submit26-b9-fclone setroubleshoot[129536]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566
Sep 19 16:21:57 submit26-b9-fclone setroubleshoot[129536]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.4rosNL. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 19 16:21:57 submit26-b9-fclone setroubleshoot[129536]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac
Sep 19 16:21:57 submit26-b9-fclone setroubleshoot[129536]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c
Sep 19 16:21:57 submit26-b9-fclone setroubleshoot[129536]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4
== wraith (1 distinct, 1 total) ==
Sep 19 16:58:46 wraith kernel: workqueue: output_poll_execute hogged CPU for >10000us 32771 times, consider switching to WQ_UNBOUND
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0540s
Status : exited 0
Output :
Syslog digest — 2026-09-19 16:05 EDT
Processed 2,861 lines, filtered 2,367 (82%). 494 unknown (163 distinct) from 17 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 15:51:07 b0b02.cs.umd.edu rustdesk[2938419]: cannot open display:
== bale (5 distinct, 86 total) ==
Sep 19 15:05:20 bale setroubleshoot[896120]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 19 15:05:21 bale setroubleshoot[896120]: 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 19 15:05:23 bale setroubleshoot[896120]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x14]
Sep 19 15:05:27 bale setroubleshoot[896120]: 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 [x10]
Sep 19 15:05:38 bale setroubleshoot[896749]: 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, 134 total) ==
Sep 19 15:03:53 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x134]
== idm00 (1 distinct, 1 total) ==
Sep 19 15:53:59 idm00 named[4166701]: client @0x7f1198074538 10.73.240.42#62912: update '73.10.in-addr.arpa/IN' denied
== idmp0 (2 distinct, 2 total) ==
Sep 19 15:37:56 idmp0 named[1598691]: client @0x7f2d2402e528 10.73.240.43#53313: update '73.10.in-addr.arpa/IN' denied
Sep 19 15:52:52 idmp0 named[1598691]: client @0x7f2d34053c48 10.73.245.12#55061: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 2 total) ==
Sep 19 15:08:22 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2]
== munin (2 distinct, 6 total) ==
Sep 19 15:08:37 munin sudo[333851]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x3]
Sep 19 15:08:37 munin sudo[333851]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x3]
== newhonors2 (1 distinct, 24 total) ==
Sep 19 15:13:03 newhonors2 dhcpcd[2863993]: dhcpcd is not running [x24]
== ntop00 (99 distinct, 143 total) ==
Sep 19 15:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 178) ***
Sep 19 15:05:30 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 178, QN: 8954/8954, ET: 29) ***
Sep 19 15:05:30 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 178, QN: 53/53, ET: 29) ***
Sep 19 15:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 179) ***
Sep 19 15:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 179, QN: 8888/8888, ET: 0) ***
Sep 19 15:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 179) ***
Sep 19 15:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 179, QN: 51/51, ET: 0) ***
Sep 19 15:08:02 ntop00 setroubleshoot[658796]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 15:08:02 ntop00 setroubleshoot[658796]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 15:08:02 ntop00 setroubleshoot[658796]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 15:08:02 ntop00 setroubleshoot[658796]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 15:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 180) ***
Sep 19 15:10:02 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 180) ***
Sep 19 15:10:31 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 180, QN: 8865/8865, ET: 30) ***
Sep 19 15:10:32 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 180, QN: 49/49, ET: 30) ***
Sep 19 15:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 181) ***
Sep 19 15:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 181) ***
Sep 19 15:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 181, QN: 46/46, ET: 0) ***
Sep 19 15:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 181, QN: 8672/8672, ET: 0) ***
Sep 19 15:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 182) ***
Sep 19 15:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 182) ***
Sep 19 15:15:32 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 182, QN: 9107/9107, ET: 31) ***
Sep 19 15:15:32 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 182, QN: 44/44, ET: 31) ***
Sep 19 15:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 183) ***
Sep 19 15:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 183, QN: 9899/9899, ET: 0) ***
Sep 19 15:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 183) ***
Sep 19 15:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 183, QN: 57/57, ET: 0) ***
Sep 19 15:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 184) ***
Sep 19 15:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 184) ***
Sep 19 15:20:36 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 184, QN: 9988/9988, ET: 35) ***
... 69 more distinct messages not shown
== outbound00.cs.umd.edu (2 distinct, 7 total) ==
Sep 19 15:09:09 outbound00.cs.umd.edu python3[1736726]: ldapdb [x6]
Sep 19 15:34:44 outbound00.cs.umd.edu krb5_child[1742686]: Preauthentication failed
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 15:13:06 outbound01.cs.umd.edu python3[3995431]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711058]: Could not generate persistent MAC address for veth42ff2ea: No such file or directory
Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711059]: Could not generate persistent MAC address for veth1b8a79e: No such file or directory
Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711062]: Could not generate persistent MAC address for veth1a4de93: No such file or directory
Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711080]: Could not generate persistent MAC address for vethe8f8853: No such file or directory
Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711078]: Could not generate persistent MAC address for veth1baac28: No such file or directory
Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711081]: Could not generate persistent MAC address for vethcd6db72: No such file or directory
Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711058]: Could not generate persistent MAC address for veth9a85fcf: No such file or directory
Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711065]: Could not generate persistent MAC address for veth1df5ba6: No such file or directory
Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711121]: Could not generate persistent MAC address for veth02a898b: No such file or directory
Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711126]: Could not generate persistent MAC address for veth8594bb0: No such file or directory
Sep 19 15:28:41 sentry-docker00.cs.umd.edu systemd-udevd[3720443]: link_config: could not set ethtool features for veth1df5ba6
Sep 19 15:28:41 sentry-docker00.cs.umd.edu systemd-udevd[3720443]: Could not set offload features of veth1df5ba6: Operation not permitted
Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720467]: Could not generate persistent MAC address for vethf8e747a: No such file or directory
Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720468]: Could not generate persistent MAC address for veth53b2dfd: No such file or directory
Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720486]: Could not generate persistent MAC address for veth7fdc3bf: No such file or directory
Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720472]: Could not generate persistent MAC address for veth0f7e5c3: No such file or directory
Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720471]: Could not generate persistent MAC address for veth107e4e9: No such file or directory
Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720473]: Could not generate persistent MAC address for veth0044d51: No such file or directory
Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720497]: Could not generate persistent MAC address for veth6f01cc8: No such file or directory
Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720498]: Could not generate persistent MAC address for veth50440e2: No such file or directory
Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720551]: Could not generate persistent MAC address for vethb33a88b: No such file or directory
Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720553]: Could not generate persistent MAC address for vethe99c145: No such file or directory
Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729812]: link_config: could not get ethtool features for vethb33a88b
Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729812]: Could not set offload features of vethb33a88b: No such device
Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729882]: Could not generate persistent MAC address for veth03e4d4a: No such file or directory
Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729883]: Could not generate persistent MAC address for vethbc5d159: No such file or directory
Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729886]: Could not generate persistent MAC address for veth9187930: No such file or directory
Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729887]: Could not generate persistent MAC address for veth6675eda: No such file or directory
Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729890]: Could not generate persistent MAC address for veth92c5839: No such file or directory
Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729906]: Could not generate persistent MAC address for veth16e0c87: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 15:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 15:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 15:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 15:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 15:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 15:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 15:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 1 total) ==
Sep 19 15:58:40 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f2 (1 distinct, 2 total) ==
Sep 19 15:39:28 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f3 (3 distinct, 6 total) ==
Sep 19 15:20:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
Sep 19 15:20:07 submit26-b9-f3 systemd-coredump[2007494]: Process 2007491 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2007491:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f68dae2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f68dae2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
Sep 19 15:20:08 submit26-b9-f3 systemd-coredump[2007508]: Process 2007505 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2007505:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f27e942a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f27e942a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 19 15:39:37 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0584s
Status : exited 0
Output :
Syslog digest — 2026-09-19 15:05 EDT
Processed 3,241 lines, filtered 2,693 (83%). 548 unknown (206 distinct) from 19 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 14:51:04 b0b02.cs.umd.edu rustdesk[2923101]: cannot open display:
== bale (5 distinct, 86 total) ==
Sep 19 14:05:20 bale setroubleshoot[883352]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 19 14:05:21 bale setroubleshoot[883352]: 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 19 14:05:23 bale setroubleshoot[883352]: 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 19 14:05:26 bale setroubleshoot[883352]: 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 19 14:05:38 bale setroubleshoot[883981]: 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]
== cmsc436-0101-redis (5 distinct, 5 total) ==
Sep 19 15:02:32 cmsc436-0101-redis sshd-session[3288774]: error: maximum authentication attempts exceeded for root from 109.63.156.168 port 37598 ssh2 [preauth]
Sep 19 15:02:38 cmsc436-0101-redis sshd-session[3288776]: error: maximum authentication attempts exceeded for root from 109.63.156.168 port 37882 ssh2 [preauth]
Sep 19 15:02:44 cmsc436-0101-redis sshd-session[3288778]: error: maximum authentication attempts exceeded for root from 109.63.156.168 port 38164 ssh2 [preauth]
Sep 19 15:02:54 cmsc436-0101-redis sshd-session[3288782]: error: maximum authentication attempts exceeded for admin from 109.63.156.168 port 38720 ssh2 [preauth]
Sep 19 15:03:03 cmsc436-0101-redis sshd-session[3288784]: error: maximum authentication attempts exceeded for admin from 109.63.156.168 port 39054 ssh2 [preauth]
== csfw00a (2 distinct, 135 total) ==
Sep 19 14:04:01 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x133]
Sep 19 14:29:50 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x2]
== idm00 (3 distinct, 3 total) ==
Sep 19 14:45:12 idm00 check-httpd-alive[832475]: httpd not responding on /server-status; forcing SIGKILL + restart
Sep 19 14:45:12 idm00 systemd[1]: httpd.service: Main process exited, code=killed, status=9/KILL
Sep 19 14:53:59 idm00 named[4166701]: client @0x7f1198074538 10.73.240.42#57509: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 14:37:56 idmp0 named[1598691]: client @0x7f2d440131e8 10.73.240.43#61785: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 2 total) ==
Sep 19 14:23:09 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2]
== munin (2 distinct, 8 total) ==
Sep 19 14:08:32 munin sudo[312389]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 19 14:08:32 munin sudo[312389]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== newhonors2 (1 distinct, 24 total) ==
Sep 19 14:13:03 newhonors2 dhcpcd[2862160]: dhcpcd is not running [x24]
== ntop00 (101 distinct, 141 total) ==
Sep 19 14:05:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 154) ***
Sep 19 14:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 154) ***
Sep 19 14:05:25 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 154, QN: 7592/7592, ET: 24) ***
Sep 19 14:05:25 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 154, QN: 60/60, ET: 24) ***
Sep 19 14:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 155) ***
Sep 19 14:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 155, QN: 8028/8028, ET: 0) ***
Sep 19 14:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 155) ***
Sep 19 14:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 155, QN: 54/54, ET: 0) ***
Sep 19 14:08:02 ntop00 setroubleshoot[650933]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x11]
Sep 19 14:08:02 ntop00 setroubleshoot[650933]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x11]
Sep 19 14:08:03 ntop00 setroubleshoot[650933]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11]
Sep 19 14:08:03 ntop00 setroubleshoot[650933]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x11]
Sep 19 14:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 156) ***
Sep 19 14:10:02 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 156) ***
Sep 19 14:10:24 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 156, QN: 7456/7456, ET: 23) ***
Sep 19 14:10:25 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 156, QN: 49/49, ET: 23) ***
Sep 19 14:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 157) ***
Sep 19 14:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 157, QN: 51/51, ET: 0) ***
Sep 19 14:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 157) ***
Sep 19 14:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 157, QN: 7058/7058, ET: 0) ***
Sep 19 14:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 158) ***
Sep 19 14:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 158) ***
Sep 19 14:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 158, QN: 55/55, ET: 0) ***
Sep 19 14:15:24 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 158, QN: 7213/7213, ET: 23) ***
Sep 19 14:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 159) ***
Sep 19 14:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 159, QN: 8060/8060, ET: 0) ***
Sep 19 14:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 159) ***
Sep 19 14:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 159, QN: 59/59, ET: 0) ***
Sep 19 14:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 160) ***
Sep 19 14:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 160) ***
... 71 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 14:09:09 outbound00.cs.umd.edu python3[1722624]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 14:13:06 outbound01.cs.umd.edu python3[3981478]: ldapdb [x6]
== portal (1 distinct, 2 total) ==
Sep 19 14:34:51 portal setroubleshoot[1693326]: SELinux is preventing /usr/bin/podman from using the nnp_transition access on a process. For complete SELinux messages run: sealert -l 7fd47d7d-0597-41f1-9a89-8a4911d8024d [x2]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 19 14:08:08 sentry-docker00.cs.umd.edu systemd-udevd[3682284]: link_config: could not get ethtool features for vethd4aa5e8
Sep 19 14:08:08 sentry-docker00.cs.umd.edu systemd-udevd[3682284]: Could not set offload features of vethd4aa5e8: No such device
Sep 19 14:08:08 sentry-docker00.cs.umd.edu systemd-udevd[3682518]: Could not generate persistent MAC address for veth468227a: No such file or directory
Sep 19 14:08:08 sentry-docker00.cs.umd.edu systemd-udevd[3682519]: Could not generate persistent MAC address for veth5cb573d: No such file or directory
Sep 19 14:08:08 sentry-docker00.cs.umd.edu systemd-udevd[3682526]: Could not generate persistent MAC address for veth3aceb1a: No such file or directory
Sep 19 14:08:08 sentry-docker00.cs.umd.edu systemd-udevd[3682528]: Could not generate persistent MAC address for veth010921e: No such file or directory
Sep 19 14:08:08 sentry-docker00.cs.umd.edu systemd-udevd[3682543]: Could not generate persistent MAC address for veth0109870: No such file or directory
Sep 19 14:08:08 sentry-docker00.cs.umd.edu systemd-udevd[3682536]: Could not generate persistent MAC address for veth90d13cb: No such file or directory
Sep 19 14:08:08 sentry-docker00.cs.umd.edu systemd-udevd[3682556]: Could not generate persistent MAC address for vethff5c843: No such file or directory
Sep 19 14:08:08 sentry-docker00.cs.umd.edu systemd-udevd[3682557]: Could not generate persistent MAC address for veth4dfeef4: No such file or directory
Sep 19 14:08:08 sentry-docker00.cs.umd.edu systemd-udevd[3682565]: Could not generate persistent MAC address for veth94dc65f: No such file or directory
Sep 19 14:08:08 sentry-docker00.cs.umd.edu systemd-udevd[3682578]: Could not generate persistent MAC address for veth778d26e: No such file or directory
Sep 19 14:28:16 sentry-docker00.cs.umd.edu systemd-udevd[3692170]: link_config: could not get ethtool features for veth468227a
Sep 19 14:28:16 sentry-docker00.cs.umd.edu systemd-udevd[3692170]: Could not set offload features of veth468227a: No such device
Sep 19 14:28:16 sentry-docker00.cs.umd.edu systemd-udevd[3692175]: link_config: could not get ethtool features for vethff5c843
Sep 19 14:28:16 sentry-docker00.cs.umd.edu systemd-udevd[3692175]: Could not set offload features of vethff5c843: No such device
Sep 19 14:28:17 sentry-docker00.cs.umd.edu systemd-udevd[3692226]: Could not generate persistent MAC address for vethf75f15d: No such file or directory
Sep 19 14:28:17 sentry-docker00.cs.umd.edu systemd-udevd[3692227]: Could not generate persistent MAC address for veth8bf8c8f: No such file or directory
Sep 19 14:28:17 sentry-docker00.cs.umd.edu systemd-udevd[3692256]: Could not generate persistent MAC address for veth8dd7e11: No such file or directory
Sep 19 14:28:17 sentry-docker00.cs.umd.edu systemd-udevd[3692246]: Could not generate persistent MAC address for veth3d74876: No such file or directory
Sep 19 14:28:17 sentry-docker00.cs.umd.edu systemd-udevd[3692271]: Could not generate persistent MAC address for vethd21d5c1: No such file or directory
Sep 19 14:28:17 sentry-docker00.cs.umd.edu systemd-udevd[3692272]: Could not generate persistent MAC address for vethac72846: No such file or directory
Sep 19 14:28:17 sentry-docker00.cs.umd.edu systemd-udevd[3692288]: Could not generate persistent MAC address for veth7485ad3: No such file or directory
Sep 19 14:28:17 sentry-docker00.cs.umd.edu systemd-udevd[3692281]: Could not generate persistent MAC address for vethffac90f: No such file or directory
Sep 19 14:28:17 sentry-docker00.cs.umd.edu systemd-udevd[3692286]: Could not generate persistent MAC address for veth13d02b0: No such file or directory
Sep 19 14:28:17 sentry-docker00.cs.umd.edu systemd-udevd[3692279]: Could not generate persistent MAC address for veth6b7be56: No such file or directory
Sep 19 14:48:25 sentry-docker00.cs.umd.edu systemd-udevd[3701614]: link_config: could not get ethtool features for veth3d74876
Sep 19 14:48:25 sentry-docker00.cs.umd.edu systemd-udevd[3701614]: Could not set offload features of veth3d74876: No such device
Sep 19 14:48:25 sentry-docker00.cs.umd.edu systemd-udevd[3701657]: Could not generate persistent MAC address for veth92281c7: No such file or directory
Sep 19 14:48:25 sentry-docker00.cs.umd.edu systemd-udevd[3701658]: Could not generate persistent MAC address for vethde8a328: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 14:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 14:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 14:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 14:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 14:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 14:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 14:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (12 distinct, 14 total) ==
Sep 19 14:15:08 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
Sep 19 14:25:53 submit26-b9-f1 setroubleshoot[2503075]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c
Sep 19 14:25:53 submit26-b9-f1 setroubleshoot[2503075]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36
Sep 19 14:25:53 submit26-b9-f1 setroubleshoot[2503075]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6
Sep 19 14:25:53 submit26-b9-f1 setroubleshoot[2503075]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.HEYmAK/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 19 14:25:53 submit26-b9-f1 setroubleshoot[2503075]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee
Sep 19 14:25:53 submit26-b9-f1 setroubleshoot[2503075]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.HEYmAK. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 19 14:25:53 submit26-b9-f1 setroubleshoot[2503075]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d
Sep 19 14:25:53 submit26-b9-f1 setroubleshoot[2503075]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9
Sep 19 14:25:53 submit26-b9-f1 setroubleshoot[2503075]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848
Sep 19 14:58:41 submit26-b9-f1 systemd-coredump[2506964]: Process 2506961 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2506961:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f431e82a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f431e82a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
Sep 19 14:58:42 submit26-b9-f1 systemd-coredump[2506991]: Process 2506988 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2506988:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f58f042a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f58f042a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f2 (14 distinct, 22 total) ==
Sep 19 14:05:27 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
Sep 19 14:06:48 submit26-b9-f2 setroubleshoot[1618679]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 [x2]
Sep 19 14:06:49 submit26-b9-f2 setroubleshoot[1618679]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a [x2]
Sep 19 14:06:49 submit26-b9-f2 setroubleshoot[1618679]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339
Sep 19 14:06:49 submit26-b9-f2 setroubleshoot[1618679]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.dH4S6M/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 19 14:06:49 submit26-b9-f2 setroubleshoot[1618679]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1
Sep 19 14:06:49 submit26-b9-f2 setroubleshoot[1618679]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.dH4S6M. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 19 14:06:49 submit26-b9-f2 setroubleshoot[1618679]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885
Sep 19 14:06:49 submit26-b9-f2 setroubleshoot[1618679]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af
Sep 19 14:06:49 submit26-b9-f2 setroubleshoot[1618679]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7
Sep 19 14:35:08 submit26-b9-f2 systemd-coredump[1621107]: Process 1621104 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1621104:#012#0 0x00007fca1b08d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fca1b03fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fca1b029873 abort (libc.so.6 + 0x29873)#012#3 0x00007fca1b02a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fca1b11d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fca1b11e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040149c Numeric (grades + 0x149c)#012#7 0x0000006400000064 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 19 14:35:08 submit26-b9-f2 systemd-coredump[1621117]: Process 1621114 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1621114:#012#0 0x00007f203308d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f203303fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f2033029873 abort (libc.so.6 + 0x29873)#012#3 0x00007f203302a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f203311d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f203311e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401a99 main (grades + 0x1a99)#012#7 0x0000000100000001 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 19 14:55:09 submit26-b9-f2 systemd-coredump[1623090]: Process 1623087 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1623087:#012#0 0x00007f3dc1c8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f3dc1c3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f3dc1c29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f3dc1c2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f3dc1d1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f3dc1d1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040149c Numeric (grades + 0x149c)#012#7 0x0000006400000064 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 19 14:55:09 submit26-b9-f2 systemd-coredump[1623100]: Process 1623097 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1623097:#012#0 0x00007f9aa2e8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f9aa2e3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f9aa2e29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f9aa2e2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f9aa2f1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f9aa2f1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401a99 main (grades + 0x1a99)#012#7 0x0000000100000001 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f3 (4 distinct, 8 total) ==
Sep 19 14:05:04 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
Sep 19 14:13:28 submit26-b9-f3 systemd-coredump[2000383]: Process 2000380 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2000380:#012#0 0x00007f09f228d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f09f223fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f09f2229873 abort (libc.so.6 + 0x29873)#012#3 0x00007f09f222a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f09f231d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f09f231e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040149c Numeric (grades + 0x149c)#012#7 0x0000006400000064 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 19 14:13:28 submit26-b9-f3 systemd-coredump[2000393]: Process 2000390 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2000390:#012#0 0x00007feb2e68d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007feb2e63fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007feb2e629873 abort (libc.so.6 + 0x29873)#012#3 0x00007feb2e62a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007feb2e71d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007feb2e71e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401a99 main (grades + 0x1a99)#012#7 0x0000000100000001 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 19 14:38:30 submit26-b9-f3 systemd-coredump[2004502]: Process 2004499 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2004499:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f40c102a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f40c102a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f4 (6 distinct, 8 total) ==
Sep 19 14:10:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
Sep 19 14:10:12 submit26-b9-f4 systemd-coredump[1441635]: Process 1441632 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1441632:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f703882a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f703882a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
Sep 19 14:10:13 submit26-b9-f4 systemd-coredump[1441645]: Process 1441642 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1441642:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f733c82a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f733c82a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
Sep 19 14:10:13 submit26-b9-f4 systemd-coredump[1441679]: Process 1441677 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1441677:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f2c7f62a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f2c7f62a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
Sep 19 14:10:14 submit26-b9-f4 systemd-coredump[1441691]: Process 1441688 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1441688:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f264c22a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f264c22a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
Sep 19 14:10:14 submit26-b9-f4 systemd-coredump[1441709]: Process 1441706 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1441706:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f841d82a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f841d82a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0563s
Status : exited 0
Output :
Syslog digest — 2026-09-19 14:05 EDT
Processed 2,867 lines, filtered 2,268 (79%). 599 unknown (199 distinct) from 19 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 13:51:00 b0b02.cs.umd.edu rustdesk[2908059]: cannot open display:
== bale (5 distinct, 85 total) ==
Sep 19 13:05:54 bale setroubleshoot[870494]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 19 13:05:55 bale setroubleshoot[870494]: 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 19 13:05:57 bale setroubleshoot[870494]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13]
Sep 19 13:06:00 bale setroubleshoot[870494]: 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 [x11]
Sep 19 13:06:12 bale setroubleshoot[871108]: 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 [x12]
== csfw00a (1 distinct, 126 total) ==
Sep 19 13:04:16 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x126]
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 19 13:53:59 idm00 named[4166701]: client @0x7f1198074538 10.73.240.42#61352: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 13:37:56 idmp0 named[1598691]: client @0x7f2d34043a38 10.73.240.43#57760: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 19 13:38:09 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3]
== krispykreme.cs.umd.edu (1 distinct, 5 total) ==
Sep 19 13:24:40 krispykreme.cs.umd.edu sshd-session[4114163]: error: send_error: write: Connection reset by peer [x5]
== munin (2 distinct, 6 total) ==
Sep 19 13:58:05 munin sudo[307400]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x3]
Sep 19 13:58:05 munin sudo[307400]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x3]
== newhonors2 (1 distinct, 24 total) ==
Sep 19 13:13:03 newhonors2 dhcpcd[2860307]: dhcpcd is not running [x24]
== ntop00 (99 distinct, 143 total) ==
Sep 19 13:05:02 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 130) ***
Sep 19 13:05:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 130, QN: 5793/5793, ET: 20) ***
Sep 19 13:05:21 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 130, QN: 47/47, ET: 19) ***
Sep 19 13:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 131) ***
Sep 19 13:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 131, QN: 56/56, ET: 0) ***
Sep 19 13:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 131) ***
Sep 19 13:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 131, QN: 6572/6572, ET: 0) ***
Sep 19 13:08:02 ntop00 setroubleshoot[642896]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 13:08:02 ntop00 setroubleshoot[642896]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 13:08:02 ntop00 setroubleshoot[642896]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 13:08:02 ntop00 setroubleshoot[642896]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 13:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 132) ***
Sep 19 13:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 132) ***
Sep 19 13:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 132, QN: 64/64, ET: 0) ***
Sep 19 13:10:22 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 132, QN: 6588/6588, ET: 21) ***
Sep 19 13:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 133) ***
Sep 19 13:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 133, QN: 59/59, ET: 0) ***
Sep 19 13:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 133) ***
Sep 19 13:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 133, QN: 6256/6256, ET: 0) ***
Sep 19 13:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 134) ***
Sep 19 13:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 134) ***
Sep 19 13:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 134, QN: 53/53, ET: 0) ***
Sep 19 13:15:22 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 134, QN: 6424/6424, ET: 21) ***
Sep 19 13:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 135) ***
Sep 19 13:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 135, QN: 6858/6858, ET: 0) ***
Sep 19 13:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 135) ***
Sep 19 13:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 135, QN: 55/55, ET: 0) ***
Sep 19 13:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 136) ***
Sep 19 13:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 136, QN: 61/61, ET: 0) ***
Sep 19 13:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 136) ***
... 69 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 13:09:09 outbound00.cs.umd.edu python3[1708501]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 13:13:06 outbound01.cs.umd.edu python3[3967206]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653374]: link_config: could not get ethtool features for veth75a1e1c
Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653374]: Could not set offload features of veth75a1e1c: No such device
Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653409]: Could not generate persistent MAC address for veth334f356: No such file or directory
Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653410]: Could not generate persistent MAC address for vethed5cda3: No such file or directory
Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653413]: Could not generate persistent MAC address for vethd154d63: No such file or directory
Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653414]: Could not generate persistent MAC address for veth2d418ab: No such file or directory
Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653428]: Could not generate persistent MAC address for veth6136334: No such file or directory
Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653432]: Could not generate persistent MAC address for vethf3478c4: No such file or directory
Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653432]: Could not generate persistent MAC address for veth5759efe: No such file or directory
Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653433]: Could not generate persistent MAC address for veth8471c1c: No such file or directory
Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653449]: Could not generate persistent MAC address for veth11422a6: No such file or directory
Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653454]: Could not generate persistent MAC address for vethdfe7f09: No such file or directory
Sep 19 13:27:51 sentry-docker00.cs.umd.edu systemd-udevd[3663001]: link_config: could not get ethtool features for veth6136334
Sep 19 13:27:51 sentry-docker00.cs.umd.edu systemd-udevd[3663001]: Could not set offload features of veth6136334: No such device
Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663037]: Could not generate persistent MAC address for veth270b11f: No such file or directory
Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663038]: Could not generate persistent MAC address for veth6ff5c5d: No such file or directory
Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663041]: Could not generate persistent MAC address for veth1637326: No such file or directory
Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663042]: Could not generate persistent MAC address for veth0d38f54: No such file or directory
Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663065]: Could not generate persistent MAC address for vethb52a269: No such file or directory
Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663066]: Could not generate persistent MAC address for vethd673ab3: No such file or directory
Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663081]: Could not generate persistent MAC address for veth542786a: No such file or directory
Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663080]: Could not generate persistent MAC address for veth5de8444: No such file or directory
Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663088]: Could not generate persistent MAC address for veth2a1a552: No such file or directory
Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663078]: Could not generate persistent MAC address for veth014b248: No such file or directory
Sep 19 13:48:00 sentry-docker00.cs.umd.edu systemd-udevd[3672430]: link_config: could not get ethtool features for veth270b11f
Sep 19 13:48:00 sentry-docker00.cs.umd.edu systemd-udevd[3672430]: Could not set offload features of veth270b11f: No such device
Sep 19 13:48:00 sentry-docker00.cs.umd.edu systemd-udevd[3672455]: Could not generate persistent MAC address for vethd4aa5e8: No such file or directory
Sep 19 13:48:00 sentry-docker00.cs.umd.edu systemd-udevd[3672456]: Could not generate persistent MAC address for vethb82a509: No such file or directory
Sep 19 13:48:00 sentry-docker00.cs.umd.edu systemd-udevd[3672474]: Could not generate persistent MAC address for veth7c256e0: No such file or directory
Sep 19 13:48:00 sentry-docker00.cs.umd.edu systemd-udevd[3672473]: Could not generate persistent MAC address for vethc607bcb: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 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 19 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 19 13:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 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 19 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 19 13:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 13:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (4 distinct, 9 total) ==
Sep 19 13:05:07 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
Sep 19 13:30:03 submit26-b9-f1 systemd-coredump[2497464]: Process 2497461 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2497461:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f5ee422a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f5ee422a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
Sep 19 13:30:03 submit26-b9-f1 systemd-coredump[2497475]: Process 2497472 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2497472:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007fb34be2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007fb34be2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
Sep 19 13:30:03 submit26-b9-f1 systemd-coredump[2497509]: Process 2497506 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2497506:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007fec9202a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007fec9202a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f2 (5 distinct, 11 total) ==
Sep 19 13:23:22 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
Sep 19 13:50:08 submit26-b9-f2 systemd-coredump[1617004]: Process 1617001 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1617001:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f5f46e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f5f46e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
Sep 19 13:50:08 submit26-b9-f2 systemd-coredump[1617032]: Process 1617029 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1617029:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f20abc2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f20abc2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
Sep 19 13:50:09 submit26-b9-f2 systemd-coredump[1617066]: Process 1617063 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1617063:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f3b8b22a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f3b8b22a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
Sep 19 13:50:09 submit26-b9-f2 systemd-coredump[1617077]: Process 1617074 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1617074:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007ff3eba2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007ff3eba2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f3 (11 distinct, 20 total) ==
Sep 19 13:05:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
Sep 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.qNuA5g/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.qNuA5g. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.yGMzk1/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
== submit26-b9-f4 (10 distinct, 12 total) ==
Sep 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.xkHbf3/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xkHbf3. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 19 13:25:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0546s
Status : exited 0
Output :
Syslog digest — 2026-09-19 13:05 EDT
Processed 2,967 lines, filtered 2,462 (82%). 505 unknown (178 distinct) from 19 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 12:50:57 b0b02.cs.umd.edu rustdesk[2892906]: cannot open display:
== bale (5 distinct, 86 total) ==
Sep 19 12:05:14 bale setroubleshoot[857763]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 19 12:05:15 bale setroubleshoot[857763]: 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 19 12:05:17 bale setroubleshoot[857763]: 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 19 12:05:20 bale setroubleshoot[857763]: 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 19 12:05:32 bale setroubleshoot[858379]: 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, 111 total) ==
Sep 19 12:05:01 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x111]
== helmsdeep (1 distinct, 1 total) ==
Sep 19 12:27:07 helmsdeep kernel: clocksource: timekeeping watchdog on CPU1: kvm-clock retried 1 times before success
== idm00 (1 distinct, 1 total) ==
Sep 19 12:53:59 idm00 named[4166701]: client @0x7f11a4068068 10.73.240.42#62981: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 12:37:56 idmp0 named[1598691]: client @0x7f2d1c04b088 10.73.240.43#51505: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 4 total) ==
Sep 19 12:44:02 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x4]
== munin (2 distinct, 4 total) ==
Sep 19 12:23:47 munin sudo[273009]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 19 12:23:47 munin sudo[273009]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 19 12:13:02 newhonors2 dhcpcd[2858466]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 19 12:05:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 106) ***
Sep 19 12:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 106, QN: 62/62, ET: 0) ***
Sep 19 12:05:20 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 106, QN: 5950/5950, ET: 19) ***
Sep 19 12:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 107) ***
Sep 19 12:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 107, QN: 52/52, ET: 0) ***
Sep 19 12:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 107) ***
Sep 19 12:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 107, QN: 6125/6125, ET: 0) ***
Sep 19 12:08:02 ntop00 setroubleshoot[635011]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 12:08:02 ntop00 setroubleshoot[635011]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 12:08:02 ntop00 setroubleshoot[635011]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 12:08:02 ntop00 setroubleshoot[635011]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 12:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 108) ***
Sep 19 12:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 108) ***
Sep 19 12:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 108, QN: 61/61, ET: 0) ***
Sep 19 12:10:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 108, QN: 6189/6189, ET: 20) ***
Sep 19 12:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 109) ***
Sep 19 12:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 109) ***
Sep 19 12:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 109, QN: 55/55, ET: 0) ***
Sep 19 12:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 109, QN: 6309/6309, ET: 0) ***
Sep 19 12:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 110) ***
Sep 19 12:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 110) ***
Sep 19 12:15:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 110, QN: 6431/6431, ET: 22) ***
Sep 19 12:15:23 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 110, QN: 50/50, ET: 22) ***
Sep 19 12:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 111) ***
Sep 19 12:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 111, QN: 6052/6052, ET: 0) ***
Sep 19 12:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 111) ***
Sep 19 12:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 111, QN: 62/62, ET: 0) ***
Sep 19 12:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 112) ***
Sep 19 12:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 112) ***
Sep 19 12:20:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 112, QN: 6050/6050, ET: 20) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 12:09:09 outbound00.cs.umd.edu python3[1694598]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 12:13:06 outbound01.cs.umd.edu python3[3953247]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625069]: Could not generate persistent MAC address for vethdc50ac0: No such file or directory
Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625070]: Could not generate persistent MAC address for vethe22bfd8: No such file or directory
Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625073]: Could not generate persistent MAC address for veth47bb496: No such file or directory
Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625074]: Could not generate persistent MAC address for veth598fc62: No such file or directory
Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625096]: Could not generate persistent MAC address for veth61bcfaf: No such file or directory
Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625093]: Could not generate persistent MAC address for veth0a59f16: No such file or directory
Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625084]: Could not generate persistent MAC address for vethabcf1b5: No such file or directory
Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625081]: Could not generate persistent MAC address for vetha87b282: No such file or directory
Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625164]: Could not generate persistent MAC address for veth4ca2589: No such file or directory
Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625167]: Could not generate persistent MAC address for veth8dea1b1: No such file or directory
Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634474]: link_config: could not get ethtool features for veth47bb496
Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634474]: Could not set offload features of veth47bb496: No such device
Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634500]: Could not generate persistent MAC address for veth0c46389: No such file or directory
Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634499]: Could not generate persistent MAC address for vethe166aa3: No such file or directory
Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634509]: Could not generate persistent MAC address for vethafadc7d: No such file or directory
Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634500]: Could not generate persistent MAC address for veth930544e: No such file or directory
Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634517]: Could not generate persistent MAC address for veth139fd86: No such file or directory
Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634507]: Could not generate persistent MAC address for veth81d1920: No such file or directory
Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634530]: Could not generate persistent MAC address for veth4a44d2b: No such file or directory
Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634529]: Could not generate persistent MAC address for vethc1981ec: No such file or directory
Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634551]: Could not generate persistent MAC address for vethe09b565: No such file or directory
Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634559]: Could not generate persistent MAC address for veth388bd54: No such file or directory
Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643893]: link_config: could not get ethtool features for vethe09b565
Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643893]: Could not set offload features of vethe09b565: No such device
Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643983]: Could not generate persistent MAC address for vethc366af0: No such file or directory
Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643984]: Could not generate persistent MAC address for veth6cde0cb: No such file or directory
Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643987]: Could not generate persistent MAC address for veth9acd0aa: No such file or directory
Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643983]: Could not generate persistent MAC address for veth6b92325: No such file or directory
Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3644000]: Could not generate persistent MAC address for veth75a1e1c: No such file or directory
Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643984]: Could not generate persistent MAC address for vethcebed5b: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 12:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 12:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 12:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 12:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 12:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 12:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 12:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (4 distinct, 12 total) ==
Sep 19 12:12:42 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x9]
Sep 19 12:15:07 submit26-b9-f1 kernel: show_signal_msg: 3 callbacks suppressed
Sep 19 12:15:07 submit26-b9-f1 systemd-coredump[2491867]: Process 2491864 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2491864:#012#0 0x0000000000401499 main (grades + 0x1499)#012#1 0x00007fb2e0c2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007fb2e0c2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64
Sep 19 12:15:07 submit26-b9-f1 systemd-coredump[2491877]: Process 2491874 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2491874:#012#0 0x0000000000401499 main (grades + 0x1499)#012#1 0x00007ff17702a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007ff17702a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f2 (4 distinct, 8 total) ==
Sep 19 12:05:05 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
Sep 19 12:55:09 submit26-b9-f2 kernel: show_signal_msg: 3 callbacks suppressed
Sep 19 12:55:09 submit26-b9-f2 systemd-coredump[1611972]: Process 1611969 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1611969:#012#0 0x0000000000401499 main (grades + 0x1499)#012#1 0x00007fee2022a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007fee2022a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64
Sep 19 12:55:09 submit26-b9-f2 systemd-coredump[1611983]: Process 1611979 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1611979:#012#0 0x0000000000401499 main (grades + 0x1499)#012#1 0x00007f20db02a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f20db02a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f3 (3 distinct, 10 total) ==
Sep 19 12:10:05 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x8]
Sep 19 12:35:08 submit26-b9-f3 systemd-coredump[1989943]: Process 1989940 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1989940:#012#0 0x0000000000401499 main (grades + 0x1499)#012#1 0x00007f0fa042a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f0fa042a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64
Sep 19 12:35:08 submit26-b9-f3 systemd-coredump[1989953]: Process 1989950 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1989950:#012#0 0x0000000000401499 main (grades + 0x1499)#012#1 0x00007f34c922a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f34c922a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f4 (1 distinct, 5 total) ==
Sep 19 12:20:43 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff
Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f
Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8
Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.cLjshq/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566
Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.cLjshq. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac
Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c
Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0516s
Status : exited 0
Output :
Syslog digest — 2026-09-19 12:05 EDT
Processed 2,607 lines, filtered 2,134 (81%). 473 unknown (161 distinct) from 17 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 11:50:53 b0b02.cs.umd.edu rustdesk[2877535]: cannot open display:
== bale (5 distinct, 86 total) ==
Sep 19 11:05:09 bale setroubleshoot[845026]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 19 11:05:10 bale setroubleshoot[845026]: 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 19 11:05:13 bale setroubleshoot[845026]: 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 19 11:05:16 bale setroubleshoot[845026]: 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 19 11:05:27 bale setroubleshoot[845642]: 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]
== cheezit.cs.umd.edu (3 distinct, 4 total) ==
Sep 19 11:29:09 cheezit.cs.umd.edu sshd-session[887721]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2]
Sep 19 11:29:10 cheezit.cs.umd.edu sshd-session[887721]: Error in Duo login for 'larry' from 71.191.93.172
Sep 19 11:29:10 cheezit.cs.umd.edu sshd-session[887718]: error: PAM: Authentication failure for larry from 71.191.93.172
== csfw00a (1 distinct, 116 total) ==
Sep 19 11:03:52 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x116]
== hspc (1 distinct, 1 total) ==
Sep 19 12:04:27 hspc kernel: kauditd_printk_skb: 2 callbacks suppressed
== idm00 (1 distinct, 1 total) ==
Sep 19 11:53:59 idm00 named[4166701]: client @0x7f11a402f3b8 10.73.240.42#63493: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 11:37:56 idmp0 named[1598691]: client @0x7f2d2803dc38 10.73.240.43#58466: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 5 total) ==
Sep 19 11:13:05 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x5]
== newhonors2 (1 distinct, 24 total) ==
Sep 19 11:13:03 newhonors2 dhcpcd[2856626]: dhcpcd is not running [x24]
== ntop00 (98 distinct, 142 total) ==
Sep 19 11:05:19 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 82, QN: 5956/5956, ET: 18) ***
Sep 19 11:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 83) ***
Sep 19 11:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 83, QN: 5840/5840, ET: 0) ***
Sep 19 11:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 83) ***
Sep 19 11:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 83, QN: 51/51, ET: 0) ***
Sep 19 11:08:02 ntop00 setroubleshoot[627132]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 11:08:02 ntop00 setroubleshoot[627132]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 11:08:02 ntop00 setroubleshoot[627132]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 11:08:02 ntop00 setroubleshoot[627132]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 11:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 84) ***
Sep 19 11:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 84) ***
Sep 19 11:10:18 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 84, QN: 5720/5720, ET: 17) ***
Sep 19 11:10:18 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 84, QN: 49/49, ET: 17) ***
Sep 19 11:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 85) ***
Sep 19 11:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 85, QN: 55/55, ET: 0) ***
Sep 19 11:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 85) ***
Sep 19 11:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 85, QN: 5563/5563, ET: 0) ***
Sep 19 11:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 86) ***
Sep 19 11:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 86) ***
Sep 19 11:15:18 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 86, QN: 5539/5539, ET: 17) ***
Sep 19 11:15:18 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 86, QN: 58/58, ET: 17) ***
Sep 19 11:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 87) ***
Sep 19 11:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 87, QN: 5493/5493, ET: 0) ***
Sep 19 11:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 87) ***
Sep 19 11:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 87, QN: 52/52, ET: 0) ***
Sep 19 11:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 88) ***
Sep 19 11:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 88) ***
Sep 19 11:20:18 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 88, QN: 5702/5702, ET: 17) ***
Sep 19 11:20:18 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 88, QN: 55/55, ET: 17) ***
Sep 19 11:23:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 89) ***
... 68 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 11:09:09 outbound00.cs.umd.edu python3[1680681]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 11:13:06 outbound01.cs.umd.edu python3[3939290]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 19 11:06:53 sentry-docker00.cs.umd.edu systemd-udevd[3596682]: link_config: could not get ethtool features for veth4993ed1
Sep 19 11:06:53 sentry-docker00.cs.umd.edu systemd-udevd[3596682]: Could not set offload features of veth4993ed1: No such device
Sep 19 11:06:54 sentry-docker00.cs.umd.edu systemd-udevd[3596715]: Could not generate persistent MAC address for veth8b90524: No such file or directory
Sep 19 11:06:54 sentry-docker00.cs.umd.edu systemd-udevd[3596716]: Could not generate persistent MAC address for vetha2e5e3b: No such file or directory
Sep 19 11:06:54 sentry-docker00.cs.umd.edu systemd-udevd[3596719]: Could not generate persistent MAC address for veth125752b: No such file or directory
Sep 19 11:06:54 sentry-docker00.cs.umd.edu systemd-udevd[3596720]: Could not generate persistent MAC address for vethff5cec9: No such file or directory
Sep 19 11:06:54 sentry-docker00.cs.umd.edu systemd-udevd[3596731]: Could not generate persistent MAC address for veth4840b1a: No such file or directory
Sep 19 11:06:54 sentry-docker00.cs.umd.edu systemd-udevd[3596727]: Could not generate persistent MAC address for veth932f499: No such file or directory
Sep 19 11:06:54 sentry-docker00.cs.umd.edu systemd-udevd[3596727]: Could not generate persistent MAC address for veth071e194: No such file or directory
Sep 19 11:06:54 sentry-docker00.cs.umd.edu systemd-udevd[3596731]: Could not generate persistent MAC address for veth3c624a5: No such file or directory
Sep 19 11:06:54 sentry-docker00.cs.umd.edu systemd-udevd[3596725]: Could not generate persistent MAC address for veth5fe1257: No such file or directory
Sep 19 11:06:54 sentry-docker00.cs.umd.edu systemd-udevd[3596739]: Could not generate persistent MAC address for veth6b42dbf: No such file or directory
Sep 19 11:27:02 sentry-docker00.cs.umd.edu systemd-udevd[3606119]: link_config: could not get ethtool features for veth071e194
Sep 19 11:27:02 sentry-docker00.cs.umd.edu systemd-udevd[3606119]: Could not set offload features of veth071e194: No such device
Sep 19 11:27:02 sentry-docker00.cs.umd.edu systemd-udevd[3606148]: Could not generate persistent MAC address for veth4e6a6f2: No such file or directory
Sep 19 11:27:02 sentry-docker00.cs.umd.edu systemd-udevd[3606149]: Could not generate persistent MAC address for veth8d7659d: No such file or directory
Sep 19 11:27:02 sentry-docker00.cs.umd.edu systemd-udevd[3606174]: Could not generate persistent MAC address for vetha7d5f15: No such file or directory
Sep 19 11:27:02 sentry-docker00.cs.umd.edu systemd-udevd[3606175]: Could not generate persistent MAC address for veth1619f04: No such file or directory
Sep 19 11:27:02 sentry-docker00.cs.umd.edu systemd-udevd[3606193]: Could not generate persistent MAC address for vethbbd3c7f: No such file or directory
Sep 19 11:27:02 sentry-docker00.cs.umd.edu systemd-udevd[3606196]: Could not generate persistent MAC address for vethe4ba6c2: No such file or directory
Sep 19 11:27:02 sentry-docker00.cs.umd.edu systemd-udevd[3606202]: Could not generate persistent MAC address for veth204131f: No such file or directory
Sep 19 11:27:02 sentry-docker00.cs.umd.edu systemd-udevd[3606203]: Could not generate persistent MAC address for vethd014070: No such file or directory
Sep 19 11:27:02 sentry-docker00.cs.umd.edu systemd-udevd[3606222]: Could not generate persistent MAC address for veth734129c: No such file or directory
Sep 19 11:27:02 sentry-docker00.cs.umd.edu systemd-udevd[3606218]: Could not generate persistent MAC address for veth2af408b: No such file or directory
Sep 19 11:47:10 sentry-docker00.cs.umd.edu systemd-udevd[3615550]: link_config: could not get ethtool features for veth734129c
Sep 19 11:47:10 sentry-docker00.cs.umd.edu systemd-udevd[3615550]: Could not set offload features of veth734129c: No such device
Sep 19 11:47:10 sentry-docker00.cs.umd.edu systemd-udevd[3615576]: Could not generate persistent MAC address for veth7079dcd: No such file or directory
Sep 19 11:47:10 sentry-docker00.cs.umd.edu systemd-udevd[3615577]: Could not generate persistent MAC address for veth0c9f66a: No such file or directory
Sep 19 11:47:10 sentry-docker00.cs.umd.edu systemd-udevd[3615602]: Could not generate persistent MAC address for veth56a3fac: No such file or directory
Sep 19 11:47:10 sentry-docker00.cs.umd.edu systemd-udevd[3615603]: Could not generate persistent MAC address for vethccad809: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 11:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 11:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 11:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 11:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 11:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 11:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 11:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 1 total) ==
Sep 19 11:43:29 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f2 (1 distinct, 1 total) ==
Sep 19 11:54:27 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f3 (1 distinct, 4 total) ==
Sep 19 11:37:42 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
1
0