Command: /usr/local/sbin/syslog-digest.py
Time : 0.0454s
Status : exited 0
Output :
Syslog digest — 2026-09-24 03:05 EDT
Processed 2,257 lines, filtered 1,981 (87%). 276 unknown (173 distinct) from 18 host(s).
== abadi-computer (1 distinct, 1 total) ==
Sep 24 03:00:21 abadi-computer kernel: kauditd_printk_skb: 2 callbacks suppressed
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 24 02:57:51 b0b02.cs.umd.edu rustdesk[449705]: cannot open display:
== biggulp.cs.umd.edu (1 distinct, 3 total) ==
Sep 24 02:45:02 biggulp.cs.umd.edu sshd-session[3807836]: error: Protocol major versions differ: 2 vs. 1 [x3]
== cheezit.cs.umd.edu (1 distinct, 3 total) ==
Sep 24 02:42:44 cheezit.cs.umd.edu sshd-session[2536781]: error: Protocol major versions differ: 2 vs. 1 [x3]
== idm00 (1 distinct, 1 total) ==
Sep 24 02:54:06 idm00 named[4166701]: client @0x7f11a93e0168 10.73.240.42#53904: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 24 02:39:31 idmp0 named[1598691]: client @0x7f2d3c0747e8 10.73.240.43#50576: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 4 total) ==
Sep 24 02:22:56 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== krispykreme.cs.umd.edu (1 distinct, 3 total) ==
Sep 24 02:43:12 krispykreme.cs.umd.edu sshd-session[1873054]: error: Protocol major versions differ: 2 vs. 1 [x3]
== munin (2 distinct, 28 total) ==
Sep 24 02:08:10 munin sudo[2660005]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x14]
Sep 24 02:08:10 munin sudo[2660005]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x14]
== newhonors2 (1 distinct, 24 total) ==
Sep 24 02:13:03 newhonors2 dhcpcd[3067519]: dhcpcd is not running [x24]
== ntop00 (96 distinct, 96 total) ==
Sep 24 02:05:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 76) ***
Sep 24 02:05:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 76, QN: 58/58, ET: 0) ***
Sep 24 02:05:11 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 76, QN: 7130/7130, ET: 10) ***
Sep 24 02:06:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 77) ***
Sep 24 02:06:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 77, QN: 6370/6370, ET: 0) ***
Sep 24 02:06:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 77) ***
Sep 24 02:06:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 77, QN: 59/59, ET: 0) ***
Sep 24 02:10:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 78) ***
Sep 24 02:10:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 78) ***
Sep 24 02:10:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 78, QN: 60/60, ET: 0) ***
Sep 24 02:10:09 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 78, QN: 5416/5416, ET: 8) ***
Sep 24 02:11:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 79) ***
Sep 24 02:11:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 79, QN: 5326/5326, ET: 0) ***
Sep 24 02:11:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 79) ***
Sep 24 02:11:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 79, QN: 59/59, ET: 0) ***
Sep 24 02:15:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 80) ***
Sep 24 02:15:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 80) ***
Sep 24 02:15:02 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 80, QN: 54/54, ET: 1) ***
Sep 24 02:15:09 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 80, QN: 5846/5846, ET: 8) ***
Sep 24 02:16:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 81) ***
Sep 24 02:16:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 81) ***
Sep 24 02:16:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 81, QN: 55/55, ET: 0) ***
Sep 24 02:16:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 81, QN: 6104/6104, ET: 0) ***
Sep 24 02:20:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 82) ***
Sep 24 02:20:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 82) ***
Sep 24 02:20:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 82, QN: 56/56, ET: 0) ***
Sep 24 02:20:10 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 82, QN: 6639/6639, ET: 9) ***
Sep 24 02:21:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 83) ***
Sep 24 02:21:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 83, QN: 6674/6674, ET: 0) ***
Sep 24 02:21:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 83) ***
... 66 more distinct messages not shown
== outbound00.cs.umd.edu (2 distinct, 7 total) ==
Sep 24 02:09:09 outbound00.cs.umd.edu python3[3279158]: ldapdb [x6]
Sep 24 03:04:53 outbound00.cs.umd.edu cockpit-ws[3292325]: /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
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 24 02:13:07 outbound01.cs.umd.edu python3[1345349]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 24 02:12:47 sentry-docker00.cs.umd.edu systemd-udevd[2562921]: link_config: could not get ethtool features for vethe3f73f8
Sep 24 02:12:47 sentry-docker00.cs.umd.edu systemd-udevd[2562921]: Could not set offload features of vethe3f73f8: No such device
Sep 24 02:12:47 sentry-docker00.cs.umd.edu systemd-udevd[2563004]: Could not generate persistent MAC address for vethc8124ea: No such file or directory
Sep 24 02:12:47 sentry-docker00.cs.umd.edu systemd-udevd[2563005]: Could not generate persistent MAC address for vethe9f17f8: No such file or directory
Sep 24 02:12:47 sentry-docker00.cs.umd.edu systemd-udevd[2563008]: Could not generate persistent MAC address for vetha17b250: No such file or directory
Sep 24 02:12:47 sentry-docker00.cs.umd.edu systemd-udevd[2563009]: Could not generate persistent MAC address for veth76be925: No such file or directory
Sep 24 02:12:47 sentry-docker00.cs.umd.edu systemd-udevd[2563032]: Could not generate persistent MAC address for vethd863aee: No such file or directory
Sep 24 02:12:47 sentry-docker00.cs.umd.edu systemd-udevd[2563033]: Could not generate persistent MAC address for veth39240db: No such file or directory
Sep 24 02:12:47 sentry-docker00.cs.umd.edu systemd-udevd[2563045]: Could not generate persistent MAC address for veth4bc2fc3: No such file or directory
Sep 24 02:12:47 sentry-docker00.cs.umd.edu systemd-udevd[2563046]: Could not generate persistent MAC address for veth772a3bd: No such file or directory
Sep 24 02:12:47 sentry-docker00.cs.umd.edu systemd-udevd[2563123]: Could not generate persistent MAC address for veth9f81f91: No such file or directory
Sep 24 02:12:47 sentry-docker00.cs.umd.edu systemd-udevd[2563128]: Could not generate persistent MAC address for vethd36c794: No such file or directory
Sep 24 02:32:55 sentry-docker00.cs.umd.edu systemd-udevd[2572734]: link_config: could not get ethtool features for vethd863aee
Sep 24 02:32:55 sentry-docker00.cs.umd.edu systemd-udevd[2572734]: Could not set offload features of vethd863aee: No such device
Sep 24 02:32:56 sentry-docker00.cs.umd.edu systemd-udevd[2572773]: Could not generate persistent MAC address for veth0c28ea6: No such file or directory
Sep 24 02:32:56 sentry-docker00.cs.umd.edu systemd-udevd[2572774]: Could not generate persistent MAC address for veth88b87ee: No such file or directory
Sep 24 02:32:56 sentry-docker00.cs.umd.edu systemd-udevd[2572777]: Could not generate persistent MAC address for veth4fad4f6: No such file or directory
Sep 24 02:32:56 sentry-docker00.cs.umd.edu systemd-udevd[2572778]: Could not generate persistent MAC address for veth685c7cc: No such file or directory
Sep 24 02:32:56 sentry-docker00.cs.umd.edu systemd-udevd[2572791]: Could not generate persistent MAC address for veth47ddcd1: No such file or directory
Sep 24 02:32:56 sentry-docker00.cs.umd.edu systemd-udevd[2572795]: Could not generate persistent MAC address for vethee52297: No such file or directory
Sep 24 02:32:56 sentry-docker00.cs.umd.edu systemd-udevd[2572795]: Could not generate persistent MAC address for veth6ec7fe2: No such file or directory
Sep 24 02:32:56 sentry-docker00.cs.umd.edu systemd-udevd[2572791]: Could not generate persistent MAC address for vethe706a11: No such file or directory
Sep 24 02:32:56 sentry-docker00.cs.umd.edu systemd-udevd[2572806]: Could not generate persistent MAC address for veth218a038: No such file or directory
Sep 24 02:32:56 sentry-docker00.cs.umd.edu systemd-udevd[2572810]: Could not generate persistent MAC address for veth6a574ef: No such file or directory
Sep 24 02:53:04 sentry-docker00.cs.umd.edu systemd-udevd[2582337]: link_config: could not get ethtool features for veth47ddcd1
Sep 24 02:53:04 sentry-docker00.cs.umd.edu systemd-udevd[2582337]: Could not set offload features of veth47ddcd1: No such device
Sep 24 02:53:04 sentry-docker00.cs.umd.edu systemd-udevd[2582369]: Could not generate persistent MAC address for veth8d73c5b: No such file or directory
Sep 24 02:53:04 sentry-docker00.cs.umd.edu systemd-udevd[2582370]: Could not generate persistent MAC address for vethb03f121: No such file or directory
Sep 24 02:53:04 sentry-docker00.cs.umd.edu systemd-udevd[2582373]: Could not generate persistent MAC address for veth7dcacb9: No such file or directory
Sep 24 02:53:04 sentry-docker00.cs.umd.edu systemd-udevd[2582379]: Could not generate persistent MAC address for veth9dace21: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 24 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 24 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 24 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 24 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 24 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 24 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 24 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 24 02:25:55 submit26-b9-f1 setroubleshoot[3273289]: 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 24 02:25:55 submit26-b9-f1 setroubleshoot[3273289]: 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 24 02:25:55 submit26-b9-f1 setroubleshoot[3273289]: 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 24 02:25:55 submit26-b9-f1 setroubleshoot[3273289]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.T9cy56/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 24 02:25:55 submit26-b9-f1 setroubleshoot[3273289]: 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 24 02:25:55 submit26-b9-f1 setroubleshoot[3273289]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.T9cy56. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 24 02:25:55 submit26-b9-f1 setroubleshoot[3273289]: 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 24 02:25:56 submit26-b9-f1 setroubleshoot[3273289]: 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 24 02:25:56 submit26-b9-f1 setroubleshoot[3273289]: 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 24 02:06:50 submit26-b9-f2 setroubleshoot[2370333]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 [x2]
Sep 24 02:06:50 submit26-b9-f2 setroubleshoot[2370333]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a [x2]
Sep 24 02:06:50 submit26-b9-f2 setroubleshoot[2370333]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339
Sep 24 02:06:50 submit26-b9-f2 setroubleshoot[2370333]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.pcFgzm/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 24 02:06:50 submit26-b9-f2 setroubleshoot[2370333]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1
Sep 24 02:06:50 submit26-b9-f2 setroubleshoot[2370333]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.pcFgzm. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 24 02:06:50 submit26-b9-f2 setroubleshoot[2370333]: 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 [x2]
Sep 24 02:06:51 submit26-b9-f2 setroubleshoot[2370333]: 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 24 02:06:51 submit26-b9-f2 setroubleshoot[2370333]: 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 [x2]
Sep 24 02:06:51 submit26-b9-f2 setroubleshoot[2370333]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.0iVzpY. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
== teaching-awards (1 distinct, 1 total) ==
Sep 24 02:15:02 teaching-awards sshd-session[1514136]: fatal: userauth_pubkey: parse publickey packet: incomplete message [preauth]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0470s
Status : exited 0
Output :
Syslog digest — 2026-09-24 02:05 EDT
Processed 2,633 lines, filtered 2,336 (88%). 297 unknown (185 distinct) from 20 host(s).
== alec.cs.umd.edu (1 distinct, 1 total) ==
Sep 24 01:57:51 alec.cs.umd.edu mariadb-drupal[3120]: 2026-09-24 5:57:51 18338 [Warning] Aborted connection 18338 to db: 'unconnected' user: 'root' host: 'localhost' (Got timeout reading communication packets)
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 24 01:57:49 b0b02.cs.umd.edu rustdesk[434483]: cannot open display:
== cheezit.cs.umd.edu (1 distinct, 1 total) ==
Sep 24 01:38:36 cheezit.cs.umd.edu sshd-session[2522212]: error: send_error: write: Connection reset by peer
== galax (1 distinct, 1 total) ==
Sep 24 01:53:17 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 2051 times, consider switching to WQ_UNBOUND
== gle-dind04 (2 distinct, 2 total) ==
Sep 24 01:32:25 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 24 01:32:25 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== idm00 (1 distinct, 1 total) ==
Sep 24 01:54:06 idm00 named[4166701]: client @0x7f119806f9c8 10.73.240.42#49394: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 24 01:39:31 idmp0 named[1598691]: client @0x7f2d3400d5c8 10.73.240.43#51759: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 1 total) ==
Sep 24 01:56:44 inbound00.cs.umd.edu krb5_child[3416924]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 3 total) ==
Sep 24 01:08:17 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== krispykreme.cs.umd.edu (4 distinct, 5 total) ==
Sep 24 01:20:47 krispykreme.cs.umd.edu sshd-session[1850526]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2]
Sep 24 01:20:48 krispykreme.cs.umd.edu sshd-session[1850526]: Error in Duo login for 'larry' from 71.191.93.172
Sep 24 01:20:48 krispykreme.cs.umd.edu sshd-session[1850339]: error: PAM: Authentication failure for larry from 71.191.93.172
Sep 24 01:38:35 krispykreme.cs.umd.edu sshd-session[1855763]: error: send_error: write: Connection reset by peer
== munin (2 distinct, 44 total) ==
Sep 24 01:08:32 munin sudo[2638787]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x22]
Sep 24 01:08:32 munin sudo[2638787]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x22]
== netman.cs.umd.edu (3 distinct, 6 total) ==
Sep 24 01:13:14 netman.cs.umd.edu krb5_child[7660]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Sep 24 01:13:18 netman.cs.umd.edu sshd[7657]: error: PAM: Authentication failure for admin from 34.38.77.240
Sep 24 01:15:16 netman.cs.umd.edu sshd[8196]: error: Protocol major versions differ: 2 vs. 1
== newhonors2 (1 distinct, 24 total) ==
Sep 24 01:13:02 newhonors2 dhcpcd[3065676]: dhcpcd is not running [x24]
== ntop00 (97 distinct, 97 total) ==
Sep 24 01:05:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 52) ***
Sep 24 01:05:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 52) ***
Sep 24 01:05:04 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 52, QN: 41/41, ET: 3) ***
Sep 24 01:06:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 53) ***
Sep 24 01:06:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 53, QN: 4851/4851, ET: 0) ***
Sep 24 01:06:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 53) ***
Sep 24 01:06:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 53, QN: 47/47, ET: 0) ***
Sep 24 01:07:03 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 52, QN: 5551/5551, ET: 122) ***
Sep 24 01:10:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 54) ***
Sep 24 01:10:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 54) ***
Sep 24 01:10:02 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 54, QN: 59/59, ET: 1) ***
Sep 24 01:10:40 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 54, QN: 4372/4372, ET: 39) ***
Sep 24 01:11:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 55) ***
Sep 24 01:11:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 55, QN: 5056/5056, ET: 0) ***
Sep 24 01:11:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 55) ***
Sep 24 01:11:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 55, QN: 53/53, ET: 0) ***
Sep 24 01:15:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 56) ***
Sep 24 01:15:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 56) ***
Sep 24 01:15:02 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 56, QN: 41/41, ET: 1) ***
Sep 24 01:16:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 57) ***
Sep 24 01:16:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 57, QN: 6399/6399, ET: 0) ***
Sep 24 01:16:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 57) ***
Sep 24 01:16:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 57, QN: 49/49, ET: 0) ***
Sep 24 01:16:07 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 56, QN: 6378/6378, ET: 66) ***
Sep 24 01:20:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 58) ***
Sep 24 01:20:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 58) ***
Sep 24 01:20:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 58, QN: 63/63, ET: 0) ***
Sep 24 01:21:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 59) ***
Sep 24 01:21:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 59, QN: 5501/5501, ET: 0) ***
Sep 24 01:21:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 59) ***
... 67 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 24 01:09:09 outbound00.cs.umd.edu python3[3265216]: ldapdb [x6]
== outbound01.cs.umd.edu (2 distinct, 7 total) ==
Sep 24 01:13:07 outbound01.cs.umd.edu python3[1331182]: ldapdb [x6]
Sep 24 02:04:25 outbound01.cs.umd.edu krb5_child[1343497]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== sentry-docker00.cs.umd.edu (40 distinct, 40 total) ==
Sep 24 01:12:22 sentry-docker00.cs.umd.edu systemd-udevd[2534572]: link_config: could not set ethtool features for vethbb1f5db
Sep 24 01:12:22 sentry-docker00.cs.umd.edu systemd-udevd[2534572]: Could not set offload features of vethbb1f5db: Operation not permitted
Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534609]: Could not generate persistent MAC address for vethe96f173: No such file or directory
Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534610]: Could not generate persistent MAC address for vethfca6af9: No such file or directory
Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534613]: Could not generate persistent MAC address for veth3d42057: No such file or directory
Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534614]: Could not generate persistent MAC address for veth921d466: No such file or directory
Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534627]: Could not generate persistent MAC address for veth7a24734: No such file or directory
Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534634]: Could not generate persistent MAC address for veth248086a: No such file or directory
Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534625]: Could not generate persistent MAC address for veth610db5c: No such file or directory
Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534623]: Could not generate persistent MAC address for veth1274925: No such file or directory
Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534619]: Could not generate persistent MAC address for vethf1123a3: No such file or directory
Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534635]: Could not generate persistent MAC address for veth9ab4a12: No such file or directory
Sep 24 01:32:30 sentry-docker00.cs.umd.edu systemd-udevd[2544175]: link_config: could not get ethtool features for vethe96f173
Sep 24 01:32:30 sentry-docker00.cs.umd.edu systemd-udevd[2544175]: Could not set offload features of vethe96f173: No such device
Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544179]: link_config: could not get ethtool features for vethf1123a3
Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544179]: Could not set offload features of vethf1123a3: No such device
Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544209]: Could not generate persistent MAC address for veth4830e5a: No such file or directory
Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544210]: Could not generate persistent MAC address for veth747043d: No such file or directory
Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544228]: Could not generate persistent MAC address for veth74ce034: No such file or directory
Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544215]: Could not generate persistent MAC address for vethb276d3e: No such file or directory
Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544215]: Could not generate persistent MAC address for veth6da9592: No such file or directory
Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544213]: Could not generate persistent MAC address for vethefc04ee: No such file or directory
Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544225]: Could not generate persistent MAC address for vethf9c55a9: No such file or directory
Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544213]: Could not generate persistent MAC address for veth4d3eeca: No such file or directory
Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544267]: Could not generate persistent MAC address for vetha9144c7: No such file or directory
Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544270]: Could not generate persistent MAC address for veth28e9970: No such file or directory
Sep 24 01:52:39 sentry-docker00.cs.umd.edu systemd-udevd[2553480]: link_config: could not get ethtool features for veth74ce034
Sep 24 01:52:39 sentry-docker00.cs.umd.edu systemd-udevd[2553480]: Could not set offload features of veth74ce034: No such device
Sep 24 01:52:39 sentry-docker00.cs.umd.edu systemd-udevd[2553577]: link_config: could not get ethtool features for vetha9144c7
Sep 24 01:52:39 sentry-docker00.cs.umd.edu systemd-udevd[2553577]: Could not set offload features of vetha9144c7: No such device
... 10 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 24 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 24 01:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 24 01:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 24 01:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 24 01:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 24 01:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 24 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 24 01:06:44 submit26-b9-f3 setroubleshoot[2917160]: 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 24 01:06:44 submit26-b9-f3 setroubleshoot[2917160]: 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 24 01:06:44 submit26-b9-f3 setroubleshoot[2917160]: 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 24 01:06:44 submit26-b9-f3 setroubleshoot[2917160]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.LBRYMq/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 24 01:06:44 submit26-b9-f3 setroubleshoot[2917160]: 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 24 01:06:45 submit26-b9-f3 setroubleshoot[2917160]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.LBRYMq. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 24 01:06:45 submit26-b9-f3 setroubleshoot[2917160]: 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 24 01:06:45 submit26-b9-f3 setroubleshoot[2917160]: 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 24 01:06:45 submit26-b9-f3 setroubleshoot[2917160]: 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, 9 total) ==
Sep 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: 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 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: 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 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: 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 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.x88Cq1/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: 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 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.x88Cq1. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: 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 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: 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 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: 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.0472s
Status : exited 0
Output :
Syslog digest — 2026-09-24 01:05 EDT
Processed 2,015 lines, filtered 1,607 (79%). 408 unknown (231 distinct) from 32 host(s).
== abuse (3 distinct, 4 total) ==
Sep 24 00:10:14 abuse systemd[1]: New main PID 29946 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 24 00:10:33 abuse systemd[1]: Daemon never wrote its PID file. Failing.
Sep 24 00:10:51 abuse systemd[1]: pmlogger.service: Supervising process 5062 which is not our child. We'll most likely not notice when it exits.
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 24 00:57:45 b0b02.cs.umd.edu rustdesk[419235]: cannot open display:
== bachata (10 distinct, 10 total) ==
Sep 24 00:11:31 bachata smbd[1078686]: [2026/09/24 00:11:31.832840, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service)
Sep 24 00:11:31 bachata smbd[1078686]: chdir_current_service: vfs_ChDir(/fs/junkfood/mount) failed: Permission denied. Current token: uid=11255, gid=11255, 12 groups: 11255 319000009 25038 15294 15229 755 25030 25025 30880 25029 770 15026
Sep 24 00:11:31 bachata smbd[1078686]: [2026/09/24 00:11:31.833619, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect)
Sep 24 00:11:31 bachata smbd[1078686]: smbXsrv_tcon_disconnect: disconnect(0xf14a5f70, 'mount'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR
Sep 24 00:11:31 bachata smbd[1078686]: [2026/09/24 00:11:31.833799, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all)
Sep 24 00:11:31 bachata smbd[1078686]: smbXsrv_tcon_disconnect_all: count[2] errors[1] first[NT_STATUS_INTERNAL_ERROR]
Sep 24 00:11:31 bachata smbd[1078686]: [2026/09/24 00:11:31.833866, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff)
Sep 24 00:11:31 bachata smbd[1078686]: smbXsrv_session_logoff: smbXsrv_session_logoff(0x321258d2): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR
Sep 24 00:11:31 bachata smbd[1078686]: [2026/09/24 00:11:31.834013, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done)
Sep 24 00:11:31 bachata smbd[1078686]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(840063186) failed: NT_STATUS_INTERNAL_ERROR
== biggulp.cs.umd.edu (4 distinct, 4 total) ==
Sep 24 01:00:00 biggulp.cs.umd.edu sshd-session[3789231]: pam_access(sshd:auth): access denied for user `admin' from `207.175.94.137'
Sep 24 01:00:00 biggulp.cs.umd.edu krb5_child[3789233]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 24 01:00:00 biggulp.cs.umd.edu sshd-session[3789229]: error: PAM: System error for admin from 207.175.94.137
Sep 24 01:00:44 biggulp.cs.umd.edu sshd-session[3789609]: error: Protocol major versions differ: 2 vs. 1
== cheezit.cs.umd.edu (1 distinct, 1 total) ==
Sep 24 00:17:58 cheezit.cs.umd.edu sshd-session[2503191]: pam_access(sshd:auth): access denied for user `bhatele' from `172.58.244.184'
== galax (8 distinct, 12 total) ==
Sep 24 00:36:16 galax systemd[1]: cups.service: Main process exited, code=dumped, status=11/SEGV [x5]
Sep 24 00:36:16 galax systemd[1]: Dependency failed for cups-browsed.service - Make remote CUPS printers available locally.
Sep 24 00:36:16 galax systemctl[66648]: Job for cups.service failed because a fatal signal was delivered causing the control process to dump core.
Sep 24 00:36:16 galax systemctl[66648]: See "systemctl status cups.service" and "journalctl -xeu cups.service" for details.
Sep 24 00:36:18 galax systemd[1]: cups.path: Start request repeated too quickly.
Sep 24 00:36:18 galax systemd[1]: cups.socket: Start request repeated too quickly.
Sep 24 00:36:18 galax systemd[1]: Failed to listen on cups.socket - CUPS Scheduler.
Sep 24 00:36:18 galax systemd[1]: Dependency failed for cups.service - CUPS Scheduler.
== grades01.cs.umd.edu (3 distinct, 4 total) ==
Sep 24 00:10:12 grades01.cs.umd.edu systemd[1]: New main PID 4146 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 24 00:10:33 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 24 00:10:48 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 11375 which is not our child. We'll most likely not notice when it exits.
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Sep 24 00:54:35 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 24 00:54:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 24 00:54:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 24 00:54:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 24 00:54:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 24 00:54:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 24 00:54:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 24 00:54:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 24 00:54:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 24 00:54:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 24 00:54:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 24 00:54:06 idm00 named[4166701]: client @0x7f11a8046198 10.73.240.42#63666: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 24 00:39:31 idmp0 named[1598691]: client @0x7f2d1c0184a8 10.73.240.43#62440: update '73.10.in-addr.arpa/IN' denied
== inbound01.cs.umd.edu (1 distinct, 1 total) ==
Sep 24 00:13:15 inbound01.cs.umd.edu krb5_child[1414884]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 3 total) ==
Sep 24 00:13:24 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== jubjub.cs.umd.edu (3 distinct, 4 total) ==
Sep 24 00:10:13 jubjub.cs.umd.edu systemd[1]: New main PID 658973 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 24 00:10:33 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 24 00:10:41 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 666510 which is not our child. We'll most likely not notice when it exits.
== mcstic (3 distinct, 6 total) ==
Sep 24 00:56:56 mcstic krb5_child[1029203]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Sep 24 00:57:00 mcstic sshd[1029198]: error: PAM: Authentication failure for admin from 34.140.66.30
Sep 24 00:57:05 mcstic sshd[1029211]: error: Protocol major versions differ: 2 vs. 1
== mirrors.cs.umd.edu (4 distinct, 6 total) ==
Sep 24 00:10:34 mirrors.cs.umd.edu root[9619]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log
Sep 24 00:10:34 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. [x2]
Sep 24 00:10:37 mirrors.cs.umd.edu systemd[1]: New main PID 8543 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 24 00:11:39 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 25222 which is not our child. We'll most likely not notice when it exits.
== misty.cs.umd.edu (3 distinct, 4 total) ==
Sep 24 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 18059 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 24 00:10:36 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 24 00:10:52 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 25612 which is not our child. We'll most likely not notice when it exits.
== munin (2 distinct, 40 total) ==
Sep 24 00:08:12 munin sudo[2615606]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x20]
Sep 24 00:08:12 munin sudo[2615606]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x20]
== newhonors2 (1 distinct, 24 total) ==
Sep 24 00:13:03 newhonors2 dhcpcd[3063851]: dhcpcd is not running [x24]
== ntop00 (96 distinct, 96 total) ==
Sep 24 00:05:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 28) ***
Sep 24 00:05:03 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 28, QN: 60/60, ET: 2) ***
Sep 24 00:05:52 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 26, QN: 11197/11197, ET: 351) ***
Sep 24 00:06:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 29) ***
Sep 24 00:06:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 29) ***
Sep 24 00:06:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 29, QN: 60/60, ET: 0) ***
Sep 24 00:06:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 29, QN: 10080/10080, ET: 0) ***
Sep 24 00:10:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 30) ***
Sep 24 00:10:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 30) ***
Sep 24 00:10:05 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 30, QN: 59/59, ET: 4) ***
Sep 24 00:11:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 31) ***
Sep 24 00:11:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 31, QN: 10669/10669, ET: 0) ***
Sep 24 00:11:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 31) ***
Sep 24 00:11:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 31, QN: 61/61, ET: 0) ***
Sep 24 00:13:08 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 28, QN: 10685/10685, ET: 487) ***
Sep 24 00:15:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 32) ***
Sep 24 00:15:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 32) ***
Sep 24 00:15:05 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 32, QN: 60/60, ET: 4) ***
Sep 24 00:16:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 33) ***
Sep 24 00:16:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 33, QN: 8392/8392, ET: 0) ***
Sep 24 00:16:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 33) ***
Sep 24 00:16:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 33, QN: 52/52, ET: 0) ***
Sep 24 00:17:25 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 30, QN: 10172/10172, ET: 444) ***
Sep 24 00:20:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 34) ***
Sep 24 00:20:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 34) ***
Sep 24 00:20:04 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 34, QN: 40/40, ET: 3) ***
Sep 24 00:21:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 35) ***
Sep 24 00:21:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 35, QN: 35/35, ET: 0) ***
Sep 24 00:21:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 35) ***
Sep 24 00:21:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 35, QN: 4827/4827, ET: 0) ***
... 66 more distinct messages not shown
== openrepo (1 distinct, 1 total) ==
Sep 24 00:08:53 openrepo (nin-node)[3624629]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 24 00:09:09 outbound00.cs.umd.edu python3[3250639]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 24 00:13:07 outbound01.cs.umd.edu python3[1317193]: ldapdb [x6]
== sebatinsky.cs.umd.edu (1 distinct, 1 total) ==
Sep 24 00:20:18 sebatinsky.cs.umd.edu kernel: hrtimer: interrupt took 2103012 ns
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 24 00:11:57 sentry-docker00.cs.umd.edu systemd-udevd[2506265]: link_config: could not get ethtool features for veth8cba554
Sep 24 00:11:57 sentry-docker00.cs.umd.edu systemd-udevd[2506265]: Could not set offload features of veth8cba554: No such device
Sep 24 00:11:58 sentry-docker00.cs.umd.edu systemd-udevd[2506333]: Could not generate persistent MAC address for veth1c4171b: No such file or directory
Sep 24 00:11:58 sentry-docker00.cs.umd.edu systemd-udevd[2506334]: Could not generate persistent MAC address for veth2fc41ee: No such file or directory
Sep 24 00:11:58 sentry-docker00.cs.umd.edu systemd-udevd[2506359]: Could not generate persistent MAC address for vethb194b3d: No such file or directory
Sep 24 00:11:58 sentry-docker00.cs.umd.edu systemd-udevd[2506360]: Could not generate persistent MAC address for veth2f8505b: No such file or directory
Sep 24 00:11:58 sentry-docker00.cs.umd.edu systemd-udevd[2506365]: Could not generate persistent MAC address for vethd182847: No such file or directory
Sep 24 00:11:58 sentry-docker00.cs.umd.edu systemd-udevd[2506363]: Could not generate persistent MAC address for veth4d00af1: No such file or directory
Sep 24 00:11:58 sentry-docker00.cs.umd.edu systemd-udevd[2506413]: Could not generate persistent MAC address for vethb6ce027: No such file or directory
Sep 24 00:11:58 sentry-docker00.cs.umd.edu systemd-udevd[2506414]: Could not generate persistent MAC address for veth2081696: No such file or directory
Sep 24 00:11:58 sentry-docker00.cs.umd.edu systemd-udevd[2506418]: Could not generate persistent MAC address for vethaaff246: No such file or directory
Sep 24 00:11:58 sentry-docker00.cs.umd.edu systemd-udevd[2506417]: Could not generate persistent MAC address for vethe0bf247: No such file or directory
Sep 24 00:32:05 sentry-docker00.cs.umd.edu systemd-udevd[2515732]: link_config: could not get ethtool features for vethe0bf247
Sep 24 00:32:05 sentry-docker00.cs.umd.edu systemd-udevd[2515732]: Could not set offload features of vethe0bf247: No such device
Sep 24 00:32:06 sentry-docker00.cs.umd.edu systemd-udevd[2515764]: Could not generate persistent MAC address for veth02c9001: No such file or directory
Sep 24 00:32:06 sentry-docker00.cs.umd.edu systemd-udevd[2515763]: Could not generate persistent MAC address for vethbc4f5b9: No such file or directory
Sep 24 00:32:06 sentry-docker00.cs.umd.edu systemd-udevd[2515767]: Could not generate persistent MAC address for veth33d8c86: No such file or directory
Sep 24 00:32:06 sentry-docker00.cs.umd.edu systemd-udevd[2515789]: Could not generate persistent MAC address for vethb537bbc: No such file or directory
Sep 24 00:32:06 sentry-docker00.cs.umd.edu systemd-udevd[2515788]: Could not generate persistent MAC address for veth1080376: No such file or directory
Sep 24 00:32:06 sentry-docker00.cs.umd.edu systemd-udevd[2515770]: Could not generate persistent MAC address for veth8a79a8e: No such file or directory
Sep 24 00:32:06 sentry-docker00.cs.umd.edu systemd-udevd[2515793]: Could not generate persistent MAC address for veth3dabde7: No such file or directory
Sep 24 00:32:06 sentry-docker00.cs.umd.edu systemd-udevd[2515794]: Could not generate persistent MAC address for veth428c913: No such file or directory
Sep 24 00:32:06 sentry-docker00.cs.umd.edu systemd-udevd[2515861]: Could not generate persistent MAC address for veth921a723: No such file or directory
Sep 24 00:32:06 sentry-docker00.cs.umd.edu systemd-udevd[2515862]: Could not generate persistent MAC address for vethbea9f43: No such file or directory
Sep 24 00:52:14 sentry-docker00.cs.umd.edu systemd-udevd[2525181]: link_config: could not get ethtool features for vethbc4f5b9
Sep 24 00:52:14 sentry-docker00.cs.umd.edu systemd-udevd[2525181]: Could not set offload features of vethbc4f5b9: No such device
Sep 24 00:52:14 sentry-docker00.cs.umd.edu systemd-udevd[2525203]: Could not generate persistent MAC address for vethbb1f5db: No such file or directory
Sep 24 00:52:14 sentry-docker00.cs.umd.edu systemd-udevd[2525204]: Could not generate persistent MAC address for veth809694a: No such file or directory
Sep 24 00:52:14 sentry-docker00.cs.umd.edu systemd-udevd[2525229]: Could not generate persistent MAC address for vethdf3ac17: No such file or directory
Sep 24 00:52:14 sentry-docker00.cs.umd.edu systemd-udevd[2525230]: Could not generate persistent MAC address for veth9a4d00b: No such file or directory
... 6 more distinct messages not shown
== strawberry (8 distinct, 39 total) ==
Sep 24 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 24 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 24 00:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 24 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 24 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 24 00:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 24 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Sep 24 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing.
== submit10-cln25 (3 distinct, 4 total) ==
Sep 24 00:10:11 submit10-cln25 systemd: New main PID 23322 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 24 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing.
Sep 24 00:10:36 submit10-cln25 systemd: pmlogger.service: Supervising process 30219 which is not our child. We'll most likely not notice when it exits.
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 24 00:22:00 submit26-b9-fclone setroubleshoot[382684]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff
Sep 24 00:22:00 submit26-b9-fclone setroubleshoot[382684]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f
Sep 24 00:22:00 submit26-b9-fclone setroubleshoot[382684]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8
Sep 24 00:22:00 submit26-b9-fclone setroubleshoot[382684]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.tX8fRN/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 24 00:22:00 submit26-b9-fclone setroubleshoot[382684]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566
Sep 24 00:22:00 submit26-b9-fclone setroubleshoot[382684]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.tX8fRN. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 24 00:22:00 submit26-b9-fclone setroubleshoot[382684]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac
Sep 24 00:22:00 submit26-b9-fclone setroubleshoot[382684]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c
Sep 24 00:22:00 submit26-b9-fclone setroubleshoot[382684]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4
== teaching-awards (2 distinct, 2 total) ==
Sep 24 00:21:09 teaching-awards krb5_child[1507644]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 24 00:22:02 teaching-awards sshd-session[1507678]: error: Protocol major versions differ: 2 vs. 1
== tma-0 (3 distinct, 4 total) ==
Sep 24 00:10:13 tma-0 systemd[1]: New main PID 2159 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 24 00:10:30 tma-0 systemd[1]: Daemon never wrote its PID file. Failing.
Sep 24 00:10:38 tma-0 systemd[1]: pmlogger.service: Supervising process 9129 which is not our child. We'll most likely not notice when it exits.
== uffish.cs.umd.edu (3 distinct, 4 total) ==
Sep 24 00:10:12 uffish.cs.umd.edu systemd[1]: New main PID 3191290 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 24 00:10:39 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 24 00:10:55 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3198981 which is not our child. We'll most likely not notice when it exits.
== vacuum.cs.umd.edu (3 distinct, 4 total) ==
Sep 24 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 21244 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 24 00:10:33 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 24 00:10:44 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 28349 which is not our child. We'll most likely not notice when it exits.
== whiffle.cs.umd.edu (3 distinct, 4 total) ==
Sep 24 00:10:14 whiffle.cs.umd.edu systemd[1]: New main PID 2733395 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 24 00:10:33 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 24 00:10:46 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 2740522 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.0439s
Status : exited 0
Output :
Syslog digest — 2026-09-24 00:05 EDT
Processed 2,536 lines, filtered 2,291 (90%). 245 unknown (173 distinct) from 25 host(s).
== abadi-computer (1 distinct, 1 total) ==
Sep 24 00:00:00 abadi-computer systemctl[373996]: Warning: The unit file, source configuration file or drop-ins of cups.service changed on disk. Run 'systemctl daemon-reload' to reload units.
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 23:57:43 b0b02.cs.umd.edu rustdesk[403090]: cannot open display:
== biggulp.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 23:27:07 biggulp.cs.umd.edu sshd-session[3770648]: pam_access(sshd:auth): access denied for user `bhatele' from `172.58.244.184'
== cheezit.cs.umd.edu (1 distinct, 4 total) ==
Sep 23 23:43:48 cheezit.cs.umd.edu sshd-session[2493504]: error: send_error: write: Connection reset by peer [x4]
== cmsc436-0101-redis (3 distinct, 3 total) ==
Sep 23 23:34:23 cmsc436-0101-redis krb5_child[3544010]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 23 23:34:25 cmsc436-0101-redis sshd-session[3544006]: error: PAM: Authentication failure for admin from 34.79.195.43
Sep 23 23:36:04 cmsc436-0101-redis sshd-session[3544026]: error: Protocol major versions differ: 2 vs. 1
== idm00 (1 distinct, 1 total) ==
Sep 23 23:54:06 idm00 named[4166701]: client @0x7f119854a418 10.73.240.42#52116: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 23 23:39:31 idmp0 named[1598691]: client @0x7f2d34043a38 10.73.240.43#61470: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 4 total) ==
Sep 23 23:13:06 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== krispykreme.cs.umd.edu (5 distinct, 5 total) ==
Sep 23 23:41:02 krispykreme.cs.umd.edu sshd-session[1822256]: error: maximum authentication attempts exceeded for root from 176.193.2.137 port 50972 ssh2 [preauth]
Sep 23 23:41:06 krispykreme.cs.umd.edu sshd-session[1822260]: error: maximum authentication attempts exceeded for root from 176.193.2.137 port 51198 ssh2 [preauth]
Sep 23 23:41:11 krispykreme.cs.umd.edu sshd-session[1822291]: error: maximum authentication attempts exceeded for root from 176.193.2.137 port 51466 ssh2 [preauth]
Sep 23 23:41:21 krispykreme.cs.umd.edu sshd-session[1822302]: error: maximum authentication attempts exceeded for admin from 176.193.2.137 port 51972 ssh2 [preauth]
Sep 23 23:41:28 krispykreme.cs.umd.edu sshd-session[1822345]: error: maximum authentication attempts exceeded for admin from 176.193.2.137 port 52312 ssh2 [preauth]
== matrix (4 distinct, 5 total) ==
Sep 23 23:52:08 matrix krb5_child[1884304]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 23 23:52:10 matrix sshd[1884280]: error: PAM: Authentication failure for admin from 34.62.71.20
Sep 23 23:53:22 matrix sshd[1884680]: error: Protocol major versions differ: 2 vs. 1
Sep 24 00:00:02 matrix (nin-node)[1887908]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== munin (2 distinct, 2 total) ==
Sep 24 00:04:09 munin sudo[2614114]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory
Sep 24 00:04:09 munin sudo[2614114]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order.
== neo-gizmonic (1 distinct, 1 total) ==
Sep 24 00:00:01 neo-gizmonic (nin-node)[2243039]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neoavion (1 distinct, 1 total) ==
Sep 24 00:00:01 neoavion (nin-node)[217354]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== newhonors2 (2 distinct, 25 total) ==
Sep 23 23:13:03 newhonors2 dhcpcd[3061744]: dhcpcd is not running [x24]
Sep 24 00:00:03 newhonors2 (nin-node)[3063292]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== ntop00 (96 distinct, 96 total) ==
Sep 23 23:05:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 4) ***
Sep 23 23:05:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 4) ***
Sep 23 23:05:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 4, QN: 13/13, ET: 0) ***
Sep 23 23:06:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 5) ***
Sep 23 23:06:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 5, QN: 5131/5131, ET: 0) ***
Sep 23 23:06:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 5) ***
Sep 23 23:06:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 5, QN: 18/18, ET: 0) ***
Sep 23 23:10:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6) ***
Sep 23 23:10:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6) ***
Sep 23 23:10:02 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6, QN: 21/21, ET: 1) ***
Sep 23 23:11:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 7) ***
Sep 23 23:11:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 7, QN: 6929/6929, ET: 0) ***
Sep 23 23:11:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 7) ***
Sep 23 23:11:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 7, QN: 24/24, ET: 0) ***
Sep 23 23:11:02 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 4, QN: 4062/4062, ET: 361) ***
Sep 23 23:15:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8) ***
Sep 23 23:15:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8) ***
Sep 23 23:15:05 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8, QN: 49/49, ET: 4) ***
Sep 23 23:16:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 9) ***
Sep 23 23:16:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 9, QN: 7480/7480, ET: 0) ***
Sep 23 23:16:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 9) ***
Sep 23 23:16:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 9, QN: 48/48, ET: 0) ***
Sep 23 23:20:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 10) ***
Sep 23 23:20:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 10) ***
Sep 23 23:20:07 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 10, QN: 52/52, ET: 6) ***
Sep 23 23:21:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 11) ***
Sep 23 23:21:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 11, QN: 6797/6797, ET: 0) ***
Sep 23 23:21:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 11) ***
Sep 23 23:21:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 11, QN: 59/59, ET: 0) ***
Sep 23 23:21:49 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6, QN: 6686/6686, ET: 708) ***
... 66 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 23 23:09:09 outbound00.cs.umd.edu python3[3236412]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 23 23:13:07 outbound01.cs.umd.edu python3[1302383]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 23 23:11:32 sentry-docker00.cs.umd.edu systemd-udevd[2477997]: link_config: could not get ethtool features for veth0174e0a
Sep 23 23:11:32 sentry-docker00.cs.umd.edu systemd-udevd[2477997]: Could not set offload features of veth0174e0a: No such device
Sep 23 23:11:32 sentry-docker00.cs.umd.edu systemd-udevd[2478031]: Could not generate persistent MAC address for vetha3885d2: No such file or directory
Sep 23 23:11:32 sentry-docker00.cs.umd.edu systemd-udevd[2478032]: Could not generate persistent MAC address for veth80c3d43: No such file or directory
Sep 23 23:11:32 sentry-docker00.cs.umd.edu systemd-udevd[2478035]: Could not generate persistent MAC address for veth17a672a: No such file or directory
Sep 23 23:11:32 sentry-docker00.cs.umd.edu systemd-udevd[2478038]: Could not generate persistent MAC address for vetheb8b51e: No such file or directory
Sep 23 23:11:32 sentry-docker00.cs.umd.edu systemd-udevd[2478055]: Could not generate persistent MAC address for veth858b007: No such file or directory
Sep 23 23:11:32 sentry-docker00.cs.umd.edu systemd-udevd[2478051]: Could not generate persistent MAC address for veth279214b: No such file or directory
Sep 23 23:11:32 sentry-docker00.cs.umd.edu systemd-udevd[2478061]: Could not generate persistent MAC address for veth8a5b50c: No such file or directory
Sep 23 23:11:32 sentry-docker00.cs.umd.edu systemd-udevd[2478062]: Could not generate persistent MAC address for veth21f559c: No such file or directory
Sep 23 23:11:32 sentry-docker00.cs.umd.edu systemd-udevd[2478080]: Could not generate persistent MAC address for vethc38a00d: No such file or directory
Sep 23 23:11:32 sentry-docker00.cs.umd.edu systemd-udevd[2478076]: Could not generate persistent MAC address for veth37177e9: No such file or directory
Sep 23 23:31:41 sentry-docker00.cs.umd.edu systemd-udevd[2487435]: link_config: could not get ethtool features for veth8a5b50c
Sep 23 23:31:41 sentry-docker00.cs.umd.edu systemd-udevd[2487435]: Could not set offload features of veth8a5b50c: No such device
Sep 23 23:31:41 sentry-docker00.cs.umd.edu systemd-udevd[2487468]: Could not generate persistent MAC address for veth74d3fcc: No such file or directory
Sep 23 23:31:41 sentry-docker00.cs.umd.edu systemd-udevd[2487469]: Could not generate persistent MAC address for veth3971789: No such file or directory
Sep 23 23:31:41 sentry-docker00.cs.umd.edu systemd-udevd[2487472]: Could not generate persistent MAC address for veth7d256ed: No such file or directory
Sep 23 23:31:41 sentry-docker00.cs.umd.edu systemd-udevd[2487473]: Could not generate persistent MAC address for veth2d893ae: No such file or directory
Sep 23 23:31:41 sentry-docker00.cs.umd.edu systemd-udevd[2487490]: Could not generate persistent MAC address for veth2375100: No such file or directory
Sep 23 23:31:41 sentry-docker00.cs.umd.edu systemd-udevd[2487476]: Could not generate persistent MAC address for veth1fcbc24: No such file or directory
Sep 23 23:31:41 sentry-docker00.cs.umd.edu systemd-udevd[2487483]: Could not generate persistent MAC address for vethdec2f95: No such file or directory
Sep 23 23:31:41 sentry-docker00.cs.umd.edu systemd-udevd[2487469]: Could not generate persistent MAC address for veth1cb0c34: No such file or directory
Sep 23 23:31:41 sentry-docker00.cs.umd.edu systemd-udevd[2487476]: Could not generate persistent MAC address for vethc8e1836: No such file or directory
Sep 23 23:31:41 sentry-docker00.cs.umd.edu systemd-udevd[2487490]: Could not generate persistent MAC address for veth27faaf0: No such file or directory
Sep 23 23:51:49 sentry-docker00.cs.umd.edu systemd-udevd[2496800]: link_config: could not get ethtool features for veth74d3fcc
Sep 23 23:51:49 sentry-docker00.cs.umd.edu systemd-udevd[2496800]: Could not set offload features of veth74d3fcc: No such device
Sep 23 23:51:49 sentry-docker00.cs.umd.edu systemd-udevd[2496832]: Could not generate persistent MAC address for vethe391aef: No such file or directory
Sep 23 23:51:49 sentry-docker00.cs.umd.edu systemd-udevd[2496833]: Could not generate persistent MAC address for veth15798ce: No such file or directory
Sep 23 23:51:49 sentry-docker00.cs.umd.edu systemd-udevd[2496846]: Could not generate persistent MAC address for vethb9afab5: No such file or directory
Sep 23 23:51:49 sentry-docker00.cs.umd.edu systemd-udevd[2496832]: Could not generate persistent MAC address for veth4ee58e7: No such file or directory
... 6 more distinct messages not shown
== soul (2 distinct, 2 total) ==
Sep 23 23:35:48 soul krb5_child[374726]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 23 23:37:03 soul sshd-session[374826]: error: Protocol major versions differ: 2 vs. 1
== strawberry (7 distinct, 38 total) ==
Sep 23 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 23 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 23 23:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 23 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 23 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 23 23:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 23 23:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 2 total) ==
Sep 23 23:13:37 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f3 (1 distinct, 1 total) ==
Sep 23 23:20:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 23 23:08:49 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== teaching-awards (1 distinct, 1 total) ==
Sep 23 23:09:25 teaching-awards krb5_child[1503259]: Preauthentication failed
== wraith (1 distinct, 1 total) ==
Sep 24 00:00:00 wraith (nin-node)[1018777]: 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.2693s
Status : exited 0
Output :
Syslog digest — 2026-09-23 23:05 EDT
Processed 13,766 lines, filtered 2,115 (15%). 11,651 unknown (377 distinct) from 25 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 22:57:39 b0b02.cs.umd.edu rustdesk[387907]: cannot open display:
== cheezit.cs.umd.edu (7 distinct, 9 total) ==
Sep 23 22:16:49 cheezit.cs.umd.edu sshd-session[2473850]: pam_access(sshd:auth): access denied for user `admin' from `34.52.146.136'
Sep 23 22:16:50 cheezit.cs.umd.edu krb5_child[2473854]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 23 22:16:50 cheezit.cs.umd.edu sshd-session[2473835]: error: PAM: System error for admin from 34.52.146.136
Sep 23 22:19:23 cheezit.cs.umd.edu sshd-session[2474044]: error: Protocol major versions differ: 2 vs. 1 [x2]
Sep 23 22:22:38 cheezit.cs.umd.edu sshd-session[2474945]: pam_access(sshd:auth): access denied for user `admin' from `34.79.195.43'
Sep 23 22:22:38 cheezit.cs.umd.edu sshd-session[2474943]: error: PAM: System error for admin from 34.79.195.43
Sep 23 22:56:20 cheezit.cs.umd.edu sshd-session[2483393]: pam_access(sshd:auth): access denied for user `leonidas' from `71.163.104.121'
== galax (1 distinct, 1 total) ==
Sep 23 22:48:38 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 1027 times, consider switching to WQ_UNBOUND
== idm00 (1 distinct, 1 total) ==
Sep 23 22:54:06 idm00 named[4166701]: client @0x7f11a4296188 10.73.240.42#64495: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 23 22:39:31 idmp0 named[1598691]: client @0x7f2d1c0184a8 10.73.240.43#53328: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 1 total) ==
Sep 23 22:23:53 itmon02 sshd[1483508]: error: beginning MaxStartups throttling
== krispykreme.cs.umd.edu (6 distinct, 7 total) ==
Sep 23 22:18:26 krispykreme.cs.umd.edu sshd-session[1799414]: pam_access(sshd:auth): access denied for user `admin' from `34.38.77.240'
Sep 23 22:18:26 krispykreme.cs.umd.edu krb5_child[1799416]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 23 22:18:26 krispykreme.cs.umd.edu sshd-session[1799412]: error: PAM: System error for admin from 34.38.77.240
Sep 23 22:27:10 krispykreme.cs.umd.edu sshd-session[1802360]: pam_access(sshd:auth): access denied for user `admin' from `35.205.166.50'
Sep 23 22:27:10 krispykreme.cs.umd.edu sshd-session[1802358]: error: PAM: System error for admin from 35.205.166.50
Sep 23 22:27:28 krispykreme.cs.umd.edu sshd-session[1802426]: error: Protocol major versions differ: 2 vs. 1
== lifepix (26 distinct, 34 total) ==
Sep 23 22:12:10 lifepix systemctl[10805]: Warning: The unit file, source configuration file or drop-ins of man-db-cache-update.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Sep 23 22:13:58 lifepix (lldpd)[16454]: lldpd.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
Sep 23 22:14:11 lifepix puppet-agent[9503]: 'puppet ssl submit_request --no-use_srv_records --server openvox08.cs.umd.edu --target postfix.lifepix.cs.umd.edu' returned 1 instead of one of [0]
Sep 23 22:14:11 lifepix puppet-agent[9503]: (/Stage[main]/Profile::Mail::Nullclient/Exec[request certs from puppet-CA]/returns) change from 'notrun' to ['0'] failed: 'puppet ssl submit_request --no-use_srv_records --server openvox08.cs.umd.edu --target postfix.lifepix.cs.umd.edu' returned 1 instead of one of [0]
Sep 23 22:14:12 lifepix puppet-agent[9503]: 'puppet ssl download_cert --no-use_srv_records --server openvox08.cs.umd.edu --target postfix.lifepix.cs.umd.edu' returned 1 instead of one of [0] [x2]
Sep 23 22:14:12 lifepix puppet-agent[9503]: (/Stage[main]/Profile::Mail::Nullclient/Exec[get certs from puppet-CA]/returns) change from 'notrun' to ['0'] failed: 'puppet ssl download_cert --no-use_srv_records --server openvox08.cs.umd.edu --target postfix.lifepix.cs.umd.edu' returned 1 instead of one of [0] (corrective) [x2]
Sep 23 22:15:21 lifepix falcon-sensor[20736]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 23 22:15:21 lifepix falcon-sensor[20736]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
Sep 23 22:15:21 lifepix falcon-sensor[20736]: CrowdStrike(4): Could not connect directly: c0000120
Sep 23 22:15:21 lifepix falcon-sensor[20736]: CrowdStrike(4): connect() failed: 65
Sep 23 22:15:21 lifepix falcon-sensor[20736]: CrowdStrike(4): Could not connect using DNS Fallback: c0000001
Sep 23 22:15:21 lifepix falcon-sensor[20736]: CrowdStrike(4): Unable to connect to ts01-lanner-lion.cloudsink.net:443
Sep 23 22:15:21 lifepix falcon-sensor[20736]: CrowdStrike(4): Connection to cloud failed (0 tries): 0xc0000001
Sep 23 22:15:28 lifepix falcon-sensor-bpf[20736]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 [x3]
Sep 23 22:15:28 lifepix falcon-sensor-bpf[20736]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 [x3]
Sep 23 22:15:29 lifepix falcon-sensor-bpf[20736]: CrowdStrike(4): Sensor is Redirected to CloudId:6 RedirectReason:1
Sep 23 22:15:29 lifepix falcon-sensor-bpf[20736]: CrowdStrike(4): SSLSocket Disconnected from Cloud.
Sep 23 22:17:28 lifepix puppet-agent[9503]: Cannot create /var/lib/photos/.config/containers/systemd; parent directory /var/lib/photos/.config/containers does not exist
Sep 23 22:17:28 lifepix puppet-agent[9503]: (/Stage[main]/Profile::Photos_server::Containers/File[/var/lib/photos/.config/containers/systemd]/ensure) change from 'absent' to 'directory' failed: Cannot create /var/lib/photos/.config/containers/systemd; parent directory /var/lib/photos/.config/containers does not exist
Sep 23 22:17:28 lifepix puppet-agent[9503]: (/Stage[main]/Profile::Photos_server::Containers/File[/var/lib/photos/.config/containers/systemd/photos.network]) Skipping because of failed dependencies
Sep 23 22:17:28 lifepix puppet-agent[9503]: (/Stage[main]/Profile::Photos_server::Containers/File[/var/lib/photos/.config/containers/systemd/photos-db.container]) Skipping because of failed dependencies
Sep 23 22:17:28 lifepix puppet-agent[9503]: (/Stage[main]/Profile::Photos_server::Containers/File[/var/lib/photos/.config/containers/systemd/photos-app.container]) Skipping because of failed dependencies
Sep 23 22:17:28 lifepix puppet-agent[9503]: (/Stage[main]/Profile::Photos_server::Containers/Exec[validate-photos-quadlets]) Skipping because of failed dependencies
Sep 23 22:17:28 lifepix puppet-agent[9503]: (/Stage[main]/Profile::Photos_server::Containers/Exec[systemctl-user-daemon-reload-photos]) Skipping because of failed dependencies
Sep 23 22:17:30 lifepix systemd[1]: resmon.service: Supervising process 23160 which is not our child. We'll most likely not notice when it exits.
Sep 23 22:17:32 lifepix (httpd)[23374]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS [x3]
== mcstic (1 distinct, 14 total) ==
Sep 23 22:24:20 mcstic krb5_child[1024091]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x14]
== munin (2 distinct, 4 total) ==
Sep 23 22:48:52 munin sudo[2587587]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 23 22:48:52 munin sudo[2587587]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== netman.cs.umd.edu (1 distinct, 30 total) ==
Sep 23 22:24:09 netman.cs.umd.edu krb5_child[4153511]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x30]
== newhonors.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 23:01:41 newhonors.cs.umd.edu systemd-tmpfiles: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
== newhonors2 (1 distinct, 24 total) ==
Sep 23 22:13:03 newhonors2 dhcpcd[3059899]: dhcpcd is not running [x24]
== ntop00 (256 distinct, 11374 total) ==
Sep 23 22:08:01 ntop00 sfacctd[86030]: INFO ( p1/print ): *** Purging cache - START (PID: 27) ***
Sep 23 22:08:01 ntop00 sfacctd[86030]: INFO ( p1/print ): *** Purging cache - END (PID: 27, QN: 8461/8461, ET: 0) ***
Sep 23 22:08:01 ntop00 nfacctd[86241]: INFO ( p1/print ): *** Purging cache - START (PID: 27) ***
Sep 23 22:08:01 ntop00 nfacctd[86241]: INFO ( p1/print ): *** Purging cache - END (PID: 27, QN: 60/60, ET: 0) ***
Sep 23 22:08:52 ntop00 sfacctd[86030]: INFO ( m1/mysql ): *** Purging cache - END (PID: 18, QN: 7939/7939, ET: 1431) ***
Sep 23 22:08:53 ntop00 nfacctd[86241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 18, QN: 59/59, ET: 1432) ***
Sep 23 22:08:54 ntop00 nfacctd[86241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 20, QN: 53/53, ET: 1133) ***
Sep 23 22:10:01 ntop00 sfacctd[86030]: INFO ( m1/mysql ): *** Purging cache - START (PID: 28) ***
Sep 23 22:10:01 ntop00 nfacctd[86241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 28) ***
Sep 23 22:13:01 ntop00 sfacctd[86030]: INFO ( p1/print ): *** Purging cache - START (PID: 29) ***
Sep 23 22:13:01 ntop00 sfacctd[86030]: INFO ( p1/print ): *** Purging cache - END (PID: 29, QN: 8614/8614, ET: 0) ***
Sep 23 22:13:01 ntop00 nfacctd[86241]: INFO ( p1/print ): *** Purging cache - START (PID: 29) ***
Sep 23 22:13:01 ntop00 nfacctd[86241]: INFO ( p1/print ): *** Purging cache - END (PID: 29, QN: 59/59, ET: 0) ***
Sep 23 22:15:01 ntop00 sfacctd[86030]: INFO ( m1/mysql ): *** Purging cache - START (PID: 30) ***
Sep 23 22:15:01 ntop00 sfacctd[86030]: INFO ( m1/mysql ): *** Purging cache - END (PID: 20, QN: 8965/8965, ET: 1500) ***
Sep 23 22:15:01 ntop00 nfacctd[86241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 30) ***
Sep 23 22:17:16 ntop00 sfacctd[86030]: INFO ( p1/print ): *** Purging cache - START (PID: 2) *** [x2]
Sep 23 22:17:16 ntop00 sfacctd[86030]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3) *** [x2]
Sep 23 22:17:16 ntop00 sfacctd[86030]: INFO ( p1/print ): *** Purging cache - END (PID: 2, QN: 7621/7621, ET: 0) ***
Sep 23 22:17:16 ntop00 sfacctd[86030]: INFO ( default/core ): OK, Exiting ... [x2]
Sep 23 22:17:16 ntop00 pmacct-mariadb[89591]: 2026-09-24 2:17:16 17 [Warning] Aborted connection 17 to db: 'pmacct' user: 'pmacct_writer' host: '127.0.0.1' (Got an error reading communication packets)
Sep 23 22:17:17 ntop00 pmacct-mariadb[89591]: 2026-09-24 2:17:17 25 [Warning] Aborted connection 25 to db: 'pmacct' user: 'pmacct_writer' host: '127.0.0.1' (Got timeout reading communication packets)
Sep 23 22:17:17 ntop00 pmacct-mariadb[89591]: 2026-09-24 2:17:17 27 [Warning] Aborted connection 27 to db: 'pmacct' user: 'pmacct_writer' host: '127.0.0.1' (Got timeout reading communication packets)
Sep 23 22:17:17 ntop00 pmacct-mariadb[89591]: 2026-09-24 2:17:17 21 [Warning] Aborted connection 21 to db: 'pmacct' user: 'pmacct_writer' host: '127.0.0.1' (Got timeout reading communication packets)
Sep 23 22:17:17 ntop00 pmacct-mariadb[89591]: 2026-09-24 2:17:17 29 [Warning] Aborted connection 29 to db: 'pmacct' user: 'pmacct_writer' host: '127.0.0.1' (Got an error reading communication packets)
Sep 23 22:17:17 ntop00 pmacct-mariadb[89591]: 2026-09-24 2:17:17 23 [Warning] Aborted connection 23 to db: 'pmacct' user: 'pmacct_writer' host: '127.0.0.1' (Got timeout reading communication packets)
Sep 23 22:17:18 ntop00 sfacctd[99997]: INFO ( default/core ): sFlow Accounting Daemon, sfacctd 1.7.9-git (20240801-0 (32fd57eb)) [x2]
Sep 23 22:17:18 ntop00 sfacctd[99997]: INFO ( default/core ): '--enable-mysql' '--enable-pgsql' '--enable-sqlite3' '--enable-kafka' '--enable-geoipv2' '--enable-jansson' '--enable-rabbitmq' '--enable-nflog' '--enable-ndpi' '--enable-zmq' '--enable-avro' '--enable-serdes' '--enable-redis' '--enable-gnutls' 'AVRO_CFLAGS=-I/usr/local/avro/include' 'AVRO_LIBS=-L/usr/local/avro/lib -lavro' '--enable-l2' '--enable-traffic-bins' '--enable-bgp-bins' '--enable-bmp-bins' '--enable-st-bins' [x2]
Sep 23 22:17:18 ntop00 sfacctd[99997]: INFO ( default/core ): Reading configuration file '/etc/pmacct/sfacctd.conf'. [x2]
Sep 23 22:17:18 ntop00 sfacctd[99997]: INFO ( p1/print ): cache entries=16411 base cache memory=72208400 bytes [x2]
... 226 more distinct messages not shown
== outbound00.cs.umd.edu (3 distinct, 23 total) ==
Sep 23 22:09:09 outbound00.cs.umd.edu python3[3222161]: ldapdb [x6]
Sep 23 22:21:29 outbound00.cs.umd.edu krb5_child[3225021]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x16]
Sep 23 22:24:51 outbound00.cs.umd.edu sshd-session[3225409]: error: Protocol major versions differ: 2 vs. 1
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 23 22:13:07 outbound01.cs.umd.edu python3[1288350]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (32 distinct, 32 total) ==
Sep 23 22:11:07 sentry-docker00.cs.umd.edu systemd-udevd[2449735]: Could not generate persistent MAC address for veth7df3d60: No such file or directory
Sep 23 22:11:07 sentry-docker00.cs.umd.edu systemd-udevd[2449734]: Could not generate persistent MAC address for vethfccb90e: No such file or directory
Sep 23 22:11:07 sentry-docker00.cs.umd.edu systemd-udevd[2449760]: Could not generate persistent MAC address for veth17c4db1: No such file or directory
Sep 23 22:11:07 sentry-docker00.cs.umd.edu systemd-udevd[2449761]: Could not generate persistent MAC address for veth30fce75: No such file or directory
Sep 23 22:11:07 sentry-docker00.cs.umd.edu systemd-udevd[2449779]: Could not generate persistent MAC address for veth5084aff: No such file or directory
Sep 23 22:11:07 sentry-docker00.cs.umd.edu systemd-udevd[2449785]: Could not generate persistent MAC address for veth89ff487: No such file or directory
Sep 23 22:11:07 sentry-docker00.cs.umd.edu systemd-udevd[2449788]: Could not generate persistent MAC address for veth8373089: No such file or directory
Sep 23 22:11:07 sentry-docker00.cs.umd.edu systemd-udevd[2449790]: Could not generate persistent MAC address for veth4e3f9e9: No such file or directory
Sep 23 22:11:07 sentry-docker00.cs.umd.edu systemd-udevd[2449847]: Could not generate persistent MAC address for vethe33b773: No such file or directory
Sep 23 22:11:07 sentry-docker00.cs.umd.edu systemd-udevd[2449854]: Could not generate persistent MAC address for veth9d542b0: No such file or directory
Sep 23 22:31:16 sentry-docker00.cs.umd.edu systemd-udevd[2459162]: link_config: could not get ethtool features for vethfccb90e
Sep 23 22:31:16 sentry-docker00.cs.umd.edu systemd-udevd[2459162]: Could not set offload features of vethfccb90e: No such device
Sep 23 22:31:16 sentry-docker00.cs.umd.edu systemd-udevd[2459197]: Could not generate persistent MAC address for veth502774d: No such file or directory
Sep 23 22:31:16 sentry-docker00.cs.umd.edu systemd-udevd[2459198]: Could not generate persistent MAC address for vethb2e38ca: No such file or directory
Sep 23 22:31:16 sentry-docker00.cs.umd.edu systemd-udevd[2459201]: Could not generate persistent MAC address for vethdb59027: No such file or directory
Sep 23 22:31:16 sentry-docker00.cs.umd.edu systemd-udevd[2459202]: Could not generate persistent MAC address for vethee67b89: No such file or directory
Sep 23 22:31:16 sentry-docker00.cs.umd.edu systemd-udevd[2459205]: Could not generate persistent MAC address for veth4558043: No such file or directory
Sep 23 22:31:16 sentry-docker00.cs.umd.edu systemd-udevd[2459215]: Could not generate persistent MAC address for veth1ce98c4: No such file or directory
Sep 23 22:31:16 sentry-docker00.cs.umd.edu systemd-udevd[2459210]: Could not generate persistent MAC address for veth85fa568: No such file or directory
Sep 23 22:31:16 sentry-docker00.cs.umd.edu systemd-udevd[2459215]: Could not generate persistent MAC address for vethfe7f228: No such file or directory
Sep 23 22:31:16 sentry-docker00.cs.umd.edu systemd-udevd[2459305]: Could not generate persistent MAC address for veth0a42770: No such file or directory
Sep 23 22:31:16 sentry-docker00.cs.umd.edu systemd-udevd[2459311]: Could not generate persistent MAC address for veth9b0d31f: No such file or directory
Sep 23 22:51:24 sentry-docker00.cs.umd.edu systemd-udevd[2468627]: Could not generate persistent MAC address for vethd1c2154: No such file or directory
Sep 23 22:51:24 sentry-docker00.cs.umd.edu systemd-udevd[2468628]: Could not generate persistent MAC address for veth171f669: No such file or directory
Sep 23 22:51:24 sentry-docker00.cs.umd.edu systemd-udevd[2468646]: Could not generate persistent MAC address for veth2c58a82: No such file or directory
Sep 23 22:51:24 sentry-docker00.cs.umd.edu systemd-udevd[2468643]: Could not generate persistent MAC address for veth3ee7290: No such file or directory
Sep 23 22:51:24 sentry-docker00.cs.umd.edu systemd-udevd[2468643]: Could not generate persistent MAC address for veth7b8baab: No such file or directory
Sep 23 22:51:24 sentry-docker00.cs.umd.edu systemd-udevd[2468642]: Could not generate persistent MAC address for vethdadab5a: No such file or directory
Sep 23 22:51:24 sentry-docker00.cs.umd.edu systemd-udevd[2468657]: Could not generate persistent MAC address for veth3e819eb: No such file or directory
Sep 23 22:51:24 sentry-docker00.cs.umd.edu systemd-udevd[2468658]: Could not generate persistent MAC address for veth4d6a0ce: No such file or directory
... 2 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 23 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 23 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 23 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 23 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 23 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 23 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 23 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (10 distinct, 13 total) ==
Sep 23 22:13:08 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
Sep 23 22:25:55 submit26-b9-f1 setroubleshoot[3241581]: 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 23 22:25:55 submit26-b9-f1 setroubleshoot[3241581]: 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 23 22:25:55 submit26-b9-f1 setroubleshoot[3241581]: 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 23 22:25:55 submit26-b9-f1 setroubleshoot[3241581]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.gzoS9w/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 23 22:25:55 submit26-b9-f1 setroubleshoot[3241581]: 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 23 22:25:55 submit26-b9-f1 setroubleshoot[3241581]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.gzoS9w. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 23 22:25:55 submit26-b9-f1 setroubleshoot[3241581]: 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 23 22:25:55 submit26-b9-f1 setroubleshoot[3241581]: 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 23 22:25:55 submit26-b9-f1 setroubleshoot[3241581]: 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, 16 total) ==
Sep 23 22:06:50 submit26-b9-f2 setroubleshoot[2337503]: 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 23 22:06:50 submit26-b9-f2 setroubleshoot[2337503]: 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 23 22:06:50 submit26-b9-f2 setroubleshoot[2337503]: 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 23 22:06:50 submit26-b9-f2 setroubleshoot[2337503]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Up9xzW/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2]
Sep 23 22:06:50 submit26-b9-f2 setroubleshoot[2337503]: 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 23 22:06:50 submit26-b9-f2 setroubleshoot[2337503]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Up9xzW. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 23 22:06:50 submit26-b9-f2 setroubleshoot[2337503]: 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 23 22:06:50 submit26-b9-f2 setroubleshoot[2337503]: 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 23 22:06:50 submit26-b9-f2 setroubleshoot[2337503]: 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 23 22:08:08 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f3 (1 distinct, 3 total) ==
Sep 23 22:20:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f4 (1 distinct, 5 total) ==
Sep 23 22:13:11 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== teaching-awards (1 distinct, 8 total) ==
Sep 23 22:24:32 teaching-awards krb5_child[1500690]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x8]
== tma-0 (1 distinct, 1 total) ==
Sep 23 22:31:18 tma-0 sshd[13824]: error: PAM: Authentication failure for admin from 20.71.62.34.bc.googleusercontent.com
== vacuum.cs.umd.edu (4 distinct, 4 total) ==
Sep 23 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[22999]: Process 18573 (driver) of user 33 killed by SIGSEGV - dumping core
Sep 23 22:11:58 vacuum.cs.umd.edu abrt-server[23001]: Package 'amanda-backup_server' isn't signed with proper key
Sep 23 22:11:58 vacuum.cs.umd.edu abrt-server[23001]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-23-22:11:58-18573' exited with 1
Sep 23 22:11:58 vacuum.cs.umd.edu abrt-server[23001]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-23-22:11:58-18573'
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0488s
Status : exited 0
Output :
Syslog digest — 2026-09-23 22:05 EDT
Processed 2,188 lines, filtered 1,805 (82%). 383 unknown (260 distinct) from 27 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 21:57:35 b0b02.cs.umd.edu rustdesk[372704]: cannot open display:
== bale (5 distinct, 7 total) ==
Sep 23 21:05:16 bale setroubleshoot[2233022]: failed to retrieve rpm info for /dev/nvme0 [x3]
Sep 23 21:05:17 bale setroubleshoot[2233022]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee
Sep 23 21:05:19 bale setroubleshoot[2233022]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9
Sep 23 21:05:22 bale setroubleshoot[2233022]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6
Sep 23 21:05:34 bale setroubleshoot[2233637]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d
== bigtuna (3 distinct, 3 total) ==
Sep 23 21:31:55 bigtuna sshd-session[2831883]: error: Certificate does not contain an authorized principal
Sep 23 21:32:03 bigtuna krb5_child[2831895]: Preauthentication failed
Sep 23 21:56:32 bigtuna sshd-session[2833942]: error: connect_to 128.8.129.113 port 22: failed.
== galax (1 distinct, 1 total) ==
Sep 23 21:16:18 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 515 times, consider switching to WQ_UNBOUND
== idm00 (1 distinct, 1 total) ==
Sep 23 21:54:05 idm00 named[4166701]: client @0x7f11a00383f8 10.73.240.42#55520: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 23 21:39:30 idmp0 named[1598691]: client @0x7f2d2401b378 10.73.240.43#57797: update '73.10.in-addr.arpa/IN' denied
== inbound01.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 21:19:04 inbound01.cs.umd.edu krb5_child[1372895]: Preauthentication failed
== irb2156 (2 distinct, 2 total) ==
Sep 23 22:01:24 irb2156 falcon-sensor-bpf[3728]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 23 22:01:24 irb2156 falcon-sensor-bpf[3728]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== itmon02 (1 distinct, 5 total) ==
Sep 23 21:08:46 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5]
== kadath.cs.umd.edu (2 distinct, 2 total) ==
Sep 23 21:43:35 kadath.cs.umd.edu falcon-sensor-bpf[938]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 23 21:43:35 kadath.cs.umd.edu falcon-sensor-bpf[938]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== krispykreme.cs.umd.edu (1 distinct, 4 total) ==
Sep 23 21:46:33 krispykreme.cs.umd.edu sshd-session[1790787]: error: send_error: write: Connection reset by peer [x4]
== mcstic (1 distinct, 10 total) ==
Sep 23 21:45:15 mcstic krb5_child[1022982]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x10]
== munin (2 distinct, 4 total) ==
Sep 23 21:38:09 munin sudo[2561453]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 23 21:38:09 munin sudo[2561453]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== netman.cs.umd.edu (1 distinct, 12 total) ==
Sep 23 21:43:11 netman.cs.umd.edu krb5_child[4142372]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x12]
== newhonors2 (1 distinct, 24 total) ==
Sep 23 21:13:02 newhonors2 dhcpcd[3058043]: dhcpcd is not running [x24]
== ntop00 (163 distinct, 164 total) ==
Sep 23 21:05:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 206) ***
Sep 23 21:07:04 ntop00 pmacct-mariadb[5571]: 2026-09-24 1:07:04 253 [Warning] Aborted connection 253 to db: 'pmacct' user: 'grafana_reader' host: '10.73.246.25' (Got an error reading communication packets)
Sep 23 21:07:58 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 2) ***
Sep 23 21:07:58 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3) ***
Sep 23 21:07:58 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 2, QN: 6709/6709, ET: 0) ***
Sep 23 21:07:58 ntop00 sfacctd[9573]: INFO ( default/core ): OK, Exiting ...
Sep 23 21:07:58 ntop00 pmacct-mariadb[5571]: 2026-09-24 1:07:58 256 [Warning] Aborted connection 256 to db: 'pmacct' user: 'pmacct_writer' host: '127.0.0.1' (Got an error reading communication packets)
Sep 23 21:07:59 ntop00 pmacct-mariadb[5571]: 2026-09-24 1:07:59 260 [Warning] Aborted connection 260 to db: 'pmacct' user: 'pmacct_writer' host: '127.0.0.1' (Got an error reading communication packets)
Sep 23 21:08:00 ntop00 setroubleshoot[85939]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 5b65c96c-a9fa-4175-8126-0641b1ec385c
Sep 23 21:08:00 ntop00 setroubleshoot[85939]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 0d1f7214-3aae-48d5-8fed-48565bd90d17
Sep 23 21:08:00 ntop00 setroubleshoot[85939]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json':
Sep 23 21:08:00 ntop00 setroubleshoot[85939]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 4a9c8c49-4f0d-4ad5-b926-84fe3642d3ee
Sep 23 21:08:00 ntop00 sfacctd[86030]: INFO ( default/core ): sFlow Accounting Daemon, sfacctd 1.7.9-git (20240801-0 (32fd57eb))
Sep 23 21:08:00 ntop00 sfacctd[86030]: INFO ( default/core ): '--enable-mysql' '--enable-pgsql' '--enable-sqlite3' '--enable-kafka' '--enable-geoipv2' '--enable-jansson' '--enable-rabbitmq' '--enable-nflog' '--enable-ndpi' '--enable-zmq' '--enable-avro' '--enable-serdes' '--enable-redis' '--enable-gnutls' 'AVRO_CFLAGS=-I/usr/local/avro/include' 'AVRO_LIBS=-L/usr/local/avro/lib -lavro' '--enable-l2' '--enable-traffic-bins' '--enable-bgp-bins' '--enable-bmp-bins' '--enable-st-bins'
Sep 23 21:08:00 ntop00 sfacctd[86030]: INFO ( default/core ): Reading configuration file '/etc/pmacct/sfacctd.conf'.
Sep 23 21:08:00 ntop00 sfacctd[86030]: INFO ( p1/print ): cache entries=16411 base cache memory=72208400 bytes
Sep 23 21:08:00 ntop00 sfacctd[86030]: INFO ( default/core ): waiting for sFlow data on interface=all ip=:: port=6343/udp
Sep 23 21:08:00 ntop00 sfacctd[86030]: INFO ( m1/mysql ): sql_table_type set to 'bgp' (aggregate includes one or more BGP primitives).
Sep 23 21:08:00 ntop00 sfacctd[86030]: INFO ( m1/mysql ): cache entries=32771 base cache memory=14899240 bytes
Sep 23 21:08:00 ntop00 sfacctd[86030]: INFO ( p1/print ): JSON: setting object handlers.
Sep 23 21:08:00 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 206, QN: 55/55, ET: 179) ***
Sep 23 21:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 207) ***
Sep 23 21:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 207, QN: 61/61, ET: 0) ***
Sep 23 21:08:12 ntop00 nfacctd[86241]: INFO ( default/core ): NetFlow Accounting Daemon, nfacctd 1.7.9-git (20240801-0 (32fd57eb))
Sep 23 21:08:12 ntop00 nfacctd[86241]: INFO ( default/core ): '--enable-mysql' '--enable-pgsql' '--enable-sqlite3' '--enable-kafka' '--enable-geoipv2' '--enable-jansson' '--enable-rabbitmq' '--enable-nflog' '--enable-ndpi' '--enable-zmq' '--enable-avro' '--enable-serdes' '--enable-redis' '--enable-gnutls' 'AVRO_CFLAGS=-I/usr/local/avro/include' 'AVRO_LIBS=-L/usr/local/avro/lib -lavro' '--enable-l2' '--enable-traffic-bins' '--enable-bgp-bins' '--enable-bmp-bins' '--enable-st-bins'
Sep 23 21:08:12 ntop00 nfacctd[86241]: INFO ( default/core ): Reading configuration file '/etc/pmacct/nfacctd.conf'.
Sep 23 21:08:12 ntop00 nfacctd[86241]: INFO ( p1/print ): cache entries=16411 base cache memory=72208400 bytes
Sep 23 21:08:12 ntop00 nfacctd[86241]: INFO ( default/core ): waiting for NetFlow/IPFIX data on interface=all ip=:: port=2055/udp
Sep 23 21:08:12 ntop00 nfacctd[86241]: INFO ( m1/mysql ): sql_table_type set to 'bgp' (aggregate includes one or more BGP primitives).
Sep 23 21:08:12 ntop00 nfacctd[86241]: INFO ( m1/mysql ): cache entries=32771 base cache memory=14899240 bytes
... 133 more distinct messages not shown
== openvox08-cmp0 (2 distinct, 2 total) ==
Sep 23 21:40:32 openvox08-cmp0 setroubleshoot[3425972]: failed to retrieve rpm info for path '/dev/pts/1':
Sep 23 21:40:33 openvox08-cmp0 setroubleshoot[3425972]: SELinux is preventing /usr/bin/who from getattr access on the chr_file /dev/pts/1. For complete SELinux messages run: sealert -l 3339fa05-becf-48e4-be60-ae2e0c9ae2fb
== outbound00.cs.umd.edu (2 distinct, 12 total) ==
Sep 23 21:09:09 outbound00.cs.umd.edu python3[3208032]: ldapdb [x6]
Sep 23 21:43:09 outbound00.cs.umd.edu krb5_child[3215946]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 23 21:13:07 outbound01.cs.umd.edu python3[1274178]: ldapdb [x6]
== quiss (1 distinct, 1 total) ==
Sep 23 21:31:37 quiss sshd-session[2218608]: error: Certificate does not contain an authorized principal
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 23 21:10:42 sentry-docker00.cs.umd.edu systemd-udevd[2420999]: link_config: could not get ethtool features for veth9d6b363
Sep 23 21:10:42 sentry-docker00.cs.umd.edu systemd-udevd[2420999]: Could not set offload features of veth9d6b363: No such device
Sep 23 21:10:43 sentry-docker00.cs.umd.edu systemd-udevd[2421032]: Could not generate persistent MAC address for veth6796391: No such file or directory
Sep 23 21:10:43 sentry-docker00.cs.umd.edu systemd-udevd[2421033]: Could not generate persistent MAC address for veth5ac70b2: No such file or directory
Sep 23 21:10:43 sentry-docker00.cs.umd.edu systemd-udevd[2421036]: Could not generate persistent MAC address for veth6179a7f: No such file or directory
Sep 23 21:10:43 sentry-docker00.cs.umd.edu systemd-udevd[2421037]: Could not generate persistent MAC address for vethc3ac1bf: No such file or directory
Sep 23 21:10:43 sentry-docker00.cs.umd.edu systemd-udevd[2421050]: Could not generate persistent MAC address for vethfc93993: No such file or directory
Sep 23 21:10:43 sentry-docker00.cs.umd.edu systemd-udevd[2421052]: Could not generate persistent MAC address for vethff6cb93: No such file or directory
Sep 23 21:10:43 sentry-docker00.cs.umd.edu systemd-udevd[2421062]: Could not generate persistent MAC address for vetha9c04d8: No such file or directory
Sep 23 21:10:43 sentry-docker00.cs.umd.edu systemd-udevd[2421063]: Could not generate persistent MAC address for veth001ba83: No such file or directory
Sep 23 21:10:43 sentry-docker00.cs.umd.edu systemd-udevd[2421068]: Could not generate persistent MAC address for vethc7016cd: No such file or directory
Sep 23 21:10:43 sentry-docker00.cs.umd.edu systemd-udevd[2421071]: Could not generate persistent MAC address for vethb70b338: No such file or directory
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430864]: link_config: could not get ethtool features for vethb70b338
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430864]: Could not set offload features of vethb70b338: No such device
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430870]: link_config: could not get ethtool features for veth6796391
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430870]: Could not set offload features of veth6796391: No such device
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430919]: Could not generate persistent MAC address for vethbd44af2: No such file or directory
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430921]: Could not generate persistent MAC address for veth0b82d85: No such file or directory
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430935]: Could not generate persistent MAC address for veth2a5c401: No such file or directory
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430938]: Could not generate persistent MAC address for veth41f18b7: No such file or directory
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430963]: Could not generate persistent MAC address for veth0a0eb1c: No such file or directory
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430964]: Could not generate persistent MAC address for veth4f34df3: No such file or directory
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430979]: Could not generate persistent MAC address for vethe32d5ee: No such file or directory
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430978]: Could not generate persistent MAC address for veth53556f2: No such file or directory
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430975]: Could not generate persistent MAC address for vethfaa2407: No such file or directory
Sep 23 21:30:51 sentry-docker00.cs.umd.edu systemd-udevd[2430976]: Could not generate persistent MAC address for veth5e74d6b: No such file or directory
Sep 23 21:50:59 sentry-docker00.cs.umd.edu systemd-udevd[2440317]: Could not generate persistent MAC address for veth2664d39: No such file or directory
Sep 23 21:50:59 sentry-docker00.cs.umd.edu systemd-udevd[2440318]: Could not generate persistent MAC address for veth0744744: No such file or directory
Sep 23 21:50:59 sentry-docker00.cs.umd.edu systemd-udevd[2440336]: Could not generate persistent MAC address for veth0a165cc: No such file or directory
Sep 23 21:50:59 sentry-docker00.cs.umd.edu systemd-udevd[2440325]: Could not generate persistent MAC address for veth8e5abfd: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 23 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 23 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 23 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 23 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 23 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 23 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 23 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 3 total) ==
Sep 23 21:18:24 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f2 (1 distinct, 6 total) ==
Sep 23 21:11:36 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f3 (11 distinct, 20 total) ==
Sep 23 21:06:45 submit26-b9-f3 setroubleshoot[2866879]: 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 23 21:06:45 submit26-b9-f3 setroubleshoot[2866879]: 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 23 21:06:45 submit26-b9-f3 setroubleshoot[2866879]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033 [x2]
Sep 23 21:06:45 submit26-b9-f3 setroubleshoot[2866879]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.R9aY2f/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 23 21:06:45 submit26-b9-f3 setroubleshoot[2866879]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba [x2]
Sep 23 21:06:45 submit26-b9-f3 setroubleshoot[2866879]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.R9aY2f. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 23 21:06:45 submit26-b9-f3 setroubleshoot[2866879]: 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 23 21:06:45 submit26-b9-f3 setroubleshoot[2866879]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65 [x2]
Sep 23 21:06:45 submit26-b9-f3 setroubleshoot[2866879]: 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 23 21:06:45 submit26-b9-f3 setroubleshoot[2866879]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.PZskZf/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 23 21:12:17 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
== submit26-b9-f4 (10 distinct, 12 total) ==
Sep 23 21:05:48 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
Sep 23 21:24:47 submit26-b9-f4 setroubleshoot[2107564]: 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 23 21:24:47 submit26-b9-f4 setroubleshoot[2107564]: 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 23 21:24:47 submit26-b9-f4 setroubleshoot[2107564]: 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 23 21:24:47 submit26-b9-f4 setroubleshoot[2107564]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.rVKUW3/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 23 21:24:47 submit26-b9-f4 setroubleshoot[2107564]: 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 23 21:24:47 submit26-b9-f4 setroubleshoot[2107564]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.rVKUW3. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 23 21:24:47 submit26-b9-f4 setroubleshoot[2107564]: 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 23 21:24:47 submit26-b9-f4 setroubleshoot[2107564]: 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 23 21:24:47 submit26-b9-f4 setroubleshoot[2107564]: 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
== teaching-awards (1 distinct, 5 total) ==
Sep 23 21:45:25 teaching-awards krb5_child[1498299]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x5]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0513s
Status : exited 0
Output :
Syslog digest — 2026-09-23 21:05 EDT
Processed 2,423 lines, filtered 2,007 (82%). 416 unknown (184 distinct) from 21 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 20:57:31 b0b02.cs.umd.edu rustdesk[357466]: cannot open display:
== bale (5 distinct, 90 total) ==
Sep 23 20:05:46 bale setroubleshoot[2220254]: failed to retrieve rpm info for /dev/nvme0 [x39]
Sep 23 20:05:46 bale setroubleshoot[2220254]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12]
Sep 23 20:05:49 bale setroubleshoot[2220254]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12]
Sep 23 20:05:52 bale setroubleshoot[2220254]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12]
Sep 23 20:06:04 bale setroubleshoot[2220869]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x15]
== cheezit.cs.umd.edu (2 distinct, 6 total) ==
Sep 23 20:15:31 cheezit.cs.umd.edu sshd-session[2445993]: error: send_error: write: Connection reset by peer [x4]
Sep 23 20:25:41 cheezit.cs.umd.edu sshd-session[2448702]: pam_access(sshd:auth): access denied for user `anwar' from `71.241.227.222' [x2]
== galax (2 distinct, 2 total) ==
Sep 23 20:07:03 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 131 times, consider switching to WQ_UNBOUND
Sep 23 20:30:08 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 259 times, consider switching to WQ_UNBOUND
== gle-dind04 (1 distinct, 1 total) ==
Sep 23 20:37:47 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): SSLSocket Disconnected from Cloud.
== idm00 (1 distinct, 1 total) ==
Sep 23 20:54:05 idm00 named[4166701]: client @0x7f1198099188 10.73.240.42#57989: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 23 20:39:31 idmp0 named[1598691]: client @0x7f2d2c0368e8 10.73.240.43#60769: update '73.10.in-addr.arpa/IN' denied
== inbound01.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 20:10:08 inbound01.cs.umd.edu krb5_child[1356890]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 5 total) ==
Sep 23 20:23:29 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5]
== munin (2 distinct, 18 total) ==
Sep 23 20:08:09 munin sudo[2529181]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x9]
Sep 23 20:08:09 munin sudo[2529181]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x9]
== newhonors2 (1 distinct, 24 total) ==
Sep 23 20:13:03 newhonors2 dhcpcd[3056214]: dhcpcd is not running [x24]
== ntop00 (102 distinct, 142 total) ==
Sep 23 20:05:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 182) ***
Sep 23 20:06:44 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 182, QN: 6387/6387, ET: 103) ***
Sep 23 20:06:46 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 182, QN: 53/53, ET: 105) ***
Sep 23 20:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 183) ***
Sep 23 20:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 183, QN: 6685/6685, ET: 0) ***
Sep 23 20:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 183) ***
Sep 23 20:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 183, QN: 60/60, ET: 0) ***
Sep 23 20:08:02 ntop00 setroubleshoot[75918]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 5b65c96c-a9fa-4175-8126-0641b1ec385c [x11]
Sep 23 20:08:02 ntop00 setroubleshoot[75918]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 0d1f7214-3aae-48d5-8fed-48565bd90d17 [x11]
Sep 23 20:08:02 ntop00 setroubleshoot[75918]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11]
Sep 23 20:08:02 ntop00 setroubleshoot[75918]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 4a9c8c49-4f0d-4ad5-b926-84fe3642d3ee [x11]
Sep 23 20:10:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 184) ***
Sep 23 20:10:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 184) ***
Sep 23 20:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 185) ***
Sep 23 20:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 185, QN: 6639/6639, ET: 0) ***
Sep 23 20:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 185) ***
Sep 23 20:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 185, QN: 43/43, ET: 0) ***
Sep 23 20:13:09 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 184, QN: 6803/6803, ET: 188) ***
Sep 23 20:13:10 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 184, QN: 46/46, ET: 189) ***
Sep 23 20:15:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 186) ***
Sep 23 20:15:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 186) ***
Sep 23 20:17:10 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 186, QN: 5998/5998, ET: 129) ***
Sep 23 20:17:10 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 186, QN: 52/52, ET: 129) ***
Sep 23 20:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 187) ***
Sep 23 20:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 187, QN: 6367/6367, ET: 0) ***
Sep 23 20:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 187) ***
Sep 23 20:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 187, QN: 49/49, ET: 0) ***
Sep 23 20:20:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 188) ***
Sep 23 20:20:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 188) ***
Sep 23 20:21:34 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 188, QN: 7068/7068, ET: 93) ***
... 72 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 23 20:09:09 outbound00.cs.umd.edu python3[3194091]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 23 20:13:06 outbound01.cs.umd.edu python3[1260139]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 23 20:10:17 sentry-docker00.cs.umd.edu systemd-udevd[2392632]: link_config: could not get ethtool features for veth98e8871
Sep 23 20:10:17 sentry-docker00.cs.umd.edu systemd-udevd[2392632]: Could not set offload features of veth98e8871: No such device
Sep 23 20:10:17 sentry-docker00.cs.umd.edu systemd-udevd[2392635]: link_config: could not get ethtool features for veth61ba222
Sep 23 20:10:17 sentry-docker00.cs.umd.edu systemd-udevd[2392635]: Could not set offload features of veth61ba222: No such device
Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392665]: Could not generate persistent MAC address for veth5e1c649: No such file or directory
Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392666]: Could not generate persistent MAC address for veth8d46c22: No such file or directory
Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392669]: Could not generate persistent MAC address for veth8d40bac: No such file or directory
Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392670]: Could not generate persistent MAC address for vethb675beb: No such file or directory
Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392669]: Could not generate persistent MAC address for vethd5d6057: No such file or directory
Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392683]: Could not generate persistent MAC address for veth4b36302: No such file or directory
Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392666]: Could not generate persistent MAC address for veth1e89c75: No such file or directory
Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392669]: Could not generate persistent MAC address for veth2b11513: No such file or directory
Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392753]: Could not generate persistent MAC address for vethe7b06de: No such file or directory
Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392752]: Could not generate persistent MAC address for veth0d398c3: No such file or directory
Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402065]: link_config: could not get ethtool features for veth2b11513
Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402065]: Could not set offload features of veth2b11513: No such device
Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402100]: Could not generate persistent MAC address for veth6a2b237: No such file or directory
Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402101]: Could not generate persistent MAC address for veth90ea233: No such file or directory
Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402104]: Could not generate persistent MAC address for vethbe2c5c9: No such file or directory
Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402117]: Could not generate persistent MAC address for veth39cc616: No such file or directory
Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402128]: Could not generate persistent MAC address for veth705d935: No such file or directory
Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402129]: Could not generate persistent MAC address for vethfcdf06f: No such file or directory
Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402147]: Could not generate persistent MAC address for vethed14bbc: No such file or directory
Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402128]: Could not generate persistent MAC address for veth0968f82: No such file or directory
Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402229]: Could not generate persistent MAC address for veth48111b4: No such file or directory
Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402239]: Could not generate persistent MAC address for vethed35e97: No such file or directory
Sep 23 20:50:34 sentry-docker00.cs.umd.edu systemd-udevd[2411759]: link_config: could not get ethtool features for veth48111b4
Sep 23 20:50:34 sentry-docker00.cs.umd.edu systemd-udevd[2411759]: Could not set offload features of veth48111b4: No such device
Sep 23 20:50:34 sentry-docker00.cs.umd.edu systemd-udevd[2411879]: Could not generate persistent MAC address for veth86bdf2e: No such file or directory
Sep 23 20:50:34 sentry-docker00.cs.umd.edu systemd-udevd[2411880]: Could not generate persistent MAC address for veth3afe65e: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 23 20:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 23 20:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 23 20:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 23 20:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 23 20:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 23 20:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 23 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 7 total) ==
Sep 23 20:09:13 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
== submit26-b9-f2 (1 distinct, 5 total) ==
Sep 23 20:13:07 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f3 (5 distinct, 9 total) ==
Sep 23 20:15:05 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
Sep 23 20:20:08 submit26-b9-f3 systemd-coredump[2857389]: Process 2857386 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2857386:#012#0 0x00007f0f4d68d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f0f4d63fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f0f4d629873 abort (libc.so.6 + 0x29873)#012#3 0x00007f0f4d62a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f0f4d71d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f0f4d71e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fe main (grades + 0x18fe)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 23 20:20:08 submit26-b9-f3 systemd-coredump[2857400]: Process 2857396 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2857396:#012#0 0x00007f6af628d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f6af623fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f6af6229873 abort (libc.so.6 + 0x29873)#012#3 0x00007f6af622a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f6af631d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f6af631e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fe main (grades + 0x18fe)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 23 20:23:38 submit26-b9-f3 systemd-coredump[2858637]: Process 2858634 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2858634:#012#0 0x00007f5f60e8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f5f60e3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f5f60e29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f5f60e2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f5f60f1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f5f60f1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401908 main (grades + 0x1908)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 23 20:23:38 submit26-b9-f3 systemd-coredump[2858647]: Process 2858644 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2858644:#012#0 0x00007fdfe868d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fdfe863fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fdfe8629873 abort (libc.so.6 + 0x29873)#012#3 0x00007fdfe862a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fdfe871d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fdfe871e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401908 main (grades + 0x1908)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f4 (1 distinct, 6 total) ==
Sep 23 20:17:45 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff
Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f
Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8
Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.xoVQTz/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566
Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xoVQTz. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac
Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c
Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0530s
Status : exited 0
Output :
Syslog digest — 2026-09-23 20:05 EDT
Processed 2,653 lines, filtered 2,200 (82%). 453 unknown (196 distinct) from 20 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 19:57:27 b0b02.cs.umd.edu rustdesk[342118]: cannot open display:
== bale (5 distinct, 84 total) ==
Sep 23 19:05:24 bale setroubleshoot[2207531]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 23 19:05:24 bale setroubleshoot[2207531]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12]
Sep 23 19:05:27 bale setroubleshoot[2207531]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12]
Sep 23 19:05:30 bale setroubleshoot[2207531]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12]
Sep 23 19:05:42 bale setroubleshoot[2208158]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x12]
== galax (11 distinct, 13 total) ==
Sep 23 19:10:06 galax systemd[1]: sysstat-collect.service: Condition check process exited, code=dumped, status=11/SEGV [x3]
Sep 23 19:38:48 galax falcon-sensor[1481]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 23 19:38:48 galax falcon-sensor[1481]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
Sep 23 19:44:09 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
Sep 23 19:44:20 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND
Sep 23 19:44:42 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 7 times, consider switching to WQ_UNBOUND
Sep 23 19:45:05 galax kernel: hrtimer: interrupt took 12153 ns
Sep 23 19:45:25 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 11 times, consider switching to WQ_UNBOUND
Sep 23 19:46:52 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 19 times, consider switching to WQ_UNBOUND
Sep 23 19:49:45 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 35 times, consider switching to WQ_UNBOUND
Sep 23 19:55:31 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 67 times, consider switching to WQ_UNBOUND
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Sep 23 19:41:11 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 23 19:41:11 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 23 19:41:11 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 23 19:41:11 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 23 19:41:11 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 23 19:41:11 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 23 19:41:11 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 23 19:41:11 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 23 19:41:11 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 23 19:41:11 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 23 19:41:11 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 23 19:54:05 idm00 named[4166701]: client @0x7f11a945b458 10.73.240.42#54550: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 23 19:39:31 idmp0 named[1598691]: client @0x7f2d500408e8 10.73.240.43#57291: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 2 total) ==
Sep 23 19:29:58 inbound00.cs.umd.edu krb5_child[3324823]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
== itmon02 (1 distinct, 3 total) ==
Sep 23 19:07:57 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== krispykreme.cs.umd.edu (2 distinct, 2 total) ==
Sep 23 19:47:33 krispykreme.cs.umd.edu krb5_child[1758947]: Preauthentication failed
Sep 23 19:47:33 krispykreme.cs.umd.edu sshd-session[1758933]: error: PAM: Authentication failure for larry from 128.8.70.66
== newhonors2 (1 distinct, 24 total) ==
Sep 23 19:13:03 newhonors2 dhcpcd[3054359]: dhcpcd is not running [x24]
== ntop00 (99 distinct, 143 total) ==
Sep 23 19:05:11 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 158, QN: 6629/6629, ET: 10) ***
Sep 23 19:05:11 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 158, QN: 46/46, ET: 10) ***
Sep 23 19:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 159) ***
Sep 23 19:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 159, QN: 7419/7419, ET: 0) ***
Sep 23 19:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 159) ***
Sep 23 19:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 159, QN: 61/61, ET: 0) ***
Sep 23 19:08:02 ntop00 setroubleshoot[67196]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 5b65c96c-a9fa-4175-8126-0641b1ec385c [x12]
Sep 23 19:08:02 ntop00 setroubleshoot[67196]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 0d1f7214-3aae-48d5-8fed-48565bd90d17 [x12]
Sep 23 19:08:02 ntop00 setroubleshoot[67196]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 23 19:08:02 ntop00 setroubleshoot[67196]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 4a9c8c49-4f0d-4ad5-b926-84fe3642d3ee [x12]
Sep 23 19:10:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 160) ***
Sep 23 19:10:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 160) ***
Sep 23 19:10:10 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 160, QN: 7176/7176, ET: 9) ***
Sep 23 19:10:10 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 160, QN: 62/62, ET: 9) ***
Sep 23 19:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 161) ***
Sep 23 19:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 161, QN: 6821/6821, ET: 0) ***
Sep 23 19:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 161) ***
Sep 23 19:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 161, QN: 58/58, ET: 0) ***
Sep 23 19:15:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 162) ***
Sep 23 19:15:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 162) ***
Sep 23 19:15:11 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 162, QN: 6717/6717, ET: 10) ***
Sep 23 19:15:11 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 162, QN: 64/64, ET: 10) ***
Sep 23 19:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 163) ***
Sep 23 19:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 163, QN: 67/67, ET: 0) ***
Sep 23 19:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 163) ***
Sep 23 19:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 163, QN: 6623/6623, ET: 0) ***
Sep 23 19:20:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 164) ***
Sep 23 19:20:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 164) ***
Sep 23 19:20:12 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 164, QN: 6980/6980, ET: 11) ***
Sep 23 19:20:12 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 164, QN: 58/58, ET: 11) ***
... 69 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 23 19:09:09 outbound00.cs.umd.edu python3[3180131]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 23 19:13:07 outbound01.cs.umd.edu python3[1246155]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 23 19:09:52 sentry-docker00.cs.umd.edu systemd-udevd[2364238]: link_config: could not get ethtool features for vethc43a0e6
Sep 23 19:09:52 sentry-docker00.cs.umd.edu systemd-udevd[2364238]: Could not set offload features of vethc43a0e6: No such device
Sep 23 19:09:52 sentry-docker00.cs.umd.edu systemd-udevd[2364326]: link_config: could not get ethtool features for veth87057b7
Sep 23 19:09:52 sentry-docker00.cs.umd.edu systemd-udevd[2364326]: Could not set offload features of veth87057b7: No such device
Sep 23 19:09:52 sentry-docker00.cs.umd.edu systemd-udevd[2364351]: Could not generate persistent MAC address for veth432918d: No such file or directory
Sep 23 19:09:52 sentry-docker00.cs.umd.edu systemd-udevd[2364350]: Could not generate persistent MAC address for veth868fe0c: No such file or directory
Sep 23 19:09:52 sentry-docker00.cs.umd.edu systemd-udevd[2364358]: Could not generate persistent MAC address for veth089f9c2: No such file or directory
Sep 23 19:09:52 sentry-docker00.cs.umd.edu systemd-udevd[2364369]: Could not generate persistent MAC address for veth4a73970: No such file or directory
Sep 23 19:09:53 sentry-docker00.cs.umd.edu systemd-udevd[2364375]: Could not generate persistent MAC address for veth6d47480: No such file or directory
Sep 23 19:09:53 sentry-docker00.cs.umd.edu systemd-udevd[2364367]: Could not generate persistent MAC address for vethd5e8b6e: No such file or directory
Sep 23 19:09:53 sentry-docker00.cs.umd.edu systemd-udevd[2364369]: Could not generate persistent MAC address for veth6124649: No such file or directory
Sep 23 19:09:53 sentry-docker00.cs.umd.edu systemd-udevd[2364358]: Could not generate persistent MAC address for veth8c6f750: No such file or directory
Sep 23 19:09:53 sentry-docker00.cs.umd.edu systemd-udevd[2364369]: Could not generate persistent MAC address for veth14ffc13: No such file or directory
Sep 23 19:09:53 sentry-docker00.cs.umd.edu systemd-udevd[2364375]: Could not generate persistent MAC address for veth2b1c149: No such file or directory
Sep 23 19:30:01 sentry-docker00.cs.umd.edu systemd-udevd[2373706]: link_config: could not get ethtool features for veth4a73970
Sep 23 19:30:01 sentry-docker00.cs.umd.edu systemd-udevd[2373706]: Could not set offload features of veth4a73970: No such device
Sep 23 19:30:01 sentry-docker00.cs.umd.edu systemd-udevd[2373749]: Could not generate persistent MAC address for veth7b74397: No such file or directory
Sep 23 19:30:01 sentry-docker00.cs.umd.edu systemd-udevd[2373750]: Could not generate persistent MAC address for veth3c8e3c8: No such file or directory
Sep 23 19:30:01 sentry-docker00.cs.umd.edu systemd-udevd[2373753]: Could not generate persistent MAC address for vethe552218: No such file or directory
Sep 23 19:30:01 sentry-docker00.cs.umd.edu systemd-udevd[2373754]: Could not generate persistent MAC address for veth6f34346: No such file or directory
Sep 23 19:30:01 sentry-docker00.cs.umd.edu systemd-udevd[2373757]: Could not generate persistent MAC address for veth20d93cf: No such file or directory
Sep 23 19:30:01 sentry-docker00.cs.umd.edu systemd-udevd[2373772]: Could not generate persistent MAC address for veth53455a8: No such file or directory
Sep 23 19:30:01 sentry-docker00.cs.umd.edu systemd-udevd[2373763]: Could not generate persistent MAC address for vethe8b1c11: No such file or directory
Sep 23 19:30:01 sentry-docker00.cs.umd.edu systemd-udevd[2373770]: Could not generate persistent MAC address for veth210a7ad: No such file or directory
Sep 23 19:30:01 sentry-docker00.cs.umd.edu systemd-udevd[2373850]: Could not generate persistent MAC address for vethf37d99e: No such file or directory
Sep 23 19:30:01 sentry-docker00.cs.umd.edu systemd-udevd[2373849]: Could not generate persistent MAC address for veth4340829: No such file or directory
Sep 23 19:50:09 sentry-docker00.cs.umd.edu systemd-udevd[2383141]: link_config: could not get ethtool features for vethe552218
Sep 23 19:50:09 sentry-docker00.cs.umd.edu systemd-udevd[2383141]: Could not set offload features of vethe552218: No such device
Sep 23 19:50:09 sentry-docker00.cs.umd.edu systemd-udevd[2383187]: Could not generate persistent MAC address for veth61ba222: No such file or directory
Sep 23 19:50:09 sentry-docker00.cs.umd.edu systemd-udevd[2383188]: Could not generate persistent MAC address for vethf02374a: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 23 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 23 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 23 19:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 23 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 23 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 23 19:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 23 19:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (7 distinct, 11 total) ==
Sep 23 19:05:37 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
Sep 23 19:05:38 submit26-b9-f1 systemd-coredump[3207776]: Process 3207773 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3207773:#012#0 0x00007f531b88d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f531b83fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f531b829873 abort (libc.so.6 + 0x29873)#012#3 0x00007f531b82a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f531b91d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f531b91e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040176d main (grades + 0x176d)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 23 19:05:39 submit26-b9-f1 systemd-coredump[3207786]: Process 3207783 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3207783:#012#0 0x00007f093a68d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f093a63fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f093a629873 abort (libc.so.6 + 0x29873)#012#3 0x00007f093a62a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f093a71d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f093a71e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040176d main (grades + 0x176d)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 23 19:39:25 submit26-b9-f1 systemd-coredump[3212809]: Process 3212806 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3212806:#012#0 0x00007f42dda8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f42dda3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f42dda29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f42dda2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f42ddb1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f42ddb1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fe main (grades + 0x18fe)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 23 19:39:25 submit26-b9-f1 systemd-coredump[3212818]: Process 3212816 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3212816:#012#0 0x00007f58aec8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f58aec3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f58aec29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f58aec2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f58aed1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f58aed1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fe main (grades + 0x18fe)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 23 20:03:10 submit26-b9-f1 systemd-coredump[3215224]: Process 3215221 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3215221:#012#0 0x00007f274448d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f274443fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f2744429873 abort (libc.so.6 + 0x29873)#012#3 0x00007f274442a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f274451d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f274451e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401908 main (grades + 0x1908)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 23 20:03:10 submit26-b9-f1 systemd-coredump[3215235]: Process 3215232 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3215232:#012#0 0x00007fe13da8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fe13da3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fe13da29873 abort (libc.so.6 + 0x29873)#012#3 0x00007fe13da2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fe13db1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fe13db1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401908 main (grades + 0x1908)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f2 (3 distinct, 6 total) ==
Sep 23 19:22:42 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
Sep 23 19:42:17 submit26-b9-f2 systemd-coredump[2306837]: Process 2306834 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2306834:#012#0 0x00007fbbdd08d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fbbdd03fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fbbdd029873 abort (libc.so.6 + 0x29873)#012#3 0x00007fbbdd02a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fbbdd11d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fbbdd11e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401908 main (grades + 0x1908)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 23 19:42:17 submit26-b9-f2 systemd-coredump[2306848]: Process 2306845 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2306845:#012#0 0x00007fe87988d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fe87983fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fe879829873 abort (libc.so.6 + 0x29873)#012#3 0x00007fe87982a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fe87991d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fe87991e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401908 main (grades + 0x1908)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f3 (1 distinct, 3 total) ==
Sep 23 19:06:04 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f4 (3 distinct, 4 total) ==
Sep 23 19:41:20 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
Sep 23 19:59:33 submit26-b9-f4 systemd-coredump[2091938]: Process 2091935 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2091935:#012#0 0x00007f6726e8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f6726e3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f6726e29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f6726e2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f6726f1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f6726f1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fe main (grades + 0x18fe)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 23 19:59:33 submit26-b9-f4 systemd-coredump[2091949]: Process 2091946 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2091946:#012#0 0x00007f4eac08d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f4eac03fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f4eac029873 abort (libc.so.6 + 0x29873)#012#3 0x00007f4eac02a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f4eac11d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f4eac11e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fe main (grades + 0x18fe)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
== yogurt (1 distinct, 1 total) ==
Sep 23 19:13:22 yogurt xdg-desktop-por[1084445]: Backend call failed: Cannot invoke method; proxy is for the well-known name org.freedesktop.ScreenSaver without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0516s
Status : exited 0
Output :
Syslog digest — 2026-09-23 19:05 EDT
Processed 2,431 lines, filtered 2,028 (83%). 403 unknown (197 distinct) from 19 host(s).
== b0b02.cs.umd.edu (4 distinct, 4 total) ==
Sep 23 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-23T22:10:59.429910465Z" level=info msg="PurgeUploads starting: olderThan=2026-09-16 22:10:59.429792684 +0000 UTC m=+4408620.189721006, actuallyDelete=true"
Sep 23 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-23T22:10:59.430667062Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1"
Sep 23 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-23T22:10:59.430697183Z" 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 23 18:57:23 b0b02.cs.umd.edu rustdesk[326951]: cannot open display:
== bale (5 distinct, 87 total) ==
Sep 23 18:06:06 bale setroubleshoot[2194807]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 23 18:06:07 bale setroubleshoot[2194807]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x13]
Sep 23 18:06:09 bale setroubleshoot[2194807]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13]
Sep 23 18:06:12 bale setroubleshoot[2194807]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x11]
Sep 23 18:06:24 bale setroubleshoot[2195422]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x13]
== biggulp.cs.umd.edu (2 distinct, 2 total) ==
Sep 23 18:53:16 biggulp.cs.umd.edu krb5_child[3721286]: Preauthentication failed
Sep 23 18:53:16 biggulp.cs.umd.edu sshd-session[3721282]: error: PAM: Authentication failure for leoliu from 128.8.126.63
== galax (1 distinct, 6 total) ==
Sep 23 18:10:03 galax systemd[1]: sysstat-collect.service: Condition check process exited, code=dumped, status=11/SEGV [x6]
== idm00 (1 distinct, 1 total) ==
Sep 23 18:54:05 idm00 named[4166701]: client @0x7f11a0057bb8 10.73.240.42#59031: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 23 18:39:31 idmp0 named[1598691]: client @0x7f2d3802f8f8 10.73.240.43#49360: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 2 total) ==
Sep 23 18:43:00 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2]
== munin (2 distinct, 4 total) ==
Sep 23 18:17:59 munin sudo[2489400]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 23 18:17:59 munin sudo[2489400]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 23 18:13:02 newhonors2 dhcpcd[3052514]: dhcpcd is not running [x24]
== ntop00 (101 distinct, 141 total) ==
Sep 23 18:05:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 134) ***
Sep 23 18:05:19 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 134, QN: 11461/11461, ET: 18) ***
Sep 23 18:05:19 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 134, QN: 70/70, ET: 18) ***
Sep 23 18:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 135) ***
Sep 23 18:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 135, QN: 12238/12238, ET: 0) ***
Sep 23 18:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 135) ***
Sep 23 18:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 135, QN: 58/58, ET: 0) ***
Sep 23 18:08:02 ntop00 setroubleshoot[58647]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 5b65c96c-a9fa-4175-8126-0641b1ec385c [x11]
Sep 23 18:08:02 ntop00 setroubleshoot[58647]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 0d1f7214-3aae-48d5-8fed-48565bd90d17 [x11]
Sep 23 18:08:02 ntop00 setroubleshoot[58647]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11]
Sep 23 18:08:02 ntop00 setroubleshoot[58647]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 4a9c8c49-4f0d-4ad5-b926-84fe3642d3ee [x11]
Sep 23 18:10:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 136) ***
Sep 23 18:10:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 136) ***
Sep 23 18:10:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 136, QN: 51/51, ET: 0) ***
Sep 23 18:10:18 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 136, QN: 13065/13065, ET: 17) ***
Sep 23 18:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 137) ***
Sep 23 18:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 137, QN: 11483/11483, ET: 0) ***
Sep 23 18:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 137) ***
Sep 23 18:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 137, QN: 63/63, ET: 0) ***
Sep 23 18:15:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 138) ***
Sep 23 18:15:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 138) ***
Sep 23 18:15:13 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 138, QN: 9249/9249, ET: 12) ***
Sep 23 18:15:13 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 138, QN: 65/65, ET: 12) ***
Sep 23 18:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 139) ***
Sep 23 18:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 139, QN: 9966/9966, ET: 0) ***
Sep 23 18:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 139) ***
Sep 23 18:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 139, QN: 47/47, ET: 0) ***
Sep 23 18:20:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 140) ***
Sep 23 18:20:02 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 140) ***
Sep 23 18:20:17 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 140, QN: 11997/11997, ET: 16) ***
... 71 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 23 18:09:09 outbound00.cs.umd.edu python3[3166031]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 23 18:13:06 outbound01.cs.umd.edu python3[1232150]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 23 18:09:27 sentry-docker00.cs.umd.edu systemd-udevd[2336058]: link_config: could not get ethtool features for vethb0f5704
Sep 23 18:09:27 sentry-docker00.cs.umd.edu systemd-udevd[2336058]: Could not set offload features of vethb0f5704: No such device
Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336074]: Could not generate persistent MAC address for veth65c37d4: No such file or directory
Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336075]: Could not generate persistent MAC address for vethd2d7db4: No such file or directory
Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336093]: Could not generate persistent MAC address for veth205b1db: No such file or directory
Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336075]: Could not generate persistent MAC address for vethba5979f: No such file or directory
Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336102]: Could not generate persistent MAC address for veth4244178: No such file or directory
Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336103]: Could not generate persistent MAC address for veth3b71b75: No such file or directory
Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336112]: Could not generate persistent MAC address for veth6def173: No such file or directory
Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336121]: Could not generate persistent MAC address for vethf0bdeb6: No such file or directory
Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336137]: Could not generate persistent MAC address for veth98d9e41: No such file or directory
Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336139]: Could not generate persistent MAC address for veth77f5f3a: No such file or directory
Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345575]: link_config: could not get ethtool features for veth98d9e41
Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345575]: Could not set offload features of veth98d9e41: No such device
Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345612]: Could not generate persistent MAC address for veth78a9c85: No such file or directory
Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345613]: Could not generate persistent MAC address for veth241aad2: No such file or directory
Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345616]: Could not generate persistent MAC address for veth04096d6: No such file or directory
Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345617]: Could not generate persistent MAC address for veth83a81bb: No such file or directory
Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345630]: Could not generate persistent MAC address for veth4b5ca59: No such file or directory
Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345613]: Could not generate persistent MAC address for veth30efd7d: No such file or directory
Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345625]: Could not generate persistent MAC address for vetha150ae3: No such file or directory
Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345628]: Could not generate persistent MAC address for veth66f0e76: No such file or directory
Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345671]: Could not generate persistent MAC address for vethfc7b455: No such file or directory
Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345675]: Could not generate persistent MAC address for veth734ebe2: No such file or directory
Sep 23 18:49:44 sentry-docker00.cs.umd.edu systemd-udevd[2354934]: link_config: could not get ethtool features for veth78a9c85
Sep 23 18:49:44 sentry-docker00.cs.umd.edu systemd-udevd[2354934]: Could not set offload features of veth78a9c85: No such device
Sep 23 18:49:44 sentry-docker00.cs.umd.edu systemd-udevd[2354963]: Could not generate persistent MAC address for veth329cc0c: No such file or directory
Sep 23 18:49:44 sentry-docker00.cs.umd.edu systemd-udevd[2354964]: Could not generate persistent MAC address for veth109f718: No such file or directory
Sep 23 18:49:44 sentry-docker00.cs.umd.edu systemd-udevd[2354971]: Could not generate persistent MAC address for vethe95fb56: No such file or directory
Sep 23 18:49:44 sentry-docker00.cs.umd.edu systemd-udevd[2354968]: Could not generate persistent MAC address for vethc43a0e6: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 23 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 23 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 23 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 23 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 23 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 23 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 23 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (12 distinct, 14 total) ==
Sep 23 18:20:36 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
Sep 23 18:25:27 submit26-b9-f1 systemd-coredump[3196000]: Process 3195997 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3195997:#012#0 0x00007f6c9e28d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f6c9e23fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f6c9e229873 abort (libc.so.6 + 0x29873)#012#3 0x00007f6c9e22a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f6c9e31d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f6c9e31e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040176d main (grades + 0x176d)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 23 18:25:27 submit26-b9-f1 systemd-coredump[3196011]: Process 3196008 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3196008:#012#0 0x00007eff8228d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007eff8223fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007eff82229873 abort (libc.so.6 + 0x29873)#012#3 0x00007eff8222a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007eff8231d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007eff8231e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040176d main (grades + 0x176d)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.9rOHc7/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.9rOHc7. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 (11 distinct, 16 total) ==
Sep 23 18:06:37 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 [x2]
Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a [x2]
Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339
Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.0wf1m9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1
Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.0wf1m9. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: 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 [x2]
Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: 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 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: 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 [x2]
Sep 23 18:06:51 submit26-b9-f2 setroubleshoot[2285035]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xY1dgk. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
== submit26-b9-f3 (3 distinct, 5 total) ==
Sep 23 18:22:24 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
Sep 23 18:45:30 submit26-b9-f3 systemd-coredump[2837975]: Process 2837972 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2837972:#012#0 0x00007f46f128d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f46f123fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f46f1229873 abort (libc.so.6 + 0x29873)#012#3 0x00007f46f122a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f46f131d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f46f131e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040176d main (grades + 0x176d)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 23 18:45:30 submit26-b9-f3 systemd-coredump[2837985]: Process 2837982 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2837982:#012#0 0x00007fcdbe28d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fcdbe23fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fcdbe229873 abort (libc.so.6 + 0x29873)#012#3 0x00007fcdbe22a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fcdbe31d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fcdbe31e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040176d main (grades + 0x176d)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f4 (1 distinct, 4 total) ==
Sep 23 18:15:04 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== vpn00a.cs.umd.edu (6 distinct, 6 total) ==
Sep 23 18:14:03 vpn00a.cs.umd.edu setroubleshoot[1294846]: failed to retrieve rpm info for path '/var/lib/ipa-client/sysrestore/sysrestore.index':
Sep 23 18:14:04 vpn00a.cs.umd.edu setroubleshoot[1294846]: SELinux is preventing /usr/bin/python3.9 from search access on the directory /var/lib/ipa-client/sysrestore/sysrestore.index. For complete SELinux messages run: sealert -l aaf84404-597f-4dfb-ac0f-2e8cbbdc14b4
Sep 23 18:14:04 vpn00a.cs.umd.edu setroubleshoot[1294846]: SELinux is preventing /usr/bin/python3.9 from read access on the file /var/lib/ipa-client/sysrestore/sysrestore.index. For complete SELinux messages run: sealert -l 666e06a7-327b-48d7-bb9f-4475f9036316
Sep 23 18:14:04 vpn00a.cs.umd.edu setroubleshoot[1294846]: SELinux is preventing /usr/bin/python3.9 from open access on the file /var/lib/ipa-client/sysrestore/sysrestore.index. For complete SELinux messages run: sealert -l 91b1a9db-b8c3-4017-8d03-a86ace59bbe4
Sep 23 18:14:04 vpn00a.cs.umd.edu setroubleshoot[1294846]: SELinux is preventing /usr/bin/python3.9 from getattr access on the file /var/lib/ipa-client/sysrestore/sysrestore.index. For complete SELinux messages run: sealert -l c81675b5-39be-478f-842c-9d78125f7f88
Sep 23 18:14:04 vpn00a.cs.umd.edu setroubleshoot[1294846]: SELinux is preventing /usr/bin/python3.9 from ioctl access on the file /var/lib/ipa-client/sysrestore/sysrestore.index. For complete SELinux messages run: sealert -l 8e209ef6-d276-493a-bbe4-409df332225e
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0557s
Status : exited 0
Output :
Syslog digest — 2026-09-23 18:05 EDT
Processed 2,538 lines, filtered 2,105 (82%). 433 unknown (224 distinct) from 26 host(s).
== abadi-computer (1 distinct, 1 total) ==
Sep 23 18:00:16 abadi-computer kernel: kauditd_printk_skb: 2 callbacks suppressed
== amoeba (6 distinct, 6 total) ==
Sep 23 18:03:42 amoeba gsd-subman[1458433]: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Sep 23 18:03:42 amoeba xdg-desktop-por[1458589]: Caught PipeWire error: connection error
Sep 23 18:03:44 amoeba org.gnome.Shell.desktop[3218123] The XKEYBOARD keymap compiler (xkbcomp) reports:
Sep 23 18:03:44 amoeba org.gnome.Shell.desktop[3218123] > Warning: Unsupported maximum keycode 708, clipping.
Sep 23 18:03:44 amoeba org.gnome.Shell.desktop[3218123] > X11 cannot support keycodes above 255.
Sep 23 18:03:44 amoeba org.gnome.Shell.desktop[3218123] Errors from xkbcomp are not fatal to the X server
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 17:57:19 b0b02.cs.umd.edu rustdesk[311720]: cannot open display:
== bale (5 distinct, 88 total) ==
Sep 23 17:05:14 bale setroubleshoot[2181860]: failed to retrieve rpm info for /dev/nvme0 [x38]
Sep 23 17:05:15 bale setroubleshoot[2181860]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12]
Sep 23 17:05:17 bale setroubleshoot[2181860]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12]
Sep 23 17:05:20 bale setroubleshoot[2181860]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12]
Sep 23 17:05:32 bale setroubleshoot[2182474]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x14]
== biggulp.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 17:59:16 biggulp.cs.umd.edu setroubleshoot[3712221]: SELinux is preventing /usr/sbin/load_policy from read access on the fifo_file fifo_file. For complete SELinux messages run: sealert -l 17e464d5-d359-4234-b1db-8fa9ed4db2bb
== cheezit.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 17:59:17 cheezit.cs.umd.edu setroubleshoot[2414184]: SELinux is preventing /usr/sbin/load_policy from read access on the fifo_file fifo_file. For complete SELinux messages run: sealert -l 5b4ea79f-b794-4eaf-8d66-731d6ab719b5
== frozone (1 distinct, 1 total) ==
Sep 23 17:35:43 frozone systemd-tmpfiles[2545005]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted
== galax (6 distinct, 14 total) ==
Sep 23 17:10:06 galax systemd[1]: sysstat-collect.service: Condition check process exited, code=dumped, status=11/SEGV [x6]
Sep 23 17:22:03 galax systemd-sysv-generator[850033]: SysV service '/etc/init.d/openipmi' lacks a native systemd unit file, automatically generating a unit file for compatibility. [x2]
Sep 23 17:22:03 galax systemd-sysv-generator[850033]: Please update package to include a native systemd unit file. [x2]
Sep 23 17:22:03 galax systemd-sysv-generator[850033]: ! This compatibility logic is deprecated, expect removal soon. ! [x2]
Sep 23 17:22:03 galax systemd[1]: snap-firmware\x2dupdater-258.mount: Mount process exited, code=dumped, status=11/SEGV
Sep 23 17:22:03 galax systemd[1]: Failed to mount snap-firmware\x2dupdater-258.mount - Mount unit for firmware-updater, revision 258.
== gle-dind04 (15 distinct, 15 total) ==
Sep 23 17:37:12 gle-dind04 systemd-coredump[2484858]: Process 2484855 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2484855:#012#0 0x00005617cf95e2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x00005617cf97d2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x00005617cf97cfc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x00005617cf9781d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x00005617cf9780a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x00005617cf978065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x00005617cf99cada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x00005617cf996651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x00005617cf9927a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x00005617cf975edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x00005617cf9a6b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x00005617cf9e0a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 17:37:12 gle-dind04 systemd-coredump[2484866]: Process 2484864 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2484864:#012#0 0x0000560adc1b22ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000560adc1d12c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000560adc1d0fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000560adc1cc1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000560adc1cc0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000560adc1cc065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000560adc1f0ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000560adc1ea651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000560adc1e67a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000560adc1c9edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000560adc1fab52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000560adc234a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 17:37:12 gle-dind04 systemd-coredump[2484874]: Process 2484872 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2484872:#012#0 0x000055dbcb5da2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055dbcb5f92c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055dbcb5f8fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055dbcb5f41d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055dbcb5f40a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055dbcb5f4065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055dbcb618ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055dbcb612651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055dbcb60e7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055dbcb5f1edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055dbcb622b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055dbcb65ca47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 17:37:13 gle-dind04 systemd-coredump[2484887]: Process 2484881 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2484881:#012#0 0x00005654f23bd2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x00005654f23dc2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x00005654f23dbfc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x00005654f23d71d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x00005654f23d70a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x00005654f23d7065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x00005654f23fbada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x00005654f23f5651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x00005654f23f17a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x00005654f23d4edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x00005654f2405b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x00005654f243fa47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 17:37:13 gle-dind04 systemd-coredump[2484910]: Process 2484908 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2484908:#012#0 0x0000560d6cdbc2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000560d6cddb2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000560d6cddafc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000560d6cdd61d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000560d6cdd60a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000560d6cdd6065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000560d6cdfaada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000560d6cdf4651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000560d6cdf07a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000560d6cdd3edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000560d6ce04b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000560d6ce3ea47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 17:37:13 gle-dind04 systemd-coredump[2484935]: Process 2484933 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2484933:#012#0 0x000055c078b2c2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055c078b4b2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055c078b4afc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055c078b461d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055c078b460a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055c078b46065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055c078b6aada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055c078b64651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055c078b607a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055c078b43edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055c078b74b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055c078baea47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 17:37:14 gle-dind04 systemd-coredump[2484967]: Process 2484965 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2484965:#012#0 0x000055dfaaed72ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055dfaaef62c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055dfaaef5fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055dfaaef11d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055dfaaef10a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055dfaaef1065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055dfaaf15ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055dfaaf0f651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055dfaaf0b7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055dfaaeeeedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055dfaaf1fb52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055dfaaf59a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 17:46:04 gle-dind04 systemd-coredump[2487468]: Process 2487464 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2487464:#012#0 0x000055aa9b9e02ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055aa9b9ff2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055aa9b9fefc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055aa9b9fa1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055aa9b9fa0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055aa9b9fa065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055aa9ba1eada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055aa9ba18651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055aa9ba147a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055aa9b9f7edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055aa9ba28b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055aa9ba62a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 17:46:05 gle-dind04 systemd-coredump[2487523]: Process 2487521 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2487521:#012#0 0x000055de381742ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055de381932c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055de38192fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055de3818e1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055de3818e0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055de3818e065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055de381b2ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055de381ac651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055de381a87a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055de3818bedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055de381bcb52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055de381f6a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 17:46:05 gle-dind04 systemd-coredump[2487530]: Process 2487528 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2487528:#012#0 0x000055cd967612ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055cd967802c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055cd9677ffc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055cd9677b1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055cd9677b0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055cd9677b065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055cd9679fada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055cd96799651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055cd967957a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055cd96778edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055cd967a9b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055cd967e3a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 17:46:05 gle-dind04 systemd-coredump[2487580]: Process 2487565 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2487565:#012#0 0x000055a12b1302ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055a12b14f2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055a12b14efc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055a12b14a1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055a12b14a0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055a12b14a065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055a12b16eada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055a12b168651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055a12b1647a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055a12b147edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055a12b178b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055a12b1b2a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 17:46:05 gle-dind04 systemd-coredump[2487612]: Process 2487610 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2487610:#012#0 0x0000562bd6ea92ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000562bd6ec82c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000562bd6ec7fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000562bd6ec31d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000562bd6ec30a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000562bd6ec3065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000562bd6ee7ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000562bd6ee1651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000562bd6edd7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000562bd6ec0edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000562bd6ef1b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000562bd6f2ba47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 17:46:06 gle-dind04 systemd-coredump[2487673]: Process 2487670 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2487670:#012#0 0x0000562b575872ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000562b575a62c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000562b575a5fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000562b575a11d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000562b575a10a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000562b575a1065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000562b575c5ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000562b575bf651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000562b575bb7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000562b5759eedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000562b575cfb52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000562b57609a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 17:46:06 gle-dind04 systemd-coredump[2487697]: Process 2487694 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2487694:#012#0 0x000055b9499072ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055b9499262c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055b949925fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055b9499211d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055b9499210a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055b949921065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055b949945ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055b94993f651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055b94993b7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055b94991eedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055b94994fb52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055b949989a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 23 18:01:21 gle-dind04 lldpd[1171]: unable to send packet on real device for veth72a86f9: No such device or address
== idm00 (1 distinct, 1 total) ==
Sep 23 17:54:05 idm00 named[4166701]: client @0x7f11a00732a8 10.73.240.42#56503: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 23 17:39:31 idmp0 named[1598691]: client @0x7f2d08972e18 10.73.240.43#56368: update '73.10.in-addr.arpa/IN' denied
== itmon02 (8 distinct, 14 total) ==
Sep 23 17:06:16 itmon02 SetroubleshootPrivileged.py[2205 failed to retrieve rpm info for path '/var/lib/selinux/targeted/active/modules/200/grafana':
Sep 23 17:06:16 itmon02 setroubleshoot[2205095]: SELinux is preventing /usr/sbin/grafana from name_connect access on the tcp_socket port 3306. For complete SELinux messages run: sealert -l deb40268-1414-43e0-8915-0a3785a3ecd5 [x2]
Sep 23 17:11:15 itmon02 SetroubleshootPrivileged.py[2214 failed to retrieve rpm info for path '/var/lib/selinux/targeted/active/modules/200/grafana':
Sep 23 17:18:55 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
Sep 23 17:23:48 itmon02 systemd-sysv-generator[2231261]: SysV service '/etc/rc.d/init.d/thruk' lacks a native systemd unit file, automatically generating a unit file for compatibility.
Sep 23 17:23:48 itmon02 systemd-sysv-generator[2231261]: Please update package to include a native systemd unit file. [x2]
Sep 23 17:23:48 itmon02 systemd-sysv-generator[2231261]: ! This compatibility logic is deprecated, expect removal soon. ! [x2]
Sep 23 17:23:48 itmon02 systemd-sysv-generator[2231261]: SysV service '/etc/rc.d/init.d/pnp_gearman_worker' lacks a native systemd unit file, automatically generating a unit file for compatibility.
== krispykreme.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 17:59:33 krispykreme.cs.umd.edu setroubleshoot[1718865]: SELinux is preventing /usr/sbin/load_policy from read access on the fifo_file fifo_file. For complete SELinux messages run: sealert -l f8324dd6-af90-49bf-b96a-f33abfe7a34a
== munin (2 distinct, 2 total) ==
Sep 23 17:08:50 munin sudo[2464659]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory
Sep 23 17:08:50 munin sudo[2464659]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order.
== neodontcare.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 17:47:17 neodontcare.cs.umd.edu krb5_child[2001345]: Preauthentication failed
== netman.cs.umd.edu (1 distinct, 1 total) ==
Sep 23 17:49:26 netman.cs.umd.edu sshd[4077408]: error: connect_to vz.cs.umd.edu port 22: failed.
== newhonors2 (1 distinct, 24 total) ==
Sep 23 17:13:03 newhonors2 dhcpcd[3050671]: dhcpcd is not running [x24]
== ntop00 (104 distinct, 144 total) ==
Sep 23 17:05:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 110) ***
Sep 23 17:05:20 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 110, QN: 7632/7632, ET: 19) ***
Sep 23 17:05:20 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 110, QN: 51/51, ET: 19) ***
Sep 23 17:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 111) ***
Sep 23 17:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 111) ***
Sep 23 17:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 111, QN: 53/53, ET: 0) ***
Sep 23 17:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 111, QN: 8777/8777, ET: 0) ***
Sep 23 17:08:02 ntop00 setroubleshoot[50111]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 5b65c96c-a9fa-4175-8126-0641b1ec385c [x11]
Sep 23 17:08:02 ntop00 setroubleshoot[50111]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 0d1f7214-3aae-48d5-8fed-48565bd90d17 [x11]
Sep 23 17:08:02 ntop00 setroubleshoot[50111]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11]
Sep 23 17:08:02 ntop00 setroubleshoot[50111]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 4a9c8c49-4f0d-4ad5-b926-84fe3642d3ee [x11]
Sep 23 17:08:37 ntop00 pmacct-mariadb[5571]: 2026-09-23 21:08:37 89 [Warning] Aborted connection 89 to db: 'pmacct' user: 'grafana_reader' host: '10.73.246.25' (Got an error reading communication packets)
Sep 23 17:10:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 112) ***
Sep 23 17:10:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 112) ***
Sep 23 17:10:15 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 112, QN: 9392/9392, ET: 14) ***
Sep 23 17:10:15 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 112, QN: 51/51, ET: 14) ***
Sep 23 17:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 113) ***
Sep 23 17:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 113, QN: 9146/9146, ET: 0) ***
Sep 23 17:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 113) ***
Sep 23 17:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 113, QN: 70/70, ET: 0) ***
Sep 23 17:13:35 ntop00 pmacct-mariadb[5571]: 2026-09-23 21:13:35 155 [Warning] Aborted connection 155 to db: 'pmacct' user: 'grafana_reader' host: '10.73.246.25' (Got an error reading communication packets)
Sep 23 17:15:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 114) ***
Sep 23 17:15:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 114) ***
Sep 23 17:15:12 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 114, QN: 8286/8286, ET: 11) ***
Sep 23 17:15:12 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 114, QN: 60/60, ET: 11) ***
Sep 23 17:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 115) ***
Sep 23 17:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 115, QN: 8634/8634, ET: 0) ***
Sep 23 17:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 115) ***
Sep 23 17:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 115, QN: 36/36, ET: 0) ***
Sep 23 17:20:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 116) ***
... 74 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 23 17:09:09 outbound00.cs.umd.edu python3[3152058]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 23 17:13:07 outbound01.cs.umd.edu python3[1217989]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 23 17:09:02 sentry-docker00.cs.umd.edu systemd-udevd[2307551]: link_config: could not get ethtool features for veth86855df
Sep 23 17:09:03 sentry-docker00.cs.umd.edu systemd-udevd[2307551]: Could not set offload features of veth86855df: No such device
Sep 23 17:09:03 sentry-docker00.cs.umd.edu systemd-udevd[2307585]: Could not generate persistent MAC address for vetha364011: No such file or directory
Sep 23 17:09:03 sentry-docker00.cs.umd.edu systemd-udevd[2307586]: Could not generate persistent MAC address for vethe6ae579: No such file or directory
Sep 23 17:09:03 sentry-docker00.cs.umd.edu systemd-udevd[2307589]: Could not generate persistent MAC address for vethc1c2bf8: No such file or directory
Sep 23 17:09:03 sentry-docker00.cs.umd.edu systemd-udevd[2307610]: Could not generate persistent MAC address for veth3f1daae: No such file or directory
Sep 23 17:09:03 sentry-docker00.cs.umd.edu systemd-udevd[2307613]: Could not generate persistent MAC address for veth3df3ddc: No such file or directory
Sep 23 17:09:03 sentry-docker00.cs.umd.edu systemd-udevd[2307614]: Could not generate persistent MAC address for veth423cf74: No such file or directory
Sep 23 17:09:03 sentry-docker00.cs.umd.edu systemd-udevd[2307617]: Could not generate persistent MAC address for veth9f9692c: No such file or directory
Sep 23 17:09:03 sentry-docker00.cs.umd.edu systemd-udevd[2307635]: Could not generate persistent MAC address for vetha11a364: No such file or directory
Sep 23 17:09:03 sentry-docker00.cs.umd.edu systemd-udevd[2307631]: Could not generate persistent MAC address for vethaddd7e0: No such file or directory
Sep 23 17:09:03 sentry-docker00.cs.umd.edu systemd-udevd[2307620]: Could not generate persistent MAC address for veth47985a1: No such file or directory
Sep 23 17:29:11 sentry-docker00.cs.umd.edu systemd-udevd[2317238]: link_config: could not get ethtool features for vetha11a364
Sep 23 17:29:11 sentry-docker00.cs.umd.edu systemd-udevd[2317238]: Could not set offload features of vetha11a364: No such device
Sep 23 17:29:11 sentry-docker00.cs.umd.edu systemd-udevd[2317264]: Could not generate persistent MAC address for veth90c40c8: No such file or directory
Sep 23 17:29:11 sentry-docker00.cs.umd.edu systemd-udevd[2317265]: Could not generate persistent MAC address for veth57484e0: No such file or directory
Sep 23 17:29:11 sentry-docker00.cs.umd.edu systemd-udevd[2317283]: Could not generate persistent MAC address for vethed9c98b: No such file or directory
Sep 23 17:29:11 sentry-docker00.cs.umd.edu systemd-udevd[2317274]: Could not generate persistent MAC address for veth47ba4aa: No such file or directory
Sep 23 17:29:11 sentry-docker00.cs.umd.edu systemd-udevd[2317264]: Could not generate persistent MAC address for veth380b246: No such file or directory
Sep 23 17:29:11 sentry-docker00.cs.umd.edu systemd-udevd[2317274]: Could not generate persistent MAC address for vethc2ce474: No such file or directory
Sep 23 17:29:11 sentry-docker00.cs.umd.edu systemd-udevd[2317276]: Could not generate persistent MAC address for vethfaf00a2: No such file or directory
Sep 23 17:29:11 sentry-docker00.cs.umd.edu systemd-udevd[2317269]: Could not generate persistent MAC address for veth8f55531: No such file or directory
Sep 23 17:29:11 sentry-docker00.cs.umd.edu systemd-udevd[2317264]: Could not generate persistent MAC address for veth6342246: No such file or directory
Sep 23 17:29:11 sentry-docker00.cs.umd.edu systemd-udevd[2317274]: Could not generate persistent MAC address for vethe5173a4: No such file or directory
Sep 23 17:49:19 sentry-docker00.cs.umd.edu systemd-udevd[2326607]: link_config: could not get ethtool features for veth90c40c8
Sep 23 17:49:19 sentry-docker00.cs.umd.edu systemd-udevd[2326607]: Could not set offload features of veth90c40c8: No such device
Sep 23 17:49:19 sentry-docker00.cs.umd.edu systemd-udevd[2326639]: Could not generate persistent MAC address for veth8cc0f14: No such file or directory
Sep 23 17:49:19 sentry-docker00.cs.umd.edu systemd-udevd[2326640]: Could not generate persistent MAC address for veth2d8813e: No such file or directory
Sep 23 17:49:19 sentry-docker00.cs.umd.edu systemd-udevd[2326643]: Could not generate persistent MAC address for vethb0f5704: No such file or directory
Sep 23 17:49:19 sentry-docker00.cs.umd.edu systemd-udevd[2326643]: Could not generate persistent MAC address for vethecd5675: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 23 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 23 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 23 17:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 23 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 23 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 23 17:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 23 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 2 total) ==
Sep 23 17:22:24 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f2 (1 distinct, 1 total) ==
Sep 23 17:49:18 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f3 (10 distinct, 13 total) ==
Sep 23 17:06:44 submit26-b9-f3 setroubleshoot[2803742]: 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 23 17:06:44 submit26-b9-f3 setroubleshoot[2803742]: 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 23 17:06:44 submit26-b9-f3 setroubleshoot[2803742]: 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 23 17:06:44 submit26-b9-f3 setroubleshoot[2803742]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Y4V0pz/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 23 17:06:44 submit26-b9-f3 setroubleshoot[2803742]: 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 23 17:06:44 submit26-b9-f3 setroubleshoot[2803742]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Y4V0pz. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 23 17:06:44 submit26-b9-f3 setroubleshoot[2803742]: 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 23 17:06:44 submit26-b9-f3 setroubleshoot[2803742]: 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 23 17:06:44 submit26-b9-f3 setroubleshoot[2803742]: 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 23 17:28:29 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f4 (10 distinct, 14 total) ==
Sep 23 17:05:50 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
Sep 23 17:24:48 submit26-b9-f4 setroubleshoot[2058183]: 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 23 17:24:48 submit26-b9-f4 setroubleshoot[2058183]: 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 23 17:24:48 submit26-b9-f4 setroubleshoot[2058183]: 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 23 17:24:48 submit26-b9-f4 setroubleshoot[2058183]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.xSI9H4/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2]
Sep 23 17:24:48 submit26-b9-f4 setroubleshoot[2058183]: 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 23 17:24:48 submit26-b9-f4 setroubleshoot[2058183]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xSI9H4. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 23 17:24:48 submit26-b9-f4 setroubleshoot[2058183]: 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 23 17:24:48 submit26-b9-f4 setroubleshoot[2058183]: 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 23 17:24:48 submit26-b9-f4 setroubleshoot[2058183]: 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