Command: /usr/local/sbin/syslog-digest.py
Time : 0.0503s
Status : exited 0
Output :
Syslog digest — 2026-09-13 03:05 EDT
Processed 2,698 lines, filtered 2,267 (84%). 431 unknown (106 distinct) from 23 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 02:41:17 b0b02.cs.umd.edu rustdesk[532833]: cannot open display:
== biggulp.cs.umd.edu (6 distinct, 6 total) ==
Sep 13 02:10:53 biggulp.cs.umd.edu sshd-session[884336]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 13 02:10:53 biggulp.cs.umd.edu sshd-session[884336]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 13 02:10:54 biggulp.cs.umd.edu sshd-session[884336]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 13 02:10:54 biggulp.cs.umd.edu sshd-session[884336]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 13 02:10:56 biggulp.cs.umd.edu sshd-session[884336]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 13 02:10:56 biggulp.cs.umd.edu sshd-session[884336]: error: kex_protocol_error: type 30 seq 7 [preauth]
== cheezit.cs.umd.edu (10 distinct, 10 total) ==
Sep 13 02:17:26 cheezit.cs.umd.edu sshd-session[2894007]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 13 02:17:26 cheezit.cs.umd.edu sshd-session[2894007]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 13 02:17:26 cheezit.cs.umd.edu sshd-session[2894007]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 13 02:17:26 cheezit.cs.umd.edu sshd-session[2894007]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 13 02:17:28 cheezit.cs.umd.edu sshd-session[2894007]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 13 02:17:28 cheezit.cs.umd.edu sshd-session[2894007]: error: kex_protocol_error: type 30 seq 7 [preauth]
Sep 13 02:20:01 cheezit.cs.umd.edu sshd-session[2894298]: pam_access(sshd:auth): access denied for user `admin' from `207.175.9.196'
Sep 13 02:20:01 cheezit.cs.umd.edu krb5_child[2894302]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 13 02:20:01 cheezit.cs.umd.edu sshd-session[2894296]: error: PAM: System error for admin from 207.175.9.196
Sep 13 02:22:02 cheezit.cs.umd.edu sshd-session[2895068]: error: Protocol major versions differ: 2 vs. 1
== csfw00a (1 distinct, 125 total) ==
Sep 13 02:04:01 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x125]
== galax (2 distinct, 80 total) ==
Sep 13 02:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 13 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 13 02:25:06 hazfs.cs.umd.edu pcp[3611638]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (1 distinct, 1 total) ==
Sep 13 02:53:53 idm00 named[4166701]: client @0x7f11a945d1c8 10.73.240.42#52253: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 13 02:37:39 idmp0 named[1598691]: client @0x7f2d48026348 10.73.240.43#52631: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 3 total) ==
Sep 13 02:28:01 inbound00.cs.umd.edu cockpit-ws[3823664]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x3]
== inbound01.cs.umd.edu (1 distinct, 2 total) ==
Sep 13 02:27:59 inbound01.cs.umd.edu cockpit-ws[1850987]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2]
== itmon02 (1 distinct, 49 total) ==
Sep 13 02:08:00 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x49]
== krispykreme.cs.umd.edu (6 distinct, 6 total) ==
Sep 13 02:10:44 krispykreme.cs.umd.edu sshd-session[1493875]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 13 02:10:44 krispykreme.cs.umd.edu sshd-session[1493875]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 13 02:10:45 krispykreme.cs.umd.edu sshd-session[1493875]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 13 02:10:45 krispykreme.cs.umd.edu sshd-session[1493875]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 13 02:10:47 krispykreme.cs.umd.edu sshd-session[1493875]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 13 02:10:47 krispykreme.cs.umd.edu sshd-session[1493875]: error: kex_protocol_error: type 30 seq 7 [preauth]
== matrix (1 distinct, 1 total) ==
Sep 13 02:42:14 matrix sshd[1227535]: error: PAM: Authentication failure for nobody from 212.116.238.51
== newhonors2 (1 distinct, 24 total) ==
Sep 13 02:13:03 newhonors2 dhcpcd[2566391]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (4 distinct, 10 total) ==
Sep 13 02:09:09 outbound00.cs.umd.edu python3[3705222]: ldapdb [x6]
Sep 13 02:12:26 outbound00.cs.umd.edu krb5_child[3706037]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 13 02:13:40 outbound00.cs.umd.edu sshd-session[3706168]: error: Protocol major versions differ: 2 vs. 1
Sep 13 02:25:02 outbound00.cs.umd.edu cockpit-ws[3708525]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2]
== outbound01.cs.umd.edu (3 distinct, 8 total) ==
Sep 13 02:11:58 outbound01.cs.umd.edu krb5_child[1769216]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 13 02:12:33 outbound01.cs.umd.edu sshd-session[1769333]: error: Protocol major versions differ: 2 vs. 1
Sep 13 02:13:06 outbound01.cs.umd.edu python3[1769578]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 13 02:23:48 sentry-docker00.cs.umd.edu systemd-udevd[3467493]: link_config: could not get ethtool features for veth44a09db
Sep 13 02:23:48 sentry-docker00.cs.umd.edu systemd-udevd[3467493]: Could not set offload features of veth44a09db: No such device
Sep 13 02:23:48 sentry-docker00.cs.umd.edu systemd-udevd[3467517]: Could not generate persistent MAC address for vetha02c110: No such file or directory
Sep 13 02:23:48 sentry-docker00.cs.umd.edu systemd-udevd[3467518]: Could not generate persistent MAC address for vethad1f183: No such file or directory
Sep 13 02:23:48 sentry-docker00.cs.umd.edu systemd-udevd[3467527]: Could not generate persistent MAC address for veth26f3b06: No such file or directory
Sep 13 02:23:48 sentry-docker00.cs.umd.edu systemd-udevd[3467536]: Could not generate persistent MAC address for vethc38b472: No such file or directory
Sep 13 02:23:48 sentry-docker00.cs.umd.edu systemd-udevd[3467570]: Could not generate persistent MAC address for veth0873464: No such file or directory
Sep 13 02:23:48 sentry-docker00.cs.umd.edu systemd-udevd[3467571]: Could not generate persistent MAC address for veth26802aa: No such file or directory
Sep 13 02:23:48 sentry-docker00.cs.umd.edu systemd-udevd[3467621]: Could not generate persistent MAC address for veth4f3878a: No such file or directory
Sep 13 02:23:48 sentry-docker00.cs.umd.edu systemd-udevd[3467622]: Could not generate persistent MAC address for veth2da42fd: No such file or directory
Sep 13 02:23:48 sentry-docker00.cs.umd.edu systemd-udevd[3467658]: Could not generate persistent MAC address for veth786913f: No such file or directory
Sep 13 02:23:48 sentry-docker00.cs.umd.edu systemd-udevd[3467663]: Could not generate persistent MAC address for veth1380936: No such file or directory
Sep 13 02:43:56 sentry-docker00.cs.umd.edu systemd-udevd[3477189]: link_config: could not get ethtool features for veth786913f
Sep 13 02:43:56 sentry-docker00.cs.umd.edu systemd-udevd[3477189]: Could not set offload features of veth786913f: No such device
Sep 13 02:43:56 sentry-docker00.cs.umd.edu systemd-udevd[3477194]: Could not generate persistent MAC address for veth206c8ee: No such file or directory
Sep 13 02:43:56 sentry-docker00.cs.umd.edu systemd-udevd[3477199]: Could not generate persistent MAC address for vethff64032: No such file or directory
Sep 13 02:43:56 sentry-docker00.cs.umd.edu systemd-udevd[3477272]: Could not generate persistent MAC address for veth9201c19: No such file or directory
Sep 13 02:43:56 sentry-docker00.cs.umd.edu systemd-udevd[3477273]: Could not generate persistent MAC address for veth59d1ba2: No such file or directory
Sep 13 02:43:56 sentry-docker00.cs.umd.edu systemd-udevd[3477290]: Could not generate persistent MAC address for veth4ffd02e: No such file or directory
Sep 13 02:43:56 sentry-docker00.cs.umd.edu systemd-udevd[3477299]: Could not generate persistent MAC address for veth7022048: No such file or directory
Sep 13 02:43:56 sentry-docker00.cs.umd.edu systemd-udevd[3477285]: Could not generate persistent MAC address for vethb98f9bf: No such file or directory
Sep 13 02:43:56 sentry-docker00.cs.umd.edu systemd-udevd[3477296]: Could not generate persistent MAC address for vethfe675ac: No such file or directory
Sep 13 02:43:56 sentry-docker00.cs.umd.edu systemd-udevd[3477284]: Could not generate persistent MAC address for veth7da59b7: No such file or directory
Sep 13 02:43:56 sentry-docker00.cs.umd.edu systemd-udevd[3477299]: Could not generate persistent MAC address for veth537ed16: No such file or directory
Sep 13 03:04:04 sentry-docker00.cs.umd.edu systemd-udevd[3486816]: link_config: could not get ethtool features for veth206c8ee
Sep 13 03:04:04 sentry-docker00.cs.umd.edu systemd-udevd[3486816]: Could not set offload features of veth206c8ee: No such device
Sep 13 03:04:04 sentry-docker00.cs.umd.edu systemd-udevd[3486840]: Could not generate persistent MAC address for vethefcce4e: No such file or directory
Sep 13 03:04:04 sentry-docker00.cs.umd.edu systemd-udevd[3486841]: Could not generate persistent MAC address for vethb1c14b4: No such file or directory
Sep 13 03:04:04 sentry-docker00.cs.umd.edu systemd-udevd[3486866]: Could not generate persistent MAC address for veth0b83883: No such file or directory
Sep 13 03:04:04 sentry-docker00.cs.umd.edu systemd-udevd[3486867]: Could not generate persistent MAC address for veth8de5582: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 13 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 13 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 13 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 13 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 13 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 13 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 13 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (9 distinct, 9 total) ==
Sep 13 02:25:50 submit26-b9-f1 setroubleshoot[1414824]: 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 02:25:50 submit26-b9-f1 setroubleshoot[1414824]: 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 02:25:50 submit26-b9-f1 setroubleshoot[1414824]: 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 02:25:50 submit26-b9-f1 setroubleshoot[1414824]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.oG4sxH/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 13 02:25:50 submit26-b9-f1 setroubleshoot[1414824]: 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 02:25:50 submit26-b9-f1 setroubleshoot[1414824]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.oG4sxH. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 13 02:25:51 submit26-b9-f1 setroubleshoot[1414824]: 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 02:25:51 submit26-b9-f1 setroubleshoot[1414824]: 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 02:25:51 submit26-b9-f1 setroubleshoot[1414824]: 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, 14 total) ==
Sep 13 02:06:46 submit26-b9-f2 setroubleshoot[555550]: 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 02:06:46 submit26-b9-f2 setroubleshoot[555550]: 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 02:06:46 submit26-b9-f2 setroubleshoot[555550]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 [x2]
Sep 13 02:06:46 submit26-b9-f2 setroubleshoot[555550]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.RuGzlx/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2]
Sep 13 02:06:46 submit26-b9-f2 setroubleshoot[555550]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 [x2]
Sep 13 02:06:46 submit26-b9-f2 setroubleshoot[555550]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.RuGzlx. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 13 02:06:46 submit26-b9-f2 setroubleshoot[555550]: 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 02:06:46 submit26-b9-f2 setroubleshoot[555550]: 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 02:06:46 submit26-b9-f2 setroubleshoot[555550]: 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 02:13:28 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f3 (1 distinct, 3 total) ==
Sep 13 02:20:20 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 13 03:03:38 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== tma-0 (1 distinct, 1 total) ==
Sep 13 02:23:54 tma-0 sshd[11496]: error: PAM: Authentication failure for admin from 160.50.77.34.bc.googleusercontent.com
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0482s
Status : exited 0
Output :
Syslog digest — 2026-09-13 02:05 EDT
Processed 2,251 lines, filtered 1,806 (80%). 445 unknown (86 distinct) from 17 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 01:41:13 b0b02.cs.umd.edu rustdesk[517666]: cannot open display:
== cmsc436-0101-redis (2 distinct, 2 total) ==
Sep 13 01:34:03 cmsc436-0101-redis krb5_child[2938521]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 13 01:34:05 cmsc436-0101-redis sshd-session[2938517]: error: PAM: Authentication failure for admin from 35.187.8.187
== csfw00a (2 distinct, 109 total) ==
Sep 13 01:05:30 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x107]
Sep 13 01:28:07 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x2]
== galax (2 distinct, 80 total) ==
Sep 13 01:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 13 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 13 01:14:49 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 13 01:14:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 13 01:14:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 13 01:14:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 13 01:14:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 13 01:14:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 13 01:14:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 13 01:14:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 13 01:14:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 13 01:14:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 13 01:14:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
Sep 13 01:25:03 hazfs.cs.umd.edu pcp[3295997]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (1 distinct, 1 total) ==
Sep 13 01:53:53 idm00 named[4166701]: client @0x7f11a4031448 10.73.240.42#60144: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 13 01:37:39 idmp0 named[1598691]: client @0x7f2d4802a308 10.73.240.43#59141: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 51 total) ==
Sep 13 01:07:48 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x51]
== matrix (3 distinct, 4 total) ==
Sep 13 01:47:03 matrix krb5_child[1195108]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 13 01:47:05 matrix sshd[1195105]: error: PAM: Authentication failure for admin from 207.175.9.196
Sep 13 01:47:22 matrix sshd[1195244]: error: Protocol major versions differ: 2 vs. 1
== newhonors2 (1 distinct, 24 total) ==
Sep 13 01:13:02 newhonors2 dhcpcd[2564545]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 01:09:09 outbound00.cs.umd.edu python3[3691236]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 01:13:07 outbound01.cs.umd.edu python3[1755404]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (32 distinct, 32 total) ==
Sep 13 01:23:23 sentry-docker00.cs.umd.edu systemd-udevd[3439286]: Could not generate persistent MAC address for veth6eae06a: No such file or directory
Sep 13 01:23:23 sentry-docker00.cs.umd.edu systemd-udevd[3439287]: Could not generate persistent MAC address for veth074e65c: No such file or directory
Sep 13 01:23:23 sentry-docker00.cs.umd.edu systemd-udevd[3439324]: Could not generate persistent MAC address for vethcfb1821: No such file or directory
Sep 13 01:23:23 sentry-docker00.cs.umd.edu systemd-udevd[3439325]: Could not generate persistent MAC address for vethada362b: No such file or directory
Sep 13 01:23:23 sentry-docker00.cs.umd.edu systemd-udevd[3439329]: Could not generate persistent MAC address for vetha26fe2c: No such file or directory
Sep 13 01:23:23 sentry-docker00.cs.umd.edu systemd-udevd[3439349]: Could not generate persistent MAC address for veth330322b: No such file or directory
Sep 13 01:23:23 sentry-docker00.cs.umd.edu systemd-udevd[3439341]: Could not generate persistent MAC address for vethca45033: No such file or directory
Sep 13 01:23:23 sentry-docker00.cs.umd.edu systemd-udevd[3439332]: Could not generate persistent MAC address for veth32f8814: No such file or directory
Sep 13 01:23:23 sentry-docker00.cs.umd.edu systemd-udevd[3439349]: Could not generate persistent MAC address for veth11587fc: No such file or directory
Sep 13 01:23:23 sentry-docker00.cs.umd.edu systemd-udevd[3439329]: Could not generate persistent MAC address for vethdaf38d1: No such file or directory
Sep 13 01:43:31 sentry-docker00.cs.umd.edu systemd-udevd[3448675]: link_config: could not get ethtool features for vethcfb1821
Sep 13 01:43:31 sentry-docker00.cs.umd.edu systemd-udevd[3448675]: Could not set offload features of vethcfb1821: No such device
Sep 13 01:43:31 sentry-docker00.cs.umd.edu systemd-udevd[3448709]: Could not generate persistent MAC address for vethbfb36d7: No such file or directory
Sep 13 01:43:31 sentry-docker00.cs.umd.edu systemd-udevd[3448710]: Could not generate persistent MAC address for veth4ef9cfc: No such file or directory
Sep 13 01:43:31 sentry-docker00.cs.umd.edu systemd-udevd[3448713]: Could not generate persistent MAC address for veth8bae2eb: No such file or directory
Sep 13 01:43:31 sentry-docker00.cs.umd.edu systemd-udevd[3448714]: Could not generate persistent MAC address for vethd528eeb: No such file or directory
Sep 13 01:43:31 sentry-docker00.cs.umd.edu systemd-udevd[3448733]: Could not generate persistent MAC address for veth4320d40: No such file or directory
Sep 13 01:43:31 sentry-docker00.cs.umd.edu systemd-udevd[3448730]: Could not generate persistent MAC address for vethb58c222: No such file or directory
Sep 13 01:43:31 sentry-docker00.cs.umd.edu systemd-udevd[3448739]: Could not generate persistent MAC address for veth0096424: No such file or directory
Sep 13 01:43:31 sentry-docker00.cs.umd.edu systemd-udevd[3448740]: Could not generate persistent MAC address for veth1745887: No such file or directory
Sep 13 01:43:31 sentry-docker00.cs.umd.edu systemd-udevd[3448739]: Could not generate persistent MAC address for veth3e96e5d: No such file or directory
Sep 13 01:43:31 sentry-docker00.cs.umd.edu systemd-udevd[3448765]: Could not generate persistent MAC address for veth475831b: No such file or directory
Sep 13 02:03:39 sentry-docker00.cs.umd.edu systemd-udevd[3458135]: Could not generate persistent MAC address for veth4205f5d: No such file or directory
Sep 13 02:03:39 sentry-docker00.cs.umd.edu systemd-udevd[3458136]: Could not generate persistent MAC address for veth6f0cb45: No such file or directory
Sep 13 02:03:39 sentry-docker00.cs.umd.edu systemd-udevd[3458139]: Could not generate persistent MAC address for veth44a09db: No such file or directory
Sep 13 02:03:39 sentry-docker00.cs.umd.edu systemd-udevd[3458143]: Could not generate persistent MAC address for vethc276a17: No such file or directory
Sep 13 02:03:39 sentry-docker00.cs.umd.edu systemd-udevd[3458141]: Could not generate persistent MAC address for vethd9fac48: No such file or directory
Sep 13 02:03:39 sentry-docker00.cs.umd.edu systemd-udevd[3458148]: Could not generate persistent MAC address for veth0d89683: No such file or directory
Sep 13 02:03:40 sentry-docker00.cs.umd.edu systemd-udevd[3458167]: Could not generate persistent MAC address for veth5babf96: No such file or directory
Sep 13 02:03:40 sentry-docker00.cs.umd.edu systemd-udevd[3458168]: Could not generate persistent MAC address for vethd43e055: No such file or directory
... 2 more distinct messages not shown
== soul (1 distinct, 1 total) ==
Sep 13 01:30:37 soul krb5_child[2306031]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== strawberry (7 distinct, 38 total) ==
Sep 13 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 13 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 13 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 13 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 13 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 13 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 13 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (9 distinct, 9 total) ==
Sep 13 01:06:40 submit26-b9-f3 setroubleshoot[671307]: 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 01:06:40 submit26-b9-f3 setroubleshoot[671307]: 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 01:06:40 submit26-b9-f3 setroubleshoot[671307]: 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 01:06:40 submit26-b9-f3 setroubleshoot[671307]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.8ucBKE/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 13 01:06:40 submit26-b9-f3 setroubleshoot[671307]: 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 01:06:40 submit26-b9-f3 setroubleshoot[671307]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.8ucBKE. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 13 01:06:40 submit26-b9-f3 setroubleshoot[671307]: 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 01:06:40 submit26-b9-f3 setroubleshoot[671307]: 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 01:06:40 submit26-b9-f3 setroubleshoot[671307]: 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 (9 distinct, 12 total) ==
Sep 13 01:24:43 submit26-b9-f4 setroubleshoot[494032]: 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 01:24:43 submit26-b9-f4 setroubleshoot[494032]: 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 01:24:43 submit26-b9-f4 setroubleshoot[494032]: 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 [x2]
Sep 13 01:24:43 submit26-b9-f4 setroubleshoot[494032]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.lnJEC5/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2]
Sep 13 01:24:43 submit26-b9-f4 setroubleshoot[494032]: 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 [x2]
Sep 13 01:24:43 submit26-b9-f4 setroubleshoot[494032]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.lnJEC5. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 13 01:24:43 submit26-b9-f4 setroubleshoot[494032]: 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 01:24:43 submit26-b9-f4 setroubleshoot[494032]: 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 01:24:43 submit26-b9-f4 setroubleshoot[494032]: 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.0457s
Status : exited 0
Output :
Syslog digest — 2026-09-13 01:05 EDT
Processed 2,009 lines, filtered 1,591 (79%). 418 unknown (114 distinct) from 36 host(s).
== abuse (3 distinct, 4 total) ==
Sep 13 00:10:14 abuse systemd[1]: New main PID 6297 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 13 00:10:33 abuse systemd[1]: Daemon never wrote its PID file. Failing.
Sep 13 00:10:44 abuse systemd[1]: pmlogger.service: Supervising process 13412 which is not our child. We'll most likely not notice when it exits.
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 00:41:09 b0b02.cs.umd.edu rustdesk[502522]: cannot open display:
== biggulp.cs.umd.edu (6 distinct, 6 total) ==
Sep 13 00:56:48 biggulp.cs.umd.edu sshd-session[871138]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 13 00:56:48 biggulp.cs.umd.edu sshd-session[871138]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 13 00:56:51 biggulp.cs.umd.edu sshd-session[871138]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 13 00:56:51 biggulp.cs.umd.edu sshd-session[871138]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 13 00:56:53 biggulp.cs.umd.edu sshd-session[871138]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 13 00:56:53 biggulp.cs.umd.edu sshd-session[871138]: error: kex_protocol_error: type 30 seq 7 [preauth]
== csfw00a (1 distinct, 109 total) ==
Sep 13 00:04:38 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x109]
== forge00 (1 distinct, 1 total) ==
Sep 13 00:51:26 forge00 (httpd)[3528996]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== galax (2 distinct, 80 total) ==
Sep 13 00:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 13 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 13 00:10:13 grades01.cs.umd.edu systemd[1]: New main PID 8793 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 13 00:10:34 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 13 00:10:49 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 16317 which is not our child. We'll most likely not notice when it exits.
== hazfs.cs.umd.edu (2 distinct, 3 total) ==
Sep 13 00:10:02 hazfs.cs.umd.edu pcp[2902029]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily.log
Sep 13 00:25:09 hazfs.cs.umd.edu pcp[2981161]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (1 distinct, 1 total) ==
Sep 13 00:53:53 idm00 named[4166701]: client @0x7f11a000e808 10.73.240.42#50038: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 13 00:37:39 idmp0 named[1598691]: client @0x7f2d2c035088 10.73.240.43#58368: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 1 total) ==
Sep 13 00:35:54 inbound00.cs.umd.edu krb5_child[3797680]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== itmon02 (2 distinct, 36 total) ==
Sep 13 00:08:04 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x35]
Sep 13 00:21:17 itmon02 (httpd)[1557012]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== jubjub.cs.umd.edu (3 distinct, 4 total) ==
Sep 13 00:10:13 jubjub.cs.umd.edu systemd[1]: New main PID 1447064 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 13 00:10:32 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 13 00:10:40 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1454577 which is not our child. We'll most likely not notice when it exits.
== krispykreme.cs.umd.edu (10 distinct, 10 total) ==
Sep 13 00:14:59 krispykreme.cs.umd.edu sshd-session[1459674]: pam_access(sshd:auth): access denied for user `admin' from `207.175.229.115'
Sep 13 00:14:59 krispykreme.cs.umd.edu krb5_child[1459676]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 13 00:14:59 krispykreme.cs.umd.edu sshd-session[1459672]: error: PAM: System error for admin from 207.175.229.115
Sep 13 00:15:23 krispykreme.cs.umd.edu sshd-session[1460322]: error: Protocol major versions differ: 2 vs. 1
Sep 13 00:55:48 krispykreme.cs.umd.edu sshd-session[1472774]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 13 00:55:48 krispykreme.cs.umd.edu sshd-session[1472774]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 13 00:55:50 krispykreme.cs.umd.edu sshd-session[1472774]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 13 00:55:50 krispykreme.cs.umd.edu sshd-session[1472774]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 13 00:55:52 krispykreme.cs.umd.edu sshd-session[1472774]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 13 00:55:52 krispykreme.cs.umd.edu sshd-session[1472774]: error: kex_protocol_error: type 30 seq 7 [preauth]
== librenms (1 distinct, 1 total) ==
Sep 13 00:37:34 librenms (httpd)[3767464]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== mirrors.cs.umd.edu (4 distinct, 6 total) ==
Sep 13 00:10:48 mirrors.cs.umd.edu root[12339]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log
Sep 13 00:10:48 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. [x2]
Sep 13 00:10:52 mirrors.cs.umd.edu systemd[1]: New main PID 11296 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 13 00:11:52 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 27866 which is not our child. We'll most likely not notice when it exits.
== misty.cs.umd.edu (3 distinct, 4 total) ==
Sep 13 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 35504 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 13 00:10:35 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 13 00:10:50 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 2743 which is not our child. We'll most likely not notice when it exits.
== munin (1 distinct, 1 total) ==
Sep 13 00:20:00 munin (httpd)[1088118]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== netbox (1 distinct, 1 total) ==
Sep 13 00:27:05 netbox (httpd)[3031013]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== newhonors2 (1 distinct, 24 total) ==
Sep 13 00:13:03 newhonors2 dhcpcd[2562703]: dhcpcd is not running [x24]
== openrepo (1 distinct, 1 total) ==
Sep 13 00:28:53 openrepo (nin-node)[2183395]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== openvox08-board (1 distinct, 1 total) ==
Sep 13 00:24:19 openvox08-board (httpd)[1254651]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== outbound00.cs.umd.edu (3 distinct, 8 total) ==
Sep 13 00:09:09 outbound00.cs.umd.edu python3[3676614]: ldapdb [x6]
Sep 13 00:28:07 outbound00.cs.umd.edu krb5_child[3681715]: Preauthentication failed
Sep 13 00:49:42 outbound00.cs.umd.edu krb5_child[3686422]: Client 'backup(a)UMD.EDU' not found in Kerberos database
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 13 00:13:06 outbound01.cs.umd.edu python3[1741345]: ldapdb [x6]
== portal (1 distinct, 1 total) ==
Sep 13 00:53:44 portal (httpd)[634532]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== sentry-docker00.cs.umd.edu (32 distinct, 32 total) ==
Sep 13 00:22:58 sentry-docker00.cs.umd.edu systemd-udevd[3410723]: Could not generate persistent MAC address for vethcc120cb: No such file or directory
Sep 13 00:22:58 sentry-docker00.cs.umd.edu systemd-udevd[3410724]: Could not generate persistent MAC address for veth08357bc: No such file or directory
Sep 13 00:22:58 sentry-docker00.cs.umd.edu systemd-udevd[3410742]: Could not generate persistent MAC address for vetheea163c: No such file or directory
Sep 13 00:22:58 sentry-docker00.cs.umd.edu systemd-udevd[3410732]: Could not generate persistent MAC address for vetha54c79b: No such file or directory
Sep 13 00:22:58 sentry-docker00.cs.umd.edu systemd-udevd[3410729]: Could not generate persistent MAC address for veth0d14be8: No such file or directory
Sep 13 00:22:58 sentry-docker00.cs.umd.edu systemd-udevd[3410733]: Could not generate persistent MAC address for vethf9e36ce: No such file or directory
Sep 13 00:22:58 sentry-docker00.cs.umd.edu systemd-udevd[3410729]: Could not generate persistent MAC address for vethae39f2e: No such file or directory
Sep 13 00:22:58 sentry-docker00.cs.umd.edu systemd-udevd[3410734]: Could not generate persistent MAC address for veth1814fd1: No such file or directory
Sep 13 00:22:58 sentry-docker00.cs.umd.edu systemd-udevd[3410767]: Could not generate persistent MAC address for veth36856c9: No such file or directory
Sep 13 00:22:58 sentry-docker00.cs.umd.edu systemd-udevd[3410768]: Could not generate persistent MAC address for veth767f84e: No such file or directory
Sep 13 00:43:06 sentry-docker00.cs.umd.edu systemd-udevd[3420086]: link_config: could not get ethtool features for veth0d14be8
Sep 13 00:43:06 sentry-docker00.cs.umd.edu systemd-udevd[3420086]: Could not set offload features of veth0d14be8: No such device
Sep 13 00:43:06 sentry-docker00.cs.umd.edu systemd-udevd[3420160]: Could not generate persistent MAC address for veth4989cdb: No such file or directory
Sep 13 00:43:06 sentry-docker00.cs.umd.edu systemd-udevd[3420161]: Could not generate persistent MAC address for vethcea5c98: No such file or directory
Sep 13 00:43:06 sentry-docker00.cs.umd.edu systemd-udevd[3420179]: Could not generate persistent MAC address for vethdc6cc70: No such file or directory
Sep 13 00:43:06 sentry-docker00.cs.umd.edu systemd-udevd[3420173]: Could not generate persistent MAC address for vethe215860: No such file or directory
Sep 13 00:43:06 sentry-docker00.cs.umd.edu systemd-udevd[3420161]: Could not generate persistent MAC address for veth04a74ce: No such file or directory
Sep 13 00:43:06 sentry-docker00.cs.umd.edu systemd-udevd[3420183]: Could not generate persistent MAC address for vethf56f122: No such file or directory
Sep 13 00:43:06 sentry-docker00.cs.umd.edu systemd-udevd[3420190]: Could not generate persistent MAC address for veth09e547f: No such file or directory
Sep 13 00:43:06 sentry-docker00.cs.umd.edu systemd-udevd[3420192]: Could not generate persistent MAC address for veth28099bf: No such file or directory
Sep 13 00:43:06 sentry-docker00.cs.umd.edu systemd-udevd[3420211]: Could not generate persistent MAC address for veth184af27: No such file or directory
Sep 13 00:43:06 sentry-docker00.cs.umd.edu systemd-udevd[3420210]: Could not generate persistent MAC address for veth2bb8bb4: No such file or directory
Sep 13 01:03:15 sentry-docker00.cs.umd.edu systemd-udevd[3429576]: Could not generate persistent MAC address for veth6f92c8e: No such file or directory
Sep 13 01:03:15 sentry-docker00.cs.umd.edu systemd-udevd[3429577]: Could not generate persistent MAC address for veth8d886d4: No such file or directory
Sep 13 01:03:15 sentry-docker00.cs.umd.edu systemd-udevd[3429580]: Could not generate persistent MAC address for veth4156cf4: No such file or directory
Sep 13 01:03:15 sentry-docker00.cs.umd.edu systemd-udevd[3429581]: Could not generate persistent MAC address for veth59f6ad1: No such file or directory
Sep 13 01:03:15 sentry-docker00.cs.umd.edu systemd-udevd[3429604]: Could not generate persistent MAC address for vethfa5618c: No such file or directory
Sep 13 01:03:15 sentry-docker00.cs.umd.edu systemd-udevd[3429605]: Could not generate persistent MAC address for vethed64f73: No such file or directory
Sep 13 01:03:15 sentry-docker00.cs.umd.edu systemd-udevd[3429628]: Could not generate persistent MAC address for veth6f83aa7: No such file or directory
Sep 13 01:03:15 sentry-docker00.cs.umd.edu systemd-udevd[3429618]: Could not generate persistent MAC address for vethe4b14bd: No such file or directory
... 2 more distinct messages not shown
== strawberry (8 distinct, 39 total) ==
Sep 13 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 13 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 13 00:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 13 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 13 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 13 00:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 13 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Sep 13 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing.
== submit10-cln25 (3 distinct, 4 total) ==
Sep 13 00:10:11 submit10-cln25 systemd: New main PID 24599 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 13 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing.
Sep 13 00:10:36 submit10-cln25 systemd: pmlogger.service: Supervising process 31525 which is not our child. We'll most likely not notice when it exits.
== submit26-b9-f1 (1 distinct, 5 total) ==
Sep 13 00:08:06 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f2 (1 distinct, 2 total) ==
Sep 13 00:08:38 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f3 (1 distinct, 4 total) ==
Sep 13 00:10:05 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== tlsrpt (1 distinct, 1 total) ==
Sep 13 00:34:26 tlsrpt (httpd)[2576582]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== tma-0 (3 distinct, 4 total) ==
Sep 13 00:10:13 tma-0 systemd[1]: New main PID 9019 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 13 00:10:30 tma-0 systemd[1]: Daemon never wrote its PID file. Failing.
Sep 13 00:10:38 tma-0 systemd[1]: pmlogger.service: Supervising process 16660 which is not our child. We'll most likely not notice when it exits.
== uffish.cs.umd.edu (3 distinct, 4 total) ==
Sep 13 00:10:13 uffish.cs.umd.edu systemd[1]: New main PID 7894 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 13 00:10:39 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 13 00:10:56 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 15494 which is not our child. We'll most likely not notice when it exits.
== vacuum.cs.umd.edu (3 distinct, 4 total) ==
Sep 13 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 16664 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 13 00:10:34 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 13 00:10:45 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 23894 which is not our child. We'll most likely not notice when it exits.
== whiffle.cs.umd.edu (3 distinct, 4 total) ==
Sep 13 00:10:13 whiffle.cs.umd.edu systemd[1]: New main PID 3805223 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 13 00:10:38 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 13 00:10:51 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3812487 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.0663s
Status : exited 0
Output :
Syslog digest — 2026-09-13 00:05 EDT
Processed 2,698 lines, filtered 1,823 (67%). 875 unknown (134 distinct) from 27 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 12 23:41:05 b0b02.cs.umd.edu rustdesk[486421]: cannot open display:
== biggulp.cs.umd.edu (6 distinct, 6 total) ==
Sep 12 23:42:36 biggulp.cs.umd.edu sshd-session[855590]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 12 23:42:36 biggulp.cs.umd.edu sshd-session[855590]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 12 23:42:37 biggulp.cs.umd.edu sshd-session[855590]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 12 23:42:37 biggulp.cs.umd.edu sshd-session[855590]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 12 23:42:39 biggulp.cs.umd.edu sshd-session[855590]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 12 23:42:39 biggulp.cs.umd.edu sshd-session[855590]: error: kex_protocol_error: type 30 seq 7 [preauth]
== borogove.cs.umd.edu (1 distinct, 3 total) ==
Sep 13 00:00:04 borogove.cs.umd.edu rsyslogd[1921]: imfile: internal error? inotify provided watch descriptor 305 which we could not find in our tables - ignored [v8.2510.0-2.el9 try https://www.rsyslog.com/e/2175 ] [x3]
== cheezit.cs.umd.edu (6 distinct, 6 total) ==
Sep 12 23:39:24 cheezit.cs.umd.edu sshd-session[2855601]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 12 23:39:24 cheezit.cs.umd.edu sshd-session[2855601]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 12 23:39:24 cheezit.cs.umd.edu sshd-session[2855601]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 12 23:39:24 cheezit.cs.umd.edu sshd-session[2855601]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 12 23:39:26 cheezit.cs.umd.edu sshd-session[2855601]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 12 23:39:26 cheezit.cs.umd.edu sshd-session[2855601]: error: kex_protocol_error: type 30 seq 7 [preauth]
== csfw00a (1 distinct, 129 total) ==
Sep 12 23:04:33 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x129]
== cskayako (2 distinct, 2 total) ==
Sep 13 00:00:04 cskayako setroubleshoot[3961686]: failed to retrieve rpm info for path '/var/log/php82-fpm_error.log':
Sep 13 00:00:05 cskayako setroubleshoot[3961686]: SELinux is preventing /opt/remi/php82/root/usr/sbin/php-fpm from open access on the file /var/log/php82-fpm_error.log. For complete SELinux messages run: sealert -l 0ba5d5da-2df6-4c48-bd39-9b458b25a6cc
== galax (2 distinct, 80 total) ==
Sep 12 23:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 12 23: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 12 23:25:07 hazfs.cs.umd.edu pcp[2665094]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (16 distinct, 157 total) ==
Sep 12 23:06:14 idm00 check-named-alive[1815624]: zone cs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:06:14 idm00 check-named-alive[1815685]: zone csdlabs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:06:14 idm00 check-named-alive[1815746]: zone csic.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:06:14 idm00 check-named-alive[1815813]: zone 72.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:06:14 idm00 check-named-alive[1815916]: zone 73.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:06:15 idm00 check-named-alive[1815977]: zone 88.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:06:15 idm00 check-named-alive[1816038]: zone 28.172.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:06:15 idm00 check-named-alive[1816099]: zone 125.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:06:15 idm00 check-named-alive[1816160]: zone 126.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:06:15 idm00 check-named-alive[1816221]: zone 127.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:06:15 idm00 check-named-alive[1816282]: zone 128.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:06:16 idm00 check-named-alive[1816343]: zone 129.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:06:16 idm00 check-named-alive[1816404]: zone 130.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:06:16 idm00 check-named-alive[1816465]: zone 131.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x11]
Sep 12 23:53:52 idm00 named[4166701]: client @0x7f11a0053278 10.73.240.42#55263: update '73.10.in-addr.arpa/IN' denied
Sep 13 00:00:02 idm00 named[4166701]: checkhints: unable to get root NS rrset from cache: not found [x2]
== idmh1 (15 distinct, 156 total) ==
Sep 12 23:08:05 idmh1 check-named-alive[2484840]: zone cs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 12 23:08:05 idmh1 check-named-alive[2484901]: zone csdlabs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 12 23:08:05 idmh1 check-named-alive[2484962]: zone csic.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 12 23:08:05 idmh1 check-named-alive[2485025]: zone 72.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 12 23:08:05 idmh1 check-named-alive[2485086]: zone 73.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 12 23:08:05 idmh1 check-named-alive[2485147]: zone 88.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 12 23:08:06 idmh1 check-named-alive[2485208]: zone 28.172.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 12 23:08:06 idmh1 check-named-alive[2485269]: zone 125.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 12 23:08:06 idmh1 check-named-alive[2485333]: zone 126.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 12 23:08:06 idmh1 check-named-alive[2485396]: zone 127.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 12 23:08:06 idmh1 check-named-alive[2485459]: zone 128.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 12 23:08:07 idmh1 check-named-alive[2485520]: zone 129.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 12 23:08:07 idmh1 check-named-alive[2485581]: zone 130.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 12 23:08:07 idmh1 check-named-alive[2485642]: zone 131.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x11]
Sep 13 00:00:00 idmh1 named[3565631]: checkhints: unable to get root NS rrset from cache: not found [x2]
== idmp0 (16 distinct, 158 total) ==
Sep 12 23:08:34 idmp0 check-named-alive[3473743]: zone cs.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x11]
Sep 12 23:08:35 idmp0 check-named-alive[3473804]: zone csdlabs.umd.edu: local SOA serial 1788943212 lags newest peer 1788955413 by 12201 (threshold 3600); not acting [x11]
Sep 12 23:08:35 idmp0 check-named-alive[3473865]: zone csic.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x11]
Sep 12 23:08:35 idmp0 check-named-alive[3473926]: zone 72.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x11]
Sep 12 23:08:36 idmp0 check-named-alive[3473987]: zone 73.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x11]
Sep 12 23:08:36 idmp0 check-named-alive[3474048]: zone 88.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x11]
Sep 12 23:08:36 idmp0 check-named-alive[3474109]: zone 28.172.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x11]
Sep 12 23:08:36 idmp0 check-named-alive[3474170]: zone 125.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x11]
Sep 12 23:08:37 idmp0 check-named-alive[3474231]: zone 126.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x11]
Sep 12 23:08:37 idmp0 check-named-alive[3474292]: zone 127.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x11]
Sep 12 23:08:37 idmp0 check-named-alive[3474353]: zone 128.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x11]
Sep 12 23:08:38 idmp0 check-named-alive[3474414]: zone 129.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x11]
Sep 12 23:08:38 idmp0 check-named-alive[3474475]: zone 130.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x11]
Sep 12 23:08:38 idmp0 check-named-alive[3474536]: zone 131.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x11]
Sep 12 23:37:39 idmp0 named[1598691]: client @0x7f2d3400d5c8 10.73.240.43#57030: update '73.10.in-addr.arpa/IN' denied
Sep 13 00:00:03 idmp0 named[1598691]: checkhints: unable to get root NS rrset from cache: not found [x3]
== idmv0 (1 distinct, 2 total) ==
Sep 13 00:00:01 idmv0 named[3973338]: checkhints: unable to get root NS rrset from cache: not found [x2]
== itmon02 (1 distinct, 37 total) ==
Sep 12 23:12:47 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x37]
== krispykreme.cs.umd.edu (9 distinct, 9 total) ==
Sep 12 23:42:00 krispykreme.cs.umd.edu sshd-session[1450012]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 12 23:42:00 krispykreme.cs.umd.edu sshd-session[1450012]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 12 23:42:02 krispykreme.cs.umd.edu sshd-session[1450012]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 12 23:42:02 krispykreme.cs.umd.edu sshd-session[1450012]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 12 23:42:04 krispykreme.cs.umd.edu sshd-session[1450012]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 12 23:42:04 krispykreme.cs.umd.edu sshd-session[1450012]: error: kex_protocol_error: type 30 seq 7 [preauth]
Sep 12 23:59:56 krispykreme.cs.umd.edu sshd-session[1455116]: pam_access(sshd:auth): access denied for user `admin' from `207.175.176.136'
Sep 12 23:59:56 krispykreme.cs.umd.edu krb5_child[1455118]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 12 23:59:56 krispykreme.cs.umd.edu sshd-session[1455113]: error: PAM: System error for admin from 207.175.176.136
== matrix (1 distinct, 1 total) ==
Sep 13 00:00:23 matrix (nin-node)[1132331]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neo-gizmonic (1 distinct, 1 total) ==
Sep 13 00:00:01 neo-gizmonic (nin-node)[971165]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neoavion (1 distinct, 1 total) ==
Sep 13 00:00:28 neoavion (nin-node)[2380518]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== newhonors2 (2 distinct, 25 total) ==
Sep 12 23:13:03 newhonors2 dhcpcd[2560595]: dhcpcd is not running [x24]
Sep 13 00:00:16 newhonors2 (nin-node)[2562152]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 23:09:09 outbound00.cs.umd.edu python3[3662301]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 23:13:06 outbound01.cs.umd.edu python3[1726557]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 12 23:22:33 sentry-docker00.cs.umd.edu systemd-udevd[3382391]: link_config: could not get ethtool features for veth00621bb
Sep 12 23:22:33 sentry-docker00.cs.umd.edu systemd-udevd[3382391]: Could not set offload features of veth00621bb: No such device
Sep 12 23:22:33 sentry-docker00.cs.umd.edu systemd-udevd[3382461]: Could not generate persistent MAC address for veth81e1a8e: No such file or directory
Sep 12 23:22:33 sentry-docker00.cs.umd.edu systemd-udevd[3382462]: Could not generate persistent MAC address for veth9f64e80: No such file or directory
Sep 12 23:22:33 sentry-docker00.cs.umd.edu systemd-udevd[3382465]: Could not generate persistent MAC address for vetha8d4fbd: No such file or directory
Sep 12 23:22:33 sentry-docker00.cs.umd.edu systemd-udevd[3382466]: Could not generate persistent MAC address for veth252f752: No such file or directory
Sep 12 23:22:33 sentry-docker00.cs.umd.edu systemd-udevd[3382484]: Could not generate persistent MAC address for vethfb4ab58: No such file or directory
Sep 12 23:22:33 sentry-docker00.cs.umd.edu systemd-udevd[3382462]: Could not generate persistent MAC address for vethafd321f: No such file or directory
Sep 12 23:22:33 sentry-docker00.cs.umd.edu systemd-udevd[3382491]: Could not generate persistent MAC address for veth805736a: No such file or directory
Sep 12 23:22:33 sentry-docker00.cs.umd.edu systemd-udevd[3382492]: Could not generate persistent MAC address for vethd0a6094: No such file or directory
Sep 12 23:22:33 sentry-docker00.cs.umd.edu systemd-udevd[3382525]: Could not generate persistent MAC address for veth7c0eb74: No such file or directory
Sep 12 23:22:33 sentry-docker00.cs.umd.edu systemd-udevd[3382492]: Could not generate persistent MAC address for vethf10b0f5: No such file or directory
Sep 12 23:42:41 sentry-docker00.cs.umd.edu systemd-udevd[3391757]: link_config: could not get ethtool features for vethfb4ab58
Sep 12 23:42:41 sentry-docker00.cs.umd.edu systemd-udevd[3391757]: Could not set offload features of vethfb4ab58: No such device
Sep 12 23:42:41 sentry-docker00.cs.umd.edu systemd-udevd[3391843]: Could not generate persistent MAC address for veth0ceeb6c: No such file or directory
Sep 12 23:42:41 sentry-docker00.cs.umd.edu systemd-udevd[3391844]: Could not generate persistent MAC address for veth483109c: No such file or directory
Sep 12 23:42:41 sentry-docker00.cs.umd.edu systemd-udevd[3391847]: Could not generate persistent MAC address for veth2a09bf8: No such file or directory
Sep 12 23:42:41 sentry-docker00.cs.umd.edu systemd-udevd[3391848]: Could not generate persistent MAC address for vethe79fa5d: No such file or directory
Sep 12 23:42:41 sentry-docker00.cs.umd.edu systemd-udevd[3391871]: Could not generate persistent MAC address for vethf0f5ea3: No such file or directory
Sep 12 23:42:41 sentry-docker00.cs.umd.edu systemd-udevd[3391872]: Could not generate persistent MAC address for veth8063ce0: No such file or directory
Sep 12 23:42:41 sentry-docker00.cs.umd.edu systemd-udevd[3391897]: Could not generate persistent MAC address for veth787ea13: No such file or directory
Sep 12 23:42:41 sentry-docker00.cs.umd.edu systemd-udevd[3391898]: Could not generate persistent MAC address for veth729d0f3: No such file or directory
Sep 12 23:42:41 sentry-docker00.cs.umd.edu systemd-udevd[3391916]: Could not generate persistent MAC address for veth9c75ef2: No such file or directory
Sep 12 23:42:41 sentry-docker00.cs.umd.edu systemd-udevd[3391910]: Could not generate persistent MAC address for veth81ed0ee: No such file or directory
Sep 13 00:02:49 sentry-docker00.cs.umd.edu systemd-udevd[3401226]: link_config: could not get ethtool features for veth9c75ef2
Sep 13 00:02:49 sentry-docker00.cs.umd.edu systemd-udevd[3401226]: Could not set offload features of veth9c75ef2: No such device
Sep 13 00:02:50 sentry-docker00.cs.umd.edu systemd-udevd[3401278]: Could not generate persistent MAC address for vethcb544ac: No such file or directory
Sep 13 00:02:50 sentry-docker00.cs.umd.edu systemd-udevd[3401279]: Could not generate persistent MAC address for vethfdfba3d: No such file or directory
Sep 13 00:02:50 sentry-docker00.cs.umd.edu systemd-udevd[3401282]: Could not generate persistent MAC address for veth9585ce6: No such file or directory
Sep 13 00:02:50 sentry-docker00.cs.umd.edu systemd-udevd[3401283]: Could not generate persistent MAC address for vethf8b3c90: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 12 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 12 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 12 23:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 12 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 12 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 12 23:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 12 23:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 3 total) ==
Sep 12 23:10:06 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f2 (1 distinct, 2 total) ==
Sep 12 23:08:06 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f3 (1 distinct, 2 total) ==
Sep 12 23:05:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f4 (1 distinct, 4 total) ==
Sep 12 23:08:56 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== wraith (2 distinct, 2 total) ==
Sep 13 00:00:00 wraith kernel: kauditd_printk_skb: 2 callbacks suppressed
Sep 13 00:00:01 wraith (nin-node)[307925]: 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.0699s
Status : exited 0
Output :
Syslog digest — 2026-09-12 23:05 EDT
Processed 2,800 lines, filtered 1,824 (65%). 976 unknown (153 distinct) from 23 host(s).
== abadi-computer (10 distinct, 10 total) ==
Sep 12 22:18:31 abadi-computer systemd-tmpfiles[4145392]: Opening file "/tmp/code-30841dcb-4f9f-4b34-b81f-92a773102506" failed, ignoring: No such device or address
Sep 12 22:18:31 abadi-computer systemd-tmpfiles[4145392]: Opening file "/tmp/code-7c27e330-4309-4186-bd9b-abb4d4745fdf" failed, ignoring: No such device or address
Sep 12 22:18:31 abadi-computer systemd-tmpfiles[4145392]: Opening file "/tmp/code-f6092ddd-e7cd-438c-9a20-afd421d62159" failed, ignoring: No such device or address
Sep 12 22:18:31 abadi-computer systemd-tmpfiles[4145392]: Opening file "/tmp/code-40043ec1-8fc3-4112-871c-17e3d48408c0" failed, ignoring: No such device or address
Sep 12 22:18:31 abadi-computer systemd-tmpfiles[4145392]: Opening file "/tmp/code-bdb75c1b-162d-4ad9-bbc0-fcf8c8ce1615" failed, ignoring: No such device or address
Sep 12 22:18:31 abadi-computer systemd-tmpfiles[4145392]: Opening file "/tmp/code-ca2dbae7-13db-45e8-a9db-4bc4fc5d79c0" failed, ignoring: No such device or address
Sep 12 22:18:31 abadi-computer systemd-tmpfiles[4145392]: Opening file "/tmp/code-68eb4d63-b05c-4ec2-84d0-615a7a14c621" failed, ignoring: No such device or address
Sep 12 22:18:31 abadi-computer systemd-tmpfiles[4145392]: Opening file "/tmp/code-4df6f69d-9a10-4968-b085-773c8f7e1014" failed, ignoring: No such device or address
Sep 12 22:18:31 abadi-computer systemd-tmpfiles[4145392]: Opening file "/tmp/code-5c51b07b-6ff8-4f59-bad8-de13933f37b8" failed, ignoring: No such device or address
Sep 12 22:18:31 abadi-computer systemd-tmpfiles[4145392]: Opening file "/tmp/code-fff7a739-7a2c-42e9-ab16-d3b43d01db4d" failed, ignoring: No such device or address
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 12 22:41:01 b0b02.cs.umd.edu rustdesk[471240]: cannot open display:
== biggulp.cs.umd.edu (10 distinct, 11 total) ==
Sep 12 22:31:28 biggulp.cs.umd.edu sshd-session[843411]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 12 22:31:28 biggulp.cs.umd.edu sshd-session[843411]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 12 22:31:30 biggulp.cs.umd.edu sshd-session[843411]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 12 22:31:30 biggulp.cs.umd.edu sshd-session[843411]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 12 22:36:21 biggulp.cs.umd.edu sshd-session[844110]: pam_access(sshd:auth): access denied for user `admin' from `34.156.116.65'
Sep 12 22:36:21 biggulp.cs.umd.edu krb5_child[844113]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 12 22:36:21 biggulp.cs.umd.edu sshd-session[844108]: error: PAM: System error for admin from 34.156.116.65
Sep 12 22:37:33 biggulp.cs.umd.edu sshd-session[844190]: pam_access(sshd:auth): access denied for user `admin' from `146.148.11.109'
Sep 12 22:37:33 biggulp.cs.umd.edu sshd-session[844188]: error: PAM: System error for admin from 146.148.11.109
Sep 12 22:38:09 biggulp.cs.umd.edu sshd-session[844285]: error: Protocol major versions differ: 2 vs. 1
== cheezit.cs.umd.edu (6 distinct, 6 total) ==
Sep 12 22:13:57 cheezit.cs.umd.edu sshd-session[2835560]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 12 22:13:57 cheezit.cs.umd.edu sshd-session[2835560]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 12 22:13:59 cheezit.cs.umd.edu sshd-session[2835560]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 12 22:13:59 cheezit.cs.umd.edu sshd-session[2835560]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 12 22:14:02 cheezit.cs.umd.edu sshd-session[2835560]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 12 22:14:02 cheezit.cs.umd.edu sshd-session[2835560]: error: kex_protocol_error: type 30 seq 7 [preauth]
== csfw00a (1 distinct, 142 total) ==
Sep 12 22:04:21 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x142]
== galax (2 distinct, 80 total) ==
Sep 12 22:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 12 22: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 12 22:25:04 hazfs.cs.umd.edu pcp[2349768]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (15 distinct, 169 total) ==
Sep 12 22:06:10 idm00 check-named-alive[1795976]: zone cs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:06:10 idm00 check-named-alive[1796037]: zone csdlabs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:06:10 idm00 check-named-alive[1796098]: zone csic.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:06:11 idm00 check-named-alive[1796159]: zone 72.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:06:11 idm00 check-named-alive[1796220]: zone 73.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:06:11 idm00 check-named-alive[1796281]: zone 88.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:06:11 idm00 check-named-alive[1796342]: zone 28.172.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:06:11 idm00 check-named-alive[1796403]: zone 125.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:06:11 idm00 check-named-alive[1796464]: zone 126.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:06:12 idm00 check-named-alive[1796525]: zone 127.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:06:12 idm00 check-named-alive[1796586]: zone 128.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:06:12 idm00 check-named-alive[1796647]: zone 129.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:06:12 idm00 check-named-alive[1796708]: zone 130.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:06:12 idm00 check-named-alive[1796769]: zone 131.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 22:53:52 idm00 named[4166701]: client @0x7f11a940bc18 10.73.240.42#64400: update '73.10.in-addr.arpa/IN' denied
== idmh1 (14 distinct, 168 total) ==
Sep 12 22:07:57 idmh1 check-named-alive[2450947]: zone cs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 22:07:57 idmh1 check-named-alive[2451008]: zone csdlabs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 22:07:58 idmh1 check-named-alive[2451070]: zone csic.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 22:07:58 idmh1 check-named-alive[2451131]: zone 72.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 22:07:58 idmh1 check-named-alive[2451195]: zone 73.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 22:07:58 idmh1 check-named-alive[2451256]: zone 88.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 22:07:58 idmh1 check-named-alive[2451317]: zone 28.172.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 22:07:59 idmh1 check-named-alive[2451385]: zone 125.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 22:07:59 idmh1 check-named-alive[2451446]: zone 126.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 22:07:59 idmh1 check-named-alive[2451507]: zone 127.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 22:07:59 idmh1 check-named-alive[2451568]: zone 128.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 22:07:59 idmh1 check-named-alive[2451629]: zone 129.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 22:08:00 idmh1 check-named-alive[2451692]: zone 130.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 22:08:00 idmh1 check-named-alive[2451756]: zone 131.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
== idmp0 (15 distinct, 169 total) ==
Sep 12 22:08:30 idmp0 check-named-alive[3453747]: zone cs.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 22:08:31 idmp0 check-named-alive[3453808]: zone csdlabs.umd.edu: local SOA serial 1788943212 lags newest peer 1788955413 by 12201 (threshold 3600); not acting [x12]
Sep 12 22:08:31 idmp0 check-named-alive[3453869]: zone csic.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 22:08:31 idmp0 check-named-alive[3453930]: zone 72.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 22:08:32 idmp0 check-named-alive[3453991]: zone 73.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 22:08:32 idmp0 check-named-alive[3454055]: zone 88.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 22:08:32 idmp0 check-named-alive[3454116]: zone 28.172.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 22:08:33 idmp0 check-named-alive[3454177]: zone 125.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 22:08:33 idmp0 check-named-alive[3454238]: zone 126.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 22:08:33 idmp0 check-named-alive[3454299]: zone 127.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 22:08:33 idmp0 check-named-alive[3454360]: zone 128.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 22:08:34 idmp0 check-named-alive[3454421]: zone 129.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 22:08:34 idmp0 check-named-alive[3454482]: zone 130.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 22:08:34 idmp0 check-named-alive[3454543]: zone 131.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 22:37:39 idmp0 named[1598691]: client @0x7f2d4c005288 10.73.240.43#61383: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 44 total) ==
Sep 12 22:08:07 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x44]
== krispykreme.cs.umd.edu (6 distinct, 6 total) ==
Sep 12 22:30:07 krispykreme.cs.umd.edu sshd-session[1429996]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 12 22:30:07 krispykreme.cs.umd.edu sshd-session[1429996]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 12 22:30:08 krispykreme.cs.umd.edu sshd-session[1429996]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 12 22:30:08 krispykreme.cs.umd.edu sshd-session[1429996]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 12 22:30:11 krispykreme.cs.umd.edu sshd-session[1429996]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 12 22:30:11 krispykreme.cs.umd.edu sshd-session[1429996]: error: kex_protocol_error: type 30 seq 7 [preauth]
== newhonors2 (1 distinct, 24 total) ==
Sep 12 22:13:02 newhonors2 dhcpcd[2558737]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 22:09:09 outbound00.cs.umd.edu python3[3648204]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 22:13:06 outbound01.cs.umd.edu python3[1712603]: ldapdb [x6]
== sebatinsky.cs.umd.edu (1 distinct, 2 total) ==
Sep 12 22:39:51 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts [x2]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 12 22:22:08 sentry-docker00.cs.umd.edu systemd-udevd[3354102]: Could not generate persistent MAC address for vethdc505e9: No such file or directory
Sep 12 22:22:08 sentry-docker00.cs.umd.edu systemd-udevd[3354103]: Could not generate persistent MAC address for vethefdb0ac: No such file or directory
Sep 12 22:22:08 sentry-docker00.cs.umd.edu systemd-udevd[3354107]: Could not generate persistent MAC address for veth56204af: No such file or directory
Sep 12 22:22:08 sentry-docker00.cs.umd.edu systemd-udevd[3354106]: Could not generate persistent MAC address for vethc1be6ac: No such file or directory
Sep 12 22:22:08 sentry-docker00.cs.umd.edu systemd-udevd[3354130]: Could not generate persistent MAC address for vethb6d7990: No such file or directory
Sep 12 22:22:08 sentry-docker00.cs.umd.edu systemd-udevd[3354131]: Could not generate persistent MAC address for veth2b9a568: No such file or directory
Sep 12 22:22:08 sentry-docker00.cs.umd.edu systemd-udevd[3354156]: Could not generate persistent MAC address for vethdddf1e8: No such file or directory
Sep 12 22:22:08 sentry-docker00.cs.umd.edu systemd-udevd[3354158]: Could not generate persistent MAC address for veth97edc6d: No such file or directory
Sep 12 22:22:08 sentry-docker00.cs.umd.edu systemd-udevd[3354205]: Could not generate persistent MAC address for veth35632ca: No such file or directory
Sep 12 22:22:08 sentry-docker00.cs.umd.edu systemd-udevd[3354209]: Could not generate persistent MAC address for vethc3c6e32: No such file or directory
Sep 12 22:42:16 sentry-docker00.cs.umd.edu systemd-udevd[3363526]: link_config: could not get ethtool features for veth35632ca
Sep 12 22:42:16 sentry-docker00.cs.umd.edu systemd-udevd[3363526]: Could not set offload features of veth35632ca: No such device
Sep 12 22:42:16 sentry-docker00.cs.umd.edu systemd-udevd[3363561]: Could not generate persistent MAC address for vethe3c534c: No such file or directory
Sep 12 22:42:16 sentry-docker00.cs.umd.edu systemd-udevd[3363562]: Could not generate persistent MAC address for vetha8423be: No such file or directory
Sep 12 22:42:16 sentry-docker00.cs.umd.edu systemd-udevd[3363580]: Could not generate persistent MAC address for veth2627fd5: No such file or directory
Sep 12 22:42:16 sentry-docker00.cs.umd.edu systemd-udevd[3363575]: Could not generate persistent MAC address for veth2bd9748: No such file or directory
Sep 12 22:42:16 sentry-docker00.cs.umd.edu systemd-udevd[3363582]: Could not generate persistent MAC address for veth464e5ab: No such file or directory
Sep 12 22:42:16 sentry-docker00.cs.umd.edu systemd-udevd[3363586]: Could not generate persistent MAC address for veth352615b: No such file or directory
Sep 12 22:42:16 sentry-docker00.cs.umd.edu systemd-udevd[3363597]: Could not generate persistent MAC address for veth14e0722: No such file or directory
Sep 12 22:42:16 sentry-docker00.cs.umd.edu systemd-udevd[3363598]: Could not generate persistent MAC address for vethc5cbd9b: No such file or directory
Sep 12 22:42:16 sentry-docker00.cs.umd.edu systemd-udevd[3363658]: Could not generate persistent MAC address for vetha400233: No such file or directory
Sep 12 22:42:16 sentry-docker00.cs.umd.edu systemd-udevd[3363659]: Could not generate persistent MAC address for vethad1f3d3: No such file or directory
Sep 12 23:02:24 sentry-docker00.cs.umd.edu systemd-udevd[3372978]: link_config: could not get ethtool features for vetha400233
Sep 12 23:02:24 sentry-docker00.cs.umd.edu systemd-udevd[3372978]: Could not set offload features of vetha400233: No such device
Sep 12 23:02:25 sentry-docker00.cs.umd.edu systemd-udevd[3373032]: Could not generate persistent MAC address for veth6d979d4: No such file or directory
Sep 12 23:02:25 sentry-docker00.cs.umd.edu systemd-udevd[3373033]: Could not generate persistent MAC address for vethdf9a748: No such file or directory
Sep 12 23:02:25 sentry-docker00.cs.umd.edu systemd-udevd[3373037]: Could not generate persistent MAC address for veth058c34f: No such file or directory
Sep 12 23:02:25 sentry-docker00.cs.umd.edu systemd-udevd[3373036]: Could not generate persistent MAC address for veth519bb51: No such file or directory
Sep 12 23:02:25 sentry-docker00.cs.umd.edu systemd-udevd[3373039]: Could not generate persistent MAC address for vethb496bb4: No such file or directory
Sep 12 23:02:25 sentry-docker00.cs.umd.edu systemd-udevd[3373036]: Could not generate persistent MAC address for veth792b9bf: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 12 22:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 12 22:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 12 22:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 12 22:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 12 22:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 12 22:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 12 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (10 distinct, 18 total) ==
Sep 12 22:16:40 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x9]
Sep 12 22:25:50 submit26-b9-f1 setroubleshoot[1397576]: 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 12 22:25:50 submit26-b9-f1 setroubleshoot[1397576]: 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 12 22:25:50 submit26-b9-f1 setroubleshoot[1397576]: 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 12 22:25:50 submit26-b9-f1 setroubleshoot[1397576]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.acOCpt/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 12 22:25:50 submit26-b9-f1 setroubleshoot[1397576]: 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 12 22:25:50 submit26-b9-f1 setroubleshoot[1397576]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.acOCpt. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 12 22:25:50 submit26-b9-f1 setroubleshoot[1397576]: 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 12 22:25:50 submit26-b9-f1 setroubleshoot[1397576]: 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 12 22:25:50 submit26-b9-f1 setroubleshoot[1397576]: 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, 22 total) ==
Sep 12 22:05:39 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x10]
Sep 12 22:06:46 submit26-b9-f2 setroubleshoot[536260]: 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 12 22:06:46 submit26-b9-f2 setroubleshoot[536260]: 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 12 22:06:46 submit26-b9-f2 setroubleshoot[536260]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 [x2]
Sep 12 22:06:46 submit26-b9-f2 setroubleshoot[536260]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.CmNeOH/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2]
Sep 12 22:06:46 submit26-b9-f2 setroubleshoot[536260]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 [x2]
Sep 12 22:06:46 submit26-b9-f2 setroubleshoot[536260]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.CmNeOH. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 12 22:06:46 submit26-b9-f2 setroubleshoot[536260]: 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 12 22:06:46 submit26-b9-f2 setroubleshoot[536260]: 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 12 22:06:46 submit26-b9-f2 setroubleshoot[536260]: 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
== submit26-b9-f3 (1 distinct, 9 total) ==
Sep 12 22:10:05 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x9]
== submit26-b9-f4 (1 distinct, 5 total) ==
Sep 12 22:08:09 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== vacuum.cs.umd.edu (4 distinct, 4 total) ==
Sep 12 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[17945]: Process 13522 (driver) of user 33 killed by SIGSEGV - dumping core
Sep 12 22:11:59 vacuum.cs.umd.edu abrt-server[17947]: Package 'amanda-backup_server' isn't signed with proper key
Sep 12 22:11:59 vacuum.cs.umd.edu abrt-server[17947]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-12-22:11:58-13522' exited with 1
Sep 12 22:11:59 vacuum.cs.umd.edu abrt-server[17947]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-12-22:11:58-13522'
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0659s
Status : exited 0
Output :
Syslog digest — 2026-09-12 22:05 EDT
Processed 2,242 lines, filtered 1,305 (58%). 937 unknown (138 distinct) from 21 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 12 21:40:58 b0b02.cs.umd.edu rustdesk[456063]: cannot open display:
== biggulp.cs.umd.edu (6 distinct, 6 total) ==
Sep 12 21:42:11 biggulp.cs.umd.edu sshd-session[834359]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 12 21:42:11 biggulp.cs.umd.edu sshd-session[834359]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 12 21:42:12 biggulp.cs.umd.edu sshd-session[834359]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 12 21:42:12 biggulp.cs.umd.edu sshd-session[834359]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 12 21:42:14 biggulp.cs.umd.edu sshd-session[834359]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 12 21:42:14 biggulp.cs.umd.edu sshd-session[834359]: error: kex_protocol_error: type 30 seq 7 [preauth]
== cheezit.cs.umd.edu (6 distinct, 12 total) ==
Sep 12 21:10:32 cheezit.cs.umd.edu sshd-session[2819602]: error: kex_protocol_error: type 20 seq 2 [preauth] [x2]
Sep 12 21:10:32 cheezit.cs.umd.edu sshd-session[2819602]: error: kex_protocol_error: type 30 seq 3 [preauth] [x2]
Sep 12 21:10:33 cheezit.cs.umd.edu sshd-session[2819602]: error: kex_protocol_error: type 20 seq 4 [preauth] [x2]
Sep 12 21:10:33 cheezit.cs.umd.edu sshd-session[2819602]: error: kex_protocol_error: type 30 seq 5 [preauth] [x2]
Sep 12 21:10:35 cheezit.cs.umd.edu sshd-session[2819602]: error: kex_protocol_error: type 20 seq 6 [preauth] [x2]
Sep 12 21:10:35 cheezit.cs.umd.edu sshd-session[2819602]: error: kex_protocol_error: type 30 seq 7 [preauth] [x2]
== csfw00a (2 distinct, 133 total) ==
Sep 12 21:03:50 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x129]
Sep 12 21:34:29 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x4]
== galax (2 distinct, 80 total) ==
Sep 12 21:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 12 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 12 21:25:01 hazfs.cs.umd.edu pcp[2034387]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (15 distinct, 169 total) ==
Sep 12 21:06:06 idm00 check-named-alive[1776151]: zone cs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:06:07 idm00 check-named-alive[1776212]: zone csdlabs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:06:07 idm00 check-named-alive[1776273]: zone csic.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:06:07 idm00 check-named-alive[1776334]: zone 72.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:06:07 idm00 check-named-alive[1776395]: zone 73.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:06:07 idm00 check-named-alive[1776456]: zone 88.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:06:07 idm00 check-named-alive[1776517]: zone 28.172.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:06:08 idm00 check-named-alive[1776578]: zone 125.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:06:08 idm00 check-named-alive[1776639]: zone 126.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:06:08 idm00 check-named-alive[1776700]: zone 127.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:06:08 idm00 check-named-alive[1776761]: zone 128.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:06:08 idm00 check-named-alive[1776822]: zone 129.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:06:08 idm00 check-named-alive[1776883]: zone 130.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:06:09 idm00 check-named-alive[1776944]: zone 131.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 21:53:52 idm00 named[4166701]: client @0x7f11a94664f8 10.73.240.42#58319: update '73.10.in-addr.arpa/IN' denied
== idmh1 (14 distinct, 168 total) ==
Sep 12 21:07:50 idmh1 check-named-alive[2417007]: zone cs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 21:07:51 idmh1 check-named-alive[2417068]: zone csdlabs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 21:07:51 idmh1 check-named-alive[2417129]: zone csic.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 21:07:51 idmh1 check-named-alive[2417190]: zone 72.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 21:07:51 idmh1 check-named-alive[2417255]: zone 73.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 21:07:51 idmh1 check-named-alive[2417317]: zone 88.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 21:07:52 idmh1 check-named-alive[2417378]: zone 28.172.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 21:07:52 idmh1 check-named-alive[2417439]: zone 125.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 21:07:52 idmh1 check-named-alive[2417502]: zone 126.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 21:07:52 idmh1 check-named-alive[2417563]: zone 127.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 21:07:52 idmh1 check-named-alive[2417624]: zone 128.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 21:07:52 idmh1 check-named-alive[2417685]: zone 129.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 21:07:53 idmh1 check-named-alive[2417746]: zone 130.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 21:07:53 idmh1 check-named-alive[2417810]: zone 131.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
== idmp0 (15 distinct, 169 total) ==
Sep 12 21:08:27 idmp0 check-named-alive[3433526]: zone cs.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 21:08:27 idmp0 check-named-alive[3433587]: zone csdlabs.umd.edu: local SOA serial 1788943212 lags newest peer 1788955413 by 12201 (threshold 3600); not acting [x12]
Sep 12 21:08:27 idmp0 check-named-alive[3433648]: zone csic.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 21:08:28 idmp0 check-named-alive[3433716]: zone 72.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 21:08:28 idmp0 check-named-alive[3433778]: zone 73.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 21:08:28 idmp0 check-named-alive[3433839]: zone 88.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 21:08:28 idmp0 check-named-alive[3433901]: zone 28.172.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 21:08:29 idmp0 check-named-alive[3433962]: zone 125.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 21:08:29 idmp0 check-named-alive[3434023]: zone 126.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 21:08:29 idmp0 check-named-alive[3434084]: zone 127.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 21:08:30 idmp0 check-named-alive[3434145]: zone 128.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 21:08:30 idmp0 check-named-alive[3434206]: zone 129.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 21:08:30 idmp0 check-named-alive[3434267]: zone 130.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 21:08:31 idmp0 check-named-alive[3434328]: zone 131.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 21:37:39 idmp0 named[1598691]: client @0x7f2d08898fa8 10.73.240.43#51923: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 37 total) ==
Sep 12 21:08:11 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x37]
== krispykreme.cs.umd.edu (6 distinct, 6 total) ==
Sep 12 21:40:47 krispykreme.cs.umd.edu sshd-session[1416408]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 12 21:40:47 krispykreme.cs.umd.edu sshd-session[1416408]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 12 21:40:48 krispykreme.cs.umd.edu sshd-session[1416408]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 12 21:40:48 krispykreme.cs.umd.edu sshd-session[1416408]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 12 21:40:50 krispykreme.cs.umd.edu sshd-session[1416408]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 12 21:40:50 krispykreme.cs.umd.edu sshd-session[1416408]: error: kex_protocol_error: type 30 seq 7 [preauth]
== newhonors2 (1 distinct, 24 total) ==
Sep 12 21:13:03 newhonors2 dhcpcd[2556910]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 21:09:09 outbound00.cs.umd.edu python3[3634251]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 21:13:06 outbound01.cs.umd.edu python3[1698474]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 12 21:21:43 sentry-docker00.cs.umd.edu systemd-udevd[3325557]: link_config: could not get ethtool features for vetheb31b33
Sep 12 21:21:43 sentry-docker00.cs.umd.edu systemd-udevd[3325557]: Could not set offload features of vetheb31b33: No such device
Sep 12 21:21:43 sentry-docker00.cs.umd.edu systemd-udevd[3325591]: Could not generate persistent MAC address for vethf0346c3: No such file or directory
Sep 12 21:21:43 sentry-docker00.cs.umd.edu systemd-udevd[3325592]: Could not generate persistent MAC address for veth2f5314b: No such file or directory
Sep 12 21:21:43 sentry-docker00.cs.umd.edu systemd-udevd[3325595]: Could not generate persistent MAC address for veth16036a2: No such file or directory
Sep 12 21:21:43 sentry-docker00.cs.umd.edu systemd-udevd[3325596]: Could not generate persistent MAC address for vethb352cc2: No such file or directory
Sep 12 21:21:43 sentry-docker00.cs.umd.edu systemd-udevd[3325599]: Could not generate persistent MAC address for veth17c5b9f: No such file or directory
Sep 12 21:21:43 sentry-docker00.cs.umd.edu systemd-udevd[3325601]: Could not generate persistent MAC address for veth1a3d9d7: No such file or directory
Sep 12 21:21:43 sentry-docker00.cs.umd.edu systemd-udevd[3325621]: Could not generate persistent MAC address for vethe762941: No such file or directory
Sep 12 21:21:43 sentry-docker00.cs.umd.edu systemd-udevd[3325622]: Could not generate persistent MAC address for vetheede580: No such file or directory
Sep 12 21:21:43 sentry-docker00.cs.umd.edu systemd-udevd[3325675]: Could not generate persistent MAC address for veth164a99b: No such file or directory
Sep 12 21:21:43 sentry-docker00.cs.umd.edu systemd-udevd[3325677]: Could not generate persistent MAC address for veth960d8d4: No such file or directory
Sep 12 21:41:51 sentry-docker00.cs.umd.edu systemd-udevd[3335196]: link_config: could not get ethtool features for vethe762941
Sep 12 21:41:51 sentry-docker00.cs.umd.edu systemd-udevd[3335196]: Could not set offload features of vethe762941: No such device
Sep 12 21:41:51 sentry-docker00.cs.umd.edu systemd-udevd[3335247]: Could not generate persistent MAC address for vethbf565b0: No such file or directory
Sep 12 21:41:51 sentry-docker00.cs.umd.edu systemd-udevd[3335248]: Could not generate persistent MAC address for veth7a55204: No such file or directory
Sep 12 21:41:51 sentry-docker00.cs.umd.edu systemd-udevd[3335266]: Could not generate persistent MAC address for vethdabb718: No such file or directory
Sep 12 21:41:51 sentry-docker00.cs.umd.edu systemd-udevd[3335251]: Could not generate persistent MAC address for veth868659e: No such file or directory
Sep 12 21:41:51 sentry-docker00.cs.umd.edu systemd-udevd[3335259]: Could not generate persistent MAC address for veth2186a19: No such file or directory
Sep 12 21:41:51 sentry-docker00.cs.umd.edu systemd-udevd[3335262]: Could not generate persistent MAC address for veth4926d7a: No such file or directory
Sep 12 21:41:51 sentry-docker00.cs.umd.edu systemd-udevd[3335279]: Could not generate persistent MAC address for veth7438207: No such file or directory
Sep 12 21:41:51 sentry-docker00.cs.umd.edu systemd-udevd[3335280]: Could not generate persistent MAC address for veth716b3d0: No such file or directory
Sep 12 21:41:51 sentry-docker00.cs.umd.edu systemd-udevd[3335308]: Could not generate persistent MAC address for vethe39381d: No such file or directory
Sep 12 21:41:51 sentry-docker00.cs.umd.edu systemd-udevd[3335316]: Could not generate persistent MAC address for veth2ae3b5b: No such file or directory
Sep 12 22:01:59 sentry-docker00.cs.umd.edu systemd-udevd[3344600]: link_config: could not get ethtool features for veth2ae3b5b
Sep 12 22:01:59 sentry-docker00.cs.umd.edu systemd-udevd[3344600]: Could not set offload features of veth2ae3b5b: No such device
Sep 12 22:02:00 sentry-docker00.cs.umd.edu systemd-udevd[3344668]: Could not generate persistent MAC address for veth5a7ee8f: No such file or directory
Sep 12 22:02:00 sentry-docker00.cs.umd.edu systemd-udevd[3344669]: Could not generate persistent MAC address for vethe709d34: No such file or directory
Sep 12 22:02:00 sentry-docker00.cs.umd.edu systemd-udevd[3344672]: Could not generate persistent MAC address for veth98e7713: No such file or directory
Sep 12 22:02:00 sentry-docker00.cs.umd.edu systemd-udevd[3344673]: Could not generate persistent MAC address for veth5ceb1e4: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 12 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 12 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 12 21:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 12 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 12 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 12 21:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 12 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 2 total) ==
Sep 12 21:29:25 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f2 (1 distinct, 6 total) ==
Sep 12 21:09:17 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f3 (10 distinct, 17 total) ==
Sep 12 21:06:40 submit26-b9-f3 setroubleshoot[645982]: 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 12 21:06:40 submit26-b9-f3 setroubleshoot[645982]: 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 12 21:06:40 submit26-b9-f3 setroubleshoot[645982]: 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 12 21:06:40 submit26-b9-f3 setroubleshoot[645982]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.MjmEbi/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 12 21:06:40 submit26-b9-f3 setroubleshoot[645982]: 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 12 21:06:40 submit26-b9-f3 setroubleshoot[645982]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.MjmEbi. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 12 21:06:40 submit26-b9-f3 setroubleshoot[645982]: 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 12 21:06:40 submit26-b9-f3 setroubleshoot[645982]: 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 12 21:06:40 submit26-b9-f3 setroubleshoot[645982]: 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 12 21:10:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x8]
== submit26-b9-f4 (10 distinct, 18 total) ==
Sep 12 21:13:09 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
Sep 12 21:24:45 submit26-b9-f4 setroubleshoot[474958]: 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 12 21:24:45 submit26-b9-f4 setroubleshoot[474958]: 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 12 21:24:45 submit26-b9-f4 setroubleshoot[474958]: 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 [x2]
Sep 12 21:24:45 submit26-b9-f4 setroubleshoot[474958]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.X4n1KS/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2]
Sep 12 21:24:45 submit26-b9-f4 setroubleshoot[474958]: 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 [x2]
Sep 12 21:24:46 submit26-b9-f4 setroubleshoot[474958]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.X4n1KS. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 12 21:24:46 submit26-b9-f4 setroubleshoot[474958]: 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 12 21:24:46 submit26-b9-f4 setroubleshoot[474958]: 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 12 21:24:46 submit26-b9-f4 setroubleshoot[474958]: 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
== wraith (1 distinct, 1 total) ==
Sep 12 21:44:00 wraith kernel: workqueue: i915_hpd_poll_init_work [i915] hogged CPU for >10000us 16387 times, consider switching to WQ_UNBOUND
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0649s
Status : exited 0
Output :
Syslog digest — 2026-09-12 21:05 EDT
Processed 2,307 lines, filtered 1,395 (60%). 912 unknown (116 distinct) from 20 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 12 20:40:54 b0b02.cs.umd.edu rustdesk[440927]: cannot open display:
== biggulp.cs.umd.edu (6 distinct, 6 total) ==
Sep 12 20:13:01 biggulp.cs.umd.edu sshd-session[818505]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 12 20:13:01 biggulp.cs.umd.edu sshd-session[818505]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 12 20:13:03 biggulp.cs.umd.edu sshd-session[818505]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 12 20:13:03 biggulp.cs.umd.edu sshd-session[818505]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 12 20:13:05 biggulp.cs.umd.edu sshd-session[818505]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 12 20:13:05 biggulp.cs.umd.edu sshd-session[818505]: error: kex_protocol_error: type 30 seq 7 [preauth]
== cheezit.cs.umd.edu (3 distinct, 4 total) ==
Sep 12 20:19:03 cheezit.cs.umd.edu sshd-session[2807540]: pam_access(sshd:auth): access denied for user `profk' from `71.191.192.56' [x2]
Sep 12 20:19:11 cheezit.cs.umd.edu krb5_child[2807545]: Preauthentication failed
Sep 12 20:19:11 cheezit.cs.umd.edu sshd-session[2807538]: error: PAM: Authentication failure for profk from 71.191.192.56
== csfw00a (1 distinct, 127 total) ==
Sep 12 20:04:20 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x127]
== galax (2 distinct, 80 total) ==
Sep 12 20:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 12 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 12 20:25:07 hazfs.cs.umd.edu pcp[1719278]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (15 distinct, 169 total) ==
Sep 12 20:06:03 idm00 check-named-alive[1756215]: zone cs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:06:03 idm00 check-named-alive[1756276]: zone csdlabs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:06:03 idm00 check-named-alive[1756337]: zone csic.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:06:03 idm00 check-named-alive[1756398]: zone 72.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:06:03 idm00 check-named-alive[1756459]: zone 73.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:06:04 idm00 check-named-alive[1756520]: zone 88.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:06:04 idm00 check-named-alive[1756581]: zone 28.172.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:06:04 idm00 check-named-alive[1756642]: zone 125.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:06:04 idm00 check-named-alive[1756703]: zone 126.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:06:04 idm00 check-named-alive[1756764]: zone 127.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:06:04 idm00 check-named-alive[1756825]: zone 128.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:06:05 idm00 check-named-alive[1756886]: zone 129.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:06:05 idm00 check-named-alive[1756947]: zone 130.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:06:05 idm00 check-named-alive[1757008]: zone 131.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 20:53:52 idm00 named[4166701]: client @0x7f11a00742e8 10.73.240.42#50601: update '73.10.in-addr.arpa/IN' denied
== idmh1 (14 distinct, 168 total) ==
Sep 12 20:07:45 idmh1 check-named-alive[2383071]: zone cs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 20:07:45 idmh1 check-named-alive[2383134]: zone csdlabs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 20:07:45 idmh1 check-named-alive[2383195]: zone csic.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 20:07:46 idmh1 check-named-alive[2383258]: zone 72.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 20:07:46 idmh1 check-named-alive[2383319]: zone 73.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 20:07:46 idmh1 check-named-alive[2383380]: zone 88.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 20:07:46 idmh1 check-named-alive[2383444]: zone 28.172.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 20:07:46 idmh1 check-named-alive[2383505]: zone 125.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 20:07:47 idmh1 check-named-alive[2383571]: zone 126.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 20:07:47 idmh1 check-named-alive[2383634]: zone 127.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 20:07:47 idmh1 check-named-alive[2383695]: zone 128.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 20:07:47 idmh1 check-named-alive[2383756]: zone 129.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 20:07:47 idmh1 check-named-alive[2383817]: zone 130.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 20:07:47 idmh1 check-named-alive[2383878]: zone 131.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
== idmp0 (15 distinct, 169 total) ==
Sep 12 20:08:23 idmp0 check-named-alive[3413544]: zone cs.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 20:08:23 idmp0 check-named-alive[3413605]: zone csdlabs.umd.edu: local SOA serial 1788943212 lags newest peer 1788955413 by 12201 (threshold 3600); not acting [x12]
Sep 12 20:08:23 idmp0 check-named-alive[3413666]: zone csic.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 20:08:24 idmp0 check-named-alive[3413727]: zone 72.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 20:08:24 idmp0 check-named-alive[3413788]: zone 73.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 20:08:24 idmp0 check-named-alive[3413849]: zone 88.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 20:08:25 idmp0 check-named-alive[3413910]: zone 28.172.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 20:08:25 idmp0 check-named-alive[3413971]: zone 125.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 20:08:25 idmp0 check-named-alive[3414032]: zone 126.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 20:08:25 idmp0 check-named-alive[3414093]: zone 127.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 20:08:26 idmp0 check-named-alive[3414154]: zone 128.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 20:08:26 idmp0 check-named-alive[3414215]: zone 129.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 20:08:26 idmp0 check-named-alive[3414276]: zone 130.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 20:08:27 idmp0 check-named-alive[3414337]: zone 131.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 20:37:39 idmp0 named[1598691]: client @0x7f2d2c0368e8 10.73.240.43#51408: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 51 total) ==
Sep 12 20:07:59 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x51]
== krispykreme.cs.umd.edu (7 distinct, 8 total) ==
Sep 12 20:25:07 krispykreme.cs.umd.edu sshd-session[1394892]: pam_access(sshd:auth): access denied for user `anwar' from `71.241.227.222' [x2]
Sep 12 20:32:46 krispykreme.cs.umd.edu sshd-session[1397631]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 12 20:32:46 krispykreme.cs.umd.edu sshd-session[1397631]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 12 20:32:49 krispykreme.cs.umd.edu sshd-session[1397631]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 12 20:32:49 krispykreme.cs.umd.edu sshd-session[1397631]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 12 20:32:50 krispykreme.cs.umd.edu sshd-session[1397631]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 12 20:32:50 krispykreme.cs.umd.edu sshd-session[1397631]: error: kex_protocol_error: type 30 seq 7 [preauth]
== newhonors2 (1 distinct, 24 total) ==
Sep 12 20:13:03 newhonors2 dhcpcd[2555053]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 20:09:08 outbound00.cs.umd.edu python3[3620315]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 20:13:06 outbound01.cs.umd.edu python3[1684474]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 12 20:21:18 sentry-docker00.cs.umd.edu systemd-udevd[3297183]: link_config: could not get ethtool features for vethf46a246
Sep 12 20:21:18 sentry-docker00.cs.umd.edu systemd-udevd[3297183]: Could not set offload features of vethf46a246: No such device
Sep 12 20:21:18 sentry-docker00.cs.umd.edu systemd-udevd[3297251]: Could not generate persistent MAC address for veth2122633: No such file or directory
Sep 12 20:21:18 sentry-docker00.cs.umd.edu systemd-udevd[3297252]: Could not generate persistent MAC address for veth1cca680: No such file or directory
Sep 12 20:21:18 sentry-docker00.cs.umd.edu systemd-udevd[3297255]: Could not generate persistent MAC address for vethdb052a1: No such file or directory
Sep 12 20:21:18 sentry-docker00.cs.umd.edu systemd-udevd[3297256]: Could not generate persistent MAC address for veth43fea04: No such file or directory
Sep 12 20:21:18 sentry-docker00.cs.umd.edu systemd-udevd[3297271]: Could not generate persistent MAC address for vetha9c9911: No such file or directory
Sep 12 20:21:18 sentry-docker00.cs.umd.edu systemd-udevd[3297273]: Could not generate persistent MAC address for veth27a1991: No such file or directory
Sep 12 20:21:18 sentry-docker00.cs.umd.edu systemd-udevd[3297277]: Could not generate persistent MAC address for vethe7eb94e: No such file or directory
Sep 12 20:21:18 sentry-docker00.cs.umd.edu systemd-udevd[3297271]: Could not generate persistent MAC address for veth4768b26: No such file or directory
Sep 12 20:21:18 sentry-docker00.cs.umd.edu systemd-udevd[3297271]: Could not generate persistent MAC address for veth03b98ae: No such file or directory
Sep 12 20:21:18 sentry-docker00.cs.umd.edu systemd-udevd[3297273]: Could not generate persistent MAC address for veth2beab49: No such file or directory
Sep 12 20:41:26 sentry-docker00.cs.umd.edu systemd-udevd[3306647]: link_config: could not get ethtool features for vetha9c9911
Sep 12 20:41:26 sentry-docker00.cs.umd.edu systemd-udevd[3306647]: Could not set offload features of vetha9c9911: No such device
Sep 12 20:41:26 sentry-docker00.cs.umd.edu systemd-udevd[3306671]: Could not generate persistent MAC address for vethee454fc: No such file or directory
Sep 12 20:41:26 sentry-docker00.cs.umd.edu systemd-udevd[3306672]: Could not generate persistent MAC address for veth5361120: No such file or directory
Sep 12 20:41:26 sentry-docker00.cs.umd.edu systemd-udevd[3306697]: Could not generate persistent MAC address for veth6f092f9: No such file or directory
Sep 12 20:41:26 sentry-docker00.cs.umd.edu systemd-udevd[3306698]: Could not generate persistent MAC address for vethc21a52b: No such file or directory
Sep 12 20:41:26 sentry-docker00.cs.umd.edu systemd-udevd[3306716]: Could not generate persistent MAC address for veth083d087: No such file or directory
Sep 12 20:41:26 sentry-docker00.cs.umd.edu systemd-udevd[3306718]: Could not generate persistent MAC address for veth5393ad1: No such file or directory
Sep 12 20:41:26 sentry-docker00.cs.umd.edu systemd-udevd[3306725]: Could not generate persistent MAC address for vethec51201: No such file or directory
Sep 12 20:41:26 sentry-docker00.cs.umd.edu systemd-udevd[3306726]: Could not generate persistent MAC address for vethe38e9d8: No such file or directory
Sep 12 20:41:26 sentry-docker00.cs.umd.edu systemd-udevd[3306787]: Could not generate persistent MAC address for vethee9bf69: No such file or directory
Sep 12 20:41:26 sentry-docker00.cs.umd.edu systemd-udevd[3306790]: Could not generate persistent MAC address for veth36ce212: No such file or directory
Sep 12 21:01:34 sentry-docker00.cs.umd.edu systemd-udevd[3316018]: link_config: could not get ethtool features for veth6f092f9
Sep 12 21:01:34 sentry-docker00.cs.umd.edu systemd-udevd[3316018]: Could not set offload features of veth6f092f9: No such device
Sep 12 21:01:35 sentry-docker00.cs.umd.edu systemd-udevd[3316108]: Could not generate persistent MAC address for veth589eb77: No such file or directory
Sep 12 21:01:35 sentry-docker00.cs.umd.edu systemd-udevd[3316109]: Could not generate persistent MAC address for veth3128b1c: No such file or directory
Sep 12 21:01:35 sentry-docker00.cs.umd.edu systemd-udevd[3316112]: Could not generate persistent MAC address for vetheb31b33: No such file or directory
Sep 12 21:01:35 sentry-docker00.cs.umd.edu systemd-udevd[3316113]: Could not generate persistent MAC address for vetha5be52b: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 12 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 12 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 12 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 12 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 12 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 12 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 12 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 3 total) ==
Sep 12 20:23:08 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f2 (1 distinct, 4 total) ==
Sep 12 20:10:56 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f3 (1 distinct, 6 total) ==
Sep 12 20:20:05 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f4 (1 distinct, 4 total) ==
Sep 12 20:08:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0672s
Status : exited 0
Output :
Syslog digest — 2026-09-12 20:05 EDT
Processed 2,418 lines, filtered 1,413 (58%). 1,005 unknown (127 distinct) from 21 host(s).
== abadi-computer (2 distinct, 2 total) ==
Sep 12 19:25:42 abadi-computer falcon-sensor-bpf[529]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 12 19:25:42 abadi-computer falcon-sensor-bpf[529]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 12 19:40:50 b0b02.cs.umd.edu rustdesk[425585]: cannot open display:
== bachata (10 distinct, 10 total) ==
Sep 12 19:21:08 bachata smbd[445077]: [2026/09/12 19:21:08.473182, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service)
Sep 12 19:21:08 bachata smbd[445077]: chdir_current_service: vfs_ChDir(/fs/junkfood/nelson) failed: Permission denied. Current token: uid=20608, gid=20608, 20 groups: 20608 319050000 25274 319000009 25057 30872 25195 30043 25038 15228 31006 15294 15206 15248 25025 30742 25200 319100011 30871 30736
Sep 12 19:21:08 bachata smbd[445077]: [2026/09/12 19:21:08.473769, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect)
Sep 12 19:21:08 bachata smbd[445077]: smbXsrv_tcon_disconnect: disconnect(0x49568b32, 'nelson'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR
Sep 12 19:21:08 bachata smbd[445077]: [2026/09/12 19:21:08.744584, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all)
Sep 12 19:21:08 bachata smbd[445077]: smbXsrv_tcon_disconnect_all: count[3] errors[1] first[NT_STATUS_INTERNAL_ERROR]
Sep 12 19:21:08 bachata smbd[445077]: [2026/09/12 19:21:08.744760, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff)
Sep 12 19:21:08 bachata smbd[445077]: smbXsrv_session_logoff: smbXsrv_session_logoff(0x6c1f3990): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR
Sep 12 19:21:08 bachata smbd[445077]: [2026/09/12 19:21:08.744823, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done)
Sep 12 19:21:08 bachata smbd[445077]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(1813985680) failed: NT_STATUS_INTERNAL_ERROR
== csfw00a (2 distinct, 144 total) ==
Sep 12 19:04:02 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x140]
Sep 12 19:35:04 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x4]
== galax (2 distinct, 80 total) ==
Sep 12 19:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 12 19: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 12 19:25:03 hazfs.cs.umd.edu pcp[1403736]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
Sep 12 19:48:17 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 12 19:48:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 12 19:48:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 12 19:48:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 12 19:48:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 12 19:48:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 12 19:48:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 12 19:48:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 12 19:48:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 12 19:48:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 12 19:48:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (15 distinct, 169 total) ==
Sep 12 19:05:59 idm00 check-named-alive[1736316]: zone cs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:05:59 idm00 check-named-alive[1736377]: zone csdlabs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:05:59 idm00 check-named-alive[1736438]: zone csic.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:05:59 idm00 check-named-alive[1736499]: zone 72.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:06:00 idm00 check-named-alive[1736560]: zone 73.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:06:00 idm00 check-named-alive[1736621]: zone 88.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:06:00 idm00 check-named-alive[1736682]: zone 28.172.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:06:00 idm00 check-named-alive[1736743]: zone 125.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:06:00 idm00 check-named-alive[1736804]: zone 126.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:06:00 idm00 check-named-alive[1736865]: zone 127.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:06:01 idm00 check-named-alive[1736926]: zone 128.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:06:01 idm00 check-named-alive[1736987]: zone 129.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:06:01 idm00 check-named-alive[1737048]: zone 130.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:06:01 idm00 check-named-alive[1737109]: zone 131.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 19:53:52 idm00 named[4166701]: client @0x7f11a93e2ef8 10.73.240.42#53427: update '73.10.in-addr.arpa/IN' denied
== idmh1 (14 distinct, 168 total) ==
Sep 12 19:07:41 idmh1 check-named-alive[2348961]: zone cs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 19:07:41 idmh1 check-named-alive[2349024]: zone csdlabs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 19:07:41 idmh1 check-named-alive[2349085]: zone csic.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 19:07:41 idmh1 check-named-alive[2349146]: zone 72.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 19:07:41 idmh1 check-named-alive[2349210]: zone 73.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 19:07:41 idmh1 check-named-alive[2349271]: zone 88.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 19:07:42 idmh1 check-named-alive[2349337]: zone 28.172.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 19:07:42 idmh1 check-named-alive[2349400]: zone 125.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 19:07:42 idmh1 check-named-alive[2349461]: zone 126.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 19:07:42 idmh1 check-named-alive[2349522]: zone 127.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 19:07:42 idmh1 check-named-alive[2349583]: zone 128.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 19:07:43 idmh1 check-named-alive[2349644]: zone 129.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 19:07:43 idmh1 check-named-alive[2349705]: zone 130.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 19:07:43 idmh1 check-named-alive[2349766]: zone 131.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
== idmp0 (15 distinct, 169 total) ==
Sep 12 19:08:19 idmp0 check-named-alive[3393782]: zone cs.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 19:08:19 idmp0 check-named-alive[3393843]: zone csdlabs.umd.edu: local SOA serial 1788943212 lags newest peer 1788955413 by 12201 (threshold 3600); not acting [x12]
Sep 12 19:08:19 idmp0 check-named-alive[3393904]: zone csic.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 19:08:20 idmp0 check-named-alive[3393965]: zone 72.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 19:08:20 idmp0 check-named-alive[3394026]: zone 73.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 19:08:20 idmp0 check-named-alive[3394087]: zone 88.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 19:08:21 idmp0 check-named-alive[3394148]: zone 28.172.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 19:08:21 idmp0 check-named-alive[3394209]: zone 125.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 19:08:21 idmp0 check-named-alive[3394270]: zone 126.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 19:08:22 idmp0 check-named-alive[3394331]: zone 127.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 19:08:22 idmp0 check-named-alive[3394392]: zone 128.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 19:08:22 idmp0 check-named-alive[3394453]: zone 129.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 19:08:23 idmp0 check-named-alive[3394514]: zone 130.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 19:08:23 idmp0 check-named-alive[3394575]: zone 131.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 19:37:39 idmp0 named[1598691]: client @0x7f2d44005288 10.73.240.43#49473: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 49 total) ==
Sep 12 19:07:58 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x49]
== munin (2 distinct, 4 total) ==
Sep 12 19:57:48 munin sudo[994527]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 12 19:57:48 munin sudo[994527]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 12 19:13:03 newhonors2 dhcpcd[2553212]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 19:09:09 outbound00.cs.umd.edu python3[3606422]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 19:13:06 outbound01.cs.umd.edu python3[1670544]: ldapdb [x6]
== sebatinsky.cs.umd.edu (1 distinct, 1 total) ==
Sep 12 19:32:51 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3268935]: link_config: could not get ethtool features for vethe977a49
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3268935]: Could not set offload features of vethe977a49: No such device
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3269032]: link_config: could not get ethtool features for vethb3b7a8a
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3269032]: Could not set offload features of vethb3b7a8a: No such device
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3269060]: Could not generate persistent MAC address for vethfa9cea5: No such file or directory
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3269061]: Could not generate persistent MAC address for vethfea8e56: No such file or directory
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3269079]: Could not generate persistent MAC address for veth7380013: No such file or directory
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3269065]: Could not generate persistent MAC address for veth29d2912: No such file or directory
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3269065]: Could not generate persistent MAC address for veth3d449ce: No such file or directory
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3269085]: Could not generate persistent MAC address for vethb53f953: No such file or directory
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3269159]: Could not generate persistent MAC address for vethf9551e2: No such file or directory
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3269160]: Could not generate persistent MAC address for veth0e83797: No such file or directory
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3269180]: Could not generate persistent MAC address for veth92b87c6: No such file or directory
Sep 12 19:20:53 sentry-docker00.cs.umd.edu systemd-udevd[3269191]: Could not generate persistent MAC address for veth02872bc: No such file or directory
Sep 12 19:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3278357]: link_config: could not get ethtool features for vethb53f953
Sep 12 19:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3278357]: Could not set offload features of vethb53f953: No such device
Sep 12 19:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3278414]: Could not generate persistent MAC address for vethc7bec4e: No such file or directory
Sep 12 19:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3278415]: Could not generate persistent MAC address for veth0b7223d: No such file or directory
Sep 12 19:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3278418]: Could not generate persistent MAC address for vetheac04c6: No such file or directory
Sep 12 19:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3278419]: Could not generate persistent MAC address for veth6648584: No such file or directory
Sep 12 19:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3278428]: Could not generate persistent MAC address for veth9cef1f0: No such file or directory
Sep 12 19:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3278431]: Could not generate persistent MAC address for veth705d252: No such file or directory
Sep 12 19:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3278444]: Could not generate persistent MAC address for veth0e094f0: No such file or directory
Sep 12 19:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3278445]: Could not generate persistent MAC address for vethea234ca: No such file or directory
Sep 12 19:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3278470]: Could not generate persistent MAC address for vethed04336: No such file or directory
Sep 12 19:41:01 sentry-docker00.cs.umd.edu systemd-udevd[3278444]: Could not generate persistent MAC address for veth9fe69c6: No such file or directory
Sep 12 20:01:10 sentry-docker00.cs.umd.edu systemd-udevd[3287817]: Could not generate persistent MAC address for vethfc40b96: No such file or directory
Sep 12 20:01:10 sentry-docker00.cs.umd.edu systemd-udevd[3287818]: Could not generate persistent MAC address for veth5c4d92a: No such file or directory
Sep 12 20:01:10 sentry-docker00.cs.umd.edu systemd-udevd[3287821]: Could not generate persistent MAC address for vethf46a246: No such file or directory
Sep 12 20:01:10 sentry-docker00.cs.umd.edu systemd-udevd[3287822]: Could not generate persistent MAC address for veth3a3096a: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 12 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 12 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 12 19:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 12 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 12 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 12 19:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 12 19:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 7 total) ==
Sep 12 19:18:04 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
== submit26-b9-f2 (1 distinct, 7 total) ==
Sep 12 19:10:06 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
== submit26-b9-f3 (1 distinct, 7 total) ==
Sep 12 19:15:05 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
== submit26-b9-f4 (1 distinct, 9 total) ==
Sep 12 19:08:09 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x9]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0663s
Status : exited 0
Output :
Syslog digest — 2026-09-12 19:05 EDT
Processed 2,302 lines, filtered 1,377 (59%). 925 unknown (121 distinct) from 18 host(s).
== b0b02.cs.umd.edu (4 distinct, 4 total) ==
Sep 12 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-12T22:10:59.421487329Z" level=info msg="PurgeUploads starting: olderThan=2026-09-05 22:10:59.421409129 +0000 UTC m=+3458220.181337435, actuallyDelete=true"
Sep 12 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-12T22:10:59.422214407Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1"
Sep 12 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-12T22:10:59.422248041Z" 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 12 18:40:46 b0b02.cs.umd.edu rustdesk[410440]: cannot open display:
== csfw00a (1 distinct, 134 total) ==
Sep 12 18:03:55 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x134]
== galax (3 distinct, 81 total) ==
Sep 12 18:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 12 18:05:42 galax systemd-journald[670]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [x40]
Sep 12 18:18:22 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 16387 times, consider switching to WQ_UNBOUND
== gle-dind04 (1 distinct, 1 total) ==
Sep 12 18:51:53 gle-dind04 lldpd[22022]: unable to send packet on real device for vetha93aa15: No such device or address
== hazfs.cs.umd.edu (1 distinct, 2 total) ==
Sep 12 18:25:06 hazfs.cs.umd.edu pcp[1088570]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (15 distinct, 169 total) ==
Sep 12 18:05:55 idm00 check-named-alive[1715354]: zone cs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:05:56 idm00 check-named-alive[1715415]: zone csdlabs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:05:56 idm00 check-named-alive[1715476]: zone csic.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:05:56 idm00 check-named-alive[1715537]: zone 72.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:05:56 idm00 check-named-alive[1715598]: zone 73.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:05:56 idm00 check-named-alive[1715659]: zone 88.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:05:56 idm00 check-named-alive[1715720]: zone 28.172.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:05:57 idm00 check-named-alive[1715781]: zone 125.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:05:57 idm00 check-named-alive[1715842]: zone 126.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:05:57 idm00 check-named-alive[1715903]: zone 127.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:05:57 idm00 check-named-alive[1715964]: zone 128.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:05:57 idm00 check-named-alive[1716025]: zone 129.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:05:57 idm00 check-named-alive[1716086]: zone 130.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:05:57 idm00 check-named-alive[1716147]: zone 131.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 18:53:52 idm00 named[4166701]: client @0x7f1198014c68 10.73.240.42#65488: update '73.10.in-addr.arpa/IN' denied
== idmh1 (14 distinct, 168 total) ==
Sep 12 18:07:32 idmh1 check-named-alive[2314883]: zone cs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 18:07:32 idmh1 check-named-alive[2314944]: zone csdlabs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 18:07:32 idmh1 check-named-alive[2315005]: zone csic.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 18:07:32 idmh1 check-named-alive[2315066]: zone 72.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 18:07:32 idmh1 check-named-alive[2315129]: zone 73.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 18:07:33 idmh1 check-named-alive[2315190]: zone 88.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 18:07:33 idmh1 check-named-alive[2315251]: zone 28.172.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 18:07:33 idmh1 check-named-alive[2315312]: zone 125.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 18:07:33 idmh1 check-named-alive[2315373]: zone 126.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 18:07:33 idmh1 check-named-alive[2315440]: zone 127.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 18:07:34 idmh1 check-named-alive[2315502]: zone 128.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 18:07:34 idmh1 check-named-alive[2315563]: zone 129.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 18:07:34 idmh1 check-named-alive[2315624]: zone 130.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 18:07:34 idmh1 check-named-alive[2315685]: zone 131.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
== idmp0 (15 distinct, 169 total) ==
Sep 12 18:08:15 idmp0 check-named-alive[3373885]: zone cs.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 18:08:15 idmp0 check-named-alive[3373946]: zone csdlabs.umd.edu: local SOA serial 1788943212 lags newest peer 1788955413 by 12201 (threshold 3600); not acting [x12]
Sep 12 18:08:16 idmp0 check-named-alive[3374007]: zone csic.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 18:08:16 idmp0 check-named-alive[3374069]: zone 72.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 18:08:16 idmp0 check-named-alive[3374130]: zone 73.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 18:08:16 idmp0 check-named-alive[3374191]: zone 88.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 18:08:17 idmp0 check-named-alive[3374252]: zone 28.172.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 18:08:17 idmp0 check-named-alive[3374313]: zone 125.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 18:08:17 idmp0 check-named-alive[3374374]: zone 126.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 18:08:18 idmp0 check-named-alive[3374437]: zone 127.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 18:08:18 idmp0 check-named-alive[3374498]: zone 128.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 18:08:18 idmp0 check-named-alive[3374559]: zone 129.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 18:08:19 idmp0 check-named-alive[3374621]: zone 130.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 18:08:19 idmp0 check-named-alive[3374682]: zone 131.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 18:37:39 idmp0 named[1598691]: client @0x7f2d40000cc8 10.73.240.43#57666: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 51 total) ==
Sep 12 18:07:53 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x51]
== newhonors2 (1 distinct, 24 total) ==
Sep 12 18:13:02 newhonors2 dhcpcd[2551370]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 18:09:09 outbound00.cs.umd.edu python3[3592312]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 18:13:06 outbound01.cs.umd.edu python3[1656600]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 12 18:20:28 sentry-docker00.cs.umd.edu systemd-udevd[3240803]: Could not generate persistent MAC address for vethb8b9d34: No such file or directory
Sep 12 18:20:28 sentry-docker00.cs.umd.edu systemd-udevd[3240804]: Could not generate persistent MAC address for veth201e05a: No such file or directory
Sep 12 18:20:28 sentry-docker00.cs.umd.edu systemd-udevd[3240819]: Could not generate persistent MAC address for veth8a276a7: No such file or directory
Sep 12 18:20:28 sentry-docker00.cs.umd.edu systemd-udevd[3240816]: Could not generate persistent MAC address for veth4aacb20: No such file or directory
Sep 12 18:20:28 sentry-docker00.cs.umd.edu systemd-udevd[3240825]: Could not generate persistent MAC address for veth6ee37aa: No such file or directory
Sep 12 18:20:28 sentry-docker00.cs.umd.edu systemd-udevd[3240815]: Could not generate persistent MAC address for veth101e4be: No such file or directory
Sep 12 18:20:28 sentry-docker00.cs.umd.edu systemd-udevd[3240815]: Could not generate persistent MAC address for veth1b072a9: No such file or directory
Sep 12 18:20:28 sentry-docker00.cs.umd.edu systemd-udevd[3240825]: Could not generate persistent MAC address for vethfcb5afe: No such file or directory
Sep 12 18:20:28 sentry-docker00.cs.umd.edu systemd-udevd[3240826]: Could not generate persistent MAC address for veth74548e5: No such file or directory
Sep 12 18:20:28 sentry-docker00.cs.umd.edu systemd-udevd[3240815]: Could not generate persistent MAC address for vethe7a087f: No such file or directory
Sep 12 18:40:36 sentry-docker00.cs.umd.edu systemd-udevd[3250173]: link_config: could not get ethtool features for veth8a276a7
Sep 12 18:40:36 sentry-docker00.cs.umd.edu systemd-udevd[3250173]: Could not set offload features of veth8a276a7: No such device
Sep 12 18:40:36 sentry-docker00.cs.umd.edu systemd-udevd[3250205]: Could not generate persistent MAC address for vethe6d1428: No such file or directory
Sep 12 18:40:36 sentry-docker00.cs.umd.edu systemd-udevd[3250206]: Could not generate persistent MAC address for vethce316a4: No such file or directory
Sep 12 18:40:36 sentry-docker00.cs.umd.edu systemd-udevd[3250209]: Could not generate persistent MAC address for vethf2a5e8e: No such file or directory
Sep 12 18:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3250214]: Could not generate persistent MAC address for veth0e2be5a: No such file or directory
Sep 12 18:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3250222]: Could not generate persistent MAC address for veth7ce9af6: No such file or directory
Sep 12 18:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3250215]: Could not generate persistent MAC address for veth3ce9b06: No such file or directory
Sep 12 18:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3250222]: Could not generate persistent MAC address for veth59c6b2c: No such file or directory
Sep 12 18:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3250215]: Could not generate persistent MAC address for veth48e248d: No such file or directory
Sep 12 18:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3250261]: Could not generate persistent MAC address for vethcbf5352: No such file or directory
Sep 12 18:40:37 sentry-docker00.cs.umd.edu systemd-udevd[3250262]: Could not generate persistent MAC address for veth92a56c7: No such file or directory
Sep 12 19:00:45 sentry-docker00.cs.umd.edu systemd-udevd[3259573]: link_config: could not get ethtool features for veth59c6b2c
Sep 12 19:00:45 sentry-docker00.cs.umd.edu systemd-udevd[3259573]: Could not set offload features of veth59c6b2c: No such device
Sep 12 19:00:45 sentry-docker00.cs.umd.edu systemd-udevd[3259625]: Could not generate persistent MAC address for veth706d078: No such file or directory
Sep 12 19:00:45 sentry-docker00.cs.umd.edu systemd-udevd[3259626]: Could not generate persistent MAC address for veth10a9fa8: No such file or directory
Sep 12 19:00:45 sentry-docker00.cs.umd.edu systemd-udevd[3259629]: Could not generate persistent MAC address for veth61cef45: No such file or directory
Sep 12 19:00:45 sentry-docker00.cs.umd.edu systemd-udevd[3259630]: Could not generate persistent MAC address for vethde738b4: No such file or directory
Sep 12 19:00:45 sentry-docker00.cs.umd.edu systemd-udevd[3259633]: Could not generate persistent MAC address for vethfd7ab1e: No such file or directory
Sep 12 19:00:45 sentry-docker00.cs.umd.edu systemd-udevd[3259641]: Could not generate persistent MAC address for vethc5356c5: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 12 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 12 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 12 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 12 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 12 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 12 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 12 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (10 distinct, 12 total) ==
Sep 12 18:15:20 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
Sep 12 18:25:50 submit26-b9-f1 setroubleshoot[1374640]: 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 12 18:25:50 submit26-b9-f1 setroubleshoot[1374640]: 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 12 18:25:50 submit26-b9-f1 setroubleshoot[1374640]: 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 12 18:25:50 submit26-b9-f1 setroubleshoot[1374640]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.SWU4pK/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 12 18:25:50 submit26-b9-f1 setroubleshoot[1374640]: 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 12 18:25:50 submit26-b9-f1 setroubleshoot[1374640]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.SWU4pK. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 12 18:25:50 submit26-b9-f1 setroubleshoot[1374640]: 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 12 18:25:50 submit26-b9-f1 setroubleshoot[1374640]: 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 12 18:25:50 submit26-b9-f1 setroubleshoot[1374640]: 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, 17 total) ==
Sep 12 18:06:46 submit26-b9-f2 setroubleshoot[514827]: 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 12 18:06:46 submit26-b9-f2 setroubleshoot[514827]: 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 12 18:06:46 submit26-b9-f2 setroubleshoot[514827]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 [x2]
Sep 12 18:06:46 submit26-b9-f2 setroubleshoot[514827]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.9y8rsR/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2]
Sep 12 18:06:46 submit26-b9-f2 setroubleshoot[514827]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 [x2]
Sep 12 18:06:46 submit26-b9-f2 setroubleshoot[514827]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.9y8rsR. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 12 18:06:46 submit26-b9-f2 setroubleshoot[514827]: 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 12 18:06:46 submit26-b9-f2 setroubleshoot[514827]: 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 12 18:06:46 submit26-b9-f2 setroubleshoot[514827]: 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 12 18:18:06 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f3 (1 distinct, 7 total) ==
Sep 12 18:14:55 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
== submit26-b9-f4 (1 distinct, 2 total) ==
Sep 12 18:16:04 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.0659s
Status : exited 0
Output :
Syslog digest — 2026-09-12 18:05 EDT
Processed 2,329 lines, filtered 1,404 (60%). 925 unknown (135 distinct) from 19 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 12 17:40:45 b0b02.cs.umd.edu rustdesk[395307]: cannot open display:
== bachata (10 distinct, 10 total) ==
Sep 12 17:08:40 bachata smbd[445077]: [2026/09/12 17:08:40.457810, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service)
Sep 12 17:08:40 bachata smbd[445077]: chdir_current_service: vfs_ChDir(/fs/junkfood/nelson) failed: Permission denied. Current token: uid=20608, gid=20608, 20 groups: 20608 319050000 25274 319000009 25057 30872 25195 30043 25038 15228 31006 15294 15206 15248 25025 30742 25200 319100011 30871 30736
Sep 12 17:08:40 bachata smbd[445077]: [2026/09/12 17:08:40.458038, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect)
Sep 12 17:08:40 bachata smbd[445077]: smbXsrv_tcon_disconnect: disconnect(0x02e582fb, 'nelson'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR
Sep 12 17:08:40 bachata smbd[445077]: [2026/09/12 17:08:40.458147, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all)
Sep 12 17:08:40 bachata smbd[445077]: smbXsrv_tcon_disconnect_all: count[3] errors[1] first[NT_STATUS_INTERNAL_ERROR]
Sep 12 17:08:40 bachata smbd[445077]: [2026/09/12 17:08:40.458189, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff)
Sep 12 17:08:40 bachata smbd[445077]: smbXsrv_session_logoff: smbXsrv_session_logoff(0x6e9889a7): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR
Sep 12 17:08:40 bachata smbd[445077]: [2026/09/12 17:08:40.458254, 0] ../../source3/smbd/smbXsrv_session.c:428(smbXsrv_session_close_shutdown_done)
Sep 12 17:08:40 bachata smbd[445077]: smbXsrv_session_close_shutdown_done: smbXsrv_session_logoff(1855490471) failed: NT_STATUS_INTERNAL_ERROR
== csfw00a (1 distinct, 130 total) ==
Sep 12 17:04:26 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x130]
== frozone (1 distinct, 1 total) ==
Sep 12 17:35:31 frozone systemd-tmpfiles[1435908]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted
== galax (2 distinct, 80 total) ==
Sep 12 17:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40]
Sep 12 17: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 12 17:25:06 hazfs.cs.umd.edu pcp[772894]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2]
== idm00 (15 distinct, 169 total) ==
Sep 12 17:05:52 idm00 check-named-alive[1695771]: zone cs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:05:52 idm00 check-named-alive[1695832]: zone csdlabs.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:05:52 idm00 check-named-alive[1695893]: zone csic.umd.edu: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:05:52 idm00 check-named-alive[1695954]: zone 72.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:05:52 idm00 check-named-alive[1696015]: zone 73.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:05:52 idm00 check-named-alive[1696076]: zone 88.10.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:05:53 idm00 check-named-alive[1696137]: zone 28.172.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:05:53 idm00 check-named-alive[1696198]: zone 125.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:05:53 idm00 check-named-alive[1696259]: zone 126.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:05:53 idm00 check-named-alive[1696320]: zone 127.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:05:53 idm00 check-named-alive[1696381]: zone 128.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:05:53 idm00 check-named-alive[1696442]: zone 129.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:05:54 idm00 check-named-alive[1696503]: zone 130.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:05:54 idm00 check-named-alive[1696564]: zone 131.8.128.in-addr.arpa: local SOA serial 1788938974 lags newest peer 1788955413 by 16439 (threshold 3600); not acting [x12]
Sep 12 17:53:52 idm00 named[4166701]: client @0x7f11a00432a8 10.73.240.42#57050: update '73.10.in-addr.arpa/IN' denied
== idmh1 (14 distinct, 168 total) ==
Sep 12 17:07:26 idmh1 check-named-alive[2280947]: zone cs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 17:07:26 idmh1 check-named-alive[2281008]: zone csdlabs.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 17:07:26 idmh1 check-named-alive[2281069]: zone csic.umd.edu: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 17:07:27 idmh1 check-named-alive[2281130]: zone 72.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 17:07:27 idmh1 check-named-alive[2281191]: zone 73.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 17:07:27 idmh1 check-named-alive[2281252]: zone 88.10.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 17:07:27 idmh1 check-named-alive[2281313]: zone 28.172.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 17:07:27 idmh1 check-named-alive[2281374]: zone 125.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 17:07:28 idmh1 check-named-alive[2281435]: zone 126.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 17:07:28 idmh1 check-named-alive[2281498]: zone 127.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 17:07:28 idmh1 check-named-alive[2281561]: zone 128.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 17:07:28 idmh1 check-named-alive[2281622]: zone 129.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 17:07:28 idmh1 check-named-alive[2281683]: zone 130.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
Sep 12 17:07:29 idmh1 check-named-alive[2281744]: zone 131.8.128.in-addr.arpa: local SOA serial 1788939166 lags newest peer 1788955413 by 16247 (threshold 3600); not acting [x12]
== idmp0 (15 distinct, 169 total) ==
Sep 12 17:08:11 idmp0 check-named-alive[3353563]: zone cs.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 17:08:11 idmp0 check-named-alive[3353624]: zone csdlabs.umd.edu: local SOA serial 1788943212 lags newest peer 1788955413 by 12201 (threshold 3600); not acting [x12]
Sep 12 17:08:12 idmp0 check-named-alive[3353685]: zone csic.umd.edu: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 17:08:12 idmp0 check-named-alive[3353746]: zone 72.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 17:08:12 idmp0 check-named-alive[3353809]: zone 73.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 17:08:13 idmp0 check-named-alive[3353870]: zone 88.10.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 17:08:13 idmp0 check-named-alive[3353931]: zone 28.172.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 17:08:13 idmp0 check-named-alive[3353992]: zone 125.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 17:08:14 idmp0 check-named-alive[3354053]: zone 126.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 17:08:14 idmp0 check-named-alive[3354114]: zone 127.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 17:08:14 idmp0 check-named-alive[3354175]: zone 128.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 17:08:14 idmp0 check-named-alive[3354236]: zone 129.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 17:08:15 idmp0 check-named-alive[3354297]: zone 130.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 17:08:15 idmp0 check-named-alive[3354358]: zone 131.8.128.in-addr.arpa: local SOA serial 1788943211 lags newest peer 1788955413 by 12202 (threshold 3600); not acting [x12]
Sep 12 17:37:39 idmp0 named[1598691]: client @0x7f2d44005288 10.73.240.43#49501: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 46 total) ==
Sep 12 17:07:59 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x46]
== newhonors2 (1 distinct, 24 total) ==
Sep 12 17:13:03 newhonors2 dhcpcd[2549525]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 17:09:09 outbound00.cs.umd.edu python3[3578392]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 12 17:13:06 outbound01.cs.umd.edu python3[1642467]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (42 distinct, 42 total) ==
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212067]: link_config: could not get ethtool features for vethc80a3e0
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212067]: Could not set offload features of vethc80a3e0: No such device
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212068]: link_config: could not set ethtool features for veth3d28953
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212068]: Could not set offload features of veth3d28953: Operation not permitted
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212103]: Could not generate persistent MAC address for veth9620856: No such file or directory
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212104]: Could not generate persistent MAC address for veth14eee71: No such file or directory
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212107]: Could not generate persistent MAC address for vethc1c487b: No such file or directory
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212108]: Could not generate persistent MAC address for vethfc58ed0: No such file or directory
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212118]: Could not generate persistent MAC address for vethceb4d5e: No such file or directory
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212115]: Could not generate persistent MAC address for veth3b255af: No such file or directory
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212113]: Could not generate persistent MAC address for veth95f394f: No such file or directory
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212118]: Could not generate persistent MAC address for vethbc02bfd: No such file or directory
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212192]: Could not generate persistent MAC address for veth816b79d: No such file or directory
Sep 12 17:20:03 sentry-docker00.cs.umd.edu systemd-udevd[3212193]: Could not generate persistent MAC address for veth4a56b65: No such file or directory
Sep 12 17:40:11 sentry-docker00.cs.umd.edu systemd-udevd[3221634]: link_config: could not get ethtool features for veth95f394f
Sep 12 17:40:11 sentry-docker00.cs.umd.edu systemd-udevd[3221634]: Could not set offload features of veth95f394f: No such device
Sep 12 17:40:11 sentry-docker00.cs.umd.edu systemd-udevd[3221636]: link_config: could not get ethtool features for veth816b79d
Sep 12 17:40:11 sentry-docker00.cs.umd.edu systemd-udevd[3221636]: Could not set offload features of veth816b79d: No such device
Sep 12 17:40:11 sentry-docker00.cs.umd.edu systemd-udevd[3221671]: Could not generate persistent MAC address for veth5b3fa94: No such file or directory
Sep 12 17:40:11 sentry-docker00.cs.umd.edu systemd-udevd[3221672]: Could not generate persistent MAC address for vethabf75cc: No such file or directory
Sep 12 17:40:11 sentry-docker00.cs.umd.edu systemd-udevd[3221675]: Could not generate persistent MAC address for veth103eb5c: No such file or directory
Sep 12 17:40:11 sentry-docker00.cs.umd.edu systemd-udevd[3221676]: Could not generate persistent MAC address for vethcec55e3: No such file or directory
Sep 12 17:40:12 sentry-docker00.cs.umd.edu systemd-udevd[3221687]: Could not generate persistent MAC address for veth7d73ba4: No such file or directory
Sep 12 17:40:12 sentry-docker00.cs.umd.edu systemd-udevd[3221685]: Could not generate persistent MAC address for veth92b734c: No such file or directory
Sep 12 17:40:12 sentry-docker00.cs.umd.edu systemd-udevd[3221687]: Could not generate persistent MAC address for veth1ab9480: No such file or directory
Sep 12 17:40:12 sentry-docker00.cs.umd.edu systemd-udevd[3221695]: Could not generate persistent MAC address for veth790dae8: No such file or directory
Sep 12 17:40:12 sentry-docker00.cs.umd.edu systemd-udevd[3221744]: Could not generate persistent MAC address for veth89221a9: No such file or directory
Sep 12 17:40:12 sentry-docker00.cs.umd.edu systemd-udevd[3221745]: Could not generate persistent MAC address for vethd217834: No such file or directory
Sep 12 18:00:20 sentry-docker00.cs.umd.edu systemd-udevd[3231298]: link_config: could not get ethtool features for veth5b3fa94
Sep 12 18:00:20 sentry-docker00.cs.umd.edu systemd-udevd[3231298]: Could not set offload features of veth5b3fa94: No such device
... 12 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 12 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 12 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 12 17:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 12 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 12 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 12 17:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 12 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 3 total) ==
Sep 12 17:10:31 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f2 (1 distinct, 3 total) ==
Sep 12 17:05:07 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f3 (10 distinct, 15 total) ==
Sep 12 17:06:40 submit26-b9-f3 setroubleshoot[620282]: 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 12 17:06:40 submit26-b9-f3 setroubleshoot[620282]: 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 12 17:06:40 submit26-b9-f3 setroubleshoot[620282]: 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 12 17:06:40 submit26-b9-f3 setroubleshoot[620282]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.TQ2LSV/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 12 17:06:40 submit26-b9-f3 setroubleshoot[620282]: 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 12 17:06:40 submit26-b9-f3 setroubleshoot[620282]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.TQ2LSV. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 12 17:06:40 submit26-b9-f3 setroubleshoot[620282]: 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 12 17:06:40 submit26-b9-f3 setroubleshoot[620282]: 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 12 17:06:40 submit26-b9-f3 setroubleshoot[620282]: 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 12 17:09:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f4 (10 distinct, 12 total) ==
Sep 12 17:18:09 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
Sep 12 17:24:43 submit26-b9-f4 setroubleshoot[457511]: 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 12 17:24:44 submit26-b9-f4 setroubleshoot[457511]: 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 12 17:24:44 submit26-b9-f4 setroubleshoot[457511]: 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 12 17:24:44 submit26-b9-f4 setroubleshoot[457511]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.d6RcAQ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 12 17:24:44 submit26-b9-f4 setroubleshoot[457511]: 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 12 17:24:44 submit26-b9-f4 setroubleshoot[457511]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.d6RcAQ. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 12 17:24:44 submit26-b9-f4 setroubleshoot[457511]: 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 12 17:24:44 submit26-b9-f4 setroubleshoot[457511]: 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 12 17:24:44 submit26-b9-f4 setroubleshoot[457511]: 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