Command: /usr/local/sbin/syslog-digest.py
Time : 0.0452s
Status : exited 0
Output :
Syslog digest — 2026-09-14 03:05 EDT
Processed 1,804 lines, filtered 1,388 (76%). 416 unknown (85 distinct) from 17 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 14 02:42:47 b0b02.cs.umd.edu rustdesk[899629]: cannot open display:
== csfw00a (2 distinct, 130 total) ==
Sep 14 02:03:55 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x124]
Sep 14 02:57:57 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x6]
== galax (2 distinct, 80 total) ==
Sep 14 02:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 14 02:05:42 galax systemd-journald[670]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [x40]
== hazfs.cs.umd.edu (1 distinct, 2 total) ==
Sep 14 02:25:06 hazfs.cs.umd.edu pcp[2799765]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (1 distinct, 1 total) ==
Sep 14 02:53:54 idm00 named[4166701]: client @0x7f11a945b458 10.73.240.42#51535: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 14 02:37:39 idmp0 named[1598691]: client @0x7f2d4c025168 10.73.240.43#57361: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 44 total) ==
Sep 14 02:07:55 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x44]
== krispykreme.cs.umd.edu (3 distinct, 3 total) ==
Sep 14 02:10:58 krispykreme.cs.umd.edu sshd-session[1900306]: pam_access(sshd:auth): access denied for user `admin' from `34.78.217.29'
Sep 14 02:10:58 krispykreme.cs.umd.edu krb5_child[1900308]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 14 02:10:58 krispykreme.cs.umd.edu sshd-session[1900304]: error: PAM: System error for admin from 34.78.217.29
== newhonors2 (1 distinct, 24 total) ==
Sep 14 02:13:03 newhonors2 dhcpcd[2611873]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (3 distinct, 8 total) ==
Sep 14 02:09:08 outbound00.cs.umd.edu python3[4044777]: ldapdb [x6]
Sep 14 03:03:26 outbound00.cs.umd.edu krb5_child[4057814]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 14 03:03:41 outbound00.cs.umd.edu sshd-session[4057825]: error: Protocol major versions differ: 2 vs. 1
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 14 02:13:06 outbound01.cs.umd.edu python3[2109471]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 14 02:13:38 sentry-docker00.cs.umd.edu systemd-udevd[4141480]: link_config: could not get ethtool features for vethdc16b7f
Sep 14 02:13:38 sentry-docker00.cs.umd.edu systemd-udevd[4141480]: Could not set offload features of vethdc16b7f: No such device
Sep 14 02:13:39 sentry-docker00.cs.umd.edu systemd-udevd[4141509]: Could not generate persistent MAC address for veth51b5ae2: No such file or directory
Sep 14 02:13:39 sentry-docker00.cs.umd.edu systemd-udevd[4141510]: Could not generate persistent MAC address for veth147fb20: No such file or directory
Sep 14 02:13:39 sentry-docker00.cs.umd.edu systemd-udevd[4141513]: Could not generate persistent MAC address for veth4b58afb: No such file or directory
Sep 14 02:13:39 sentry-docker00.cs.umd.edu systemd-udevd[4141514]: Could not generate persistent MAC address for vethf6bfc90: No such file or directory
Sep 14 02:13:39 sentry-docker00.cs.umd.edu systemd-udevd[4141537]: Could not generate persistent MAC address for veth77ec00f: No such file or directory
Sep 14 02:13:39 sentry-docker00.cs.umd.edu systemd-udevd[4141538]: Could not generate persistent MAC address for veth1e81ff1: No such file or directory
Sep 14 02:13:39 sentry-docker00.cs.umd.edu systemd-udevd[4141555]: Could not generate persistent MAC address for veth1ef3701: No such file or directory
Sep 14 02:13:39 sentry-docker00.cs.umd.edu systemd-udevd[4141548]: Could not generate persistent MAC address for veth6e78147: No such file or directory
Sep 14 02:13:39 sentry-docker00.cs.umd.edu systemd-udevd[4141560]: Could not generate persistent MAC address for vetha4ae2c4: No such file or directory
Sep 14 02:13:39 sentry-docker00.cs.umd.edu systemd-udevd[4141552]: Could not generate persistent MAC address for vethe70404b: No such file or directory
Sep 14 02:33:47 sentry-docker00.cs.umd.edu systemd-udevd[4151019]: link_config: could not get ethtool features for veth51b5ae2
Sep 14 02:33:47 sentry-docker00.cs.umd.edu systemd-udevd[4151019]: Could not set offload features of veth51b5ae2: No such device
Sep 14 02:33:47 sentry-docker00.cs.umd.edu systemd-udevd[4151055]: Could not generate persistent MAC address for vethb3d4ebd: No such file or directory
Sep 14 02:33:47 sentry-docker00.cs.umd.edu systemd-udevd[4151056]: Could not generate persistent MAC address for veth412306b: No such file or directory
Sep 14 02:33:47 sentry-docker00.cs.umd.edu systemd-udevd[4151059]: Could not generate persistent MAC address for veth05fc29b: No such file or directory
Sep 14 02:33:47 sentry-docker00.cs.umd.edu systemd-udevd[4151060]: Could not generate persistent MAC address for veth7d57833: No such file or directory
Sep 14 02:33:47 sentry-docker00.cs.umd.edu systemd-udevd[4151066]: Could not generate persistent MAC address for veth31bdd3b: No such file or directory
Sep 14 02:33:47 sentry-docker00.cs.umd.edu systemd-udevd[4151076]: Could not generate persistent MAC address for vethf9d7772: No such file or directory
Sep 14 02:33:47 sentry-docker00.cs.umd.edu systemd-udevd[4151060]: Could not generate persistent MAC address for vethbe0d6c4: No such file or directory
Sep 14 02:33:47 sentry-docker00.cs.umd.edu systemd-udevd[4151064]: Could not generate persistent MAC address for veth235778a: No such file or directory
Sep 14 02:33:47 sentry-docker00.cs.umd.edu systemd-udevd[4151066]: Could not generate persistent MAC address for vethd6ca763: No such file or directory
Sep 14 02:33:47 sentry-docker00.cs.umd.edu systemd-udevd[4151064]: Could not generate persistent MAC address for vethb2b3f7b: No such file or directory
Sep 14 02:53:55 sentry-docker00.cs.umd.edu systemd-udevd[4160715]: link_config: could not get ethtool features for veth235778a
Sep 14 02:53:55 sentry-docker00.cs.umd.edu systemd-udevd[4160715]: Could not set offload features of veth235778a: No such device
Sep 14 02:53:55 sentry-docker00.cs.umd.edu systemd-udevd[4160750]: link_config: could not get ethtool features for vethd6ca763
Sep 14 02:53:55 sentry-docker00.cs.umd.edu systemd-udevd[4160750]: Could not set offload features of vethd6ca763: No such device
Sep 14 02:53:55 sentry-docker00.cs.umd.edu systemd-udevd[4160764]: Could not generate persistent MAC address for vethe7a1fde: No such file or directory
Sep 14 02:53:55 sentry-docker00.cs.umd.edu systemd-udevd[4160765]: Could not generate persistent MAC address for veth856b65c: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 14 02:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 14 02:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 14 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 14 02:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 14 02:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 14 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 14 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (11 distinct, 17 total) ==
Sep 14 02:18:07 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
Sep 14 02:25:51 submit26-b9-f1 setroubleshoot[1527324]: 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 14 02:25:51 submit26-b9-f1 setroubleshoot[1527324]: 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 14 02:25:51 submit26-b9-f1 setroubleshoot[1527324]: 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 14 02:25:51 submit26-b9-f1 setroubleshoot[1527324]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.tLY0DU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 14 02:25:51 submit26-b9-f1 setroubleshoot[1527324]: 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 14 02:25:51 submit26-b9-f1 setroubleshoot[1527324]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.tLY0DU. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 14 02:25:51 submit26-b9-f1 setroubleshoot[1527324]: 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 14 02:25:51 submit26-b9-f1 setroubleshoot[1527324]: 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 [x2]
Sep 14 02:25:51 submit26-b9-f1 setroubleshoot[1527324]: 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 14 02:25:51 submit26-b9-f1 setroubleshoot[1527324]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.8n2wbw/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
== submit26-b9-f2 (10 distinct, 12 total) ==
Sep 14 02:06:46 submit26-b9-f2 setroubleshoot[662401]: 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 14 02:06:46 submit26-b9-f2 setroubleshoot[662401]: 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 14 02:06:46 submit26-b9-f2 setroubleshoot[662401]: 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 14 02:06:47 submit26-b9-f2 setroubleshoot[662401]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.u2Yvj0/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 14 02:06:47 submit26-b9-f2 setroubleshoot[662401]: 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 14 02:06:47 submit26-b9-f2 setroubleshoot[662401]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.u2Yvj0. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 14 02:06:47 submit26-b9-f2 setroubleshoot[662401]: 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 14 02:06:47 submit26-b9-f2 setroubleshoot[662401]: 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 14 02:06:47 submit26-b9-f2 setroubleshoot[662401]: 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 14 02:18:22 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f3 (1 distinct, 9 total) ==
Sep 14 02:08:07 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x9]
== submit26-b9-f4 (1 distinct, 2 total) ==
Sep 14 02:23:08 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0456s
Status : exited 0
Output :
Syslog digest — 2026-09-14 02:05 EDT
Processed 1,776 lines, filtered 1,318 (74%). 458 unknown (93 distinct) from 18 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 14 01:42:43 b0b02.cs.umd.edu rustdesk[884408]: cannot open display:
== biggulp.cs.umd.edu (4 distinct, 4 total) ==
Sep 14 01:42:57 biggulp.cs.umd.edu sshd-session[1140425]: pam_access(sshd:auth): access denied for user `admin' from `34.52.217.210'
Sep 14 01:42:57 biggulp.cs.umd.edu krb5_child[1140427]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 14 01:42:58 biggulp.cs.umd.edu sshd-session[1140399]: error: PAM: System error for admin from 34.52.217.210
Sep 14 01:43:06 biggulp.cs.umd.edu sshd-session[1140446]: error: Protocol major versions differ: 2 vs. 1
== csfw00a (1 distinct, 120 total) ==
Sep 14 01:04:41 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x120]
== galax (2 distinct, 80 total) ==
Sep 14 01:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 14 01:05:42 galax systemd-journald[670]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [x40]
== hazfs.cs.umd.edu (12 distinct, 68 total) ==
Sep 14 01:25:02 hazfs.cs.umd.edu pcp[2484341]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
Sep 14 01:30:53 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 14 01:30:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 14 01:30:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 14 01:30:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 14 01:30:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 14 01:30:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 14 01:30:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 14 01:30:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 14 01:30:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 14 01:30:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 14 01:30:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 14 01:53:53 idm00 named[4166701]: client @0x7f1198079d88 10.73.240.42#61458: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 14 01:37:39 idmp0 named[1598691]: client @0x7f2d30021688 10.73.240.43#56297: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 38 total) ==
Sep 14 01:08:08 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x38]
== newhonors2 (1 distinct, 24 total) ==
Sep 14 01:13:03 newhonors2 dhcpcd[2610025]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 14 01:09:09 outbound00.cs.umd.edu python3[4030865]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 14 01:13:06 outbound01.cs.umd.edu python3[2095341]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 14 01:13:13 sentry-docker00.cs.umd.edu systemd-udevd[4112894]: link_config: could not get ethtool features for vethdf4f168
Sep 14 01:13:13 sentry-docker00.cs.umd.edu systemd-udevd[4112894]: Could not set offload features of vethdf4f168: No such device
Sep 14 01:13:13 sentry-docker00.cs.umd.edu systemd-udevd[4112899]: link_config: could not get ethtool features for veth02fd2a9
Sep 14 01:13:13 sentry-docker00.cs.umd.edu systemd-udevd[4112899]: Could not set offload features of veth02fd2a9: No such device
Sep 14 01:13:14 sentry-docker00.cs.umd.edu systemd-udevd[4112934]: Could not generate persistent MAC address for veth2befeb1: No such file or directory
Sep 14 01:13:14 sentry-docker00.cs.umd.edu systemd-udevd[4112935]: Could not generate persistent MAC address for veth9c28315: No such file or directory
Sep 14 01:13:14 sentry-docker00.cs.umd.edu systemd-udevd[4112938]: Could not generate persistent MAC address for vethfc94f16: No such file or directory
Sep 14 01:13:14 sentry-docker00.cs.umd.edu systemd-udevd[4112939]: Could not generate persistent MAC address for vethb7e7181: No such file or directory
Sep 14 01:13:14 sentry-docker00.cs.umd.edu systemd-udevd[4112953]: Could not generate persistent MAC address for veth66fbfe9: No such file or directory
Sep 14 01:13:14 sentry-docker00.cs.umd.edu systemd-udevd[4112949]: Could not generate persistent MAC address for veth67f1769: No such file or directory
Sep 14 01:13:14 sentry-docker00.cs.umd.edu systemd-udevd[4112935]: Could not generate persistent MAC address for vethed7ee8b: No such file or directory
Sep 14 01:13:14 sentry-docker00.cs.umd.edu systemd-udevd[4112955]: Could not generate persistent MAC address for vethd9c5c19: No such file or directory
Sep 14 01:13:14 sentry-docker00.cs.umd.edu systemd-udevd[4112949]: Could not generate persistent MAC address for veth03a5f4d: No such file or directory
Sep 14 01:13:14 sentry-docker00.cs.umd.edu systemd-udevd[4112946]: Could not generate persistent MAC address for vethc35ef84: No such file or directory
Sep 14 01:33:22 sentry-docker00.cs.umd.edu systemd-udevd[4122530]: link_config: could not get ethtool features for veth66fbfe9
Sep 14 01:33:22 sentry-docker00.cs.umd.edu systemd-udevd[4122530]: Could not set offload features of veth66fbfe9: No such device
Sep 14 01:33:22 sentry-docker00.cs.umd.edu systemd-udevd[4122559]: Could not generate persistent MAC address for veth50b4b1b: No such file or directory
Sep 14 01:33:22 sentry-docker00.cs.umd.edu systemd-udevd[4122558]: Could not generate persistent MAC address for veth392d1a5: No such file or directory
Sep 14 01:33:22 sentry-docker00.cs.umd.edu systemd-udevd[4122562]: Could not generate persistent MAC address for veth558961f: No such file or directory
Sep 14 01:33:22 sentry-docker00.cs.umd.edu systemd-udevd[4122578]: Could not generate persistent MAC address for veth9f1da2e: No such file or directory
Sep 14 01:33:22 sentry-docker00.cs.umd.edu systemd-udevd[4122586]: Could not generate persistent MAC address for veth5f6906a: No such file or directory
Sep 14 01:33:22 sentry-docker00.cs.umd.edu systemd-udevd[4122587]: Could not generate persistent MAC address for veth0fa2733: No such file or directory
Sep 14 01:33:22 sentry-docker00.cs.umd.edu systemd-udevd[4122612]: Could not generate persistent MAC address for vethb6eefc2: No such file or directory
Sep 14 01:33:22 sentry-docker00.cs.umd.edu systemd-udevd[4122614]: Could not generate persistent MAC address for veth0406896: No such file or directory
Sep 14 01:33:22 sentry-docker00.cs.umd.edu systemd-udevd[4122653]: Could not generate persistent MAC address for vethb79785a: No such file or directory
Sep 14 01:33:22 sentry-docker00.cs.umd.edu systemd-udevd[4122641]: Could not generate persistent MAC address for veth98ea2e0: No such file or directory
Sep 14 01:53:30 sentry-docker00.cs.umd.edu systemd-udevd[4131957]: link_config: could not get ethtool features for veth5f6906a
Sep 14 01:53:30 sentry-docker00.cs.umd.edu systemd-udevd[4131957]: Could not set offload features of veth5f6906a: No such device
Sep 14 01:53:30 sentry-docker00.cs.umd.edu systemd-udevd[4132029]: Could not generate persistent MAC address for vethdc16b7f: No such file or directory
Sep 14 01:53:30 sentry-docker00.cs.umd.edu systemd-udevd[4132030]: Could not generate persistent MAC address for veth940e9f4: No such file or directory
... 8 more distinct messages not shown
== soul (1 distinct, 1 total) ==
Sep 14 01:47:49 soul krb5_child[2487708]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== strawberry (7 distinct, 38 total) ==
Sep 14 01:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 14 01:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 14 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 14 01:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 14 01:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 14 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 14 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 4 total) ==
Sep 14 01:37:06 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f2 (1 distinct, 4 total) ==
Sep 14 01:43:33 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f3 (10 distinct, 15 total) ==
Sep 14 01:06:40 submit26-b9-f3 setroubleshoot[796982]: 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 14 01:06:40 submit26-b9-f3 setroubleshoot[796982]: 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 14 01:06:40 submit26-b9-f3 setroubleshoot[796982]: 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 14 01:06:40 submit26-b9-f3 setroubleshoot[796982]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.QJkvno/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 14 01:06:40 submit26-b9-f3 setroubleshoot[796982]: 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 14 01:06:40 submit26-b9-f3 setroubleshoot[796982]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.QJkvno. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 14 01:06:40 submit26-b9-f3 setroubleshoot[796982]: 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 14 01:06:40 submit26-b9-f3 setroubleshoot[796982]: 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 14 01:06:41 submit26-b9-f3 setroubleshoot[796982]: 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 14 01:07:23 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f4 (9 distinct, 9 total) ==
Sep 14 01:24:44 submit26-b9-f4 setroubleshoot[592256]: 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 14 01:24:44 submit26-b9-f4 setroubleshoot[592256]: 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 14 01:24:44 submit26-b9-f4 setroubleshoot[592256]: 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 14 01:24:44 submit26-b9-f4 setroubleshoot[592256]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.aHvWKg/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 14 01:24:44 submit26-b9-f4 setroubleshoot[592256]: 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 14 01:24:44 submit26-b9-f4 setroubleshoot[592256]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.aHvWKg. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 14 01:24:44 submit26-b9-f4 setroubleshoot[592256]: 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 14 01:24:44 submit26-b9-f4 setroubleshoot[592256]: 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 14 01:24:44 submit26-b9-f4 setroubleshoot[592256]: 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.0476s
Status : exited 0
Output :
Syslog digest — 2026-09-14 01:05 EDT
Processed 2,066 lines, filtered 1,592 (77%). 474 unknown (102 distinct) from 30 host(s).
== abuse (3 distinct, 4 total) ==
Sep 14 00:10:14 abuse systemd[1]: New main PID 28737 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 14 00:10:32 abuse systemd[1]: Daemon never wrote its PID file. Failing.
Sep 14 00:10:43 abuse systemd[1]: pmlogger.service: Supervising process 3827 which is not our child. We'll most likely not notice when it exits.
== atif01.cs.umd.edu (1 distinct, 1 total) ==
Sep 14 00:32:52 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)!
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 14 00:42:40 b0b02.cs.umd.edu rustdesk[869249]: cannot open display:
== cheezit.cs.umd.edu (4 distinct, 4 total) ==
Sep 14 00:16:41 cheezit.cs.umd.edu sshd-session[3208834]: pam_access(sshd:auth): access denied for user `admin' from `34.38.97.154'
Sep 14 00:16:41 cheezit.cs.umd.edu krb5_child[3208836]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 14 00:16:41 cheezit.cs.umd.edu sshd-session[3208832]: error: PAM: System error for admin from 34.38.97.154
Sep 14 00:17:27 cheezit.cs.umd.edu sshd-session[3208909]: error: Protocol major versions differ: 2 vs. 1
== csfw00a (1 distinct, 155 total) ==
Sep 14 00:04:05 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x155]
== galax (2 distinct, 80 total) ==
Sep 14 00:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 14 00:05:42 galax systemd-journald[670]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [x40]
== grades01.cs.umd.edu (3 distinct, 4 total) ==
Sep 14 00:10:13 grades01.cs.umd.edu systemd[1]: New main PID 6318 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 14 00:10:34 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 14 00:10:49 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 13843 which is not our child. We'll most likely not notice when it exits.
== hazfs.cs.umd.edu (2 distinct, 3 total) ==
Sep 14 00:10:02 hazfs.cs.umd.edu pcp[2089902]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily.log
Sep 14 00:25:09 hazfs.cs.umd.edu pcp[2168959]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (1 distinct, 1 total) ==
Sep 14 00:53:53 idm00 named[4166701]: client @0x7f11a8c67778 10.73.240.42#50428: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 14 00:37:38 idmp0 named[1598691]: client @0x7f2d3400d5c8 10.73.240.43#63500: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 44 total) ==
Sep 14 00:08:09 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x44]
== jubjub.cs.umd.edu (3 distinct, 4 total) ==
Sep 14 00:10:12 jubjub.cs.umd.edu systemd[1]: New main PID 1761888 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 14 00:10:32 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 14 00:10:41 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1769245 which is not our child. We'll most likely not notice when it exits.
== matrix (3 distinct, 4 total) ==
Sep 14 00:12:08 matrix krb5_child[1970592]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 14 00:12:10 matrix sshd[1970586]: error: PAM: Authentication failure for admin from 35.195.203.14
Sep 14 00:12:19 matrix sshd[1970667]: error: Protocol major versions differ: 2 vs. 1
== mirrors.cs.umd.edu (4 distinct, 6 total) ==
Sep 14 00:10:34 mirrors.cs.umd.edu root[32611]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log
Sep 14 00:10:34 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. [x2]
Sep 14 00:10:37 mirrors.cs.umd.edu systemd[1]: New main PID 31553 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 14 00:11:38 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 16001 which is not our child. We'll most likely not notice when it exits.
== misty.cs.umd.edu (3 distinct, 4 total) ==
Sep 14 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 22776 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 14 00:10:34 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 14 00:10:50 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 30589 which is not our child. We'll most likely not notice when it exits.
== newhonors2 (1 distinct, 24 total) ==
Sep 14 00:13:03 newhonors2 dhcpcd[2608197]: dhcpcd is not running [x24]
== openrepo (1 distinct, 1 total) ==
Sep 14 00:06:27 openrepo (nin-node)[2312311]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 14 00:09:09 outbound00.cs.umd.edu python3[4016031]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 14 00:13:06 outbound01.cs.umd.edu python3[2080671]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 14 00:12:48 sentry-docker00.cs.umd.edu systemd-udevd[4084771]: link_config: could not get ethtool features for veth83bc1bb
Sep 14 00:12:48 sentry-docker00.cs.umd.edu systemd-udevd[4084771]: Could not set offload features of veth83bc1bb: No such device
Sep 14 00:12:49 sentry-docker00.cs.umd.edu systemd-udevd[4084798]: Could not generate persistent MAC address for veth7905a38: No such file or directory
Sep 14 00:12:49 sentry-docker00.cs.umd.edu systemd-udevd[4084799]: Could not generate persistent MAC address for veth3787725: No such file or directory
Sep 14 00:12:49 sentry-docker00.cs.umd.edu systemd-udevd[4084802]: Could not generate persistent MAC address for veth8848387: No such file or directory
Sep 14 00:12:49 sentry-docker00.cs.umd.edu systemd-udevd[4084803]: Could not generate persistent MAC address for veth00d11d5: No such file or directory
Sep 14 00:12:49 sentry-docker00.cs.umd.edu systemd-udevd[4084823]: Could not generate persistent MAC address for vethf19eb55: No such file or directory
Sep 14 00:12:49 sentry-docker00.cs.umd.edu systemd-udevd[4084811]: Could not generate persistent MAC address for veth3b54f1e: No such file or directory
Sep 14 00:12:49 sentry-docker00.cs.umd.edu systemd-udevd[4084812]: Could not generate persistent MAC address for veth04b6c41: No such file or directory
Sep 14 00:12:49 sentry-docker00.cs.umd.edu systemd-udevd[4084798]: Could not generate persistent MAC address for veth5685d70: No such file or directory
Sep 14 00:12:49 sentry-docker00.cs.umd.edu systemd-udevd[4084823]: Could not generate persistent MAC address for vethcc4cc78: No such file or directory
Sep 14 00:12:49 sentry-docker00.cs.umd.edu systemd-udevd[4084811]: Could not generate persistent MAC address for veth2f699e9: No such file or directory
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094112]: link_config: could not get ethtool features for veth2f699e9
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094112]: Could not set offload features of veth2f699e9: No such device
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094114]: link_config: could not get ethtool features for veth7905a38
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094114]: Could not set offload features of veth7905a38: No such device
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094151]: Could not generate persistent MAC address for vethc62dd88: No such file or directory
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094152]: Could not generate persistent MAC address for veth72164bc: No such file or directory
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094155]: Could not generate persistent MAC address for veth7f586c3: No such file or directory
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094156]: Could not generate persistent MAC address for veth874e4a4: No such file or directory
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094159]: Could not generate persistent MAC address for vethcea5576: No such file or directory
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094175]: Could not generate persistent MAC address for vetha20c758: No such file or directory
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094172]: Could not generate persistent MAC address for vethdc8d036: No such file or directory
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094175]: Could not generate persistent MAC address for vethf68cba6: No such file or directory
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094227]: Could not generate persistent MAC address for vethd3be239: No such file or directory
Sep 14 00:32:57 sentry-docker00.cs.umd.edu systemd-udevd[4094229]: Could not generate persistent MAC address for veth260dda5: No such file or directory
Sep 14 00:53:05 sentry-docker00.cs.umd.edu systemd-udevd[4103509]: link_config: could not get ethtool features for vethc62dd88
Sep 14 00:53:05 sentry-docker00.cs.umd.edu systemd-udevd[4103509]: Could not set offload features of vethc62dd88: No such device
Sep 14 00:53:05 sentry-docker00.cs.umd.edu systemd-udevd[4103540]: Could not generate persistent MAC address for vethbef2b3d: No such file or directory
Sep 14 00:53:05 sentry-docker00.cs.umd.edu systemd-udevd[4103541]: Could not generate persistent MAC address for veth2d56bd4: No such file or directory
... 8 more distinct messages not shown
== strawberry (8 distinct, 39 total) ==
Sep 14 00:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 14 00:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 14 00:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 14 00:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 14 00:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 14 00:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 14 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Sep 14 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing.
== submit10-cln25 (3 distinct, 4 total) ==
Sep 14 00:10:12 submit10-cln25 systemd: New main PID 12752 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 14 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing.
Sep 14 00:10:36 submit10-cln25 systemd: pmlogger.service: Supervising process 19650 which is not our child. We'll most likely not notice when it exits.
== submit26-b9-f1 (1 distinct, 8 total) ==
Sep 14 00:06:44 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x8]
== submit26-b9-f2 (1 distinct, 6 total) ==
Sep 14 00:13:12 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f3 (1 distinct, 4 total) ==
Sep 14 00:07:46 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f4 (1 distinct, 6 total) ==
Sep 14 00:05:08 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== tma-0 (3 distinct, 4 total) ==
Sep 14 00:10:13 tma-0 systemd[1]: New main PID 23066 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 14 00:10:30 tma-0 systemd[1]: Daemon never wrote its PID file. Failing.
Sep 14 00:10:38 tma-0 systemd[1]: pmlogger.service: Supervising process 30688 which is not our child. We'll most likely not notice when it exits.
== uffish.cs.umd.edu (3 distinct, 4 total) ==
Sep 14 00:10:14 uffish.cs.umd.edu systemd[1]: New main PID 302453 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 14 00:10:35 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 14 00:10:52 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 310091 which is not our child. We'll most likely not notice when it exits.
== vacuum.cs.umd.edu (3 distinct, 4 total) ==
Sep 14 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 4951 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 14 00:10:33 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 14 00:10:44 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 12467 which is not our child. We'll most likely not notice when it exits.
== whiffle.cs.umd.edu (3 distinct, 4 total) ==
Sep 14 00:10:14 whiffle.cs.umd.edu systemd[1]: New main PID 4088715 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 14 00:10:40 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 14 00:10:53 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 4096350 which is not our child. We'll most likely not notice when it exits.
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0491s
Status : exited 0
Output :
Syslog digest — 2026-09-14 00:05 EDT
Processed 1,956 lines, filtered 1,528 (78%). 428 unknown (105 distinct) from 26 host(s).
== atif01.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 23:59:57 atif01.cs.umd.edu kernel: net_ratelimit: 18 callbacks suppressed
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 23:42:36 b0b02.cs.umd.edu rustdesk[853152]: cannot open display:
== csfw00a (2 distinct, 123 total) ==
Sep 13 23:04:04 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x121]
Sep 13 23:48:41 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x2]
== galax (2 distinct, 80 total) ==
Sep 13 23:05:40 galax systemd-journald[670]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [x40]
Sep 13 23:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
== hazfs.cs.umd.edu (1 distinct, 2 total) ==
Sep 13 23:25:05 hazfs.cs.umd.edu pcp[1853209]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== hspc (1 distinct, 1 total) ==
Sep 14 00:00:02 hspc kernel: kauditd_printk_skb: 4 callbacks suppressed
== idm00 (1 distinct, 1 total) ==
Sep 13 23:53:53 idm00 named[4166701]: client @0x7f11980727c8 10.73.240.42#63612: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 13 23:37:38 idmp0 named[1598691]: client @0x7f2d3802ab18 10.73.240.43#61179: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (2 distinct, 2 total) ==
Sep 14 00:00:34 inbound00.cs.umd.edu krb5_child[4129026]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 14 00:00:57 inbound00.cs.umd.edu sshd-session[4129037]: error: Protocol major versions differ: 2 vs. 1
== itmon02 (1 distinct, 35 total) ==
Sep 13 23:07:58 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x35]
== krispykreme.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 23:55:01 krispykreme.cs.umd.edu sshd-session[1859921]: pam_access(sshd:auth): access denied for user `bhatele' from `172.58.244.184'
== matrix (2 distinct, 3 total) ==
Sep 13 23:19:07 matrix sshd[1938659]: error: PAM: Authentication failure for root from 212.116.238.51 [x2]
Sep 14 00:00:02 matrix (nin-node)[1961943]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neo-gizmonic (1 distinct, 1 total) ==
Sep 14 00:00:01 neo-gizmonic (nin-node)[1086612]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neoavion (1 distinct, 1 total) ==
Sep 14 00:00:04 neoavion (nin-node)[2564750]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== newhonors2 (2 distinct, 25 total) ==
Sep 13 23:13:03 newhonors2 dhcpcd[2606129]: dhcpcd is not running [x24]
Sep 14 00:00:16 newhonors2 (nin-node)[2607650]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 23:09:08 outbound00.cs.umd.edu python3[4001767]: ldapdb [x6]
== outbound01.cs.umd.edu (4 distinct, 9 total) ==
Sep 13 23:13:06 outbound01.cs.umd.edu python3[2065734]: ldapdb [x6]
Sep 13 23:48:51 outbound01.cs.umd.edu krb5_child[2073821]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 13 23:49:10 outbound01.cs.umd.edu sshd-session[2073893]: error: Protocol major versions differ: 2 vs. 1
Sep 13 23:52:17 outbound01.cs.umd.edu cockpit-ws[2074555]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory
== sentry-docker00.cs.umd.edu (32 distinct, 32 total) ==
Sep 13 23:12:23 sentry-docker00.cs.umd.edu systemd-udevd[4056500]: link_config: could not set ethtool features for veth26fa98b
Sep 13 23:12:23 sentry-docker00.cs.umd.edu systemd-udevd[4056500]: Could not set offload features of veth26fa98b: Operation not permitted
Sep 13 23:12:24 sentry-docker00.cs.umd.edu systemd-udevd[4056523]: Could not generate persistent MAC address for veth7f1c7d4: No such file or directory
Sep 13 23:12:24 sentry-docker00.cs.umd.edu systemd-udevd[4056524]: Could not generate persistent MAC address for veth5054ddd: No such file or directory
Sep 13 23:12:24 sentry-docker00.cs.umd.edu systemd-udevd[4056553]: Could not generate persistent MAC address for veth6e1a1bf: No such file or directory
Sep 13 23:12:24 sentry-docker00.cs.umd.edu systemd-udevd[4056537]: Could not generate persistent MAC address for veth5d5f7d3: No such file or directory
Sep 13 23:12:24 sentry-docker00.cs.umd.edu systemd-udevd[4056553]: Could not generate persistent MAC address for veth38a8138: No such file or directory
Sep 13 23:12:24 sentry-docker00.cs.umd.edu systemd-udevd[4056537]: Could not generate persistent MAC address for veth5ad026f: No such file or directory
Sep 13 23:12:24 sentry-docker00.cs.umd.edu systemd-udevd[4056609]: Could not generate persistent MAC address for veth0e0268f: No such file or directory
Sep 13 23:12:24 sentry-docker00.cs.umd.edu systemd-udevd[4056610]: Could not generate persistent MAC address for veth90af8be: No such file or directory
Sep 13 23:12:24 sentry-docker00.cs.umd.edu systemd-udevd[4056635]: Could not generate persistent MAC address for vethce3db26: No such file or directory
Sep 13 23:12:24 sentry-docker00.cs.umd.edu systemd-udevd[4056630]: Could not generate persistent MAC address for veth90e5515: No such file or directory
Sep 13 23:32:32 sentry-docker00.cs.umd.edu systemd-udevd[4065960]: Could not generate persistent MAC address for veth03ea254: No such file or directory
Sep 13 23:32:32 sentry-docker00.cs.umd.edu systemd-udevd[4065962]: Could not generate persistent MAC address for veth14bf7ba: No such file or directory
Sep 13 23:32:32 sentry-docker00.cs.umd.edu systemd-udevd[4065993]: Could not generate persistent MAC address for veth2cea9fb: No such file or directory
Sep 13 23:32:32 sentry-docker00.cs.umd.edu systemd-udevd[4065994]: Could not generate persistent MAC address for veth6f41edb: No such file or directory
Sep 13 23:32:32 sentry-docker00.cs.umd.edu systemd-udevd[4066012]: Could not generate persistent MAC address for vethcb442c8: No such file or directory
Sep 13 23:32:32 sentry-docker00.cs.umd.edu systemd-udevd[4066007]: Could not generate persistent MAC address for veth8c5d005: No such file or directory
Sep 13 23:32:32 sentry-docker00.cs.umd.edu systemd-udevd[4066005]: Could not generate persistent MAC address for veth7961686: No such file or directory
Sep 13 23:32:32 sentry-docker00.cs.umd.edu systemd-udevd[4066017]: Could not generate persistent MAC address for veth7ec4aea: No such file or directory
Sep 13 23:32:32 sentry-docker00.cs.umd.edu systemd-udevd[4066023]: Could not generate persistent MAC address for veth52aeb00: No such file or directory
Sep 13 23:32:32 sentry-docker00.cs.umd.edu systemd-udevd[4066025]: Could not generate persistent MAC address for veth5406e0a: No such file or directory
Sep 13 23:52:40 sentry-docker00.cs.umd.edu systemd-udevd[4075401]: Could not generate persistent MAC address for veth83bc1bb: No such file or directory
Sep 13 23:52:40 sentry-docker00.cs.umd.edu systemd-udevd[4075402]: Could not generate persistent MAC address for vethd530288: No such file or directory
Sep 13 23:52:40 sentry-docker00.cs.umd.edu systemd-udevd[4075420]: Could not generate persistent MAC address for vethd6aa696: No such file or directory
Sep 13 23:52:40 sentry-docker00.cs.umd.edu systemd-udevd[4075410]: Could not generate persistent MAC address for vethd598920: No such file or directory
Sep 13 23:52:40 sentry-docker00.cs.umd.edu systemd-udevd[4075402]: Could not generate persistent MAC address for veth42a0c59: No such file or directory
Sep 13 23:52:40 sentry-docker00.cs.umd.edu systemd-udevd[4075412]: Could not generate persistent MAC address for veth047db53: No such file or directory
Sep 13 23:52:40 sentry-docker00.cs.umd.edu systemd-udevd[4075431]: Could not generate persistent MAC address for veth216e7da: No such file or directory
Sep 13 23:52:40 sentry-docker00.cs.umd.edu systemd-udevd[4075432]: Could not generate persistent MAC address for veth8389fd9: No such file or directory
... 2 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 13 23:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 13 23:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 13 23:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 13 23:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 13 23:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 13 23:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 13 23:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (15 distinct, 21 total) ==
Sep 13 23:11:39 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
Sep 13 23:13:07 submit26-b9-f1 kernel: show_signal_msg: 3 callbacks suppressed
Sep 13 23:13:07 submit26-b9-f1 systemd-coredump[1505291]: Process 1505288 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1505288:#012#0 0x00007f3891e66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f3891e55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f3891e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f3891e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:13:07 submit26-b9-f1 systemd-coredump[1505303]: Process 1505299 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1505299:#012#0 0x00007f3403466456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f3403455412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f340342a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f340342a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:13:07 submit26-b9-f1 systemd-coredump[1505313]: Process 1505310 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1505310:#012#0 0x00007fa526466456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fa526455412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fa52642a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fa52642a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:13:08 submit26-b9-f1 systemd-coredump[1505325]: Process 1505321 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1505321:#012#0 0x00007fe162e66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fe162e55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fe162e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fe162e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:13:08 submit26-b9-f1 systemd-coredump[1505335]: Process 1505332 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1505332:#012#0 0x00007f04aac66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f04aac55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f04aac2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f04aac2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:13:08 submit26-b9-f1 systemd-coredump[1505345]: Process 1505342 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1505342:#012#0 0x00007fa886266456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fa886255412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fa88622a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fa88622a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:13:08 submit26-b9-f1 systemd-coredump[1505355]: Process 1505352 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1505352:#012#0 0x00007f7bfb666456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f7bfb655412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f7bfb62a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f7bfb62a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:13:08 submit26-b9-f1 systemd-coredump[1505365]: Process 1505362 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1505362:#012#0 0x00007f82aa866456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f82aa855412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f82aa82a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f82aa82a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:13:08 submit26-b9-f1 systemd-coredump[1505374]: Process 1505372 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1505372:#012#0 0x00007f544f066456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f544f055412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f544f02a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f544f02a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:13:09 submit26-b9-f1 systemd-coredump[1505385]: Process 1505382 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1505382:#012#0 0x00007f2d80666456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f2d80655412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f2d8062a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f2d8062a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:13:09 submit26-b9-f1 systemd-coredump[1505395]: Process 1505392 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1505392:#012#0 0x00007f655fc66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f655fc55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f655fc2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f655fc2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:13:09 submit26-b9-f1 systemd-coredump[1505406]: Process 1505403 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1505403:#012#0 0x00007faa5f266456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007faa5f255412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007faa5f22a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007faa5f22a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:13:09 submit26-b9-f1 systemd-coredump[1505417]: Process 1505413 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1505413:#012#0 0x00007fad61a66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fad61a55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fad61a2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fad61a2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f2 (14 distinct, 20 total) ==
Sep 13 23:11:21 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
Sep 13 23:33:07 submit26-b9-f2 systemd-coredump[647036]: Process 647033 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 647033:#012#0 0x00007fa590466456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fa590455412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fa59042a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fa59042a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:33:07 submit26-b9-f2 systemd-coredump[647047]: Process 647043 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 647043:#012#0 0x00007f1866666456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f1866655412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f186662a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f186662a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:33:08 submit26-b9-f2 systemd-coredump[647058]: Process 647054 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 647054:#012#0 0x00007f20b8c66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f20b8c55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f20b8c2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f20b8c2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:33:08 submit26-b9-f2 systemd-coredump[647068]: Process 647065 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 647065:#012#0 0x00007fd474a66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fd474a55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fd474a2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fd474a2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:33:08 submit26-b9-f2 systemd-coredump[647078]: Process 647075 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 647075:#012#0 0x00007fb15b066456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fb15b055412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fb15b02a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fb15b02a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:33:08 submit26-b9-f2 systemd-coredump[647089]: Process 647085 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 647085:#012#0 0x00007fe9a9c66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fe9a9c55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fe9a9c2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fe9a9c2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:33:08 submit26-b9-f2 systemd-coredump[647099]: Process 647096 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 647096:#012#0 0x00007fca65866456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fca65855412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fca6582a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fca6582a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:33:09 submit26-b9-f2 systemd-coredump[647109]: Process 647106 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 647106:#012#0 0x00007f2d2bc66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f2d2bc55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f2d2bc2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f2d2bc2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:33:09 submit26-b9-f2 systemd-coredump[647119]: Process 647116 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 647116:#012#0 0x00007f190e866456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f190e855412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f190e82a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f190e82a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:33:09 submit26-b9-f2 systemd-coredump[647129]: Process 647126 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 647126:#012#0 0x00007f51ed666456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f51ed655412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f51ed62a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f51ed62a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:33:09 submit26-b9-f2 systemd-coredump[647139]: Process 647136 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 647136:#012#0 0x00007fd68fa66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fd68fa55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fd68fa2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fd68fa2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:33:09 submit26-b9-f2 systemd-coredump[647149]: Process 647146 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 647146:#012#0 0x00007f9970666456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f9970655412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f997062a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f997062a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 23:33:10 submit26-b9-f2 systemd-coredump[647159]: Process 647156 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 647156:#012#0 0x00007fa5d9466456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fa5d9455412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fa5d942a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fa5d942a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f3 (1 distinct, 6 total) ==
Sep 13 23:17:15 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f4 (1 distinct, 8 total) ==
Sep 13 23:16:07 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x8]
== teaching-awards (8 distinct, 8 total) ==
Sep 13 23:30:13 teaching-awards krb5_child[673209]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 13 23:30:23 teaching-awards sshd-session[673227]: error: Protocol major versions differ: 2 vs. 1
Sep 13 23:38:49 teaching-awards sshd-session[673666]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 13 23:38:49 teaching-awards sshd-session[673666]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 13 23:38:50 teaching-awards sshd-session[673666]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 13 23:38:50 teaching-awards sshd-session[673666]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 13 23:38:52 teaching-awards sshd-session[673666]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 13 23:38:52 teaching-awards sshd-session[673666]: error: kex_protocol_error: type 30 seq 7 [preauth]
== tma-0 (1 distinct, 1 total) ==
Sep 13 23:57:03 tma-0 sshd[19585]: error: PAM: Authentication failure for admin from 121.46.175.207.bc.googleusercontent.com
== wraith (1 distinct, 1 total) ==
Sep 14 00:00:00 wraith (nin-node)[371874]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0491s
Status : exited 0
Output :
Syslog digest — 2026-09-13 23:05 EDT
Processed 2,056 lines, filtered 1,578 (76%). 478 unknown (112 distinct) from 25 host(s).
== abadi-computer (4 distinct, 4 total) ==
Sep 13 22:18:31 abadi-computer systemd-tmpfiles[81858]: Opening file "/tmp/code-32b8541f-418a-4242-b22f-4da3aa38d9dc" failed, ignoring: No such device or address
Sep 13 22:18:31 abadi-computer systemd-tmpfiles[81858]: Opening file "/tmp/code-f4684350-65e7-487b-8a54-be65b9f1a5ed" failed, ignoring: No such device or address
Sep 13 22:18:31 abadi-computer systemd-tmpfiles[81858]: Opening file "/tmp/code-09a0f3d4-157c-43db-a724-afc6223f2dd1" failed, ignoring: No such device or address
Sep 13 22:18:31 abadi-computer systemd-tmpfiles[81858]: Opening file "/tmp/code-d7fe1c3b-568b-4d6d-82ac-3b30c55702ff" failed, ignoring: No such device or address
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 22:42:33 b0b02.cs.umd.edu rustdesk[838006]: cannot open display:
== cheezit.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 22:26:48 cheezit.cs.umd.edu sshd-session[3181098]: pam_access(sshd:auth): access denied for user `dpalam' from `100.15.141.186'
== cmsc436-0101-redis (3 distinct, 3 total) ==
Sep 13 22:44:48 cmsc436-0101-redis krb5_child[2985565]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 13 22:44:50 cmsc436-0101-redis sshd-session[2985561]: error: PAM: Authentication failure for admin from 34.52.217.210
Sep 13 22:48:59 cmsc436-0101-redis sshd-session[2985610]: error: Protocol major versions differ: 2 vs. 1
== csfw00a (1 distinct, 158 total) ==
Sep 13 22:04:46 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x158]
== galax (3 distinct, 81 total) ==
Sep 13 22:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 13 22:05:42 galax systemd-journald[670]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [x40]
Sep 13 22:55:40 galax kernel: rtw89_8922ae 0000:06:00.0: failed to wait RF DACK
== hazfs.cs.umd.edu (1 distinct, 2 total) ==
Sep 13 22:25:01 hazfs.cs.umd.edu pcp[1537782]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (1 distinct, 1 total) ==
Sep 13 22:53:53 idm00 named[4166701]: client @0x7f11a0045838 10.73.240.42#58389: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 13 22:37:38 idmp0 named[1598691]: client @0x7f2d3400d5c8 10.73.240.43#56958: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 42 total) ==
Sep 13 22:08:06 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x42]
== matrix (1 distinct, 2 total) ==
Sep 13 22:20:28 matrix sshd[1904647]: error: PAM: Authentication failure for root from 212.116.238.51 [x2]
== mcstic (3 distinct, 6 total) ==
Sep 13 22:18:43 mcstic krb5_child[548606]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Sep 13 22:18:49 mcstic sshd[548601]: error: PAM: Authentication failure for admin from 34.78.161.183
Sep 13 22:30:41 mcstic sshd[548957]: error: Protocol major versions differ: 2 vs. 1
== munin (2 distinct, 4 total) ==
Sep 13 22:18:02 munin sudo[1555194]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 13 22:18:02 munin sudo[1555194]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== netman.cs.umd.edu (3 distinct, 7 total) ==
Sep 13 22:18:42 netman.cs.umd.edu sshd[178110]: error: Protocol major versions differ: 2 vs. 1 [x2]
Sep 13 22:20:39 netman.cs.umd.edu krb5_child[178932]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Sep 13 22:20:43 netman.cs.umd.edu sshd[178927]: error: PAM: Authentication failure for admin from 130.211.104.162
== newhonors2 (1 distinct, 24 total) ==
Sep 13 22:13:02 newhonors2 dhcpcd[2604304]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 22:09:09 outbound00.cs.umd.edu python3[3987670]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 22:13:06 outbound01.cs.umd.edu python3[2051747]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 13 22:11:59 sentry-docker00.cs.umd.edu systemd-udevd[4028210]: link_config: could not set ethtool features for veth55dbca0
Sep 13 22:11:59 sentry-docker00.cs.umd.edu systemd-udevd[4028210]: Could not set offload features of veth55dbca0: Operation not permitted
Sep 13 22:11:59 sentry-docker00.cs.umd.edu systemd-udevd[4028244]: Could not generate persistent MAC address for veth7496e85: No such file or directory
Sep 13 22:11:59 sentry-docker00.cs.umd.edu systemd-udevd[4028245]: Could not generate persistent MAC address for veth9336415: No such file or directory
Sep 13 22:11:59 sentry-docker00.cs.umd.edu systemd-udevd[4028248]: Could not generate persistent MAC address for veth8f68b81: No such file or directory
Sep 13 22:11:59 sentry-docker00.cs.umd.edu systemd-udevd[4028249]: Could not generate persistent MAC address for veth8e02a83: No such file or directory
Sep 13 22:11:59 sentry-docker00.cs.umd.edu systemd-udevd[4028272]: Could not generate persistent MAC address for veth0aa53a0: No such file or directory
Sep 13 22:11:59 sentry-docker00.cs.umd.edu systemd-udevd[4028273]: Could not generate persistent MAC address for vetheb58842: No such file or directory
Sep 13 22:11:59 sentry-docker00.cs.umd.edu systemd-udevd[4028291]: Could not generate persistent MAC address for vethe9fa70e: No such file or directory
Sep 13 22:11:59 sentry-docker00.cs.umd.edu systemd-udevd[4028280]: Could not generate persistent MAC address for vetha78325a: No such file or directory
Sep 13 22:11:59 sentry-docker00.cs.umd.edu systemd-udevd[4028292]: Could not generate persistent MAC address for veth1876c84: No such file or directory
Sep 13 22:11:59 sentry-docker00.cs.umd.edu systemd-udevd[4028285]: Could not generate persistent MAC address for veth55cd679: No such file or directory
Sep 13 22:32:07 sentry-docker00.cs.umd.edu systemd-udevd[4037624]: link_config: could not get ethtool features for veth0aa53a0
Sep 13 22:32:07 sentry-docker00.cs.umd.edu systemd-udevd[4037624]: Could not set offload features of veth0aa53a0: No such device
Sep 13 22:32:07 sentry-docker00.cs.umd.edu systemd-udevd[4037655]: Could not generate persistent MAC address for vethec48afd: No such file or directory
Sep 13 22:32:07 sentry-docker00.cs.umd.edu systemd-udevd[4037656]: Could not generate persistent MAC address for veth4bff004: No such file or directory
Sep 13 22:32:07 sentry-docker00.cs.umd.edu systemd-udevd[4037659]: Could not generate persistent MAC address for veth34a47d4: No such file or directory
Sep 13 22:32:07 sentry-docker00.cs.umd.edu systemd-udevd[4037660]: Could not generate persistent MAC address for veth4c92df1: No such file or directory
Sep 13 22:32:07 sentry-docker00.cs.umd.edu systemd-udevd[4037683]: Could not generate persistent MAC address for veth22b7217: No such file or directory
Sep 13 22:32:07 sentry-docker00.cs.umd.edu systemd-udevd[4037684]: Could not generate persistent MAC address for vethdad69f4: No such file or directory
Sep 13 22:32:07 sentry-docker00.cs.umd.edu systemd-udevd[4037702]: Could not generate persistent MAC address for vethe4aab8f: No such file or directory
Sep 13 22:32:07 sentry-docker00.cs.umd.edu systemd-udevd[4037693]: Could not generate persistent MAC address for veth964f351: No such file or directory
Sep 13 22:32:07 sentry-docker00.cs.umd.edu systemd-udevd[4037704]: Could not generate persistent MAC address for veth81f5e49: No such file or directory
Sep 13 22:32:07 sentry-docker00.cs.umd.edu systemd-udevd[4037701]: Could not generate persistent MAC address for vethe7c7a3b: No such file or directory
Sep 13 22:52:15 sentry-docker00.cs.umd.edu systemd-udevd[4047032]: link_config: could not get ethtool features for vethe7c7a3b
Sep 13 22:52:15 sentry-docker00.cs.umd.edu systemd-udevd[4047032]: Could not set offload features of vethe7c7a3b: No such device
Sep 13 22:52:15 sentry-docker00.cs.umd.edu systemd-udevd[4047068]: Could not generate persistent MAC address for veth26fa98b: No such file or directory
Sep 13 22:52:15 sentry-docker00.cs.umd.edu systemd-udevd[4047069]: Could not generate persistent MAC address for veth46d28e3: No such file or directory
Sep 13 22:52:15 sentry-docker00.cs.umd.edu systemd-udevd[4047072]: Could not generate persistent MAC address for veth5106d4f: No such file or directory
Sep 13 22:52:15 sentry-docker00.cs.umd.edu systemd-udevd[4047073]: Could not generate persistent MAC address for veth08dd48c: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 13 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 13 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 13 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 13 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 13 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 13 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 13 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (23 distinct, 27 total) ==
Sep 13 22:13:07 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
Sep 13 22:25:51 submit26-b9-f1 setroubleshoot[1498393]: 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 13 22:25:51 submit26-b9-f1 setroubleshoot[1498393]: 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 13 22:25:51 submit26-b9-f1 setroubleshoot[1498393]: 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 13 22:25:51 submit26-b9-f1 setroubleshoot[1498393]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.5bv5Lg/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 13 22:25:51 submit26-b9-f1 setroubleshoot[1498393]: 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 13 22:25:51 submit26-b9-f1 setroubleshoot[1498393]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.5bv5Lg. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 13 22:25:51 submit26-b9-f1 setroubleshoot[1498393]: 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 13 22:25:51 submit26-b9-f1 setroubleshoot[1498393]: 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 13 22:25:51 submit26-b9-f1 setroubleshoot[1498393]: 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 13 22:52:56 submit26-b9-f1 systemd-coredump[1502259]: Process 1502256 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1502256:#012#0 0x00007fa033466456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fa033455412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fa03342a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fa03342a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 22:52:56 submit26-b9-f1 systemd-coredump[1502271]: Process 1502268 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1502268:#012#0 0x00007f7155e66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f7155e55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f7155e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f7155e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 22:52:56 submit26-b9-f1 systemd-coredump[1502281]: Process 1502278 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1502278:#012#0 0x00007f125e666456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f125e655412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f125e62a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f125e62a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 22:52:56 submit26-b9-f1 systemd-coredump[1502292]: Process 1502289 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1502289:#012#0 0x00007fa8a1866456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fa8a1855412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fa8a182a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fa8a182a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 22:52:56 submit26-b9-f1 systemd-coredump[1502302]: Process 1502299 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1502299:#012#0 0x00007f705c466456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f705c455412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f705c42a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f705c42a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 22:52:57 submit26-b9-f1 systemd-coredump[1502313]: Process 1502310 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1502310:#012#0 0x00007fc54f266456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fc54f255412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fc54f22a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fc54f22a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 22:52:57 submit26-b9-f1 systemd-coredump[1502323]: Process 1502320 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1502320:#012#0 0x00007f21efe66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f21efe55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f21efe2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f21efe2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 22:52:57 submit26-b9-f1 systemd-coredump[1502334]: Process 1502330 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1502330:#012#0 0x00007f1673866456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f1673855412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f167382a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f167382a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 22:52:57 submit26-b9-f1 systemd-coredump[1502344]: Process 1502341 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1502341:#012#0 0x00007f50bf066456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007f50bf055412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007f50bf02a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f50bf02a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 22:52:57 submit26-b9-f1 systemd-coredump[1502354]: Process 1502351 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1502351:#012#0 0x00007fa1d8866456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fa1d8855412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fa1d882a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fa1d882a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 22:52:57 submit26-b9-f1 systemd-coredump[1502364]: Process 1502361 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1502361:#012#0 0x00007efce8266456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007efce8255412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007efce822a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007efce822a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 22:52:58 submit26-b9-f1 systemd-coredump[1502374]: Process 1502371 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1502371:#012#0 0x00007fb48aa66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007fb48aa55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007fb48aa2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fb48aa2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
Sep 13 22:52:58 submit26-b9-f1 systemd-coredump[1502384]: Process 1502381 (draw_figures) of user 1001 dumped core.#012#012Stack trace of thread 1502381:#012#0 0x00007ff212c66456 __vfscanf_internal (libc.so.6 + 0x66456)#012#1 0x00007ff212c55412 __isoc99_scanf (libc.so.6 + 0x55412)#012#2 0x00000000004011a0 main (draw_figures + 0x11a0)#012#3 0x00007ff212c2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007ff212c2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x00000000004010a5 _start (draw_figures + 0x10a5)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f2 (10 distinct, 15 total) ==
Sep 13 22:06:46 submit26-b9-f2 setroubleshoot[637188]: 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 13 22:06:46 submit26-b9-f2 setroubleshoot[637188]: 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 13 22:06:46 submit26-b9-f2 setroubleshoot[637188]: 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 13 22:06:46 submit26-b9-f2 setroubleshoot[637188]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.1yL0iZ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 13 22:06:47 submit26-b9-f2 setroubleshoot[637188]: 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 13 22:06:47 submit26-b9-f2 setroubleshoot[637188]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.1yL0iZ. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 13 22:06:47 submit26-b9-f2 setroubleshoot[637188]: 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 13 22:06:47 submit26-b9-f2 setroubleshoot[637188]: 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 13 22:06:47 submit26-b9-f2 setroubleshoot[637188]: 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 13 22:07:43 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f3 (1 distinct, 6 total) ==
Sep 13 22:10:19 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f4 (1 distinct, 2 total) ==
Sep 13 22:35:08 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== vacuum.cs.umd.edu (4 distinct, 4 total) ==
Sep 13 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[6591]: Process 2105 (driver) of user 33 killed by SIGABRT - dumping core
Sep 13 22:11:58 vacuum.cs.umd.edu abrt-server[6593]: Package 'amanda-backup_server' isn't signed with proper key
Sep 13 22:11:58 vacuum.cs.umd.edu abrt-server[6593]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-13-22:11:58-2105' exited with 1
Sep 13 22:11:58 vacuum.cs.umd.edu abrt-server[6593]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-13-22:11:58-2105'
== wraith (1 distinct, 1 total) ==
Sep 13 23:04:47 wraith kernel: workqueue: output_poll_execute hogged CPU for >10000us 16387 times, consider switching to WQ_UNBOUND
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0477s
Status : exited 0
Output :
Syslog digest — 2026-09-13 22:05 EDT
Processed 1,989 lines, filtered 1,556 (78%). 433 unknown (89 distinct) from 20 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 21:42:29 b0b02.cs.umd.edu rustdesk[822832]: cannot open display:
== biggulp.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 21:39:01 biggulp.cs.umd.edu sshd-session[1094840]: pam_access(sshd:auth): access denied for user `bahar' from `173.66.226.128'
== cheezit.cs.umd.edu (2 distinct, 3 total) ==
Sep 13 21:59:57 cheezit.cs.umd.edu sshd-session[3174477]: pam_access(sshd:auth): access denied for user `seriv' from `2601:14d:4e01:890::40f' [x2]
Sep 13 22:00:04 cheezit.cs.umd.edu sshd-session[3174481]: pam_access(sshd:auth): access denied for user `root' from `2601:14d:4e01:890::40f'
== csfw00a (1 distinct, 133 total) ==
Sep 13 21:04:03 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x133]
== galax (2 distinct, 80 total) ==
Sep 13 21:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 13 21:05:42 galax systemd-journald[670]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [x40]
== hazfs.cs.umd.edu (1 distinct, 2 total) ==
Sep 13 21:25:07 hazfs.cs.umd.edu pcp[1222296]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (1 distinct, 1 total) ==
Sep 13 21:53:53 idm00 named[4166701]: client @0x7f11a006bce8 10.73.240.42#56106: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 13 21:37:38 idmp0 named[1598691]: client @0x7f2d1c046568 10.73.240.43#65340: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 48 total) ==
Sep 13 21:08:13 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x48]
== krispykreme.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 21:19:50 krispykreme.cs.umd.edu sshd-session[1816373]: pam_access(sshd:auth): access denied for user `heng' from `173.73.25.237'
== matrix (7 distinct, 8 total) ==
Sep 13 21:07:09 matrix sshd[1863384]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 13 21:07:09 matrix sshd[1863384]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 13 21:07:09 matrix sshd[1863384]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 13 21:07:09 matrix sshd[1863384]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 13 21:07:11 matrix sshd[1863384]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 13 21:07:11 matrix sshd[1863384]: error: kex_protocol_error: type 30 seq 7 [preauth]
Sep 13 21:19:07 matrix sshd[1869778]: error: PAM: Authentication failure for root from 212.116.238.51 [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 13 21:13:03 newhonors2 dhcpcd[2602412]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 21:09:09 outbound00.cs.umd.edu python3[3973715]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 21:13:06 outbound01.cs.umd.edu python3[2037575]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 13 21:11:33 sentry-docker00.cs.umd.edu systemd-udevd[3999607]: link_config: could not get ethtool features for veth943d495
Sep 13 21:11:33 sentry-docker00.cs.umd.edu systemd-udevd[3999607]: Could not set offload features of veth943d495: No such device
Sep 13 21:11:34 sentry-docker00.cs.umd.edu systemd-udevd[3999701]: link_config: could not get ethtool features for vethd49b1fe
Sep 13 21:11:34 sentry-docker00.cs.umd.edu systemd-udevd[3999701]: Could not set offload features of vethd49b1fe: No such device
Sep 13 21:11:34 sentry-docker00.cs.umd.edu systemd-udevd[3999731]: Could not generate persistent MAC address for vethd5c0e57: No such file or directory
Sep 13 21:11:34 sentry-docker00.cs.umd.edu systemd-udevd[3999732]: Could not generate persistent MAC address for veth7e15705: No such file or directory
Sep 13 21:11:34 sentry-docker00.cs.umd.edu systemd-udevd[3999735]: Could not generate persistent MAC address for veth6437d39: No such file or directory
Sep 13 21:11:34 sentry-docker00.cs.umd.edu systemd-udevd[3999736]: Could not generate persistent MAC address for veth5664dba: No such file or directory
Sep 13 21:11:34 sentry-docker00.cs.umd.edu systemd-udevd[3999737]: Could not generate persistent MAC address for vethf4d19f7: No such file or directory
Sep 13 21:11:34 sentry-docker00.cs.umd.edu systemd-udevd[3999740]: Could not generate persistent MAC address for vetheb36b92: No such file or directory
Sep 13 21:11:34 sentry-docker00.cs.umd.edu systemd-udevd[3999741]: Could not generate persistent MAC address for veth92df3ac: No such file or directory
Sep 13 21:11:34 sentry-docker00.cs.umd.edu systemd-udevd[3999742]: Could not generate persistent MAC address for veth5daf12c: No such file or directory
Sep 13 21:11:34 sentry-docker00.cs.umd.edu systemd-udevd[3999823]: Could not generate persistent MAC address for vethe1963c9: No such file or directory
Sep 13 21:11:34 sentry-docker00.cs.umd.edu systemd-udevd[3999825]: Could not generate persistent MAC address for veth28bcb19: No such file or directory
Sep 13 21:31:42 sentry-docker00.cs.umd.edu systemd-udevd[4009332]: link_config: could not get ethtool features for vethd5c0e57
Sep 13 21:31:42 sentry-docker00.cs.umd.edu systemd-udevd[4009332]: Could not set offload features of vethd5c0e57: No such device
Sep 13 21:31:42 sentry-docker00.cs.umd.edu systemd-udevd[4009370]: Could not generate persistent MAC address for vethe68c957: No such file or directory
Sep 13 21:31:42 sentry-docker00.cs.umd.edu systemd-udevd[4009371]: Could not generate persistent MAC address for veth719438a: No such file or directory
Sep 13 21:31:42 sentry-docker00.cs.umd.edu systemd-udevd[4009374]: Could not generate persistent MAC address for veth8faed61: No such file or directory
Sep 13 21:31:42 sentry-docker00.cs.umd.edu systemd-udevd[4009375]: Could not generate persistent MAC address for veth403982a: No such file or directory
Sep 13 21:31:42 sentry-docker00.cs.umd.edu systemd-udevd[4009381]: Could not generate persistent MAC address for veth7936b87: No such file or directory
Sep 13 21:31:42 sentry-docker00.cs.umd.edu systemd-udevd[4009383]: Could not generate persistent MAC address for vethaceb5af: No such file or directory
Sep 13 21:31:42 sentry-docker00.cs.umd.edu systemd-udevd[4009400]: Could not generate persistent MAC address for veth6819120: No such file or directory
Sep 13 21:31:42 sentry-docker00.cs.umd.edu systemd-udevd[4009401]: Could not generate persistent MAC address for veth288c88b: No such file or directory
Sep 13 21:31:42 sentry-docker00.cs.umd.edu systemd-udevd[4009419]: Could not generate persistent MAC address for vethe87445c: No such file or directory
Sep 13 21:31:42 sentry-docker00.cs.umd.edu systemd-udevd[4009424]: Could not generate persistent MAC address for veth0b4028d: No such file or directory
Sep 13 21:51:50 sentry-docker00.cs.umd.edu systemd-udevd[4018766]: link_config: could not get ethtool features for veth7936b87
Sep 13 21:51:50 sentry-docker00.cs.umd.edu systemd-udevd[4018766]: Could not set offload features of veth7936b87: No such device
Sep 13 21:51:50 sentry-docker00.cs.umd.edu systemd-udevd[4018801]: Could not generate persistent MAC address for veth30e4374: No such file or directory
Sep 13 21:51:50 sentry-docker00.cs.umd.edu systemd-udevd[4018802]: Could not generate persistent MAC address for veth9c79f8e: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 13 21:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 13 21:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 13 21:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 13 21:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 13 21:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 13 21:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 13 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 10 total) ==
Sep 13 21:12:34 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x10]
== submit26-b9-f2 (1 distinct, 3 total) ==
Sep 13 21:13:55 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f3 (10 distinct, 17 total) ==
Sep 13 21:05:05 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x8]
Sep 13 21:06:40 submit26-b9-f3 setroubleshoot[766677]: 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 13 21:06:40 submit26-b9-f3 setroubleshoot[766677]: 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 13 21:06:40 submit26-b9-f3 setroubleshoot[766677]: 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 13 21:06:40 submit26-b9-f3 setroubleshoot[766677]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.h8wGCX/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 13 21:06:41 submit26-b9-f3 setroubleshoot[766677]: 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 13 21:06:41 submit26-b9-f3 setroubleshoot[766677]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.h8wGCX. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 13 21:06:41 submit26-b9-f3 setroubleshoot[766677]: 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 13 21:06:41 submit26-b9-f3 setroubleshoot[766677]: 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 13 21:06:41 submit26-b9-f3 setroubleshoot[766677]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68
== submit26-b9-f4 (10 distinct, 12 total) ==
Sep 13 21:24:44 submit26-b9-f4 setroubleshoot[566239]: 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 13 21:24:44 submit26-b9-f4 setroubleshoot[566239]: 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 13 21:24:44 submit26-b9-f4 setroubleshoot[566239]: 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 13 21:24:44 submit26-b9-f4 setroubleshoot[566239]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.l6n6cV/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 13 21:24:44 submit26-b9-f4 setroubleshoot[566239]: 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 13 21:24:44 submit26-b9-f4 setroubleshoot[566239]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.l6n6cV. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 13 21:24:44 submit26-b9-f4 setroubleshoot[566239]: 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 13 21:24:44 submit26-b9-f4 setroubleshoot[566239]: 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 13 21:24:44 submit26-b9-f4 setroubleshoot[566239]: 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 13 21:40:08 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.0443s
Status : exited 0
Output :
Syslog digest — 2026-09-13 21:05 EDT
Processed 1,855 lines, filtered 1,472 (79%). 383 unknown (64 distinct) from 19 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 20:42:26 b0b02.cs.umd.edu rustdesk[807684]: cannot open display:
== biggulp.cs.umd.edu (2 distinct, 2 total) ==
Sep 13 20:12:20 biggulp.cs.umd.edu sshd-session[1079231]: pam_access(sshd:auth): access denied for user `egolub' from `108.28.255.142'
Sep 13 20:25:54 biggulp.cs.umd.edu sshd-session[1082162]: pam_access(sshd:auth): access denied for user `profk' from `71.191.192.56'
== csfw00a (1 distinct, 119 total) ==
Sep 13 20:04:19 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x119]
== galax (2 distinct, 80 total) ==
Sep 13 20:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 13 20:05:42 galax systemd-journald[670]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [x40]
== hazfs.cs.umd.edu (1 distinct, 2 total) ==
Sep 13 20:25:04 hazfs.cs.umd.edu pcp[907098]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (1 distinct, 1 total) ==
Sep 13 20:53:53 idm00 named[4166701]: client @0x7f11a004d0a8 10.73.240.42#58265: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 13 20:37:38 idmp0 named[1598691]: client @0x7f2d3802ab18 10.73.240.43#62362: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 42 total) ==
Sep 13 20:07:48 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x42]
== matrix (1 distinct, 2 total) ==
Sep 13 20:15:29 matrix sshd[1834107]: error: PAM: Authentication failure for root from 212.116.238.51 [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 13 20:13:03 newhonors2 dhcpcd[2600471]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 20:09:09 outbound00.cs.umd.edu python3[3959769]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 20:13:06 outbound01.cs.umd.edu python3[2023650]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 13 20:11:09 sentry-docker00.cs.umd.edu systemd-udevd[3971389]: link_config: could not get ethtool features for veth0590594
Sep 13 20:11:09 sentry-docker00.cs.umd.edu systemd-udevd[3971389]: Could not set offload features of veth0590594: No such device
Sep 13 20:11:09 sentry-docker00.cs.umd.edu systemd-udevd[3971479]: Could not generate persistent MAC address for vethe0c25ee: No such file or directory
Sep 13 20:11:09 sentry-docker00.cs.umd.edu systemd-udevd[3971480]: Could not generate persistent MAC address for veth304a1a8: No such file or directory
Sep 13 20:11:09 sentry-docker00.cs.umd.edu systemd-udevd[3971503]: Could not generate persistent MAC address for veth4888ec9: No such file or directory
Sep 13 20:11:09 sentry-docker00.cs.umd.edu systemd-udevd[3971492]: Could not generate persistent MAC address for vethf5298f7: No such file or directory
Sep 13 20:11:09 sentry-docker00.cs.umd.edu systemd-udevd[3971493]: Could not generate persistent MAC address for veth363c6f8: No such file or directory
Sep 13 20:11:09 sentry-docker00.cs.umd.edu systemd-udevd[3971485]: Could not generate persistent MAC address for vethe2c3941: No such file or directory
Sep 13 20:11:09 sentry-docker00.cs.umd.edu systemd-udevd[3971487]: Could not generate persistent MAC address for veth9cfe07b: No such file or directory
Sep 13 20:11:09 sentry-docker00.cs.umd.edu systemd-udevd[3971498]: Could not generate persistent MAC address for vethd88d77e: No such file or directory
Sep 13 20:11:09 sentry-docker00.cs.umd.edu systemd-udevd[3971487]: Could not generate persistent MAC address for veth4b53d7c: No such file or directory
Sep 13 20:11:09 sentry-docker00.cs.umd.edu systemd-udevd[3971498]: Could not generate persistent MAC address for vethe565fa5: No such file or directory
Sep 13 20:31:17 sentry-docker00.cs.umd.edu systemd-udevd[3980814]: link_config: could not get ethtool features for vethf5298f7
Sep 13 20:31:17 sentry-docker00.cs.umd.edu systemd-udevd[3980814]: Could not set offload features of vethf5298f7: No such device
Sep 13 20:31:17 sentry-docker00.cs.umd.edu systemd-udevd[3980842]: Could not generate persistent MAC address for vethae02a9c: No such file or directory
Sep 13 20:31:17 sentry-docker00.cs.umd.edu systemd-udevd[3980843]: Could not generate persistent MAC address for veth0e03323: No such file or directory
Sep 13 20:31:17 sentry-docker00.cs.umd.edu systemd-udevd[3980846]: Could not generate persistent MAC address for veth9159f03: No such file or directory
Sep 13 20:31:17 sentry-docker00.cs.umd.edu systemd-udevd[3980847]: Could not generate persistent MAC address for vethfd0caf1: No such file or directory
Sep 13 20:31:17 sentry-docker00.cs.umd.edu systemd-udevd[3980852]: Could not generate persistent MAC address for vethcbc9793: No such file or directory
Sep 13 20:31:17 sentry-docker00.cs.umd.edu systemd-udevd[3980850]: Could not generate persistent MAC address for veth6c80c0d: No such file or directory
Sep 13 20:31:17 sentry-docker00.cs.umd.edu systemd-udevd[3980858]: Could not generate persistent MAC address for veth01a3e04: No such file or directory
Sep 13 20:31:17 sentry-docker00.cs.umd.edu systemd-udevd[3980851]: Could not generate persistent MAC address for veth9735e6f: No such file or directory
Sep 13 20:31:17 sentry-docker00.cs.umd.edu systemd-udevd[3980858]: Could not generate persistent MAC address for vetha9ee264: No such file or directory
Sep 13 20:31:17 sentry-docker00.cs.umd.edu systemd-udevd[3980843]: Could not generate persistent MAC address for vethca9cf0b: No such file or directory
Sep 13 20:51:25 sentry-docker00.cs.umd.edu systemd-udevd[3990265]: link_config: could not get ethtool features for vethcbc9793
Sep 13 20:51:25 sentry-docker00.cs.umd.edu systemd-udevd[3990265]: Could not set offload features of vethcbc9793: No such device
Sep 13 20:51:25 sentry-docker00.cs.umd.edu systemd-udevd[3990269]: link_config: could not set ethtool features for veth9159f03
Sep 13 20:51:25 sentry-docker00.cs.umd.edu systemd-udevd[3990269]: Could not set offload features of veth9159f03: Operation not permitted
Sep 13 20:51:25 sentry-docker00.cs.umd.edu systemd-udevd[3990296]: Could not generate persistent MAC address for veth3c90438: No such file or directory
Sep 13 20:51:25 sentry-docker00.cs.umd.edu systemd-udevd[3990297]: Could not generate persistent MAC address for veth2220fa1: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 13 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 13 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 13 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 13 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 13 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 13 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 13 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 4 total) ==
Sep 13 20:06:30 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f2 (1 distinct, 4 total) ==
Sep 13 20:28:32 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f3 (1 distinct, 8 total) ==
Sep 13 20:07:21 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x8]
== submit26-b9-f4 (1 distinct, 4 total) ==
Sep 13 20:18:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== tma-0 (1 distinct, 1 total) ==
Sep 13 20:12:41 tma-0 sshd[5840]: fatal: ssh_packet_get_string: incomplete message [preauth]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0489s
Status : exited 0
Output :
Syslog digest — 2026-09-13 20:05 EDT
Processed 2,270 lines, filtered 1,757 (77%). 513 unknown (125 distinct) from 20 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 19:42:22 b0b02.cs.umd.edu rustdesk[792406]: cannot open display:
== csfw00a (2 distinct, 131 total) ==
Sep 13 19:03:58 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x127]
Sep 13 19:36:21 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x4]
== galax (2 distinct, 80 total) ==
Sep 13 19:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 13 19:05:42 galax systemd-journald[670]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [x40]
== gle-dind00.cs.umd.edu (32 distinct, 32 total) ==
Sep 13 19:41:31 gle-dind00.cs.umd.edu systemd-udevd[2985216]: Could not generate persistent MAC address for vethe2d0541: No such file or directory
Sep 13 19:41:31 gle-dind00.cs.umd.edu systemd-udevd[2985218]: Could not generate persistent MAC address for vethfa73652: No such file or directory
Sep 13 19:41:32 gle-dind00.cs.umd.edu systemd-udevd[2985316]: Could not generate persistent MAC address for veth9d9f214: No such file or directory
Sep 13 19:41:32 gle-dind00.cs.umd.edu systemd-udevd[2985317]: Could not generate persistent MAC address for veth3f034c7: No such file or directory
Sep 13 19:41:32 gle-dind00.cs.umd.edu systemd-udevd[2985416]: Could not generate persistent MAC address for veth5eec317: No such file or directory
Sep 13 19:41:32 gle-dind00.cs.umd.edu systemd-udevd[2985417]: Could not generate persistent MAC address for veth7b97c75: No such file or directory
Sep 13 19:41:33 gle-dind00.cs.umd.edu systemd-udevd[2985514]: Could not generate persistent MAC address for veth4aedba1: No such file or directory
Sep 13 19:41:33 gle-dind00.cs.umd.edu systemd-udevd[2985515]: Could not generate persistent MAC address for veth827eac7: No such file or directory
Sep 13 19:41:34 gle-dind00.cs.umd.edu systemd-udevd[2985611]: Could not generate persistent MAC address for vethd89176a: No such file or directory
Sep 13 19:41:34 gle-dind00.cs.umd.edu systemd-udevd[2985612]: Could not generate persistent MAC address for veth7c10e2a: No such file or directory
Sep 13 19:41:39 gle-dind00.cs.umd.edu systemd-udevd[2985794]: Could not generate persistent MAC address for veth20a24ad: No such file or directory
Sep 13 19:41:39 gle-dind00.cs.umd.edu systemd-udevd[2985795]: Could not generate persistent MAC address for veth8ae3daa: No such file or directory
Sep 13 19:41:43 gle-dind00.cs.umd.edu systemd-udevd[2985910]: Could not generate persistent MAC address for veth3ff532a: No such file or directory
Sep 13 19:41:43 gle-dind00.cs.umd.edu systemd-udevd[2985911]: Could not generate persistent MAC address for vethb36b49a: No such file or directory
Sep 13 19:41:51 gle-dind00.cs.umd.edu systemd-udevd[2986065]: Could not generate persistent MAC address for vethc4a008e: No such file or directory
Sep 13 19:41:51 gle-dind00.cs.umd.edu systemd-udevd[2986066]: Could not generate persistent MAC address for vetha7ed096: No such file or directory
Sep 13 19:41:52 gle-dind00.cs.umd.edu systemd-udevd[2986193]: Could not generate persistent MAC address for veth0da852b: No such file or directory
Sep 13 19:41:52 gle-dind00.cs.umd.edu systemd-udevd[2986192]: Could not generate persistent MAC address for veth3911e1f: No such file or directory
Sep 13 19:41:53 gle-dind00.cs.umd.edu systemd-udevd[2986291]: Could not generate persistent MAC address for vethcd2a577: No such file or directory
Sep 13 19:41:53 gle-dind00.cs.umd.edu systemd-udevd[2986292]: Could not generate persistent MAC address for veth01f0a45: No such file or directory
Sep 13 19:41:54 gle-dind00.cs.umd.edu systemd-udevd[2986389]: Could not generate persistent MAC address for vethb0ba1a8: No such file or directory
Sep 13 19:41:54 gle-dind00.cs.umd.edu systemd-udevd[2986390]: Could not generate persistent MAC address for vethb1911d7: No such file or directory
Sep 13 19:41:55 gle-dind00.cs.umd.edu systemd-udevd[2986487]: Could not generate persistent MAC address for vethd0817d2: No such file or directory
Sep 13 19:41:55 gle-dind00.cs.umd.edu systemd-udevd[2986488]: Could not generate persistent MAC address for veth54e4f1b: No such file or directory
Sep 13 19:41:55 gle-dind00.cs.umd.edu systemd-udevd[2986587]: Could not generate persistent MAC address for vethcd93d4d: No such file or directory
Sep 13 19:41:55 gle-dind00.cs.umd.edu systemd-udevd[2986586]: Could not generate persistent MAC address for vethc7c556c: No such file or directory
Sep 13 19:42:01 gle-dind00.cs.umd.edu systemd-udevd[2986780]: Could not generate persistent MAC address for vethfd12016: No such file or directory
Sep 13 19:42:01 gle-dind00.cs.umd.edu systemd-udevd[2986781]: Could not generate persistent MAC address for veth9e760c9: No such file or directory
Sep 13 19:42:04 gle-dind00.cs.umd.edu systemd-udevd[2986899]: Could not generate persistent MAC address for veth134554d: No such file or directory
Sep 13 19:42:04 gle-dind00.cs.umd.edu systemd-udevd[2986900]: Could not generate persistent MAC address for vethc8fdeb4: No such file or directory
... 2 more distinct messages not shown
== gle-dind02.cs.umd.edu (21 distinct, 21 total) ==
Sep 13 19:40:31 gle-dind02.cs.umd.edu systemd-udevd[3526139]: Could not generate persistent MAC address for veth2874cbf: No such file or directory
Sep 13 19:40:31 gle-dind02.cs.umd.edu systemd-udevd[3526140]: Could not generate persistent MAC address for vethbff6178: No such file or directory
Sep 13 19:40:31 gle-dind02.cs.umd.edu systemd-udevd[3526241]: Could not generate persistent MAC address for veth9f9b7c8: No such file or directory
Sep 13 19:40:31 gle-dind02.cs.umd.edu systemd-udevd[3526242]: Could not generate persistent MAC address for vethb2de08f: No such file or directory
Sep 13 19:40:32 gle-dind02.cs.umd.edu systemd-udevd[3526341]: Could not generate persistent MAC address for vethdd61538: No such file or directory
Sep 13 19:40:32 gle-dind02.cs.umd.edu systemd-udevd[3526342]: Could not generate persistent MAC address for vethd3143ba: No such file or directory
Sep 13 19:40:33 gle-dind02.cs.umd.edu systemd-udevd[3526440]: Could not generate persistent MAC address for veth7092836: No such file or directory
Sep 13 19:40:33 gle-dind02.cs.umd.edu systemd-udevd[3526441]: Could not generate persistent MAC address for veth65f4d2b: No such file or directory
Sep 13 19:40:34 gle-dind02.cs.umd.edu systemd-udevd[3526540]: Could not generate persistent MAC address for vetha8ef8cd: No such file or directory
Sep 13 19:40:34 gle-dind02.cs.umd.edu systemd-udevd[3526541]: Could not generate persistent MAC address for veth4ff0b64: No such file or directory
Sep 13 19:40:37 gle-dind02.cs.umd.edu systemd-udevd[3526730]: Could not generate persistent MAC address for veth3f0cef0: No such file or directory
Sep 13 19:40:37 gle-dind02.cs.umd.edu systemd-udevd[3526731]: Could not generate persistent MAC address for vethd445402: No such file or directory
Sep 13 19:40:39 gle-dind02.cs.umd.edu lldpd[984]: unable to send packet on real device for vethd445402: No such device or address
Sep 13 19:40:39 gle-dind02.cs.umd.edu systemd-udevd[3526847]: Could not generate persistent MAC address for veth73ca8b0: No such file or directory
Sep 13 19:40:39 gle-dind02.cs.umd.edu systemd-udevd[3526848]: Could not generate persistent MAC address for veth9b0972d: No such file or directory
Sep 13 19:41:37 gle-dind02.cs.umd.edu systemd-udevd[3527966]: Could not generate persistent MAC address for veth17f12cc: No such file or directory
Sep 13 19:41:37 gle-dind02.cs.umd.edu systemd-udevd[3527965]: Could not generate persistent MAC address for veth2a6db49: No such file or directory
Sep 13 19:41:40 gle-dind02.cs.umd.edu systemd-udevd[3528088]: Could not generate persistent MAC address for vethe1e4c2a: No such file or directory
Sep 13 19:41:40 gle-dind02.cs.umd.edu systemd-udevd[3528089]: Could not generate persistent MAC address for veth0f71535: No such file or directory
Sep 13 19:41:48 gle-dind02.cs.umd.edu systemd-udevd[3528238]: Could not generate persistent MAC address for vethc1bbe17: No such file or directory
Sep 13 19:41:48 gle-dind02.cs.umd.edu systemd-udevd[3528239]: Could not generate persistent MAC address for veth74e3f72: No such file or directory
== gle-dind04 (1 distinct, 1 total) ==
Sep 13 19:14:30 gle-dind04 lldpd[22022]: unable to send packet on real device for veth842b573: No such device or address
== hazfs.cs.umd.edu (12 distinct, 68 total) ==
Sep 13 19:25:10 hazfs.cs.umd.edu pcp[591569]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
Sep 13 20:01:04 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 13 20:01:04 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 13 20:01:04 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 13 20:01:04 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 13 20:01:04 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 13 20:01:04 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 13 20:01:04 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 13 20:01:04 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 13 20:01:04 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 13 20:01:04 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 13 20:01:04 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 13 19:53:53 idm00 named[4166701]: client @0x7f11980511b8 10.73.240.42#56400: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 13 19:37:38 idmp0 named[1598691]: client @0x7f2d440131e8 10.73.240.43#62677: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 42 total) ==
Sep 13 19:07:55 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x42]
== matrix (1 distinct, 2 total) ==
Sep 13 19:11:44 matrix sshd[1797502]: error: PAM: Authentication failure for root from 212.116.238.51 [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 13 19:13:03 newhonors2 dhcpcd[2598629]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 19:09:09 outbound00.cs.umd.edu python3[3945803]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 19:13:06 outbound01.cs.umd.edu python3[2009684]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 13 19:10:44 sentry-docker00.cs.umd.edu systemd-udevd[3943151]: link_config: could not get ethtool features for vethdf664c5
Sep 13 19:10:44 sentry-docker00.cs.umd.edu systemd-udevd[3943151]: Could not set offload features of vethdf664c5: No such device
Sep 13 19:10:44 sentry-docker00.cs.umd.edu systemd-udevd[3943182]: Could not generate persistent MAC address for vetha865440: No such file or directory
Sep 13 19:10:44 sentry-docker00.cs.umd.edu systemd-udevd[3943183]: Could not generate persistent MAC address for veth4aad1bc: No such file or directory
Sep 13 19:10:44 sentry-docker00.cs.umd.edu systemd-udevd[3943186]: Could not generate persistent MAC address for vethe378d56: No such file or directory
Sep 13 19:10:44 sentry-docker00.cs.umd.edu systemd-udevd[3943187]: Could not generate persistent MAC address for veth8b59e42: No such file or directory
Sep 13 19:10:44 sentry-docker00.cs.umd.edu systemd-udevd[3943210]: Could not generate persistent MAC address for veth9adac79: No such file or directory
Sep 13 19:10:44 sentry-docker00.cs.umd.edu systemd-udevd[3943211]: Could not generate persistent MAC address for veth57f493f: No such file or directory
Sep 13 19:10:44 sentry-docker00.cs.umd.edu systemd-udevd[3943229]: Could not generate persistent MAC address for vetha2b4a0d: No such file or directory
Sep 13 19:10:44 sentry-docker00.cs.umd.edu systemd-udevd[3943228]: Could not generate persistent MAC address for vethfc3b8a6: No such file or directory
Sep 13 19:10:44 sentry-docker00.cs.umd.edu systemd-udevd[3943220]: Could not generate persistent MAC address for vethbdd14d4: No such file or directory
Sep 13 19:10:44 sentry-docker00.cs.umd.edu systemd-udevd[3943222]: Could not generate persistent MAC address for veth8b44973: No such file or directory
Sep 13 19:30:52 sentry-docker00.cs.umd.edu systemd-udevd[3952601]: link_config: could not get ethtool features for vetha865440
Sep 13 19:30:52 sentry-docker00.cs.umd.edu systemd-udevd[3952601]: Could not set offload features of vetha865440: No such device
Sep 13 19:30:52 sentry-docker00.cs.umd.edu systemd-udevd[3952629]: Could not generate persistent MAC address for vethd74d184: No such file or directory
Sep 13 19:30:52 sentry-docker00.cs.umd.edu systemd-udevd[3952630]: Could not generate persistent MAC address for vethc6fd4cc: No such file or directory
Sep 13 19:30:52 sentry-docker00.cs.umd.edu systemd-udevd[3952633]: Could not generate persistent MAC address for vethd225c56: No such file or directory
Sep 13 19:30:52 sentry-docker00.cs.umd.edu systemd-udevd[3952634]: Could not generate persistent MAC address for vethd8312d3: No such file or directory
Sep 13 19:30:52 sentry-docker00.cs.umd.edu systemd-udevd[3952657]: Could not generate persistent MAC address for vetha896a6c: No such file or directory
Sep 13 19:30:52 sentry-docker00.cs.umd.edu systemd-udevd[3952658]: Could not generate persistent MAC address for veth0b83257: No such file or directory
Sep 13 19:30:52 sentry-docker00.cs.umd.edu systemd-udevd[3952672]: Could not generate persistent MAC address for vethfc9776c: No such file or directory
Sep 13 19:30:52 sentry-docker00.cs.umd.edu systemd-udevd[3952682]: Could not generate persistent MAC address for veth8740cb6: No such file or directory
Sep 13 19:30:52 sentry-docker00.cs.umd.edu systemd-udevd[3952672]: Could not generate persistent MAC address for vethccf631c: No such file or directory
Sep 13 19:30:52 sentry-docker00.cs.umd.edu systemd-udevd[3952682]: Could not generate persistent MAC address for vethb899197: No such file or directory
Sep 13 19:51:00 sentry-docker00.cs.umd.edu systemd-udevd[3962046]: link_config: could not get ethtool features for vethfc9776c
Sep 13 19:51:00 sentry-docker00.cs.umd.edu systemd-udevd[3962046]: Could not set offload features of vethfc9776c: No such device
Sep 13 19:51:00 sentry-docker00.cs.umd.edu systemd-udevd[3962076]: Could not generate persistent MAC address for veth199c828: No such file or directory
Sep 13 19:51:00 sentry-docker00.cs.umd.edu systemd-udevd[3962077]: Could not generate persistent MAC address for veth8e966c0: No such file or directory
Sep 13 19:51:00 sentry-docker00.cs.umd.edu systemd-udevd[3962080]: Could not generate persistent MAC address for veth13ffcc1: No such file or directory
Sep 13 19:51:00 sentry-docker00.cs.umd.edu systemd-udevd[3962097]: Could not generate persistent MAC address for vethf9b53d2: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 13 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 13 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 13 19:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 13 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 13 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 13 19:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 13 19:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 4 total) ==
Sep 13 19:13:07 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f2 (1 distinct, 7 total) ==
Sep 13 19:09:17 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
== submit26-b9-f3 (1 distinct, 9 total) ==
Sep 13 19:14:53 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x9]
== submit26-b9-f4 (1 distinct, 3 total) ==
Sep 13 19:05:08 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.0473s
Status : exited 0
Output :
Syslog digest — 2026-09-13 19:05 EDT
Processed 1,919 lines, filtered 1,460 (76%). 459 unknown (140 distinct) from 21 host(s).
== b0b02.cs.umd.edu (4 distinct, 4 total) ==
Sep 13 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-13T22:10:59.422407363Z" level=info msg="PurgeUploads starting: olderThan=2026-09-06 22:10:59.422329243 +0000 UTC m=+3544620.182257552, actuallyDelete=true"
Sep 13 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-13T22:10:59.422889817Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1"
Sep 13 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-13T22:10:59.422909742Z" 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 13 18:42:18 b0b02.cs.umd.edu rustdesk[777262]: cannot open display:
== csfw00a (1 distinct, 124 total) ==
Sep 13 18:03:46 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x124]
== galax (2 distinct, 80 total) ==
Sep 13 18:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 13 18:05:42 galax systemd-journald[670]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [x40]
== gle-dind00.cs.umd.edu (20 distinct, 20 total) ==
Sep 13 18:53:14 gle-dind00.cs.umd.edu systemd-udevd[2972820]: Could not generate persistent MAC address for veth3082f37: No such file or directory
Sep 13 18:53:14 gle-dind00.cs.umd.edu systemd-udevd[2972819]: Could not generate persistent MAC address for vethf4fda16: No such file or directory
Sep 13 18:53:15 gle-dind00.cs.umd.edu systemd-udevd[2972920]: Could not generate persistent MAC address for veth1af9fb8: No such file or directory
Sep 13 18:53:15 gle-dind00.cs.umd.edu systemd-udevd[2972921]: Could not generate persistent MAC address for veth7fa63ee: No such file or directory
Sep 13 18:53:16 gle-dind00.cs.umd.edu systemd-udevd[2973021]: Could not generate persistent MAC address for vethc287f88: No such file or directory
Sep 13 18:53:16 gle-dind00.cs.umd.edu systemd-udevd[2973022]: Could not generate persistent MAC address for vethbb95bbe: No such file or directory
Sep 13 18:53:17 gle-dind00.cs.umd.edu systemd-udevd[2973123]: Could not generate persistent MAC address for vethd05d5a9: No such file or directory
Sep 13 18:53:17 gle-dind00.cs.umd.edu systemd-udevd[2973124]: Could not generate persistent MAC address for veth3d8794a: No such file or directory
Sep 13 18:53:18 gle-dind00.cs.umd.edu systemd-udevd[2973223]: Could not generate persistent MAC address for vethb5e5d95: No such file or directory
Sep 13 18:53:18 gle-dind00.cs.umd.edu systemd-udevd[2973224]: Could not generate persistent MAC address for veth45e3ede: No such file or directory
Sep 13 18:53:21 gle-dind00.cs.umd.edu systemd-udevd[2973437]: Could not generate persistent MAC address for veth5b52cee: No such file or directory
Sep 13 18:53:21 gle-dind00.cs.umd.edu systemd-udevd[2973438]: Could not generate persistent MAC address for veth0e63339: No such file or directory
Sep 13 18:53:22 gle-dind00.cs.umd.edu systemd-udevd[2973550]: Could not generate persistent MAC address for vethe881ab2: No such file or directory
Sep 13 18:53:22 gle-dind00.cs.umd.edu systemd-udevd[2973551]: Could not generate persistent MAC address for veth7009c56: No such file or directory
Sep 13 18:54:11 gle-dind00.cs.umd.edu systemd-udevd[2974533]: Could not generate persistent MAC address for veth2327ae8: No such file or directory
Sep 13 18:54:11 gle-dind00.cs.umd.edu systemd-udevd[2974534]: Could not generate persistent MAC address for veth07611de: No such file or directory
Sep 13 18:54:14 gle-dind00.cs.umd.edu systemd-udevd[2974645]: Could not generate persistent MAC address for vetha5de9a9: No such file or directory
Sep 13 18:54:14 gle-dind00.cs.umd.edu systemd-udevd[2974646]: Could not generate persistent MAC address for veth115bf2d: No such file or directory
Sep 13 18:54:22 gle-dind00.cs.umd.edu systemd-udevd[2974786]: Could not generate persistent MAC address for veth9a1e92a: No such file or directory
Sep 13 18:54:22 gle-dind00.cs.umd.edu systemd-udevd[2974787]: Could not generate persistent MAC address for veth695ef19: No such file or directory
== gle-dind02.cs.umd.edu (36 distinct, 36 total) ==
Sep 13 18:52:57 gle-dind02.cs.umd.edu systemd-udevd[3514935]: Could not generate persistent MAC address for veth7623d80: No such file or directory
Sep 13 18:52:57 gle-dind02.cs.umd.edu systemd-udevd[3514936]: Could not generate persistent MAC address for veth8646c6d: No such file or directory
Sep 13 18:52:57 gle-dind02.cs.umd.edu systemd-udevd[3515032]: Could not generate persistent MAC address for veth551fe5e: No such file or directory
Sep 13 18:52:57 gle-dind02.cs.umd.edu systemd-udevd[3515033]: Could not generate persistent MAC address for veth5d82b2e: No such file or directory
Sep 13 18:52:58 gle-dind02.cs.umd.edu systemd-udevd[3515129]: Could not generate persistent MAC address for veth1849bea: No such file or directory
Sep 13 18:52:58 gle-dind02.cs.umd.edu systemd-udevd[3515130]: Could not generate persistent MAC address for veth155fa7f: No such file or directory
Sep 13 18:52:59 gle-dind02.cs.umd.edu systemd-udevd[3515230]: Could not generate persistent MAC address for vethcc92aea: No such file or directory
Sep 13 18:52:59 gle-dind02.cs.umd.edu systemd-udevd[3515231]: Could not generate persistent MAC address for veth7edd4ff: No such file or directory
Sep 13 18:53:00 gle-dind02.cs.umd.edu systemd-udevd[3515330]: Could not generate persistent MAC address for veth2e51c03: No such file or directory
Sep 13 18:53:00 gle-dind02.cs.umd.edu systemd-udevd[3515329]: Could not generate persistent MAC address for vethd803a8c: No such file or directory
Sep 13 18:53:03 gle-dind02.cs.umd.edu systemd-udevd[3515520]: Could not generate persistent MAC address for vethf747524: No such file or directory
Sep 13 18:53:03 gle-dind02.cs.umd.edu systemd-udevd[3515521]: Could not generate persistent MAC address for veth940a56f: No such file or directory
Sep 13 18:53:03 gle-dind02.cs.umd.edu systemd-udevd[3515628]: Could not generate persistent MAC address for veth8b39856: No such file or directory
Sep 13 18:53:03 gle-dind02.cs.umd.edu systemd-udevd[3515629]: Could not generate persistent MAC address for vethe42b126: No such file or directory
Sep 13 18:53:55 gle-dind02.cs.umd.edu systemd-udevd[3516721]: Could not generate persistent MAC address for veth95ab391: No such file or directory
Sep 13 18:53:55 gle-dind02.cs.umd.edu systemd-udevd[3516722]: Could not generate persistent MAC address for veth2f647c5: No such file or directory
Sep 13 18:53:58 gle-dind02.cs.umd.edu systemd-udevd[3516832]: Could not generate persistent MAC address for veth7831abd: No such file or directory
Sep 13 18:53:58 gle-dind02.cs.umd.edu systemd-udevd[3516833]: Could not generate persistent MAC address for veth0d0362e: No such file or directory
Sep 13 18:54:05 gle-dind02.cs.umd.edu systemd-udevd[3516952]: Could not generate persistent MAC address for vethe6bf297: No such file or directory
Sep 13 18:54:05 gle-dind02.cs.umd.edu systemd-udevd[3516953]: Could not generate persistent MAC address for vethaca437e: No such file or directory
Sep 13 18:54:27 gle-dind02.cs.umd.edu systemd-udevd[3517111]: Could not generate persistent MAC address for vethd98719c: No such file or directory
Sep 13 18:54:27 gle-dind02.cs.umd.edu systemd-udevd[3517110]: Could not generate persistent MAC address for veth159f7ff: No such file or directory
Sep 13 18:54:28 gle-dind02.cs.umd.edu systemd-udevd[3517210]: Could not generate persistent MAC address for veth7f48038: No such file or directory
Sep 13 18:54:28 gle-dind02.cs.umd.edu systemd-udevd[3517209]: Could not generate persistent MAC address for veth4582803: No such file or directory
Sep 13 18:54:29 gle-dind02.cs.umd.edu systemd-udevd[3517308]: Could not generate persistent MAC address for veth08de75b: No such file or directory
Sep 13 18:54:29 gle-dind02.cs.umd.edu systemd-udevd[3517309]: Could not generate persistent MAC address for veth182d5c2: No such file or directory
Sep 13 18:54:30 gle-dind02.cs.umd.edu systemd-udevd[3517407]: Could not generate persistent MAC address for vethb62aefe: No such file or directory
Sep 13 18:54:30 gle-dind02.cs.umd.edu systemd-udevd[3517408]: Could not generate persistent MAC address for veth2f9818e: No such file or directory
Sep 13 18:54:31 gle-dind02.cs.umd.edu systemd-udevd[3517506]: Could not generate persistent MAC address for vethd833839: No such file or directory
Sep 13 18:54:31 gle-dind02.cs.umd.edu systemd-udevd[3517505]: Could not generate persistent MAC address for vethe18dccf: No such file or directory
... 6 more distinct messages not shown
== gle-dind04 (1 distinct, 1 total) ==
Sep 13 18:35:23 gle-dind04 lldpd[22022]: unable to send packet on real device for veth23c8002: No such device or address
== hazfs.cs.umd.edu (1 distinct, 2 total) ==
Sep 13 18:25:06 hazfs.cs.umd.edu pcp[276008]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== helmsdeep (1 distinct, 1 total) ==
Sep 13 18:51:14 helmsdeep kernel: clocksource: timekeeping watchdog on CPU0: kvm-clock retried 1 times before success
== idm00 (1 distinct, 1 total) ==
Sep 13 18:53:53 idm00 named[4166701]: client @0x7f11a9430488 10.73.240.42#53428: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 13 18:37:38 idmp0 named[1598691]: client @0x7f2d2c035088 10.73.240.43#57147: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 34 total) ==
Sep 13 18:07:49 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x34]
== matrix (1 distinct, 2 total) ==
Sep 13 18:07:49 matrix sshd[1760234]: error: PAM: Authentication failure for root from 212.116.238.51 [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 13 18:13:02 newhonors2 dhcpcd[2596785]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 18:09:09 outbound00.cs.umd.edu python3[3931688]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 18:13:06 outbound01.cs.umd.edu python3[1995696]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914668]: link_config: could not get ethtool features for veth12a1f9d
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914668]: Could not set offload features of veth12a1f9d: No such device
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914669]: link_config: could not get ethtool features for vethd3debc7
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914669]: Could not set offload features of vethd3debc7: No such device
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914713]: Could not generate persistent MAC address for vethcde04b9: No such file or directory
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914714]: Could not generate persistent MAC address for vethd011312: No such file or directory
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914717]: Could not generate persistent MAC address for veth06669d5: No such file or directory
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914718]: Could not generate persistent MAC address for vetha08cf66: No such file or directory
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914730]: Could not generate persistent MAC address for vethc96e619: No such file or directory
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914726]: Could not generate persistent MAC address for veth75c4552: No such file or directory
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914714]: Could not generate persistent MAC address for veth9f137a9: No such file or directory
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914721]: Could not generate persistent MAC address for veth896cc39: No such file or directory
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914836]: Could not generate persistent MAC address for veth11bffbb: No such file or directory
Sep 13 18:10:19 sentry-docker00.cs.umd.edu systemd-udevd[3914837]: Could not generate persistent MAC address for vethb10255f: No such file or directory
Sep 13 18:30:27 sentry-docker00.cs.umd.edu systemd-udevd[3924306]: link_config: could not get ethtool features for veth06669d5
Sep 13 18:30:27 sentry-docker00.cs.umd.edu systemd-udevd[3924306]: Could not set offload features of veth06669d5: No such device
Sep 13 18:30:27 sentry-docker00.cs.umd.edu systemd-udevd[3924338]: Could not generate persistent MAC address for vethee15456: No such file or directory
Sep 13 18:30:27 sentry-docker00.cs.umd.edu systemd-udevd[3924339]: Could not generate persistent MAC address for vethdfe541d: No such file or directory
Sep 13 18:30:27 sentry-docker00.cs.umd.edu systemd-udevd[3924342]: Could not generate persistent MAC address for vethef8f7f8: No such file or directory
Sep 13 18:30:27 sentry-docker00.cs.umd.edu systemd-udevd[3924343]: Could not generate persistent MAC address for veth4a0c0b6: No such file or directory
Sep 13 18:30:27 sentry-docker00.cs.umd.edu systemd-udevd[3924354]: Could not generate persistent MAC address for veth27ff802: No such file or directory
Sep 13 18:30:27 sentry-docker00.cs.umd.edu systemd-udevd[3924364]: Could not generate persistent MAC address for vethc8f3912: No such file or directory
Sep 13 18:30:27 sentry-docker00.cs.umd.edu systemd-udevd[3924354]: Could not generate persistent MAC address for vethac0e2f3: No such file or directory
Sep 13 18:30:27 sentry-docker00.cs.umd.edu systemd-udevd[3924364]: Could not generate persistent MAC address for vethc347260: No such file or directory
Sep 13 18:30:27 sentry-docker00.cs.umd.edu systemd-udevd[3924375]: Could not generate persistent MAC address for vethd72fff7: No such file or directory
Sep 13 18:30:27 sentry-docker00.cs.umd.edu systemd-udevd[3924374]: Could not generate persistent MAC address for veth60e71ad: No such file or directory
Sep 13 18:50:35 sentry-docker00.cs.umd.edu systemd-udevd[3933775]: link_config: could not get ethtool features for vethee15456
Sep 13 18:50:35 sentry-docker00.cs.umd.edu systemd-udevd[3933775]: Could not set offload features of vethee15456: No such device
Sep 13 18:50:36 sentry-docker00.cs.umd.edu systemd-udevd[3933809]: Could not generate persistent MAC address for vethfb877fb: No such file or directory
Sep 13 18:50:36 sentry-docker00.cs.umd.edu systemd-udevd[3933808]: Could not generate persistent MAC address for vethdf664c5: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 13 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 13 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 13 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 13 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 13 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 13 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 13 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (10 distinct, 13 total) ==
Sep 13 18:10:06 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
Sep 13 18:25:51 submit26-b9-f1 setroubleshoot[1475943]: 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 13 18:25:51 submit26-b9-f1 setroubleshoot[1475943]: 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 13 18:25:51 submit26-b9-f1 setroubleshoot[1475943]: 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 13 18:25:51 submit26-b9-f1 setroubleshoot[1475943]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.9bB54D/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 13 18:25:51 submit26-b9-f1 setroubleshoot[1475943]: 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 13 18:25:51 submit26-b9-f1 setroubleshoot[1475943]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.9bB54D. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 13 18:25:51 submit26-b9-f1 setroubleshoot[1475943]: 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 13 18:25:51 submit26-b9-f1 setroubleshoot[1475943]: 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 13 18:25:51 submit26-b9-f1 setroubleshoot[1475943]: 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, 15 total) ==
Sep 13 18:06:46 submit26-b9-f2 setroubleshoot[617065]: 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 13 18:06:46 submit26-b9-f2 setroubleshoot[617065]: 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 13 18:06:46 submit26-b9-f2 setroubleshoot[617065]: 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 13 18:06:46 submit26-b9-f2 setroubleshoot[617065]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3xbNGS/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 13 18:06:46 submit26-b9-f2 setroubleshoot[617065]: 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 13 18:06:46 submit26-b9-f2 setroubleshoot[617065]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3xbNGS. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 13 18:06:46 submit26-b9-f2 setroubleshoot[617065]: 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 13 18:06:46 submit26-b9-f2 setroubleshoot[617065]: 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 13 18:06:46 submit26-b9-f2 setroubleshoot[617065]: 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 13 18:08:49 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f3 (1 distinct, 6 total) ==
Sep 13 18:08:11 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f4 (1 distinct, 7 total) ==
Sep 13 18:15:50 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0464s
Status : exited 0
Output :
Syslog digest — 2026-09-13 18:05 EDT
Processed 2,090 lines, filtered 1,685 (80%). 405 unknown (82 distinct) from 19 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 17:42:14 b0b02.cs.umd.edu rustdesk[762119]: cannot open display:
== csfw00a (1 distinct, 122 total) ==
Sep 13 17:04:08 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x122]
== frozone (1 distinct, 1 total) ==
Sep 13 17:35:32 frozone systemd-tmpfiles[1534957]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted
== galax (2 distinct, 80 total) ==
Sep 13 17:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 13 17:05:42 galax systemd-journald[670]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [x40]
== gle-dind04 (1 distinct, 1 total) ==
Sep 13 17:31:56 gle-dind04 lldpd[22022]: unable to send packet on real device for vethb4a9a1e: No such device or address
== hazfs.cs.umd.edu (1 distinct, 2 total) ==
Sep 13 17:25:03 hazfs.cs.umd.edu pcp[4154106]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (1 distinct, 1 total) ==
Sep 13 17:53:53 idm00 named[4166701]: client @0x7f11a93e2ef8 10.73.240.42#63066: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 13 17:37:38 idmp0 named[1598691]: client @0x7f2d1c03fa28 10.73.240.43#57713: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 41 total) ==
Sep 13 17:08:14 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x41]
== matrix (1 distinct, 1 total) ==
Sep 13 17:36:04 matrix sshd[1742444]: error: PAM: Authentication failure for root from 212.116.238.51
== newhonors2 (1 distinct, 24 total) ==
Sep 13 17:13:03 newhonors2 dhcpcd[2594943]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 17:09:08 outbound00.cs.umd.edu python3[3917752]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 17:13:07 outbound01.cs.umd.edu python3[1981526]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886152]: link_config: could not get ethtool features for vetheb6bbf4
Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886152]: Could not set offload features of vetheb6bbf4: No such device
Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886183]: Could not generate persistent MAC address for veth6f687cb: No such file or directory
Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886184]: Could not generate persistent MAC address for veth1f069b9: No such file or directory
Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886187]: Could not generate persistent MAC address for veth8e8b098: No such file or directory
Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886188]: Could not generate persistent MAC address for vetha1ab822: No such file or directory
Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886207]: Could not generate persistent MAC address for vethea5f6bd: No such file or directory
Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886199]: Could not generate persistent MAC address for veth0008ba7: No such file or directory
Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886199]: Could not generate persistent MAC address for veth4305a0e: No such file or directory
Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886207]: Could not generate persistent MAC address for veth3a11390: No such file or directory
Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886198]: Could not generate persistent MAC address for veth72a6cbb: No such file or directory
Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886199]: Could not generate persistent MAC address for veth9d9d4f4: No such file or directory
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895746]: link_config: could not get ethtool features for veth0008ba7
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895746]: Could not set offload features of veth0008ba7: No such device
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895774]: link_config: could not get ethtool features for veth3a11390
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895774]: Could not set offload features of veth3a11390: No such device
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895808]: Could not generate persistent MAC address for vethe3c6b36: No such file or directory
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895807]: Could not generate persistent MAC address for veth6f2f3d7: No such file or directory
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895811]: Could not generate persistent MAC address for veth42320cb: No such file or directory
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895812]: Could not generate persistent MAC address for veth40b9cac: No such file or directory
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895851]: Could not generate persistent MAC address for vethaa379f7: No such file or directory
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895852]: Could not generate persistent MAC address for veth33f88ba: No such file or directory
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895879]: Could not generate persistent MAC address for veth631a69d: No such file or directory
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895874]: Could not generate persistent MAC address for veth2c22c4f: No such file or directory
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895870]: Could not generate persistent MAC address for veth4cf60a7: No such file or directory
Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895883]: Could not generate persistent MAC address for veth64ae8dc: No such file or directory
Sep 13 17:50:10 sentry-docker00.cs.umd.edu systemd-udevd[3905247]: link_config: could not get ethtool features for veth631a69d
Sep 13 17:50:10 sentry-docker00.cs.umd.edu systemd-udevd[3905247]: Could not set offload features of veth631a69d: No such device
Sep 13 17:50:11 sentry-docker00.cs.umd.edu systemd-udevd[3905289]: Could not generate persistent MAC address for veth2bc1a81: No such file or directory
Sep 13 17:50:11 sentry-docker00.cs.umd.edu systemd-udevd[3905290]: Could not generate persistent MAC address for veth2d6c5cb: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 13 17:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 13 17:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 13 17:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 13 17:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 13 17:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 13 17:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 13 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 5 total) ==
Sep 13 17:33:06 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f2 (1 distinct, 7 total) ==
Sep 13 17:10:15 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
== submit26-b9-f3 (11 distinct, 20 total) ==
Sep 13 17:06:40 submit26-b9-f3 setroubleshoot[733562]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b [x2]
Sep 13 17:06:40 submit26-b9-f3 setroubleshoot[733562]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859 [x2]
Sep 13 17:06:40 submit26-b9-f3 setroubleshoot[733562]: 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 13 17:06:40 submit26-b9-f3 setroubleshoot[733562]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.A2ur28/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 13 17:06:40 submit26-b9-f3 setroubleshoot[733562]: 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 13 17:06:40 submit26-b9-f3 setroubleshoot[733562]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.A2ur28. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 13 17:06:41 submit26-b9-f3 setroubleshoot[733562]: 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 [x2]
Sep 13 17:06:41 submit26-b9-f3 setroubleshoot[733562]: 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 13 17:06:41 submit26-b9-f3 setroubleshoot[733562]: 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 [x2]
Sep 13 17:06:41 submit26-b9-f3 setroubleshoot[733562]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.D42JJM. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 13 17:12:01 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f4 (10 distinct, 10 total) ==
Sep 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: 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 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: 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 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: 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 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.h5TnTX/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: 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 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.h5TnTX. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: 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 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: 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 13 17:24:44 submit26-b9-f4 setroubleshoot[542538]: 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 13 17:53:09 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
1
0