Command: /usr/local/sbin/syslog-digest.py
Time : 0.0518s
Status : exited 0
Output :
Syslog digest — 2026-09-20 03:05 EDT
Processed 2,618 lines, filtered 2,111 (80%). 507 unknown (180 distinct) from 16 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 20 02:51:46 b0b02.cs.umd.edu rustdesk[3106834]: cannot open display:
== bale (5 distinct, 91 total) ==
Sep 20 02:05:19 bale setroubleshoot[1037153]: failed to retrieve rpm info for /dev/nvme0 [x39]
Sep 20 02:05:19 bale setroubleshoot[1037153]: 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 20 02:05:22 bale setroubleshoot[1037153]: 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 20 02:05:25 bale setroubleshoot[1037153]: 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 20 02:05:37 bale setroubleshoot[1037781]: 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 (3 distinct, 4 total) ==
Sep 20 02:27:51 cheezit.cs.umd.edu sshd-session[1097677]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2]
Sep 20 02:27:52 cheezit.cs.umd.edu sshd-session[1097677]: Error in Duo login for 'larry' from 71.191.93.172
Sep 20 02:27:52 cheezit.cs.umd.edu sshd-session[1097675]: error: PAM: Authentication failure for larry from 71.191.93.172
== csfw00a (1 distinct, 118 total) ==
Sep 20 02:04:33 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x118]
== idm00 (1 distinct, 1 total) ==
Sep 20 02:53:59 idm00 named[4166701]: client @0x7f11a940bc18 10.73.240.42#50189: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 20 02:37:57 idmp0 named[1598691]: client @0x7f2d08d9fa18 10.73.240.43#53053: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 7 total) ==
Sep 20 02:14:04 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x7]
== munin (2 distinct, 12 total) ==
Sep 20 02:08:48 munin sudo[572901]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6]
Sep 20 02:08:48 munin sudo[572901]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6]
== newhonors2 (1 distinct, 24 total) ==
Sep 20 02:13:02 newhonors2 dhcpcd[2885098]: dhcpcd is not running [x24]
== ntop00 (101 distinct, 141 total) ==
Sep 20 02:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 442) ***
Sep 20 02:05:22 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 5757/5757, ET: 21) ***
Sep 20 02:05:22 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 49/49, ET: 21) ***
Sep 20 02:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 443) ***
Sep 20 02:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 5629/5629, ET: 0) ***
Sep 20 02:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 443) ***
Sep 20 02:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 49/49, ET: 0) ***
Sep 20 02:08:02 ntop00 setroubleshoot[745959]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x11]
Sep 20 02:08:02 ntop00 setroubleshoot[745959]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x11]
Sep 20 02:08:02 ntop00 setroubleshoot[745959]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11]
Sep 20 02:08:02 ntop00 setroubleshoot[745959]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x11]
Sep 20 02:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) ***
Sep 20 02:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) ***
Sep 20 02:10:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 5564/5564, ET: 20) ***
Sep 20 02:10:22 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 56/56, ET: 21) ***
Sep 20 02:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 445) ***
Sep 20 02:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 5625/5625, ET: 0) ***
Sep 20 02:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 445) ***
Sep 20 02:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 52/52, ET: 0) ***
Sep 20 02:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) ***
Sep 20 02:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) ***
Sep 20 02:15:25 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 6415/6415, ET: 24) ***
Sep 20 02:15:25 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 59/59, ET: 24) ***
Sep 20 02:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 447) ***
Sep 20 02:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 6410/6410, ET: 0) ***
Sep 20 02:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 447) ***
Sep 20 02:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 58/58, ET: 0) ***
Sep 20 02:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) ***
Sep 20 02:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) ***
Sep 20 02:20:24 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 448, QN: 5744/5744, ET: 23) ***
... 71 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 20 02:09:09 outbound00.cs.umd.edu python3[1891156]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 20 02:13:07 outbound01.cs.umd.edu python3[4150586]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023052]: link_config: could not get ethtool features for vethea6ed10
Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023052]: Could not set offload features of vethea6ed10: No such device
Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023076]: Could not generate persistent MAC address for vethc90f824: No such file or directory
Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023077]: Could not generate persistent MAC address for vethf5d320c: No such file or directory
Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023103]: Could not generate persistent MAC address for veth9f332ed: No such file or directory
Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023102]: Could not generate persistent MAC address for veth8b62113: No such file or directory
Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023106]: Could not generate persistent MAC address for vethe6f8718: No such file or directory
Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023103]: Could not generate persistent MAC address for vethc3e4bac: No such file or directory
Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023111]: Could not generate persistent MAC address for vethd15a99f: No such file or directory
Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023128]: Could not generate persistent MAC address for vethf98393d: No such file or directory
Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023166]: Could not generate persistent MAC address for veth0c9f9ef: No such file or directory
Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023171]: Could not generate persistent MAC address for veth47f5349: No such file or directory
Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032760]: link_config: could not get ethtool features for veth8b62113
Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032760]: Could not set offload features of veth8b62113: No such device
Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032793]: Could not generate persistent MAC address for veth66999bf: No such file or directory
Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032794]: Could not generate persistent MAC address for veth4a6a482: No such file or directory
Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032797]: Could not generate persistent MAC address for veth403e6e4: No such file or directory
Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032798]: Could not generate persistent MAC address for veth1ebf4dc: No such file or directory
Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032821]: Could not generate persistent MAC address for veth1a87588: No such file or directory
Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032822]: Could not generate persistent MAC address for veth2d130fa: No such file or directory
Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032831]: Could not generate persistent MAC address for veth8fde257: No such file or directory
Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032839]: Could not generate persistent MAC address for vethe67695f: No such file or directory
Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032861]: Could not generate persistent MAC address for vethe5523a8: No such file or directory
Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032862]: Could not generate persistent MAC address for vethf24ee46: No such file or directory
Sep 20 02:53:24 sentry-docker00.cs.umd.edu systemd-udevd[4042411]: link_config: could not get ethtool features for vethe67695f
Sep 20 02:53:24 sentry-docker00.cs.umd.edu systemd-udevd[4042411]: Could not set offload features of vethe67695f: No such device
Sep 20 02:53:24 sentry-docker00.cs.umd.edu systemd-udevd[4042446]: Could not generate persistent MAC address for vethda77f66: No such file or directory
Sep 20 02:53:24 sentry-docker00.cs.umd.edu systemd-udevd[4042447]: Could not generate persistent MAC address for veth7126878: No such file or directory
Sep 20 02:53:24 sentry-docker00.cs.umd.edu systemd-udevd[4042450]: Could not generate persistent MAC address for vethf1fd103: No such file or directory
Sep 20 02:53:24 sentry-docker00.cs.umd.edu systemd-udevd[4042451]: Could not generate persistent MAC address for vetha8813ef: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 20 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 20 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 20 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 20 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 20 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 20 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 20 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 20 02:25:53 submit26-b9-f1 setroubleshoot[2561421]: 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 20 02:25:53 submit26-b9-f1 setroubleshoot[2561421]: 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 20 02:25:53 submit26-b9-f1 setroubleshoot[2561421]: 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 20 02:25:54 submit26-b9-f1 setroubleshoot[2561421]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.aRSEiE/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 20 02:25:54 submit26-b9-f1 setroubleshoot[2561421]: 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 20 02:25:54 submit26-b9-f1 setroubleshoot[2561421]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.aRSEiE. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 20 02:25:54 submit26-b9-f1 setroubleshoot[2561421]: 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 20 02:25:54 submit26-b9-f1 setroubleshoot[2561421]: 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 20 02:25:54 submit26-b9-f1 setroubleshoot[2561421]: 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 (9 distinct, 12 total) ==
Sep 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: 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 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: 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 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: 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 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.lRft7C/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2]
Sep 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: 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 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.lRft7C. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: 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 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: 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 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: 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
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0535s
Status : exited 0
Output :
Syslog digest — 2026-09-20 02:05 EDT
Processed 2,716 lines, filtered 2,199 (80%). 517 unknown (190 distinct) from 20 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 20 01:51:42 b0b02.cs.umd.edu rustdesk[3091615]: cannot open display:
== bale (5 distinct, 86 total) ==
Sep 20 01:05:22 bale setroubleshoot[1024266]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 20 01:05:22 bale setroubleshoot[1024266]: 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 20 01:05:25 bale setroubleshoot[1024266]: 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 20 01:05:28 bale setroubleshoot[1024266]: 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 20 01:05:40 bale setroubleshoot[1024895]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x13]
== cheezit.cs.umd.edu (3 distinct, 8 total) ==
Sep 20 01:27:14 cheezit.cs.umd.edu sshd-session[1083975]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x4]
Sep 20 01:27:15 cheezit.cs.umd.edu sshd-session[1083975]: Error in Duo login for 'larry' from 71.191.93.172 [x2]
Sep 20 01:27:15 cheezit.cs.umd.edu sshd-session[1083973]: error: PAM: Authentication failure for larry from 71.191.93.172 [x2]
== cmsc436-0101-redis (3 distinct, 3 total) ==
Sep 20 01:15:54 cmsc436-0101-redis krb5_child[3310880]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 20 01:15:55 cmsc436-0101-redis sshd-session[3310876]: error: PAM: Authentication failure for admin from 34.14.2.117
Sep 20 01:19:40 cmsc436-0101-redis sshd-session[3310928]: error: Protocol major versions differ: 2 vs. 1
== csfw00a (1 distinct, 122 total) ==
Sep 20 01:04:19 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x122]
== idm00 (1 distinct, 1 total) ==
Sep 20 01:53:59 idm00 named[4166701]: client @0x7f11a8045438 10.73.240.42#51806: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 20 01:37:57 idmp0 named[1598691]: client @0x7f2d4c005288 10.73.240.43#49346: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 1 total) ==
Sep 20 01:33:30 itmon02 sshd[1750555]: error: beginning MaxStartups throttling
== matrix (3 distinct, 4 total) ==
Sep 20 01:22:38 matrix krb5_child[2806538]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 20 01:22:40 matrix sshd[2806532]: error: PAM: Authentication failure for admin from 207.175.45.86
Sep 20 01:22:54 matrix sshd[2806656]: error: Protocol major versions differ: 2 vs. 1
== munin (2 distinct, 10 total) ==
Sep 20 01:23:53 munin sudo[555270]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x5]
Sep 20 01:23:53 munin sudo[555270]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x5]
== newhonors2 (1 distinct, 24 total) ==
Sep 20 01:13:03 newhonors2 dhcpcd[2883239]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 20 01:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 418) ***
Sep 20 01:05:24 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 6018/6018, ET: 23) ***
Sep 20 01:05:25 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 53/53, ET: 24) ***
Sep 20 01:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 419) ***
Sep 20 01:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 6166/6166, ET: 0) ***
Sep 20 01:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 419) ***
Sep 20 01:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 50/50, ET: 0) ***
Sep 20 01:08:02 ntop00 setroubleshoot[737926]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 20 01:08:02 ntop00 setroubleshoot[737926]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 20 01:08:02 ntop00 setroubleshoot[737926]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 20 01:08:02 ntop00 setroubleshoot[737926]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 20 01:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) ***
Sep 20 01:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) ***
Sep 20 01:10:26 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 6326/6326, ET: 25) ***
Sep 20 01:10:26 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 59/59, ET: 25) ***
Sep 20 01:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 421) ***
Sep 20 01:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 6601/6601, ET: 0) ***
Sep 20 01:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 421) ***
Sep 20 01:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 66/66, ET: 0) ***
Sep 20 01:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) ***
Sep 20 01:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) ***
Sep 20 01:15:25 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 6436/6436, ET: 24) ***
Sep 20 01:15:26 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 69/69, ET: 25) ***
Sep 20 01:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 423) ***
Sep 20 01:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 6144/6144, ET: 0) ***
Sep 20 01:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 423) ***
Sep 20 01:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 77/77, ET: 0) ***
Sep 20 01:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) ***
Sep 20 01:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) ***
Sep 20 01:20:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 6059/6059, ET: 22) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 20 01:09:09 outbound00.cs.umd.edu python3[1877187]: ldapdb [x6]
== outbound01.cs.umd.edu (2 distinct, 7 total) ==
Sep 20 01:13:06 outbound01.cs.umd.edu python3[4136449]: ldapdb [x6]
Sep 20 01:24:50 outbound01.cs.umd.edu krb5_child[4138810]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994602]: link_config: could not get ethtool features for vetha1a9337
Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994602]: Could not set offload features of vetha1a9337: No such device
Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994637]: Could not generate persistent MAC address for vethf2bfa3a: No such file or directory
Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994638]: Could not generate persistent MAC address for vethd34b8b5: No such file or directory
Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994641]: Could not generate persistent MAC address for veth7d52270: No such file or directory
Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994642]: Could not generate persistent MAC address for veth1028cdc: No such file or directory
Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994665]: Could not generate persistent MAC address for vethfeb600d: No such file or directory
Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994666]: Could not generate persistent MAC address for veth15d554a: No such file or directory
Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994691]: Could not generate persistent MAC address for vethfbd2cf8: No such file or directory
Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994692]: Could not generate persistent MAC address for veth2636677: No such file or directory
Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994710]: Could not generate persistent MAC address for veth8171b73: No such file or directory
Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994716]: Could not generate persistent MAC address for veth769d04d: No such file or directory
Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004148]: link_config: could not get ethtool features for vethfbd2cf8
Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004148]: Could not set offload features of vethfbd2cf8: No such device
Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004263]: Could not generate persistent MAC address for veth59b8582: No such file or directory
Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004264]: Could not generate persistent MAC address for veth816cb6b: No such file or directory
Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004289]: Could not generate persistent MAC address for veth9d0b1b9: No such file or directory
Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004290]: Could not generate persistent MAC address for veth8503f3b: No such file or directory
Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004290]: Could not generate persistent MAC address for veth226976c: No such file or directory
Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004295]: Could not generate persistent MAC address for veth4f7810c: No such file or directory
Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004317]: Could not generate persistent MAC address for veth6ed228a: No such file or directory
Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004318]: Could not generate persistent MAC address for veth349d1a7: No such file or directory
Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004334]: Could not generate persistent MAC address for veth22bc751: No such file or directory
Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004362]: Could not generate persistent MAC address for vethcf29f74: No such file or directory
Sep 20 01:52:59 sentry-docker00.cs.umd.edu systemd-udevd[4013639]: link_config: could not get ethtool features for veth59b8582
Sep 20 01:52:59 sentry-docker00.cs.umd.edu systemd-udevd[4013639]: Could not set offload features of veth59b8582: No such device
Sep 20 01:52:59 sentry-docker00.cs.umd.edu systemd-udevd[4013641]: link_config: could not get ethtool features for veth6ed228a
Sep 20 01:52:59 sentry-docker00.cs.umd.edu systemd-udevd[4013641]: Could not set offload features of veth6ed228a: No such device
Sep 20 01:53:00 sentry-docker00.cs.umd.edu systemd-udevd[4013672]: Could not generate persistent MAC address for veth408adde: No such file or directory
Sep 20 01:53:00 sentry-docker00.cs.umd.edu systemd-udevd[4013673]: Could not generate persistent MAC address for veth8860a5b: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 20 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 20 01:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 20 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 20 01:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 20 01:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 20 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 20 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 1 total) ==
Sep 20 01:13:08 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f3 (9 distinct, 12 total) ==
Sep 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Fv5kj7/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f [x2]
Sep 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Fv5kj7. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.BSLo5X/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.BSLo5X. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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
== tma-0 (1 distinct, 1 total) ==
Sep 20 01:54:55 tma-0 sshd[7248]: error: PAM: Authentication failure for admin from 107.116.79.34.bc.googleusercontent.com
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0576s
Status : exited 0
Output :
Syslog digest — 2026-09-20 01:05 EDT
Processed 2,817 lines, filtered 2,143 (76%). 674 unknown (231 distinct) from 39 host(s).
== abuse (3 distinct, 4 total) ==
Sep 20 00:10:12 abuse systemd[1]: New main PID 3886 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 20 00:10:31 abuse systemd[1]: Daemon never wrote its PID file. Failing.
Sep 20 00:10:41 abuse systemd[1]: pmlogger.service: Supervising process 10974 which is not our child. We'll most likely not notice when it exits.
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 20 00:51:38 b0b02.cs.umd.edu rustdesk[3076428]: cannot open display:
== bale (5 distinct, 85 total) ==
Sep 20 00:06:07 bale setroubleshoot[1011056]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 20 00:06:08 bale setroubleshoot[1011056]: 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 20 00:06:10 bale setroubleshoot[1011056]: 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 20 00:06:13 bale setroubleshoot[1011056]: 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 20 00:06:25 bale setroubleshoot[1011672]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x13]
== csfw00a (1 distinct, 127 total) ==
Sep 20 00:04:06 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x127]
== forge00 (1 distinct, 1 total) ==
Sep 20 00:14:11 forge00 (httpd)[347884]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== grades01.cs.umd.edu (3 distinct, 4 total) ==
Sep 20 00:10:13 grades01.cs.umd.edu systemd[1]: New main PID 31238 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 20 00:10:34 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 20 00:10:49 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 6291 which is not our child. We'll most likely not notice when it exits.
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Sep 20 00:54:30 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 20 00:54:30 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 20 00:54:30 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 20 00:54:30 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 20 00:54:30 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 20 00:54:30 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 20 00:54:30 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 20 00:54:30 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 20 00:54:30 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 20 00:54:30 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 20 00:54:30 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 20 00:53:59 idm00 named[4166701]: client @0x7f11a0000cc8 10.73.240.42#63016: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 20 00:37:57 idmp0 named[1598691]: client @0x7f2d500408e8 10.73.240.43#54949: update '73.10.in-addr.arpa/IN' denied
== inbound01.cs.umd.edu (2 distinct, 2 total) ==
Sep 20 00:05:10 inbound01.cs.umd.edu krb5_child[16948]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 20 00:06:29 inbound01.cs.umd.edu sshd-session[17362]: error: Protocol major versions differ: 2 vs. 1
== itmon02 (2 distinct, 4 total) ==
Sep 20 00:23:47 itmon02 (httpd)[3098653]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
Sep 20 00:33:02 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3]
== jubjub.cs.umd.edu (3 distinct, 4 total) ==
Sep 20 00:10:12 jubjub.cs.umd.edu systemd[1]: New main PID 3620222 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 20 00:10:32 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 20 00:10:40 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3627759 which is not our child. We'll most likely not notice when it exits.
== krispykreme.cs.umd.edu (4 distinct, 4 total) ==
Sep 20 00:32:45 krispykreme.cs.umd.edu sshd-session[107870]: pam_access(sshd:auth): access denied for user `admin' from `207.175.122.208'
Sep 20 00:32:45 krispykreme.cs.umd.edu krb5_child[107872]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 20 00:32:45 krispykreme.cs.umd.edu sshd-session[107868]: error: PAM: System error for admin from 207.175.122.208
Sep 20 00:32:54 krispykreme.cs.umd.edu sshd-session[107880]: error: Protocol major versions differ: 2 vs. 1
== librenms (1 distinct, 1 total) ==
Sep 20 00:51:29 librenms (httpd)[205096]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== mirrors.cs.umd.edu (4 distinct, 6 total) ==
Sep 20 00:10:32 mirrors.cs.umd.edu root[25165]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log
Sep 20 00:10:32 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. [x2]
Sep 20 00:10:36 mirrors.cs.umd.edu systemd[1]: New main PID 24089 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 20 00:11:36 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 8488 which is not our child. We'll most likely not notice when it exits.
== misty.cs.umd.edu (3 distinct, 4 total) ==
Sep 20 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 27916 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 20 00:10:35 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 20 00:10:51 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 35753 which is not our child. We'll most likely not notice when it exits.
== munin (3 distinct, 53 total) ==
Sep 20 00:13:38 munin sudo[529663]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x26]
Sep 20 00:13:38 munin sudo[529663]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x26]
Sep 20 00:44:19 munin (httpd)[541924]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== netbox (1 distinct, 1 total) ==
Sep 20 00:24:06 netbox (httpd)[4022391]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== netman.cs.umd.edu (1 distinct, 2 total) ==
Sep 20 01:01:58 netman.cs.umd.edu krb5_child[2608106]: Preauthentication failed [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 20 00:13:03 newhonors2 dhcpcd[2881415]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 20 00:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 394) ***
Sep 20 00:05:20 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 394, QN: 5444/5444, ET: 19) ***
Sep 20 00:05:20 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 394, QN: 52/52, ET: 19) ***
Sep 20 00:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 395) ***
Sep 20 00:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 395, QN: 5826/5826, ET: 0) ***
Sep 20 00:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 395) ***
Sep 20 00:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 395, QN: 55/55, ET: 0) ***
Sep 20 00:08:02 ntop00 setroubleshoot[730036]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 20 00:08:02 ntop00 setroubleshoot[730036]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 20 00:08:02 ntop00 setroubleshoot[730036]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 20 00:08:02 ntop00 setroubleshoot[730036]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 20 00:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 396) ***
Sep 20 00:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 396) ***
Sep 20 00:10:25 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 396, QN: 5862/5862, ET: 24) ***
Sep 20 00:10:25 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 396, QN: 55/55, ET: 24) ***
Sep 20 00:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 397) ***
Sep 20 00:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 397, QN: 5742/5742, ET: 0) ***
Sep 20 00:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 397) ***
Sep 20 00:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 397, QN: 55/55, ET: 0) ***
Sep 20 00:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 398) ***
Sep 20 00:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 398) ***
Sep 20 00:15:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 398, QN: 5692/5692, ET: 22) ***
Sep 20 00:15:24 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 398, QN: 54/54, ET: 23) ***
Sep 20 00:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 399) ***
Sep 20 00:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 399, QN: 5493/5493, ET: 0) ***
Sep 20 00:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 399) ***
Sep 20 00:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 399, QN: 58/58, ET: 0) ***
Sep 20 00:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 400) ***
Sep 20 00:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 400) ***
Sep 20 00:20:22 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 400, QN: 5394/5394, ET: 21) ***
... 70 more distinct messages not shown
== openrepo (1 distinct, 1 total) ==
Sep 20 00:52:53 openrepo (nin-node)[3104019]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== openvox08-board (1 distinct, 1 total) ==
Sep 20 00:10:00 openvox08-board (httpd)[1632163]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 20 00:09:09 outbound00.cs.umd.edu python3[1862668]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 20 00:13:07 outbound01.cs.umd.edu python3[4122430]: ldapdb [x6]
== portal (1 distinct, 1 total) ==
Sep 20 00:47:13 portal (httpd)[1759209]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 20 00:12:18 sentry-docker00.cs.umd.edu systemd-udevd[3966271]: link_config: could not get ethtool features for vethd95ba3e
Sep 20 00:12:18 sentry-docker00.cs.umd.edu systemd-udevd[3966271]: Could not set offload features of vethd95ba3e: No such device
Sep 20 00:12:18 sentry-docker00.cs.umd.edu systemd-udevd[3966306]: Could not generate persistent MAC address for veth39db475: No such file or directory
Sep 20 00:12:18 sentry-docker00.cs.umd.edu systemd-udevd[3966307]: Could not generate persistent MAC address for veth884d530: No such file or directory
Sep 20 00:12:18 sentry-docker00.cs.umd.edu systemd-udevd[3966310]: Could not generate persistent MAC address for veth4314f93: No such file or directory
Sep 20 00:12:18 sentry-docker00.cs.umd.edu systemd-udevd[3966311]: Could not generate persistent MAC address for veth6e170c7: No such file or directory
Sep 20 00:12:18 sentry-docker00.cs.umd.edu systemd-udevd[3966320]: Could not generate persistent MAC address for veth104a721: No such file or directory
Sep 20 00:12:18 sentry-docker00.cs.umd.edu systemd-udevd[3966317]: Could not generate persistent MAC address for veth57f956b: No such file or directory
Sep 20 00:12:18 sentry-docker00.cs.umd.edu systemd-udevd[3966320]: Could not generate persistent MAC address for veth3be71a5: No such file or directory
Sep 20 00:12:18 sentry-docker00.cs.umd.edu systemd-udevd[3966326]: Could not generate persistent MAC address for vethff0eea8: No such file or directory
Sep 20 00:12:18 sentry-docker00.cs.umd.edu systemd-udevd[3966316]: Could not generate persistent MAC address for veth4dab85b: No such file or directory
Sep 20 00:12:18 sentry-docker00.cs.umd.edu systemd-udevd[3966325]: Could not generate persistent MAC address for vethf08d475: No such file or directory
Sep 20 00:32:26 sentry-docker00.cs.umd.edu systemd-udevd[3975746]: link_config: could not get ethtool features for veth4314f93
Sep 20 00:32:26 sentry-docker00.cs.umd.edu systemd-udevd[3975746]: Could not set offload features of veth4314f93: No such device
Sep 20 00:32:26 sentry-docker00.cs.umd.edu systemd-udevd[3975775]: Could not generate persistent MAC address for vethbeeac20: No such file or directory
Sep 20 00:32:26 sentry-docker00.cs.umd.edu systemd-udevd[3975776]: Could not generate persistent MAC address for veth267823b: No such file or directory
Sep 20 00:32:26 sentry-docker00.cs.umd.edu systemd-udevd[3975794]: Could not generate persistent MAC address for veth71287ce: No such file or directory
Sep 20 00:32:26 sentry-docker00.cs.umd.edu systemd-udevd[3975790]: Could not generate persistent MAC address for veth9a03109: No such file or directory
Sep 20 00:32:26 sentry-docker00.cs.umd.edu systemd-udevd[3975803]: Could not generate persistent MAC address for veth85bf60d: No such file or directory
Sep 20 00:32:26 sentry-docker00.cs.umd.edu systemd-udevd[3975804]: Could not generate persistent MAC address for veth3e1e46a: No such file or directory
Sep 20 00:32:26 sentry-docker00.cs.umd.edu systemd-udevd[3975829]: Could not generate persistent MAC address for veth641c09f: No such file or directory
Sep 20 00:32:26 sentry-docker00.cs.umd.edu systemd-udevd[3975830]: Could not generate persistent MAC address for vethb406d22: No such file or directory
Sep 20 00:32:26 sentry-docker00.cs.umd.edu systemd-udevd[3975848]: Could not generate persistent MAC address for veth78e8f3a: No such file or directory
Sep 20 00:32:26 sentry-docker00.cs.umd.edu systemd-udevd[3975830]: Could not generate persistent MAC address for veth8d2318f: No such file or directory
Sep 20 00:52:34 sentry-docker00.cs.umd.edu systemd-udevd[3985148]: link_config: could not get ethtool features for veth85bf60d
Sep 20 00:52:34 sentry-docker00.cs.umd.edu systemd-udevd[3985148]: Could not set offload features of veth85bf60d: No such device
Sep 20 00:52:35 sentry-docker00.cs.umd.edu systemd-udevd[3985184]: Could not generate persistent MAC address for vethd1595ba: No such file or directory
Sep 20 00:52:35 sentry-docker00.cs.umd.edu systemd-udevd[3985185]: Could not generate persistent MAC address for vethaa3dce1: No such file or directory
Sep 20 00:52:35 sentry-docker00.cs.umd.edu systemd-udevd[3985188]: Could not generate persistent MAC address for veth5607b01: No such file or directory
Sep 20 00:52:35 sentry-docker00.cs.umd.edu systemd-udevd[3985189]: Could not generate persistent MAC address for veth5d6a9cd: No such file or directory
... 6 more distinct messages not shown
== strawberry (8 distinct, 39 total) ==
Sep 20 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 20 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 20 00:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 20 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 20 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 20 00:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 20 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Sep 20 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing.
== submit10-cln25 (3 distinct, 4 total) ==
Sep 20 00:10:11 submit10-cln25 systemd: New main PID 5978 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 20 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing.
Sep 20 00:10:36 submit10-cln25 systemd: pmlogger.service: Supervising process 12879 which is not our child. We'll most likely not notice when it exits.
== submit26-b9-f1 (1 distinct, 3 total) ==
Sep 20 00:14:18 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f2 (1 distinct, 3 total) ==
Sep 20 00:30:25 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f3 (1 distinct, 3 total) ==
Sep 20 00:08:43 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 20 00:38:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-fclone (10 distinct, 14 total) ==
Sep 20 00:21:56 submit26-b9-fclone setroubleshoot[149023]: 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 [x2]
Sep 20 00:21:56 submit26-b9-fclone setroubleshoot[149023]: 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 [x2]
Sep 20 00:21:56 submit26-b9-fclone setroubleshoot[149023]: 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 20 00:21:56 submit26-b9-fclone setroubleshoot[149023]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.jHnPGt/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 20 00:21:56 submit26-b9-fclone setroubleshoot[149023]: 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 20 00:21:56 submit26-b9-fclone setroubleshoot[149023]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.jHnPGt. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 20 00:21:56 submit26-b9-fclone setroubleshoot[149023]: 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 [x2]
Sep 20 00:21:56 submit26-b9-fclone setroubleshoot[149023]: 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 20 00:21:56 submit26-b9-fclone setroubleshoot[149023]: 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 [x2]
Sep 20 00:21:57 submit26-b9-fclone setroubleshoot[149023]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.0LWwnS. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
== tlsrpt (1 distinct, 1 total) ==
Sep 20 00:05:06 tlsrpt (httpd)[2915308]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== tma-0 (3 distinct, 4 total) ==
Sep 20 00:10:13 tma-0 systemd[1]: New main PID 10912 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 20 00:10:30 tma-0 systemd[1]: Daemon never wrote its PID file. Failing.
Sep 20 00:10:38 tma-0 systemd[1]: pmlogger.service: Supervising process 18537 which is not our child. We'll most likely not notice when it exits.
== uffish.cs.umd.edu (3 distinct, 4 total) ==
Sep 20 00:10:12 uffish.cs.umd.edu systemd[1]: New main PID 2039095 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 20 00:10:39 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 20 00:10:56 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 2046595 which is not our child. We'll most likely not notice when it exits.
== vacuum.cs.umd.edu (3 distinct, 4 total) ==
Sep 20 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 2188 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 20 00:10:33 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 20 00:10:44 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 9848 which is not our child. We'll most likely not notice when it exits.
== whiffle.cs.umd.edu (3 distinct, 4 total) ==
Sep 20 00:10:13 whiffle.cs.umd.edu systemd[1]: New main PID 1598856 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 20 00:10:38 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 20 00:10:52 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1606310 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.0536s
Status : exited 0
Output :
Syslog digest — 2026-09-20 00:05 EDT
Processed 2,752 lines, filtered 2,223 (80%). 529 unknown (183 distinct) from 29 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 23:51:35 b0b02.cs.umd.edu rustdesk[3060234]: cannot open display:
== bale (5 distinct, 92 total) ==
Sep 19 23:05:09 bale setroubleshoot[998307]: failed to retrieve rpm info for /dev/nvme0 [x40]
Sep 19 23:05:10 bale setroubleshoot[998307]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12]
Sep 19 23:05:12 bale setroubleshoot[998307]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12]
Sep 19 23:05:16 bale setroubleshoot[998307]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12]
Sep 19 23:05:27 bale setroubleshoot[998923]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x16]
== biggulp.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 23:30:41 biggulp.cs.umd.edu sshd-session[2675751]: error: send_error: write: Connection reset by peer [x6]
== borogove.cs.umd.edu (2 distinct, 2 total) ==
Sep 20 00:00:02 borogove.cs.umd.edu rsyslogd[1921]: imfile: internal error? inotify provided watch descriptor 364 which we could not find in our tables - ignored [v8.2510.0-2.el9 try https://www.rsyslog.com/e/2175 ]
Sep 20 00:00:02 borogove.cs.umd.edu rsyslogd[1921]: imfile: internal error? inotify provided watch descriptor 348 which we could not find in our tables - ignored [v8.2510.0-2.el9 try https://www.rsyslog.com/e/2175 ]
== cheezit.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 23:30:42 cheezit.cs.umd.edu sshd-session[1055719]: error: send_error: write: Connection reset by peer
== csfw00a (1 distinct, 125 total) ==
Sep 19 23:04:02 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x125]
== cskayako (2 distinct, 2 total) ==
Sep 20 00:00:08 cskayako setroubleshoot[883754]: failed to retrieve rpm info for path '/var/log/php82-fpm_error.log':
Sep 20 00:00:09 cskayako setroubleshoot[883754]: SELinux is preventing /opt/remi/php82/root/usr/sbin/php-fpm from open access on the file /var/log/php82-fpm_error.log. For complete SELinux messages run: sealert -l 0ba5d5da-2df6-4c48-bd39-9b458b25a6cc
== hspc (1 distinct, 1 total) ==
Sep 20 00:00:00 hspc kernel: kauditd_printk_skb: 4 callbacks suppressed
== idm00 (2 distinct, 5 total) ==
Sep 19 23:53:59 idm00 named[4166701]: client @0x7f11a00432a8 10.73.240.42#63012: update '73.10.in-addr.arpa/IN' denied
Sep 20 00:00:01 idm00 named[4166701]: checkhints: unable to get root NS rrset from cache: not found [x4]
== idmh1 (1 distinct, 2 total) ==
Sep 20 00:00:00 idmh1 named[3565631]: checkhints: unable to get root NS rrset from cache: not found [x2]
== idmp0 (2 distinct, 3 total) ==
Sep 19 23:37:57 idmp0 named[1598691]: client @0x7f2d3c076558 10.73.240.43#60574: update '73.10.in-addr.arpa/IN' denied
Sep 20 00:00:01 idmp0 named[1598691]: checkhints: unable to get root NS rrset from cache: not found [x2]
== idmv0 (1 distinct, 2 total) ==
Sep 20 00:00:06 idmv0 named[3973338]: checkhints: unable to get root NS rrset from cache: not found [x2]
== itmon02 (1 distinct, 2 total) ==
Sep 19 23:08:43 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2]
== matrix (1 distinct, 1 total) ==
Sep 20 00:00:25 matrix (nin-node)[2757592]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== munin (2 distinct, 14 total) ==
Sep 19 23:08:44 munin sudo[506107]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x7]
Sep 19 23:08:44 munin sudo[506107]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x7]
== neo-gizmonic (1 distinct, 1 total) ==
Sep 20 00:00:01 neo-gizmonic (nin-node)[1780188]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neoavion (1 distinct, 1 total) ==
Sep 20 00:00:22 neoavion (nin-node)[3672118]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== newhonors2 (2 distinct, 25 total) ==
Sep 19 23:13:02 newhonors2 dhcpcd[2879354]: dhcpcd is not running [x24]
Sep 20 00:00:16 newhonors2 (nin-node)[2880869]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== ntop00 (100 distinct, 140 total) ==
Sep 19 23:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 370) ***
Sep 19 23:05:20 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 370, QN: 5374/5374, ET: 19) ***
Sep 19 23:05:20 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 370, QN: 48/48, ET: 19) ***
Sep 19 23:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 371) ***
Sep 19 23:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 371, QN: 5562/5562, ET: 0) ***
Sep 19 23:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 371) ***
Sep 19 23:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 371, QN: 53/53, ET: 0) ***
Sep 19 23:08:02 ntop00 setroubleshoot[722178]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x11]
Sep 19 23:08:02 ntop00 setroubleshoot[722178]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x11]
Sep 19 23:08:02 ntop00 setroubleshoot[722178]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11]
Sep 19 23:08:02 ntop00 setroubleshoot[722178]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x11]
Sep 19 23:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 372) ***
Sep 19 23:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 372) ***
Sep 19 23:10:22 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 372, QN: 5747/5747, ET: 21) ***
Sep 19 23:10:22 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 372, QN: 52/52, ET: 21) ***
Sep 19 23:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 373) ***
Sep 19 23:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 373, QN: 5802/5802, ET: 0) ***
Sep 19 23:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 373) ***
Sep 19 23:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 373, QN: 48/48, ET: 0) ***
Sep 19 23:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 374) ***
Sep 19 23:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 374) ***
Sep 19 23:15:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 374, QN: 5742/5742, ET: 22) ***
Sep 19 23:15:23 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 374, QN: 52/52, ET: 22) ***
Sep 19 23:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 375) ***
Sep 19 23:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 375, QN: 5571/5571, ET: 0) ***
Sep 19 23:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 375) ***
Sep 19 23:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 375, QN: 54/54, ET: 0) ***
Sep 19 23:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 376) ***
Sep 19 23:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 376) ***
Sep 19 23:20:22 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 376, QN: 5704/5704, ET: 21) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (2 distinct, 7 total) ==
Sep 19 23:09:09 outbound00.cs.umd.edu python3[1848457]: ldapdb [x6]
Sep 19 23:35:31 outbound00.cs.umd.edu krb5_child[1854519]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== outbound01.cs.umd.edu (3 distinct, 9 total) ==
Sep 19 23:06:46 outbound01.cs.umd.edu krb5_child[4106436]: Preauthentication failed
Sep 19 23:10:22 outbound01.cs.umd.edu krb5_child[4106873]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 19 23:13:06 outbound01.cs.umd.edu python3[4107635]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 19 23:11:53 sentry-docker00.cs.umd.edu systemd-udevd[3937976]: link_config: could not get ethtool features for veth77b3a30
Sep 19 23:11:53 sentry-docker00.cs.umd.edu systemd-udevd[3937976]: Could not set offload features of veth77b3a30: No such device
Sep 19 23:11:53 sentry-docker00.cs.umd.edu systemd-udevd[3938010]: Could not generate persistent MAC address for veth222a56a: No such file or directory
Sep 19 23:11:53 sentry-docker00.cs.umd.edu systemd-udevd[3938011]: Could not generate persistent MAC address for veth02ca4b5: No such file or directory
Sep 19 23:11:53 sentry-docker00.cs.umd.edu systemd-udevd[3938014]: Could not generate persistent MAC address for veth0486ef9: No such file or directory
Sep 19 23:11:53 sentry-docker00.cs.umd.edu systemd-udevd[3938015]: Could not generate persistent MAC address for veth2faa212: No such file or directory
Sep 19 23:11:53 sentry-docker00.cs.umd.edu systemd-udevd[3938038]: Could not generate persistent MAC address for veth8a77e2d: No such file or directory
Sep 19 23:11:53 sentry-docker00.cs.umd.edu systemd-udevd[3938040]: Could not generate persistent MAC address for veth1c5e334: No such file or directory
Sep 19 23:11:53 sentry-docker00.cs.umd.edu systemd-udevd[3938058]: Could not generate persistent MAC address for vethd20f1bc: No such file or directory
Sep 19 23:11:53 sentry-docker00.cs.umd.edu systemd-udevd[3938044]: Could not generate persistent MAC address for veth5549488: No such file or directory
Sep 19 23:11:53 sentry-docker00.cs.umd.edu systemd-udevd[3938087]: Could not generate persistent MAC address for veth3efc33f: No such file or directory
Sep 19 23:11:53 sentry-docker00.cs.umd.edu systemd-udevd[3938085]: Could not generate persistent MAC address for veth7d12052: No such file or directory
Sep 19 23:32:01 sentry-docker00.cs.umd.edu systemd-udevd[3947402]: link_config: could not get ethtool features for veth7d12052
Sep 19 23:32:01 sentry-docker00.cs.umd.edu systemd-udevd[3947402]: Could not set offload features of veth7d12052: No such device
Sep 19 23:32:01 sentry-docker00.cs.umd.edu systemd-udevd[3947441]: Could not generate persistent MAC address for veth2810ce2: No such file or directory
Sep 19 23:32:01 sentry-docker00.cs.umd.edu systemd-udevd[3947442]: Could not generate persistent MAC address for veth3b649d6: No such file or directory
Sep 19 23:32:01 sentry-docker00.cs.umd.edu systemd-udevd[3947445]: Could not generate persistent MAC address for vethbaf27e5: No such file or directory
Sep 19 23:32:01 sentry-docker00.cs.umd.edu systemd-udevd[3947446]: Could not generate persistent MAC address for vetheddb1b8: No such file or directory
Sep 19 23:32:01 sentry-docker00.cs.umd.edu systemd-udevd[3947469]: Could not generate persistent MAC address for vethdfeb2c1: No such file or directory
Sep 19 23:32:01 sentry-docker00.cs.umd.edu systemd-udevd[3947470]: Could not generate persistent MAC address for vethe321e15: No such file or directory
Sep 19 23:32:01 sentry-docker00.cs.umd.edu systemd-udevd[3947480]: Could not generate persistent MAC address for veth5f72020: No such file or directory
Sep 19 23:32:01 sentry-docker00.cs.umd.edu systemd-udevd[3947492]: Could not generate persistent MAC address for veth13fb2ab: No such file or directory
Sep 19 23:32:01 sentry-docker00.cs.umd.edu systemd-udevd[3947488]: Could not generate persistent MAC address for veth0f8d439: No such file or directory
Sep 19 23:32:01 sentry-docker00.cs.umd.edu systemd-udevd[3947480]: Could not generate persistent MAC address for vethc6b4c0c: No such file or directory
Sep 19 23:52:09 sentry-docker00.cs.umd.edu systemd-udevd[3956827]: link_config: could not get ethtool features for veth2810ce2
Sep 19 23:52:09 sentry-docker00.cs.umd.edu systemd-udevd[3956827]: Could not set offload features of veth2810ce2: No such device
Sep 19 23:52:10 sentry-docker00.cs.umd.edu systemd-udevd[3956860]: Could not generate persistent MAC address for veth143d181: No such file or directory
Sep 19 23:52:10 sentry-docker00.cs.umd.edu systemd-udevd[3956861]: Could not generate persistent MAC address for veth2ea14dd: No such file or directory
Sep 19 23:52:10 sentry-docker00.cs.umd.edu systemd-udevd[3956864]: Could not generate persistent MAC address for veth7c63c78: No such file or directory
Sep 19 23:52:10 sentry-docker00.cs.umd.edu systemd-udevd[3956865]: Could not generate persistent MAC address for veth832ed41: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 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 19 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 19 23:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 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 19 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 19 23:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 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 19 23:38:07 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 19 23:53:48 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f3 (1 distinct, 3 total) ==
Sep 19 23:17:36 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f4 (1 distinct, 4 total) ==
Sep 19 23:08:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== test-ipv6 (1 distinct, 1 total) ==
Sep 20 00:00:06 test-ipv6 named[1015]: managed-keys-zone: Unable to fetch DNSKEY set '.': operation canceled
== wraith (2 distinct, 2 total) ==
Sep 20 00:00:00 wraith kernel: kauditd_printk_skb: 2 callbacks suppressed
Sep 20 00:00:01 wraith (nin-node)[763367]: 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.0527s
Status : exited 0
Output :
Syslog digest — 2026-09-19 23:05 EDT
Processed 2,618 lines, filtered 2,084 (79%). 534 unknown (199 distinct) from 21 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 22:51:31 b0b02.cs.umd.edu rustdesk[3045031]: cannot open display:
== bale (5 distinct, 86 total) ==
Sep 19 22:05:09 bale setroubleshoot[985556]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 19 22:05:10 bale setroubleshoot[985556]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12]
Sep 19 22:05:13 bale setroubleshoot[985556]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12]
Sep 19 22:05:16 bale setroubleshoot[985556]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12]
Sep 19 22:05:27 bale setroubleshoot[986172]: 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 (6 distinct, 7 total) ==
Sep 19 22:08:01 biggulp.cs.umd.edu sshd-session[2661875]: pam_access(sshd:auth): access denied for user `admin' from `34.78.143.65'
Sep 19 22:08:03 biggulp.cs.umd.edu krb5_child[2661890]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 19 22:08:03 biggulp.cs.umd.edu sshd-session[2661872]: error: PAM: System error for admin from 34.78.143.65
Sep 19 22:08:35 biggulp.cs.umd.edu sshd-session[2661915]: pam_access(sshd:auth): access denied for user `admin' from `146.148.113.204'
Sep 19 22:08:37 biggulp.cs.umd.edu sshd-session[2661907]: error: PAM: System error for admin from 146.148.113.204
Sep 19 22:09:29 biggulp.cs.umd.edu sshd-session[2661979]: error: Protocol major versions differ: 2 vs. 1
== csfw00a (1 distinct, 133 total) ==
Sep 19 22:04:22 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x133]
== idm00 (1 distinct, 1 total) ==
Sep 19 22:53:59 idm00 named[4166701]: client @0x7f1198074538 10.73.240.42#56959: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 22:37:57 idmp0 named[1598691]: client @0x7f2d20030738 10.73.240.43#60129: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 19 22:23:05 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3]
== munin (2 distinct, 2 total) ==
Sep 19 23:03:41 munin sudo[504453]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory
Sep 19 23:03:41 munin sudo[504453]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order.
== netman.cs.umd.edu (3 distinct, 6 total) ==
Sep 19 22:05:37 netman.cs.umd.edu krb5_child[2558877]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Sep 19 22:05:44 netman.cs.umd.edu sshd[2558872]: error: PAM: Authentication failure for admin from 34.79.116.107
Sep 19 22:10:40 netman.cs.umd.edu sshd[2559669]: error: Protocol major versions differ: 2 vs. 1
== newhonors.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 22:58: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 19 22:13:03 newhonors2 dhcpcd[2877515]: dhcpcd is not running [x24]
== ntop00 (101 distinct, 145 total) ==
Sep 19 22:05:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 346) ***
Sep 19 22:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 346) ***
Sep 19 22:05:24 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 6048/6048, ET: 23) ***
Sep 19 22:05:24 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 59/59, ET: 23) ***
Sep 19 22:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 347) ***
Sep 19 22:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 5963/5963, ET: 0) ***
Sep 19 22:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 347) ***
Sep 19 22:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 62/62, ET: 0) ***
Sep 19 22:08:02 ntop00 setroubleshoot[714301]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 22:08:02 ntop00 setroubleshoot[714301]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 22:08:02 ntop00 setroubleshoot[714301]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 22:08:02 ntop00 setroubleshoot[714301]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 22:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) ***
Sep 19 22:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) ***
Sep 19 22:10:22 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 5895/5895, ET: 21) ***
Sep 19 22:10:22 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 67/67, ET: 21) ***
Sep 19 22:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 349) ***
Sep 19 22:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 5694/5694, ET: 0) ***
Sep 19 22:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 349) ***
Sep 19 22:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 61/61, ET: 0) ***
Sep 19 22:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) ***
Sep 19 22:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) ***
Sep 19 22:15:20 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 5433/5433, ET: 19) ***
Sep 19 22:15:20 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 66/66, ET: 19) ***
Sep 19 22:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 351) ***
Sep 19 22:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 5440/5440, ET: 0) ***
Sep 19 22:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 351) ***
Sep 19 22:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 59/59, ET: 1) ***
Sep 19 22:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) ***
Sep 19 22:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) ***
... 71 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 22:09:09 outbound00.cs.umd.edu python3[1834392]: ldapdb [x6]
== outbound01.cs.umd.edu (3 distinct, 9 total) ==
Sep 19 22:13:06 outbound01.cs.umd.edu python3[4093644]: ldapdb [x6]
Sep 19 22:53:09 outbound01.cs.umd.edu krb5_child[4102714]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 19 22:55:08 outbound01.cs.umd.edu krb5_child[4103049]: Preauthentication failed
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909654]: link_config: could not get ethtool features for veth76ae185
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909654]: Could not set offload features of veth76ae185: No such device
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909749]: link_config: could not get ethtool features for vethdadc635
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909749]: Could not set offload features of vethdadc635: No such device
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909770]: Could not generate persistent MAC address for vethc982304: No such file or directory
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909771]: Could not generate persistent MAC address for vetha95abd2: No such file or directory
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909774]: Could not generate persistent MAC address for vethfcf2ace: No such file or directory
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909775]: Could not generate persistent MAC address for veth8f1046c: No such file or directory
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909830]: Could not generate persistent MAC address for veth09195c5: No such file or directory
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909831]: Could not generate persistent MAC address for vetha344954: No such file or directory
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909869]: Could not generate persistent MAC address for veth68a1f3a: No such file or directory
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909875]: Could not generate persistent MAC address for veth718697f: No such file or directory
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909895]: Could not generate persistent MAC address for veth630a736: No such file or directory
Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909887]: Could not generate persistent MAC address for vethd65d293: No such file or directory
Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919146]: link_config: could not get ethtool features for veth09195c5
Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919146]: Could not set offload features of veth09195c5: No such device
Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919182]: Could not generate persistent MAC address for vethe103e49: No such file or directory
Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919183]: Could not generate persistent MAC address for veth6e1f8e2: No such file or directory
Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919186]: Could not generate persistent MAC address for vethd19e050: No such file or directory
Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919187]: Could not generate persistent MAC address for vethb3e1c9d: No such file or directory
Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919187]: Could not generate persistent MAC address for veth9e0d5c1: No such file or directory
Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919196]: Could not generate persistent MAC address for veth4a70f7d: No such file or directory
Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919196]: Could not generate persistent MAC address for veth31bde4a: No such file or directory
Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919187]: Could not generate persistent MAC address for veth3614537: No such file or directory
Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919214]: Could not generate persistent MAC address for vethdedf544: No such file or directory
Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919215]: Could not generate persistent MAC address for vethb89bc6e: No such file or directory
Sep 19 22:51:44 sentry-docker00.cs.umd.edu systemd-udevd[3928528]: link_config: could not get ethtool features for veth3614537
Sep 19 22:51:44 sentry-docker00.cs.umd.edu systemd-udevd[3928528]: Could not set offload features of veth3614537: No such device
Sep 19 22:51:45 sentry-docker00.cs.umd.edu systemd-udevd[3928595]: Could not generate persistent MAC address for veth15dc03e: No such file or directory
Sep 19 22:51:45 sentry-docker00.cs.umd.edu systemd-udevd[3928596]: Could not generate persistent MAC address for veth9c13283: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 22:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 22:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 22:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 22:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 22:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 22:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 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 19 22:08:08 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
Sep 19 22:25:53 submit26-b9-f1 setroubleshoot[2545739]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c
Sep 19 22:25:53 submit26-b9-f1 setroubleshoot[2545739]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36
Sep 19 22:25:53 submit26-b9-f1 setroubleshoot[2545739]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6
Sep 19 22:25:54 submit26-b9-f1 setroubleshoot[2545739]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.JFZGWw/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 19 22:25:54 submit26-b9-f1 setroubleshoot[2545739]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee
Sep 19 22:25:54 submit26-b9-f1 setroubleshoot[2545739]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.JFZGWw. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 19 22:25:54 submit26-b9-f1 setroubleshoot[2545739]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d
Sep 19 22:25:54 submit26-b9-f1 setroubleshoot[2545739]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9
Sep 19 22:25:54 submit26-b9-f1 setroubleshoot[2545739]: 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, 12 total) ==
Sep 19 22:05:07 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
Sep 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6
Sep 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a
Sep 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339
Sep 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.2zz6WM/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1
Sep 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.2zz6WM. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885
Sep 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af
Sep 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7
== submit26-b9-f3 (1 distinct, 2 total) ==
Sep 19 22:26:27 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f4 (1 distinct, 2 total) ==
Sep 19 22:08:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== vacuum.cs.umd.edu (4 distinct, 4 total) ==
Sep 19 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[3949]: Process 31785 (driver) of user 33 killed by SIGABRT - dumping core
Sep 19 22:11:58 vacuum.cs.umd.edu abrt-server[3951]: Package 'amanda-backup_server' isn't signed with proper key
Sep 19 22:11:58 vacuum.cs.umd.edu abrt-server[3951]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-19-22:11:58-31785' exited with 1
Sep 19 22:11:58 vacuum.cs.umd.edu abrt-server[3951]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-19-22:11:58-31785'
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0549s
Status : exited 0
Output :
Syslog digest — 2026-09-19 22:05 EDT
Processed 2,974 lines, filtered 2,429 (81%). 545 unknown (202 distinct) from 20 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 21:51:27 b0b02.cs.umd.edu rustdesk[3029867]: cannot open display:
== bale (5 distinct, 88 total) ==
Sep 19 21:05:09 bale setroubleshoot[972665]: failed to retrieve rpm info for /dev/nvme0 [x38]
Sep 19 21:05:10 bale setroubleshoot[972665]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12]
Sep 19 21:05:13 bale setroubleshoot[972665]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12]
Sep 19 21:05:16 bale setroubleshoot[972665]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12]
Sep 19 21:05:27 bale setroubleshoot[973281]: 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 (5 distinct, 5 total) ==
Sep 19 21:18:12 biggulp.cs.umd.edu sshd-session[2653247]: error: send_error: write: Connection reset by peer
Sep 19 21:58:48 biggulp.cs.umd.edu sshd-session[2660542]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 19 21:58:48 biggulp.cs.umd.edu sshd-session[2660542]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 19 21:58:50 biggulp.cs.umd.edu sshd-session[2660542]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 19 21:58:50 biggulp.cs.umd.edu sshd-session[2660542]: error: kex_protocol_error: type 30 seq 5 [preauth]
== csfw00a (1 distinct, 138 total) ==
Sep 19 21:04:02 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x138]
== idm00 (1 distinct, 1 total) ==
Sep 19 21:53:59 idm00 named[4166701]: client @0x7f11986d48e8 10.73.240.42#63046: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 21:37:57 idmp0 named[1598691]: client @0x7f2d4c039bf8 10.73.240.43#60244: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 5 total) ==
Sep 19 21:07:58 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x5]
== krispykreme.cs.umd.edu (4 distinct, 4 total) ==
Sep 19 21:59:19 krispykreme.cs.umd.edu sshd-session[64575]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 19 21:59:19 krispykreme.cs.umd.edu sshd-session[64575]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 19 21:59:21 krispykreme.cs.umd.edu sshd-session[64575]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 19 21:59:21 krispykreme.cs.umd.edu sshd-session[64575]: error: kex_protocol_error: type 30 seq 5 [preauth]
== munin (2 distinct, 4 total) ==
Sep 19 21:57:57 munin sudo[480728]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 19 21:57:57 munin sudo[480728]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== netman.cs.umd.edu (2 distinct, 2 total) ==
Sep 19 21:58:48 netman.cs.umd.edu sshd[2556612]: error: type 20 seq 2 [preauth]
Sep 19 21:58:48 netman.cs.umd.edu sshd[2556612]: error: type 30 seq 3 [preauth]
== newhonors2 (1 distinct, 24 total) ==
Sep 19 21:13:03 newhonors2 dhcpcd[2875673]: dhcpcd is not running [x24]
== ntop00 (99 distinct, 143 total) ==
Sep 19 21:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) ***
Sep 19 21:05:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 6250/6250, ET: 22) ***
Sep 19 21:05:24 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 43/43, ET: 23) ***
Sep 19 21:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 323) ***
Sep 19 21:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 6476/6476, ET: 0) ***
Sep 19 21:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 323) ***
Sep 19 21:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 42/42, ET: 0) ***
Sep 19 21:08:02 ntop00 setroubleshoot[706258]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 21:08:02 ntop00 setroubleshoot[706258]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 21:08:03 ntop00 setroubleshoot[706258]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 21:08:03 ntop00 setroubleshoot[706258]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 21:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) ***
Sep 19 21:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) ***
Sep 19 21:10:26 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 6655/6655, ET: 25) ***
Sep 19 21:10:26 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 48/48, ET: 25) ***
Sep 19 21:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 325) ***
Sep 19 21:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 6777/6777, ET: 0) ***
Sep 19 21:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 325) ***
Sep 19 21:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 46/46, ET: 0) ***
Sep 19 21:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) ***
Sep 19 21:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) ***
Sep 19 21:15:26 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 6648/6648, ET: 25) ***
Sep 19 21:15:26 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 53/53, ET: 25) ***
Sep 19 21:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 327) ***
Sep 19 21:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 6248/6248, ET: 0) ***
Sep 19 21:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 327) ***
Sep 19 21:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 55/55, ET: 0) ***
Sep 19 21:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) ***
Sep 19 21:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) ***
Sep 19 21:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 328, QN: 51/51, ET: 0) ***
... 69 more distinct messages not shown
== outbound00.cs.umd.edu (7 distinct, 12 total) ==
Sep 19 21:09:09 outbound00.cs.umd.edu python3[1820447]: ldapdb [x6]
Sep 19 21:49:53 outbound00.cs.umd.edu sshd-session[1829556]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 19 21:49:53 outbound00.cs.umd.edu sshd-session[1829556]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 19 21:49:54 outbound00.cs.umd.edu sshd-session[1829556]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 19 21:49:54 outbound00.cs.umd.edu sshd-session[1829556]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 19 21:49:57 outbound00.cs.umd.edu sshd-session[1829556]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 19 21:49:57 outbound00.cs.umd.edu sshd-session[1829556]: error: kex_protocol_error: type 30 seq 7 [preauth]
== outbound01.cs.umd.edu (7 distinct, 12 total) ==
Sep 19 21:13:06 outbound01.cs.umd.edu python3[4079481]: ldapdb [x6]
Sep 19 21:49:52 outbound01.cs.umd.edu sshd-session[4087872]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 19 21:49:52 outbound01.cs.umd.edu sshd-session[4087872]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 19 21:49:54 outbound01.cs.umd.edu sshd-session[4087872]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 19 21:49:54 outbound01.cs.umd.edu sshd-session[4087872]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 19 21:49:56 outbound01.cs.umd.edu sshd-session[4087872]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 19 21:49:56 outbound01.cs.umd.edu sshd-session[4087872]: error: kex_protocol_error: type 30 seq 7 [preauth]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881214]: link_config: could not get ethtool features for vethcc8dbd5
Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881214]: Could not set offload features of vethcc8dbd5: No such device
Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881249]: Could not generate persistent MAC address for vethadbd008: No such file or directory
Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881250]: Could not generate persistent MAC address for vethaabb594: No such file or directory
Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881259]: Could not generate persistent MAC address for veth036eaea: No such file or directory
Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881269]: Could not generate persistent MAC address for veth6ba88ff: No such file or directory
Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881273]: Could not generate persistent MAC address for veth3d05ec9: No such file or directory
Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881268]: Could not generate persistent MAC address for veth983b7e7: No such file or directory
Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881271]: Could not generate persistent MAC address for vethbb4cb0b: No such file or directory
Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881268]: Could not generate persistent MAC address for vethb2e77aa: No such file or directory
Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881349]: Could not generate persistent MAC address for veth655c4ff: No such file or directory
Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881353]: Could not generate persistent MAC address for veth0cf726f: No such file or directory
Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890624]: link_config: could not get ethtool features for vethb2e77aa
Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890624]: Could not set offload features of vethb2e77aa: No such device
Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890658]: Could not generate persistent MAC address for vethbb8f393: No such file or directory
Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890659]: Could not generate persistent MAC address for veth26af7b4: No such file or directory
Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890662]: Could not generate persistent MAC address for vethce13964: No such file or directory
Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890663]: Could not generate persistent MAC address for veth403c27c: No such file or directory
Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890679]: Could not generate persistent MAC address for vethf49e63c: No such file or directory
Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890669]: Could not generate persistent MAC address for veth905ef90: No such file or directory
Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890689]: Could not generate persistent MAC address for veth1d25d40: No such file or directory
Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890688]: Could not generate persistent MAC address for vethfe3531e: No such file or directory
Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890693]: Could not generate persistent MAC address for veth212d9de: No such file or directory
Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890688]: Could not generate persistent MAC address for vethd74e3dc: No such file or directory
Sep 19 21:51:19 sentry-docker00.cs.umd.edu systemd-udevd[3900239]: link_config: could not get ethtool features for vethd74e3dc
Sep 19 21:51:19 sentry-docker00.cs.umd.edu systemd-udevd[3900239]: Could not set offload features of vethd74e3dc: No such device
Sep 19 21:51:20 sentry-docker00.cs.umd.edu systemd-udevd[3900282]: Could not generate persistent MAC address for veth76ae185: No such file or directory
Sep 19 21:51:20 sentry-docker00.cs.umd.edu systemd-udevd[3900283]: Could not generate persistent MAC address for veth8f198a4: No such file or directory
Sep 19 21:51:20 sentry-docker00.cs.umd.edu systemd-udevd[3900286]: Could not generate persistent MAC address for vethc9ec482: No such file or directory
Sep 19 21:51:20 sentry-docker00.cs.umd.edu systemd-udevd[3900287]: Could not generate persistent MAC address for veth149a0fc: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 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 19 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 19 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 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 19 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 19 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 1 total) ==
Sep 19 22:03:08 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f2 (1 distinct, 5 total) ==
Sep 19 21:09:51 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f3 (10 distinct, 14 total) ==
Sep 19 21:05:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
Sep 19 21:06:42 submit26-b9-f3 setroubleshoot[2043991]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b
Sep 19 21:06:42 submit26-b9-f3 setroubleshoot[2043991]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859
Sep 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033
Sep 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.TD96o9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba
Sep 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.TD96o9. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407
Sep 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65
Sep 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68
== submit26-b9-f4 (10 distinct, 11 total) ==
Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb
Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4
Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d
Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Vwtm2x/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e
Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Vwtm2x. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d
Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74
Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915
Sep 19 21:25:09 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0522s
Status : exited 0
Output :
Syslog digest — 2026-09-19 21:05 EDT
Processed 2,716 lines, filtered 2,213 (81%). 503 unknown (176 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 20:51:23 b0b02.cs.umd.edu rustdesk[3014699]: cannot open display:
== bale (5 distinct, 92 total) ==
Sep 19 20:05:34 bale setroubleshoot[959961]: failed to retrieve rpm info for /dev/nvme0 [x40]
Sep 19 20:05:35 bale setroubleshoot[959961]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12]
Sep 19 20:05:37 bale setroubleshoot[959961]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12]
Sep 19 20:05:40 bale setroubleshoot[959961]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12]
Sep 19 20:05:52 bale setroubleshoot[960575]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x16]
== csfw00a (1 distinct, 125 total) ==
Sep 19 20:03:44 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x125]
== idm00 (1 distinct, 1 total) ==
Sep 19 20:53:59 idm00 named[4166701]: client @0x7f11a9407128 10.73.240.42#55237: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 20:37:57 idmp0 named[1598691]: client @0x7f2d28029f68 10.73.240.43#64411: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 5 total) ==
Sep 19 20:08:26 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x5]
== matrix (10 distinct, 14 total) ==
Sep 19 20:13:49 matrix sshd[2625570]: error: Refused by certificate options [x4]
Sep 19 20:45:28 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2644723, but reception only permitted for main PID 720
Sep 19 20:45:28 matrix networkctl[2644887]: Interface "veth3fcb00b" not found.
Sep 19 20:45:28 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2644887, but reception only permitted for main PID 720 [x2]
Sep 19 20:45:29 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2644967, but reception only permitted for main PID 720
Sep 19 20:45:29 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2644972, but reception only permitted for main PID 720
Sep 19 20:45:29 matrix networkctl[2644984]: Interface "vethf9567cd" not found.
Sep 19 20:45:29 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2645101, but reception only permitted for main PID 720
Sep 19 20:45:29 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2645280, but reception only permitted for main PID 720
Sep 19 20:45:44 matrix kernel: kauditd_printk_skb: 8 callbacks suppressed
== newhonors2 (1 distinct, 24 total) ==
Sep 19 20:13:03 newhonors2 dhcpcd[2873832]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 19 20:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 298) ***
Sep 19 20:05:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 6533/6533, ET: 22) ***
Sep 19 20:05:23 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 48/48, ET: 22) ***
Sep 19 20:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 299) ***
Sep 19 20:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 5692/5692, ET: 0) ***
Sep 19 20:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 299) ***
Sep 19 20:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 54/54, ET: 0) ***
Sep 19 20:08:03 ntop00 setroubleshoot[698381]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 20:08:03 ntop00 setroubleshoot[698381]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 20:08:03 ntop00 setroubleshoot[698381]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 20:08:03 ntop00 setroubleshoot[698381]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 20:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) ***
Sep 19 20:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) ***
Sep 19 20:10:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 5732/5732, ET: 20) ***
Sep 19 20:10:21 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 50/50, ET: 20) ***
Sep 19 20:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 301) ***
Sep 19 20:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 6174/6174, ET: 0) ***
Sep 19 20:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 301) ***
Sep 19 20:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 54/54, ET: 0) ***
Sep 19 20:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) ***
Sep 19 20:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) ***
Sep 19 20:15:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 5971/5971, ET: 22) ***
Sep 19 20:15:23 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 53/53, ET: 22) ***
Sep 19 20:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 303) ***
Sep 19 20:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 5645/5645, ET: 0) ***
Sep 19 20:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 303) ***
Sep 19 20:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 39/39, ET: 0) ***
Sep 19 20:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) ***
Sep 19 20:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) ***
Sep 19 20:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 304, QN: 41/41, ET: 0) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 20:09:09 outbound00.cs.umd.edu python3[1806558]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 20:13:06 outbound01.cs.umd.edu python3[4065542]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852951]: link_config: could not get ethtool features for vetha660928
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852951]: Could not set offload features of vetha660928: No such device
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852985]: Could not generate persistent MAC address for veth1ef7a26: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852986]: Could not generate persistent MAC address for veth0531380: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852989]: Could not generate persistent MAC address for vethabe7f2c: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852997]: Could not generate persistent MAC address for vethf512cf0: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852998]: Could not generate persistent MAC address for vethcaeb6e9: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853009]: Could not generate persistent MAC address for veth2a74ba5: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853015]: Could not generate persistent MAC address for vethee1e149: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853016]: Could not generate persistent MAC address for vethcc2b2cf: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853034]: Could not generate persistent MAC address for vethefe56f4: No such file or directory
Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853029]: Could not generate persistent MAC address for veth52eca01: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862351]: link_config: could not get ethtool features for vethabe7f2c
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862351]: Could not set offload features of vethabe7f2c: No such device
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862401]: Could not generate persistent MAC address for veth50818d2: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862402]: Could not generate persistent MAC address for vethc951973: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862405]: Could not generate persistent MAC address for veth64b2976: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862406]: Could not generate persistent MAC address for veth8ba369b: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862416]: Could not generate persistent MAC address for vethf07cf1f: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862411]: Could not generate persistent MAC address for vethfe9221a: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862424]: Could not generate persistent MAC address for veth832e528: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862410]: Could not generate persistent MAC address for veth021e78d: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862487]: Could not generate persistent MAC address for vethc6622c9: No such file or directory
Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862490]: Could not generate persistent MAC address for veth9c6631c: No such file or directory
Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871824]: link_config: could not get ethtool features for vethc6622c9
Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871824]: Could not set offload features of vethc6622c9: No such device
Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871846]: Could not generate persistent MAC address for vetha964c49: No such file or directory
Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871847]: Could not generate persistent MAC address for veth622f661: No such file or directory
Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871865]: Could not generate persistent MAC address for veth26f7273: No such file or directory
Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871852]: Could not generate persistent MAC address for vethd627946: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 20:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 20:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 20:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 20:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (1 distinct, 1 total) ==
Sep 19 20:44:38 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.tVmNgA/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.tVmNgA. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac
Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c
Sep 19 20:21:58 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0534s
Status : exited 0
Output :
Syslog digest — 2026-09-19 20:05 EDT
Processed 2,695 lines, filtered 2,146 (79%). 549 unknown (172 distinct) from 14 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 19:51:19 b0b02.cs.umd.edu rustdesk[2999309]: cannot open display:
== bale (5 distinct, 88 total) ==
Sep 19 19:05:15 bale setroubleshoot[947192]: failed to retrieve rpm info for /dev/nvme0 [x38]
Sep 19 19:05:16 bale setroubleshoot[947192]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12]
Sep 19 19:05:18 bale setroubleshoot[947192]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12]
Sep 19 19:05:21 bale setroubleshoot[947192]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12]
Sep 19 19:05:33 bale setroubleshoot[947818]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x14]
== csfw00a (1 distinct, 130 total) ==
Sep 19 19:03:40 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x130]
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 19 19:42:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 19 19:53:59 idm00 named[4166701]: client @0x7f11a93e2ef8 10.73.240.42#49765: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 19:37:56 idmp0 named[1598691]: client @0x7f2d4802a308 10.73.240.43#60602: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 19 19:23:08 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3]
== newhonors2 (1 distinct, 24 total) ==
Sep 19 19:13:02 newhonors2 dhcpcd[2871958]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 19 19:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 274) ***
Sep 19 19:05:39 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 274, QN: 10366/10366, ET: 38) ***
Sep 19 19:05:39 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 274, QN: 45/45, ET: 38) ***
Sep 19 19:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 275) ***
Sep 19 19:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 275, QN: 9224/9224, ET: 0) ***
Sep 19 19:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 275) ***
Sep 19 19:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 275, QN: 55/55, ET: 0) ***
Sep 19 19:08:02 ntop00 setroubleshoot[690486]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 19:08:02 ntop00 setroubleshoot[690486]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 19:08:03 ntop00 setroubleshoot[690486]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 19:08:03 ntop00 setroubleshoot[690486]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 19:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 276) ***
Sep 19 19:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 276) ***
Sep 19 19:10:31 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 276, QN: 7892/7892, ET: 30) ***
Sep 19 19:10:31 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 276, QN: 67/67, ET: 30) ***
Sep 19 19:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 277) ***
Sep 19 19:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 277, QN: 12029/12029, ET: 0) ***
Sep 19 19:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 277) ***
Sep 19 19:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 277, QN: 65/65, ET: 0) ***
Sep 19 19:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 278) ***
Sep 19 19:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 278) ***
Sep 19 19:15:50 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 278, QN: 13432/13432, ET: 49) ***
Sep 19 19:15:50 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 278, QN: 64/64, ET: 49) ***
Sep 19 19:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 279) ***
Sep 19 19:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 279, QN: 10955/10955, ET: 0) ***
Sep 19 19:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 279) ***
Sep 19 19:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 279, QN: 59/59, ET: 0) ***
Sep 19 19:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 280) ***
Sep 19 19:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 280) ***
Sep 19 19:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 280, QN: 60/60, ET: 0) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 19:09:09 outbound00.cs.umd.edu python3[1792633]: ldapdb [x6]
== outbound01.cs.umd.edu (3 distinct, 8 total) ==
Sep 19 19:13:06 outbound01.cs.umd.edu python3[4051555]: ldapdb [x6]
Sep 19 19:25:50 outbound01.cs.umd.edu krb5_child[4055017]: Preauthentication failed
Sep 19 19:29:14 outbound01.cs.umd.edu krb5_child[4055583]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824649]: link_config: could not get ethtool features for veth2469b9d
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824649]: Could not set offload features of veth2469b9d: No such device
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824685]: Could not generate persistent MAC address for vethfc5f999: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824686]: Could not generate persistent MAC address for vethed6ebbd: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824689]: Could not generate persistent MAC address for vethddac317: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824690]: Could not generate persistent MAC address for veth684ad41: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824709]: Could not generate persistent MAC address for veth5a8e00e: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824686]: Could not generate persistent MAC address for veth0b92870: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824715]: Could not generate persistent MAC address for veth388cad8: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824716]: Could not generate persistent MAC address for vethf1fca53: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824734]: Could not generate persistent MAC address for veth61f1a52: No such file or directory
Sep 19 19:10:13 sentry-docker00.cs.umd.edu systemd-udevd[3824726]: Could not generate persistent MAC address for vethc00aaae: No such file or directory
Sep 19 19:30:21 sentry-docker00.cs.umd.edu systemd-udevd[3834064]: link_config: could not get ethtool features for vethfc5f999
Sep 19 19:30:21 sentry-docker00.cs.umd.edu systemd-udevd[3834064]: Could not set offload features of vethfc5f999: No such device
Sep 19 19:30:21 sentry-docker00.cs.umd.edu systemd-udevd[3834099]: Could not generate persistent MAC address for vethf88d4e7: No such file or directory
Sep 19 19:30:21 sentry-docker00.cs.umd.edu systemd-udevd[3834100]: Could not generate persistent MAC address for veth4f7910b: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834103]: Could not generate persistent MAC address for vethcae1808: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834104]: Could not generate persistent MAC address for veth2d80353: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834115]: Could not generate persistent MAC address for veth2bc5cc2: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834113]: Could not generate persistent MAC address for veth05dd065: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834129]: Could not generate persistent MAC address for veth5b9d016: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834130]: Could not generate persistent MAC address for veth78560f3: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834148]: Could not generate persistent MAC address for veth0af52bb: No such file or directory
Sep 19 19:30:22 sentry-docker00.cs.umd.edu systemd-udevd[3834136]: Could not generate persistent MAC address for veth6ee54cc: No such file or directory
Sep 19 19:50:29 sentry-docker00.cs.umd.edu systemd-udevd[3843111]: link_config: could not get ethtool features for veth05dd065
Sep 19 19:50:29 sentry-docker00.cs.umd.edu systemd-udevd[3843111]: Could not set offload features of veth05dd065: No such device
Sep 19 19:50:30 sentry-docker00.cs.umd.edu systemd-udevd[3843118]: link_config: could not get ethtool features for vethf88d4e7
Sep 19 19:50:30 sentry-docker00.cs.umd.edu systemd-udevd[3843118]: Could not set offload features of vethf88d4e7: No such device
Sep 19 19:50:30 sentry-docker00.cs.umd.edu systemd-udevd[3843233]: Could not generate persistent MAC address for veth08e65f2: No such file or directory
Sep 19 19:50:30 sentry-docker00.cs.umd.edu systemd-udevd[3843234]: Could not generate persistent MAC address for veth4628bdc: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 19:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 19:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 19:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 19:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 19:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 19:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 19:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== teaching-awards (1 distinct, 1 total) ==
Sep 19 19:46:28 teaching-awards krb5_child[1118941]: Client 'admin(a)UMD.EDU' not found in Kerberos database
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0526s
Status : exited 0
Output :
Syslog digest — 2026-09-19 19:05 EDT
Processed 2,553 lines, filtered 2,043 (80%). 510 unknown (184 distinct) from 19 host(s).
== b0b02.cs.umd.edu (4 distinct, 4 total) ==
Sep 19 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-19T22:10:59.426919828Z" level=info msg="PurgeUploads starting: olderThan=2026-09-12 22:10:59.426842535 +0000 UTC m=+4063020.186770847, actuallyDelete=true"
Sep 19 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-19T22:10:59.427410979Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1"
Sep 19 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-19T22:10:59.427430854Z" level=info msg="Starting upload purge in 24h0m0s" go.version=go1.11.2 instance.id=68469aa4-7857-4a69-bf12-c2190b4f96d8 service=registry version=v2.7.1
Sep 19 18:51:16 b0b02.cs.umd.edu rustdesk[2984122]: cannot open display:
== bale (5 distinct, 87 total) ==
Sep 19 18:06:04 bale setroubleshoot[934499]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 19 18:06:05 bale setroubleshoot[934499]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12]
Sep 19 18:06:07 bale setroubleshoot[934499]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13]
Sep 19 18:06:10 bale setroubleshoot[934499]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x11]
Sep 19 18:06:22 bale setroubleshoot[935113]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x14]
== csfw00a (1 distinct, 128 total) ==
Sep 19 18:04:09 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x128]
== idm00 (1 distinct, 1 total) ==
Sep 19 18:53:59 idm00 named[4166701]: client @0x7f11980184a8 10.73.240.42#64044: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 18:37:56 idmp0 named[1598691]: client @0x7f2d3c076558 10.73.240.43#63053: update '73.10.in-addr.arpa/IN' denied
== irb2156 (1 distinct, 1 total) ==
Sep 19 18:08:41 irb2156 systemd-tmpfiles[572914]: Opening file "/tmp/org.chromium.Chromium.pnSOAt/SingletonSocket" failed, proceeding without lock: No such device or address
== itmon02 (1 distinct, 2 total) ==
Sep 19 18:18:25 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2]
== munin (2 distinct, 4 total) ==
Sep 19 18:28:59 munin sudo[405059]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 19 18:28:59 munin sudo[405059]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== neoavion (1 distinct, 1 total) ==
Sep 19 18:32:35 neoavion krb5_child[3630822]: No credentials cache found
== newhonors2 (1 distinct, 24 total) ==
Sep 19 18:13:03 newhonors2 dhcpcd[2870113]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 19 18:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 250) ***
Sep 19 18:05:29 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 250, QN: 7481/7481, ET: 28) ***
Sep 19 18:05:29 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 250, QN: 45/45, ET: 28) ***
Sep 19 18:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 251) ***
Sep 19 18:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 251, QN: 9416/9416, ET: 0) ***
Sep 19 18:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 251) ***
Sep 19 18:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 251, QN: 58/58, ET: 0) ***
Sep 19 18:08:02 ntop00 setroubleshoot[682597]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 18:08:02 ntop00 setroubleshoot[682597]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 18:08:03 ntop00 setroubleshoot[682597]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 18:08:03 ntop00 setroubleshoot[682597]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 18:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 252) ***
Sep 19 18:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 252) ***
Sep 19 18:10:29 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 252, QN: 8306/8306, ET: 28) ***
Sep 19 18:10:29 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 252, QN: 71/71, ET: 28) ***
Sep 19 18:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 253) ***
Sep 19 18:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 253, QN: 14544/14544, ET: 0) ***
Sep 19 18:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 253) ***
Sep 19 18:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 253, QN: 82/82, ET: 0) ***
Sep 19 18:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 254) ***
Sep 19 18:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 254) ***
Sep 19 18:16:07 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 254, QN: 19635/19635, ET: 66) ***
Sep 19 18:16:08 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 254, QN: 78/78, ET: 67) ***
Sep 19 18:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 255) ***
Sep 19 18:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 255, QN: 24509/24509, ET: 0) ***
Sep 19 18:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 255) ***
Sep 19 18:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 255, QN: 68/68, ET: 1) ***
Sep 19 18:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 256) ***
Sep 19 18:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 256) ***
Sep 19 18:21:33 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 256, QN: 26844/26844, ET: 92) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 18:09:09 outbound00.cs.umd.edu python3[1778552]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 18:13:06 outbound01.cs.umd.edu python3[4037632]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796075]: link_config: could not get ethtool features for veth69ad032
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796075]: Could not set offload features of veth69ad032: No such device
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796106]: Could not generate persistent MAC address for veth99cdb86: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796107]: Could not generate persistent MAC address for veth97ebd42: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796110]: Could not generate persistent MAC address for vethe7f36d9: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796111]: Could not generate persistent MAC address for veth1c82051: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796111]: Could not generate persistent MAC address for veth20702d5: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796121]: Could not generate persistent MAC address for veth63f8e31: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796122]: Could not generate persistent MAC address for vethcb15d1a: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796129]: Could not generate persistent MAC address for vetha53d8f6: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796152]: Could not generate persistent MAC address for veth5fd93ec: No such file or directory
Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796151]: Could not generate persistent MAC address for veth4c6561c: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805464]: link_config: could not get ethtool features for vethe7f36d9
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805464]: Could not set offload features of vethe7f36d9: No such device
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805537]: Could not generate persistent MAC address for vethc5f68d5: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805538]: Could not generate persistent MAC address for vethd3bc0eb: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805541]: Could not generate persistent MAC address for veth875e42f: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805542]: Could not generate persistent MAC address for veth3acfc7d: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805565]: Could not generate persistent MAC address for vethf2f220c: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805566]: Could not generate persistent MAC address for vethae3f43a: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805611]: Could not generate persistent MAC address for veth2be16b5: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805622]: Could not generate persistent MAC address for vetha339108: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805639]: Could not generate persistent MAC address for veth4674d73: No such file or directory
Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805662]: Could not generate persistent MAC address for vethb8400f8: No such file or directory
Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814913]: link_config: could not get ethtool features for veth875e42f
Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814913]: Could not set offload features of veth875e42f: No such device
Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814982]: Could not generate persistent MAC address for vethfbbb2b4: No such file or directory
Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814983]: Could not generate persistent MAC address for veth96a93c2: No such file or directory
Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814986]: Could not generate persistent MAC address for vethb85b833: No such file or directory
Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814995]: Could not generate persistent MAC address for veth21c3f98: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 18:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 18:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 18:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 18:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (9 distinct, 12 total) ==
Sep 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c
Sep 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36
Sep 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6 [x2]
Sep 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.R33FVJ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d [x2]
Sep 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee [x2]
Sep 19 18:25:54 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.R33FVJ. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 19 18:25:54 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d
Sep 19 18:25:54 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9
Sep 19 18:25:54 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848
== submit26-b9-f2 (10 distinct, 13 total) ==
Sep 19 18:06:48 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6
Sep 19 18:06:48 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a
Sep 19 18:06:48 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 [x2]
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Cd0ZAk/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 [x2]
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Cd0ZAk. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af [x2]
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7
Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.F0sZXe/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
== submit26-b9-f3 (1 distinct, 1 total) ==
Sep 19 18:08:07 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 19 18:23:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0535s
Status : exited 0
Output :
Syslog digest — 2026-09-19 18:05 EDT
Processed 2,788 lines, filtered 2,268 (81%). 520 unknown (179 distinct) from 17 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 17:51:14 b0b02.cs.umd.edu rustdesk[2968958]: cannot open display:
== bale (5 distinct, 89 total) ==
Sep 19 17:06:07 bale setroubleshoot[921607]: failed to retrieve rpm info for /dev/nvme0 [x38]
Sep 19 17:06:07 bale setroubleshoot[921607]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x13]
Sep 19 17:06:10 bale setroubleshoot[921607]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13]
Sep 19 17:06:13 bale setroubleshoot[921607]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x11]
Sep 19 17:06:25 bale setroubleshoot[922223]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x14]
== csfw00a (1 distinct, 133 total) ==
Sep 19 17:04:08 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x133]
== frozone (1 distinct, 1 total) ==
Sep 19 17:35:38 frozone systemd-tmpfiles[2107225]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted
== idm00 (1 distinct, 1 total) ==
Sep 19 17:53:58 idm00 named[4166701]: client @0x7f11a93cbc38 10.73.240.42#65160: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 17:37:56 idmp0 named[1598691]: client @0x7f2d24019b88 10.73.240.43#53179: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 19 17:38:08 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3]
== newhonors2 (1 distinct, 24 total) ==
Sep 19 17:13:03 newhonors2 dhcpcd[2868272]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 19 17:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 226) ***
Sep 19 17:05:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 226, QN: 6001/6001, ET: 20) ***
Sep 19 17:05:21 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 226, QN: 73/73, ET: 20) ***
Sep 19 17:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 227) ***
Sep 19 17:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 227, QN: 6109/6109, ET: 0) ***
Sep 19 17:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 227) ***
Sep 19 17:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 227, QN: 67/67, ET: 0) ***
Sep 19 17:08:02 ntop00 setroubleshoot[674562]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12]
Sep 19 17:08:02 ntop00 setroubleshoot[674562]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12]
Sep 19 17:08:02 ntop00 setroubleshoot[674562]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 17:08:02 ntop00 setroubleshoot[674562]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12]
Sep 19 17:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 228) ***
Sep 19 17:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 228) ***
Sep 19 17:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 228, QN: 65/65, ET: 0) ***
Sep 19 17:10:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 228, QN: 5973/5973, ET: 20) ***
Sep 19 17:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 229) ***
Sep 19 17:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 229, QN: 6089/6089, ET: 0) ***
Sep 19 17:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 229) ***
Sep 19 17:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 229, QN: 60/60, ET: 0) ***
Sep 19 17:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 230) ***
Sep 19 17:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 230) ***
Sep 19 17:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 230, QN: 49/49, ET: 0) ***
Sep 19 17:15:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 230, QN: 6390/6390, ET: 22) ***
Sep 19 17:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 231) ***
Sep 19 17:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 231) ***
Sep 19 17:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 231, QN: 57/57, ET: 0) ***
Sep 19 17:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 231, QN: 6228/6228, ET: 0) ***
Sep 19 17:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 232) ***
Sep 19 17:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 232) ***
Sep 19 17:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 232, QN: 51/51, ET: 0) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 17:09:09 outbound00.cs.umd.edu python3[1764603]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 17:13:07 outbound01.cs.umd.edu python3[4023465]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767523]: link_config: could not get ethtool features for vethbdd6d47
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767523]: Could not set offload features of vethbdd6d47: No such device
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767569]: Could not generate persistent MAC address for veth7edc101: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767570]: Could not generate persistent MAC address for vethe43aa76: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767573]: Could not generate persistent MAC address for veth93a15e1: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767574]: Could not generate persistent MAC address for veth930beff: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767597]: Could not generate persistent MAC address for veth704f1a2: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767598]: Could not generate persistent MAC address for vethde2c127: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767623]: Could not generate persistent MAC address for vethf756fc7: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767624]: Could not generate persistent MAC address for veth92101ae: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767642]: Could not generate persistent MAC address for veth46ab34f: No such file or directory
Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767627]: Could not generate persistent MAC address for veth2413952: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777207]: link_config: could not set ethtool features for veth93a15e1
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777207]: Could not set offload features of veth93a15e1: Operation not permitted
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777236]: Could not generate persistent MAC address for veth882bb97: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777237]: Could not generate persistent MAC address for veth9324a28: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777240]: Could not generate persistent MAC address for veth3ea44f0: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777241]: Could not generate persistent MAC address for vethd2e57e4: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777264]: Could not generate persistent MAC address for vethaaae73e: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777265]: Could not generate persistent MAC address for vethe096ac7: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777274]: Could not generate persistent MAC address for veth55cbef3: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777280]: Could not generate persistent MAC address for veth7014535: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777274]: Could not generate persistent MAC address for vethd3f3f7d: No such file or directory
Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777280]: Could not generate persistent MAC address for veth00e543d: No such file or directory
Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786632]: link_config: could not get ethtool features for vethd3f3f7d
Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786632]: Could not set offload features of vethd3f3f7d: No such device
Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786669]: Could not generate persistent MAC address for vethed42401: No such file or directory
Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786670]: Could not generate persistent MAC address for vethc20fa18: No such file or directory
Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786695]: Could not generate persistent MAC address for vethf5b5d57: No such file or directory
Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786696]: Could not generate persistent MAC address for veth9404756: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 17:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 17:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 17:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 17:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 19 17:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 19 17:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 4 total) ==
Sep 19 17:06:54 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f2 (1 distinct, 5 total) ==
Sep 19 17:18:07 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f3 (10 distinct, 14 total) ==
Sep 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b
Sep 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859
Sep 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033
Sep 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.NmGr6G/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba
Sep 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.NmGr6G. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 19 17:06:43 submit26-b9-f3 setroubleshoot[2019594]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407
Sep 19 17:06:43 submit26-b9-f3 setroubleshoot[2019594]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65
Sep 19 17:06:43 submit26-b9-f3 setroubleshoot[2019594]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68
Sep 19 17:14:33 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f4 (10 distinct, 14 total) ==
Sep 19 17:11:00 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb [x2]
Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4 [x2]
Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d
Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.GE5aXs/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e
Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GE5aXs. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d
Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74
Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915
1
0