Command: /usr/local/sbin/syslog-digest.py
Time : 0.0525s
Status : exited 0
Output :
Syslog digest — 2026-09-19 03:05 EDT
Processed 2,670 lines, filtered 2,160 (80%). 510 unknown (188 distinct) from 20 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 02:50:20 b0b02.cs.umd.edu rustdesk[2739014]: cannot open display:
== bale (5 distinct, 87 total) ==
Sep 19 02:05:14 bale setroubleshoot[729337]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 19 02:05:15 bale setroubleshoot[729337]: 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 02:05:29 bale setroubleshoot[729947]: 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 02:05:29 bale setroubleshoot[729947]: 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]
Sep 19 02:10:15 bale setroubleshoot[730100]: 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]
== biggulp.cs.umd.edu (4 distinct, 4 total) ==
Sep 19 02:38:48 biggulp.cs.umd.edu sshd-session[2461355]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 19 02:38:48 biggulp.cs.umd.edu sshd-session[2461355]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 19 02:38:50 biggulp.cs.umd.edu sshd-session[2461355]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 19 02:38:50 biggulp.cs.umd.edu sshd-session[2461355]: error: kex_protocol_error: type 30 seq 5 [preauth]
== cheezit.cs.umd.edu (4 distinct, 4 total) ==
Sep 19 02:28:03 cheezit.cs.umd.edu sshd-session[760593]: pam_access(sshd:auth): access denied for user `admin' from `207.175.221.71'
Sep 19 02:28:03 cheezit.cs.umd.edu krb5_child[760595]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 19 02:28:03 cheezit.cs.umd.edu sshd-session[760591]: error: PAM: System error for admin from 207.175.221.71
Sep 19 02:31:58 cheezit.cs.umd.edu sshd-session[761686]: error: Protocol major versions differ: 2 vs. 1
== cmsc436-0101-redis (2 distinct, 2 total) ==
Sep 19 02:30:13 cmsc436-0101-redis krb5_child[3260689]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 19 02:30:15 cmsc436-0101-redis sshd-session[3260685]: error: PAM: Authentication failure for admin from 35.187.86.229
== csfw00a (1 distinct, 126 total) ==
Sep 19 02:03:58 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x126]
== idm00 (1 distinct, 1 total) ==
Sep 19 02:53:58 idm00 named[4166701]: client @0x7f11a004b338 10.73.240.42#64785: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 02:37:58 idmp0 named[1598691]: client @0x7f2d34041cc8 10.73.240.43#61568: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 02:47:38 inbound00.cs.umd.edu krb5_child[1691598]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 7 total) ==
Sep 19 02:23:52 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x7]
== krispykreme.cs.umd.edu (3 distinct, 4 total) ==
Sep 19 02:07:56 krispykreme.cs.umd.edu sshd-session[3919551]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2]
Sep 19 02:07:57 krispykreme.cs.umd.edu sshd-session[3919551]: Error in Duo login for 'larry' from 71.191.93.172
Sep 19 02:07:57 krispykreme.cs.umd.edu sshd-session[3919549]: error: PAM: Authentication failure for larry from 71.191.93.172
== munin (2 distinct, 2 total) ==
Sep 19 03:03:08 munin sudo[69853]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory
Sep 19 03:03:08 munin sudo[69853]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order.
== newhonors2 (1 distinct, 24 total) ==
Sep 19 02:13:03 newhonors2 dhcpcd[2839855]: dhcpcd is not running [x24]
== ntop00 (98 distinct, 142 total) ==
Sep 19 02:05:27 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 9132/9132, ET: 26) ***
Sep 19 02:05:27 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 58/58, ET: 26) ***
Sep 19 02:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 443) ***
Sep 19 02:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 70/70, ET: 0) ***
Sep 19 02:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 443) ***
Sep 19 02:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 8641/8641, ET: 0) ***
Sep 19 02:08:02 ntop00 setroubleshoot[555019]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12]
Sep 19 02:08:02 ntop00 setroubleshoot[555019]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12]
Sep 19 02:08:02 ntop00 setroubleshoot[555019]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 02:08:02 ntop00 setroubleshoot[555019]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12]
Sep 19 02:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) ***
Sep 19 02:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) ***
Sep 19 02:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 76/76, ET: 0) ***
Sep 19 02:10:25 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 8519/8519, ET: 24) ***
Sep 19 02:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 445) ***
Sep 19 02:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 8414/8414, ET: 0) ***
Sep 19 02:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 445) ***
Sep 19 02:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 75/75, ET: 0) ***
Sep 19 02:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) ***
Sep 19 02:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) ***
Sep 19 02:15:25 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 8129/8129, ET: 24) ***
Sep 19 02:15:25 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 67/67, ET: 24) ***
Sep 19 02:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 447) ***
Sep 19 02:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 8084/8084, ET: 0) ***
Sep 19 02:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 447) ***
Sep 19 02:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 58/58, ET: 0) ***
Sep 19 02:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) ***
Sep 19 02:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) ***
Sep 19 02:20:25 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 448, QN: 8138/8138, ET: 24) ***
Sep 19 02:20:25 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 448, QN: 52/52, ET: 24) ***
... 68 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 02:09:09 outbound00.cs.umd.edu python3[1553955]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 02:13:06 outbound01.cs.umd.edu python3[3812324]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348884]: link_config: could not get ethtool features for veth347fdab
Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348884]: Could not set offload features of veth347fdab: No such device
Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348921]: Could not generate persistent MAC address for veth755eca7: No such file or directory
Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348922]: Could not generate persistent MAC address for vethd61fd3a: No such file or directory
Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348926]: Could not generate persistent MAC address for veth5446cd2: No such file or directory
Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348925]: Could not generate persistent MAC address for vetheb2462e: No such file or directory
Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348930]: Could not generate persistent MAC address for veth6e5a698: No such file or directory
Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348933]: Could not generate persistent MAC address for veth5fa3319: No such file or directory
Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348951]: Could not generate persistent MAC address for veth80716b9: No such file or directory
Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348952]: Could not generate persistent MAC address for veth9fe78cb: No such file or directory
Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348977]: Could not generate persistent MAC address for vethb446c28: No such file or directory
Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348989]: Could not generate persistent MAC address for vethe453c06: No such file or directory
Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358688]: link_config: could not get ethtool features for veth755eca7
Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358688]: Could not set offload features of veth755eca7: No such device
Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358721]: Could not generate persistent MAC address for veth6e99b32: No such file or directory
Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358722]: Could not generate persistent MAC address for veth78277ab: No such file or directory
Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358725]: Could not generate persistent MAC address for veth7e10ebd: No such file or directory
Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358726]: Could not generate persistent MAC address for vetha6c27ae: No such file or directory
Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358727]: Could not generate persistent MAC address for vethf24e852: No such file or directory
Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358741]: Could not generate persistent MAC address for veth6e17f0f: No such file or directory
Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358741]: Could not generate persistent MAC address for veth7ed5c30: No such file or directory
Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358727]: Could not generate persistent MAC address for veth25f98d7: No such file or directory
Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358741]: Could not generate persistent MAC address for vethfd370ab: No such file or directory
Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358727]: Could not generate persistent MAC address for veth7d26920: No such file or directory
Sep 19 03:03:33 sentry-docker00.cs.umd.edu systemd-udevd[3368184]: link_config: could not get ethtool features for vethfd370ab
Sep 19 03:03:33 sentry-docker00.cs.umd.edu systemd-udevd[3368184]: Could not set offload features of vethfd370ab: No such device
Sep 19 03:03:34 sentry-docker00.cs.umd.edu systemd-udevd[3368235]: Could not generate persistent MAC address for vethdff059c: No such file or directory
Sep 19 03:03:34 sentry-docker00.cs.umd.edu systemd-udevd[3368236]: Could not generate persistent MAC address for veth4ceb219: No such file or directory
Sep 19 03:03:34 sentry-docker00.cs.umd.edu systemd-udevd[3368246]: Could not generate persistent MAC address for vethd417f9a: No such file or directory
Sep 19 03:03:34 sentry-docker00.cs.umd.edu systemd-udevd[3368247]: Could not generate persistent MAC address for vethc7bfc8f: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 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 19 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 19 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 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 19 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 19 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 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 19 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.NxgO88/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 19 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.NxgO88. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 19 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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, 9 total) ==
Sep 19 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.amKiSy/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 19 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.amKiSy. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 19 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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.0577s
Status : exited 0
Output :
Syslog digest — 2026-09-19 02:05 EDT
Processed 3,385 lines, filtered 2,789 (82%). 596 unknown (199 distinct) from 20 host(s).
== atif01.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 01:31:35 atif01.cs.umd.edu kernel: net_ratelimit: 11 callbacks suppressed
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 01:50:15 b0b02.cs.umd.edu rustdesk[2724185]: cannot open display:
== bale (6 distinct, 84 total) ==
Sep 19 01:05:23 bale setroubleshoot[716468]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 19 01:05:23 bale setroubleshoot[716468]: 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 01:05:26 bale setroubleshoot[716468]: 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 01:05:29 bale setroubleshoot[716468]: 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 01:05:41 bale setroubleshoot[717095]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x12]
Sep 19 01:45:36 bale setroubleshoot[724876]: SELinux is preventing smartctl from 'read, open' accesses on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 1e5089ac-b715-4395-b985-b89be7cbd438
== csfw00a (1 distinct, 139 total) ==
Sep 19 01:03:48 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x139]
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 19 01:53:58 idm00 named[4166701]: client @0x7f11a4006dd8 10.73.240.42#59602: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 01:37:58 idmp0 named[1598691]: client @0x7f2d200319e8 10.73.240.43#55122: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 5 total) ==
Sep 19 01:13:31 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x5]
== krispykreme.cs.umd.edu (6 distinct, 7 total) ==
Sep 19 01:37:24 krispykreme.cs.umd.edu sshd-session[3911559]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2]
Sep 19 01:37:25 krispykreme.cs.umd.edu sshd-session[3911559]: Error in Duo login for 'larry' from 71.191.93.172
Sep 19 01:37:25 krispykreme.cs.umd.edu sshd-session[3911557]: error: PAM: Authentication failure for larry from 71.191.93.172
Sep 19 01:51:01 krispykreme.cs.umd.edu sshd-session[3914764]: pam_access(sshd:auth): access denied for user `admin' from `35.187.108.183'
Sep 19 01:51:01 krispykreme.cs.umd.edu krb5_child[3914766]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 19 01:51:01 krispykreme.cs.umd.edu sshd-session[3914762]: error: PAM: System error for admin from 35.187.108.183
== munin (2 distinct, 12 total) ==
Sep 19 01:09:01 munin sudo[28312]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6]
Sep 19 01:09:01 munin sudo[28312]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6]
== newhonors2 (1 distinct, 24 total) ==
Sep 19 01:13:02 newhonors2 dhcpcd[2838016]: dhcpcd is not running [x24]
== ntop00 (101 distinct, 145 total) ==
Sep 19 01:05:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 418) ***
Sep 19 01:05:22 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 6847/6847, ET: 21) ***
Sep 19 01:05:23 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 59/59, ET: 22) ***
Sep 19 01:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 419) ***
Sep 19 01:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 6992/6992, ET: 0) ***
Sep 19 01:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 419) ***
Sep 19 01:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 48/48, ET: 0) ***
Sep 19 01:08:02 ntop00 setroubleshoot[546990]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12]
Sep 19 01:08:02 ntop00 setroubleshoot[546990]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12]
Sep 19 01:08:02 ntop00 setroubleshoot[546990]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 01:08:02 ntop00 setroubleshoot[546990]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12]
Sep 19 01:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) ***
Sep 19 01:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) ***
Sep 19 01:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 51/51, ET: 0) ***
Sep 19 01:10:24 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 7276/7276, ET: 23) ***
Sep 19 01:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 421) ***
Sep 19 01:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 61/61, ET: 0) ***
Sep 19 01:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 421) ***
Sep 19 01:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 7545/7545, ET: 0) ***
Sep 19 01:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) ***
Sep 19 01:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) ***
Sep 19 01:15:25 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 7872/7872, ET: 24) ***
Sep 19 01:15:25 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 59/59, ET: 24) ***
Sep 19 01:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 423) ***
Sep 19 01:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 63/63, ET: 0) ***
Sep 19 01:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 423) ***
Sep 19 01:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 7844/7844, ET: 0) ***
Sep 19 01:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) ***
Sep 19 01:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) ***
Sep 19 01:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 72/72, ET: 0) ***
... 71 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 01:09:09 outbound00.cs.umd.edu python3[1539422]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 19 01:13:06 outbound01.cs.umd.edu python3[3797657]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320634]: link_config: could not get ethtool features for vethd4d10cc
Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320634]: Could not set offload features of vethd4d10cc: No such device
Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320668]: Could not generate persistent MAC address for veth0e90554: No such file or directory
Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320669]: Could not generate persistent MAC address for veth9b9a303: No such file or directory
Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320672]: Could not generate persistent MAC address for vethbaf7ddc: No such file or directory
Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320673]: Could not generate persistent MAC address for vethb357ffb: No such file or directory
Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320696]: Could not generate persistent MAC address for vethf2425ef: No such file or directory
Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320697]: Could not generate persistent MAC address for veth4eaf0f2: No such file or directory
Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320696]: Could not generate persistent MAC address for veth496652a: No such file or directory
Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320701]: Could not generate persistent MAC address for vethd579039: No such file or directory
Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320704]: Could not generate persistent MAC address for veth6ea75d5: No such file or directory
Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320710]: Could not generate persistent MAC address for veth5e78a7e: No such file or directory
Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330081]: link_config: could not set ethtool features for vethbaf7ddc
Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330081]: Could not set offload features of vethbaf7ddc: Operation not permitted
Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330121]: Could not generate persistent MAC address for veth3b9eae2: No such file or directory
Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330122]: Could not generate persistent MAC address for veth9ecbc95: No such file or directory
Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330126]: Could not generate persistent MAC address for veth7e857c7: No such file or directory
Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330125]: Could not generate persistent MAC address for veth5cbc686: No such file or directory
Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330125]: Could not generate persistent MAC address for vethad4adde: No such file or directory
Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330146]: Could not generate persistent MAC address for vetha4ee9d3: No such file or directory
Sep 19 01:43:01 sentry-docker00.cs.umd.edu systemd-udevd[3330152]: Could not generate persistent MAC address for veth707a0c5: No such file or directory
Sep 19 01:43:01 sentry-docker00.cs.umd.edu systemd-udevd[3330156]: Could not generate persistent MAC address for veth9b9d969: No such file or directory
Sep 19 01:43:01 sentry-docker00.cs.umd.edu systemd-udevd[3330189]: Could not generate persistent MAC address for veth9820e61: No such file or directory
Sep 19 01:43:01 sentry-docker00.cs.umd.edu systemd-udevd[3330186]: Could not generate persistent MAC address for veth23689d8: No such file or directory
Sep 19 02:03:09 sentry-docker00.cs.umd.edu systemd-udevd[3339491]: link_config: could not set ethtool features for veth707a0c5
Sep 19 02:03:09 sentry-docker00.cs.umd.edu systemd-udevd[3339491]: Could not set offload features of veth707a0c5: Operation not permitted
Sep 19 02:03:09 sentry-docker00.cs.umd.edu systemd-udevd[3339528]: Could not generate persistent MAC address for veth347fdab: No such file or directory
Sep 19 02:03:09 sentry-docker00.cs.umd.edu systemd-udevd[3339529]: Could not generate persistent MAC address for veth421aa8d: No such file or directory
Sep 19 02:03:09 sentry-docker00.cs.umd.edu systemd-udevd[3339532]: Could not generate persistent MAC address for veth04643e7: No such file or directory
Sep 19 02:03:09 sentry-docker00.cs.umd.edu systemd-udevd[3339533]: Could not generate persistent MAC address for veth2f1fe34: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 19 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 19 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 19 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 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 19 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 19 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (9 distinct, 12 total) ==
Sep 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: 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 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: 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 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033 [x2]
Sep 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.IkqhPV/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f [x2]
Sep 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba [x2]
Sep 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.IkqhPV. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: 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 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: 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 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: 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 19 01:24:46 submit26-b9-f4 setroubleshoot[1401957]: 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 01:24:46 submit26-b9-f4 setroubleshoot[1401957]: 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 01:24:46 submit26-b9-f4 setroubleshoot[1401957]: 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 01:24:46 submit26-b9-f4 setroubleshoot[1401957]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.WsFtHa/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 19 01:24:47 submit26-b9-f4 setroubleshoot[1401957]: 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 01:24:47 submit26-b9-f4 setroubleshoot[1401957]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.WsFtHa. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 19 01:24:47 submit26-b9-f4 setroubleshoot[1401957]: 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 01:24:47 submit26-b9-f4 setroubleshoot[1401957]: 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 01:24:47 submit26-b9-f4 setroubleshoot[1401957]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915
== teaching-awards (2 distinct, 2 total) ==
Sep 19 01:24:51 teaching-awards krb5_child[1064258]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 19 01:25:10 teaching-awards sshd-session[1064266]: error: Protocol major versions differ: 2 vs. 1
== tma-0 (1 distinct, 1 total) ==
Sep 19 01:49:40 tma-0 sshd[24870]: error: PAM: Authentication failure for admin from 71.221.175.207.bc.googleusercontent.com
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0593s
Status : exited 0
Output :
Syslog digest — 2026-09-19 01:05 EDT
Processed 3,069 lines, filtered 2,435 (79%). 634 unknown (216 distinct) from 32 host(s).
== abuse (3 distinct, 4 total) ==
Sep 19 00:10:13 abuse systemd[1]: New main PID 13129 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 19 00:10:32 abuse systemd[1]: Daemon never wrote its PID file. Failing.
Sep 19 00:10:42 abuse systemd[1]: pmlogger.service: Supervising process 20525 which is not our child. We'll most likely not notice when it exits.
== atif01.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 00:58:56 atif01.cs.umd.edu kernel: net_ratelimit: 11 callbacks suppressed
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 00:50:13 b0b02.cs.umd.edu rustdesk[2708595]: cannot open display:
== bachata (4 distinct, 4 total) ==
Sep 19 00:52:46 bachata smbd[768614]: [2026/09/19 00:52:46.152255, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service)
Sep 19 00:52:46 bachata smbd[768614]: chdir_current_service: vfs_ChDir(/fs/junkfood/larry) failed: Permission denied. Current token: uid=20263, gid=20263, 14 groups: 20263 25274 319000009 25057 25195 112012 25038 268 105273 276 25025 30066 15097 301
Sep 19 00:52:46 bachata smbd[768614]: [2026/09/19 00:52:46.153004, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect)
Sep 19 00:52:46 bachata smbd[768614]: smbXsrv_tcon_disconnect: disconnect(0xdcc80609, 'larry'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR
== bale (5 distinct, 84 total) ==
Sep 19 00:05:10 bale setroubleshoot[703193]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 19 00:05:10 bale setroubleshoot[703193]: 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 00:05:13 bale setroubleshoot[703193]: 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 00:05:16 bale setroubleshoot[703193]: 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 00:05:28 bale setroubleshoot[703809]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x12]
== biggulp.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 00:18:02 biggulp.cs.umd.edu systemd-coredump[2432252]: Process 3702710 (code-a44adf7f53) of user 14637 dumped core.#012#012Stack trace of thread 3702711:#012#0 0x00007f708d2037f0 n/a (n/a + 0x0)#012#1 0x00007f708d20119f n/a (n/a + 0x0)#012#2 0x00007f708d2029e0 n/a (n/a + 0x0)#012#3 0x00007f708c3ca7a4 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
== csfw00a (2 distinct, 139 total) ==
Sep 19 00:04:13 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x135]
Sep 19 00:56:29 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x4]
== grades01.cs.umd.edu (3 distinct, 4 total) ==
Sep 19 00:10:14 grades01.cs.umd.edu systemd[1]: New main PID 524 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 19 00:10:34 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 19 00:10:50 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 7940 which is not our child. We'll most likely not notice when it exits.
== idm00 (1 distinct, 1 total) ==
Sep 19 00:53:58 idm00 named[4166701]: client @0x7f11a93d09c8 10.73.240.42#64844: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 19 00:37:58 idmp0 named[1598691]: client @0x7f2d3802f8f8 10.73.240.43#57100: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 2 total) ==
Sep 19 00:12:20 inbound00.cs.umd.edu cockpit-ws[1654553]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2]
== inbound01.cs.umd.edu (1 distinct, 3 total) ==
Sep 19 00:12:22 inbound01.cs.umd.edu cockpit-ws[3872733]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x3]
== itmon02 (1 distinct, 1 total) ==
Sep 19 00:43:01 itmon02 sshd[1750555]: error: beginning MaxStartups throttling
== jubjub.cs.umd.edu (3 distinct, 4 total) ==
Sep 19 00:10:13 jubjub.cs.umd.edu systemd[1]: New main PID 3312234 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 19 00:10:33 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 19 00:10:41 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3319322 which is not our child. We'll most likely not notice when it exits.
== mirrors.cs.umd.edu (4 distinct, 6 total) ==
Sep 19 00:10:34 mirrors.cs.umd.edu root[4981]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log
Sep 19 00:10:34 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. [x2]
Sep 19 00:10:37 mirrors.cs.umd.edu systemd[1]: New main PID 3938 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 19 00:11:39 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 20558 which is not our child. We'll most likely not notice when it exits.
== misty.cs.umd.edu (3 distinct, 4 total) ==
Sep 19 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 40541 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 19 00:10:35 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 19 00:10:51 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 7904 which is not our child. We'll most likely not notice when it exits.
== munin (2 distinct, 76 total) ==
Sep 19 00:08:31 munin sudo[6418]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x38]
Sep 19 00:08:31 munin sudo[6418]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x38]
== netman.cs.umd.edu (3 distinct, 6 total) ==
Sep 19 00:57:24 netman.cs.umd.edu krb5_child[2207332]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Sep 19 00:57:28 netman.cs.umd.edu sshd[2207329]: error: PAM: Authentication failure for admin from 35.240.76.34
Sep 19 00:57:43 netman.cs.umd.edu sshd[2207392]: error: Protocol major versions differ: 2 vs. 1
== newhonors2 (1 distinct, 24 total) ==
Sep 19 00:13:03 newhonors2 dhcpcd[2836187]: dhcpcd is not running [x24]
== ntop00 (99 distinct, 143 total) ==
Sep 19 00:05:22 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 394, QN: 7106/7106, ET: 21) ***
Sep 19 00:05:22 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 394, QN: 63/63, ET: 21) ***
Sep 19 00:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 395) ***
Sep 19 00:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 395, QN: 6783/6783, ET: 0) ***
Sep 19 00:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 395) ***
Sep 19 00:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 395, QN: 64/64, ET: 0) ***
Sep 19 00:08:02 ntop00 setroubleshoot[539091]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12]
Sep 19 00:08:02 ntop00 setroubleshoot[539091]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12]
Sep 19 00:08:03 ntop00 setroubleshoot[539091]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 19 00:08:03 ntop00 setroubleshoot[539091]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12]
Sep 19 00:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 396) ***
Sep 19 00:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 396) ***
Sep 19 00:10:23 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 396, QN: 6802/6802, ET: 22) ***
Sep 19 00:10:23 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 396, QN: 80/80, ET: 22) ***
Sep 19 00:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 397) ***
Sep 19 00:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 397, QN: 6711/6711, ET: 0) ***
Sep 19 00:13:02 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 397) ***
Sep 19 00:13:02 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 397, QN: 74/74, ET: 0) ***
Sep 19 00:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 398) ***
Sep 19 00:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 398) ***
Sep 19 00:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 398, QN: 72/72, ET: 0) ***
Sep 19 00:15:19 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 398, QN: 6513/6513, ET: 18) ***
Sep 19 00:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 399) ***
Sep 19 00:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 399, QN: 60/60, ET: 0) ***
Sep 19 00:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 399) ***
Sep 19 00:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 399, QN: 6615/6615, ET: 0) ***
Sep 19 00:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 400) ***
Sep 19 00:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 400) ***
Sep 19 00:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 400, QN: 53/53, ET: 0) ***
Sep 19 00:20:20 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 400, QN: 6780/6780, ET: 19) ***
... 69 more distinct messages not shown
== openrepo (1 distinct, 1 total) ==
Sep 19 00:31:27 openrepo (nin-node)[2970949]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== outbound00.cs.umd.edu (2 distinct, 9 total) ==
Sep 19 00:09:08 outbound00.cs.umd.edu python3[1524134]: ldapdb [x6]
Sep 19 00:09:22 outbound00.cs.umd.edu cockpit-ws[1524150]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x3]
== outbound01.cs.umd.edu (2 distinct, 8 total) ==
Sep 19 00:13:06 outbound01.cs.umd.edu python3[3782900]: ldapdb [x6]
Sep 19 00:50:26 outbound01.cs.umd.edu cockpit-ws[3791118]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2]
== sebatinsky.cs.umd.edu (1 distinct, 1 total) ==
Sep 19 01:03:33 sebatinsky.cs.umd.edu sshd[3088059]: error: Protocol major versions differ: 2 vs. 1
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 19 00:22:27 sentry-docker00.cs.umd.edu systemd-udevd[3292195]: link_config: could not get ethtool features for vethd2c23ae
Sep 19 00:22:27 sentry-docker00.cs.umd.edu systemd-udevd[3292195]: Could not set offload features of vethd2c23ae: No such device
Sep 19 00:22:27 sentry-docker00.cs.umd.edu systemd-udevd[3292229]: Could not generate persistent MAC address for vethc1fe76a: No such file or directory
Sep 19 00:22:27 sentry-docker00.cs.umd.edu systemd-udevd[3292230]: Could not generate persistent MAC address for vethe2e1e4d: No such file or directory
Sep 19 00:22:27 sentry-docker00.cs.umd.edu systemd-udevd[3292234]: Could not generate persistent MAC address for vethdc1df9e: No such file or directory
Sep 19 00:22:27 sentry-docker00.cs.umd.edu systemd-udevd[3292233]: Could not generate persistent MAC address for veth710c435: No such file or directory
Sep 19 00:22:27 sentry-docker00.cs.umd.edu systemd-udevd[3292240]: Could not generate persistent MAC address for veth406d4a5: No such file or directory
Sep 19 00:22:27 sentry-docker00.cs.umd.edu systemd-udevd[3292246]: Could not generate persistent MAC address for vethf124c9d: No such file or directory
Sep 19 00:22:27 sentry-docker00.cs.umd.edu systemd-udevd[3292259]: Could not generate persistent MAC address for vethffdc1b9: No such file or directory
Sep 19 00:22:27 sentry-docker00.cs.umd.edu systemd-udevd[3292260]: Could not generate persistent MAC address for veth1ca76c5: No such file or directory
Sep 19 00:22:27 sentry-docker00.cs.umd.edu systemd-udevd[3292313]: Could not generate persistent MAC address for veth8697a21: No such file or directory
Sep 19 00:22:27 sentry-docker00.cs.umd.edu systemd-udevd[3292305]: Could not generate persistent MAC address for veth57d5f43: No such file or directory
Sep 19 00:42:35 sentry-docker00.cs.umd.edu systemd-udevd[3301537]: link_config: could not get ethtool features for veth710c435
Sep 19 00:42:35 sentry-docker00.cs.umd.edu systemd-udevd[3301537]: Could not set offload features of veth710c435: No such device
Sep 19 00:42:35 sentry-docker00.cs.umd.edu systemd-udevd[3301624]: link_config: could not get ethtool features for veth57d5f43
Sep 19 00:42:35 sentry-docker00.cs.umd.edu systemd-udevd[3301624]: Could not set offload features of veth57d5f43: No such device
Sep 19 00:42:35 sentry-docker00.cs.umd.edu systemd-udevd[3301652]: Could not generate persistent MAC address for vethd868afb: No such file or directory
Sep 19 00:42:35 sentry-docker00.cs.umd.edu systemd-udevd[3301653]: Could not generate persistent MAC address for vethf012b5f: No such file or directory
Sep 19 00:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3301685]: Could not generate persistent MAC address for vetha0c8668: No such file or directory
Sep 19 00:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3301687]: Could not generate persistent MAC address for vetha01635a: No such file or directory
Sep 19 00:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3301719]: Could not generate persistent MAC address for vetha86d1cf: No such file or directory
Sep 19 00:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3301727]: Could not generate persistent MAC address for veth12edc8a: No such file or directory
Sep 19 00:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3301763]: Could not generate persistent MAC address for vethe2b805a: No such file or directory
Sep 19 00:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3301759]: Could not generate persistent MAC address for veth2674017: No such file or directory
Sep 19 00:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3301777]: Could not generate persistent MAC address for vethd88394c: No such file or directory
Sep 19 00:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3301779]: Could not generate persistent MAC address for veth573b0c1: No such file or directory
Sep 19 01:02:44 sentry-docker00.cs.umd.edu systemd-udevd[3311017]: link_config: could not get ethtool features for veth12edc8a
Sep 19 01:02:44 sentry-docker00.cs.umd.edu systemd-udevd[3311017]: Could not set offload features of veth12edc8a: No such device
Sep 19 01:02:44 sentry-docker00.cs.umd.edu systemd-udevd[3311068]: Could not generate persistent MAC address for vethc4aae6c: No such file or directory
Sep 19 01:02:44 sentry-docker00.cs.umd.edu systemd-udevd[3311069]: Could not generate persistent MAC address for veth134f6e2: No such file or directory
... 8 more distinct messages not shown
== strawberry (8 distinct, 39 total) ==
Sep 19 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 19 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 19 00:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 19 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 19 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 19 00:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 19 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Sep 19 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing.
== submit10-cln25 (3 distinct, 4 total) ==
Sep 19 00:10:11 submit10-cln25 systemd: New main PID 17906 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 19 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing.
Sep 19 00:10:36 submit10-cln25 systemd: pmlogger.service: Supervising process 24806 which is not our child. We'll most likely not notice when it exits.
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 19 00:21:57 submit26-b9-fclone setroubleshoot[90616]: 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 00:21:57 submit26-b9-fclone setroubleshoot[90616]: 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 00:21:57 submit26-b9-fclone setroubleshoot[90616]: 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 00:21:57 submit26-b9-fclone setroubleshoot[90616]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Zwctc5/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 19 00:21:57 submit26-b9-fclone setroubleshoot[90616]: 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 00:21:57 submit26-b9-fclone setroubleshoot[90616]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Zwctc5. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 19 00:21:57 submit26-b9-fclone setroubleshoot[90616]: 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 00:21:57 submit26-b9-fclone setroubleshoot[90616]: 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 00:21:57 submit26-b9-fclone setroubleshoot[90616]: 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
== tma-0 (3 distinct, 4 total) ==
Sep 19 00:10:13 tma-0 systemd[1]: New main PID 29318 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 19 00:10:31 tma-0 systemd[1]: Daemon never wrote its PID file. Failing.
Sep 19 00:10:38 tma-0 systemd[1]: pmlogger.service: Supervising process 3948 which is not our child. We'll most likely not notice when it exits.
== uffish.cs.umd.edu (3 distinct, 4 total) ==
Sep 19 00:10:13 uffish.cs.umd.edu systemd[1]: New main PID 1750848 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 19 00:10:40 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 19 00:10:57 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1758554 which is not our child. We'll most likely not notice when it exits.
== vacuum.cs.umd.edu (3 distinct, 4 total) ==
Sep 19 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 13550 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 19 00:10:33 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 19 00:10:44 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 21102 which is not our child. We'll most likely not notice when it exits.
== whiffle.cs.umd.edu (3 distinct, 4 total) ==
Sep 19 00:10:13 whiffle.cs.umd.edu systemd[1]: New main PID 1315127 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 19 00:10:32 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 19 00:10:45 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1322241 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.0566s
Status : exited 0
Output :
Syslog digest — 2026-09-19 00:05 EDT
Processed 3,248 lines, filtered 2,672 (82%). 576 unknown (206 distinct) from 27 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 18 23:50:11 b0b02.cs.umd.edu rustdesk[2692810]: cannot open display:
== bale (5 distinct, 85 total) ==
Sep 18 23:05:57 bale setroubleshoot[690514]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 18 23:05:58 bale setroubleshoot[690514]: 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 18 23:06:00 bale setroubleshoot[690514]: 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 18 23:06:03 bale setroubleshoot[690514]: 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 18 23:06:15 bale setroubleshoot[691128]: 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 18 23:27:43 biggulp.cs.umd.edu sshd-session[2422203]: pam_access(sshd:auth): access denied for user `admin' from `34.14.25.5'
Sep 18 23:27:43 biggulp.cs.umd.edu krb5_child[2422205]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 18 23:27:43 biggulp.cs.umd.edu sshd-session[2422201]: error: PAM: System error for admin from 34.14.25.5
Sep 18 23:29:05 biggulp.cs.umd.edu sshd-session[2422581]: error: Protocol major versions differ: 2 vs. 1
Sep 18 23:52:18 biggulp.cs.umd.edu sshd-session[2426758]: pam_access(sshd:auth): access denied for user `admin' from `34.38.73.78'
Sep 18 23:52:19 biggulp.cs.umd.edu sshd-session[2426744]: error: PAM: System error for admin from 34.38.73.78
== csfw00a (1 distinct, 139 total) ==
Sep 18 23:04:18 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x139]
== idm00 (1 distinct, 1 total) ==
Sep 18 23:53:58 idm00 named[4166701]: client @0x7f11a4069dd8 10.73.240.42#63772: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 18 23:37:58 idmp0 named[1598691]: client @0x7f2d200319e8 10.73.240.43#62310: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 1 total) ==
Sep 18 23:27:41 inbound00.cs.umd.edu krb5_child[1643139]: Client 'backup(a)UMD.EDU' not found in Kerberos database
== inbound01.cs.umd.edu (1 distinct, 1 total) ==
Sep 18 23:50:52 inbound01.cs.umd.edu krb5_child[3866284]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 2 total) ==
Sep 18 23:48:35 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2]
== matrix (1 distinct, 1 total) ==
Sep 19 00:00:02 matrix (nin-node)[1925289]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== munin (1 distinct, 1 total) ==
Sep 19 00:00:15 munin (httpd)[3989]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== neo-gizmonic (1 distinct, 1 total) ==
Sep 19 00:00:01 neo-gizmonic (nin-node)[1664864]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neoavion (1 distinct, 1 total) ==
Sep 19 00:00:05 neoavion (nin-node)[3487398]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== netman.cs.umd.edu (2 distinct, 8 total) ==
Sep 18 23:16:28 netman.cs.umd.edu krb5_child[2178765]: Preauthentication failed [x4]
Sep 18 23:21:45 netman.cs.umd.edu krb5_child[2179939]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
== newhonors2 (2 distinct, 25 total) ==
Sep 18 23:13:03 newhonors2 dhcpcd[2834126]: dhcpcd is not running [x24]
Sep 19 00:00:16 newhonors2 (nin-node)[2835643]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== ntop00 (102 distinct, 146 total) ==
Sep 18 23:05:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 370) ***
Sep 18 23:05:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 370) ***
Sep 18 23:05:24 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 370, QN: 7741/7741, ET: 23) ***
Sep 18 23:05:24 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 370, QN: 64/64, ET: 23) ***
Sep 18 23:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 371) ***
Sep 18 23:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 371, QN: 66/66, ET: 0) ***
Sep 18 23:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 371) ***
Sep 18 23:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 371, QN: 8214/8214, ET: 0) ***
Sep 18 23:08:02 ntop00 setroubleshoot[531213]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12]
Sep 18 23:08:02 ntop00 setroubleshoot[531213]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12]
Sep 18 23:08:02 ntop00 setroubleshoot[531213]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 18 23:08:02 ntop00 setroubleshoot[531213]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12]
Sep 18 23:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 372) ***
Sep 18 23:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 372) ***
Sep 18 23:10:26 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 372, QN: 8369/8369, ET: 25) ***
Sep 18 23:10:27 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 372, QN: 75/75, ET: 26) ***
Sep 18 23:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 373) ***
Sep 18 23:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 373, QN: 8380/8380, ET: 0) ***
Sep 18 23:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 373) ***
Sep 18 23:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 373, QN: 78/78, ET: 0) ***
Sep 18 23:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 374) ***
Sep 18 23:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 374) ***
Sep 18 23:15:26 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 374, QN: 8621/8621, ET: 25) ***
Sep 18 23:15:26 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 374, QN: 72/72, ET: 25) ***
Sep 18 23:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 375) ***
Sep 18 23:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 375, QN: 8874/8874, ET: 0) ***
Sep 18 23:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 375) ***
Sep 18 23:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 375, QN: 72/72, ET: 0) ***
Sep 18 23:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 376) ***
Sep 18 23:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 376) ***
... 72 more distinct messages not shown
== outbound00.cs.umd.edu (25 distinct, 58 total) ==
Sep 18 23:09:08 outbound00.cs.umd.edu python3[1509632]: ldapdb [x6]
Sep 18 23:11:55 outbound00.cs.umd.edu krb5_child[1510304]: Client 'vinay(a)UMD.EDU' not found in Kerberos database
Sep 18 23:51:57 outbound00.cs.umd.edu krb5_child[1519470]: Preauthentication failed
Sep 18 23:52:09 outbound00.cs.umd.edu sshd-session[1519434]: error: maximum authentication attempts exceeded for root from 80.180.212.218 port 34628 ssh2 [preauth]
Sep 18 23:52:31 outbound00.cs.umd.edu sshd-session[1519547]: error: maximum authentication attempts exceeded for root from 80.180.212.218 port 38846 ssh2 [preauth]
Sep 18 23:52:50 outbound00.cs.umd.edu sshd-session[1519560]: error: maximum authentication attempts exceeded for root from 80.180.212.218 port 43408 ssh2 [preauth]
Sep 18 23:52:56 outbound00.cs.umd.edu krb5_child[1519608]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x16]
Sep 18 23:53:17 outbound00.cs.umd.edu sshd-session[1519580]: error: maximum authentication attempts exceeded for admin from 80.180.212.218 port 48188 ssh2 [preauth]
Sep 18 23:53:40 outbound00.cs.umd.edu sshd-session[1519711]: error: maximum authentication attempts exceeded for admin from 80.180.212.218 port 53132 ssh2 [preauth]
Sep 18 23:54:23 outbound00.cs.umd.edu sshd-session[1519772]: error: maximum authentication attempts exceeded for invalid user oracle from 80.180.212.218 port 33638 ssh2 [preauth]
Sep 18 23:54:47 outbound00.cs.umd.edu sshd-session[1519853]: error: maximum authentication attempts exceeded for invalid user oracle from 80.180.212.218 port 38786 ssh2 [preauth]
Sep 18 23:55:15 outbound00.cs.umd.edu sshd-session[1519866]: error: maximum authentication attempts exceeded for invalid user usuario from 80.180.212.218 port 45212 ssh2 [preauth]
Sep 18 23:55:39 outbound00.cs.umd.edu sshd-session[1520693]: error: maximum authentication attempts exceeded for invalid user usuario from 80.180.212.218 port 49516 ssh2 [preauth]
Sep 18 23:56:07 outbound00.cs.umd.edu sshd-session[1520725]: error: maximum authentication attempts exceeded for invalid user test from 80.180.212.218 port 56212 ssh2 [preauth]
Sep 18 23:56:29 outbound00.cs.umd.edu sshd-session[1521107]: error: maximum authentication attempts exceeded for invalid user test from 80.180.212.218 port 60746 ssh2 [preauth]
Sep 18 23:56:58 outbound00.cs.umd.edu sshd-session[1521119]: error: maximum authentication attempts exceeded for invalid user user from 80.180.212.218 port 38502 ssh2 [preauth]
Sep 18 23:57:18 outbound00.cs.umd.edu sshd-session[1521156]: error: maximum authentication attempts exceeded for invalid user user from 80.180.212.218 port 43000 ssh2 [preauth]
Sep 18 23:57:51 outbound00.cs.umd.edu sshd-session[1521234]: error: maximum authentication attempts exceeded for invalid user ftpuser from 80.180.212.218 port 49826 ssh2 [preauth]
Sep 18 23:58:13 outbound00.cs.umd.edu sshd-session[1521244]: error: maximum authentication attempts exceeded for invalid user ftpuser from 80.180.212.218 port 54064 ssh2 [preauth]
Sep 18 23:58:30 outbound00.cs.umd.edu krb5_child[1521556]: Client 'test1(a)UMD.EDU' not found in Kerberos database [x14]
Sep 18 23:58:47 outbound00.cs.umd.edu sshd-session[1521552]: error: maximum authentication attempts exceeded for test1 from 80.180.212.218 port 33570 ssh2 [preauth]
Sep 18 23:59:07 outbound00.cs.umd.edu sshd-session[1521572]: error: maximum authentication attempts exceeded for test1 from 80.180.212.218 port 37734 ssh2 [preauth]
Sep 18 23:59:33 outbound00.cs.umd.edu sshd-session[1521931]: error: maximum authentication attempts exceeded for invalid user test2 from 80.180.212.218 port 43506 ssh2 [preauth]
Sep 18 23:59:52 outbound00.cs.umd.edu sshd-session[1521954]: error: maximum authentication attempts exceeded for invalid user test2 from 80.180.212.218 port 47440 ssh2 [preauth]
Sep 19 00:00:24 outbound00.cs.umd.edu sshd-session[1522003]: error: maximum authentication attempts exceeded for invalid user ubuntu from 80.180.212.218 port 53004 ssh2 [preauth]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 18 23:13:06 outbound01.cs.umd.edu python3[3768098]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 18 23:22:02 sentry-docker00.cs.umd.edu systemd-udevd[3263874]: link_config: could not get ethtool features for veth7a5f72a
Sep 18 23:22:02 sentry-docker00.cs.umd.edu systemd-udevd[3263874]: Could not set offload features of veth7a5f72a: No such device
Sep 18 23:22:02 sentry-docker00.cs.umd.edu systemd-udevd[3263932]: Could not generate persistent MAC address for vethd0bccc5: No such file or directory
Sep 18 23:22:02 sentry-docker00.cs.umd.edu systemd-udevd[3263933]: Could not generate persistent MAC address for veth00bfa32: No such file or directory
Sep 18 23:22:02 sentry-docker00.cs.umd.edu systemd-udevd[3263958]: Could not generate persistent MAC address for veth0cefaa7: No such file or directory
Sep 18 23:22:02 sentry-docker00.cs.umd.edu systemd-udevd[3263959]: Could not generate persistent MAC address for veth4ba62fc: No such file or directory
Sep 18 23:22:02 sentry-docker00.cs.umd.edu systemd-udevd[3263962]: Could not generate persistent MAC address for veth8e374e6: No such file or directory
Sep 18 23:22:02 sentry-docker00.cs.umd.edu systemd-udevd[3263963]: Could not generate persistent MAC address for vetha296924: No such file or directory
Sep 18 23:22:02 sentry-docker00.cs.umd.edu systemd-udevd[3264005]: Could not generate persistent MAC address for vethef51a53: No such file or directory
Sep 18 23:22:02 sentry-docker00.cs.umd.edu systemd-udevd[3264006]: Could not generate persistent MAC address for veth6452da5: No such file or directory
Sep 18 23:22:02 sentry-docker00.cs.umd.edu systemd-udevd[3264037]: Could not generate persistent MAC address for vethb106498: No such file or directory
Sep 18 23:22:02 sentry-docker00.cs.umd.edu systemd-udevd[3264027]: Could not generate persistent MAC address for veth775e429: No such file or directory
Sep 18 23:42:10 sentry-docker00.cs.umd.edu systemd-udevd[3273299]: link_config: could not get ethtool features for vethb106498
Sep 18 23:42:10 sentry-docker00.cs.umd.edu systemd-udevd[3273299]: Could not set offload features of vethb106498: No such device
Sep 18 23:42:11 sentry-docker00.cs.umd.edu systemd-udevd[3273331]: Could not generate persistent MAC address for vethe0f0b78: No such file or directory
Sep 18 23:42:11 sentry-docker00.cs.umd.edu systemd-udevd[3273332]: Could not generate persistent MAC address for vethc92375b: No such file or directory
Sep 18 23:42:11 sentry-docker00.cs.umd.edu systemd-udevd[3273335]: Could not generate persistent MAC address for vethad01e59: No such file or directory
Sep 18 23:42:11 sentry-docker00.cs.umd.edu systemd-udevd[3273336]: Could not generate persistent MAC address for vethd26bb81: No such file or directory
Sep 18 23:42:11 sentry-docker00.cs.umd.edu systemd-udevd[3273352]: Could not generate persistent MAC address for veth78cbf41: No such file or directory
Sep 18 23:42:11 sentry-docker00.cs.umd.edu systemd-udevd[3273355]: Could not generate persistent MAC address for vethdf3a4c5: No such file or directory
Sep 18 23:42:11 sentry-docker00.cs.umd.edu systemd-udevd[3273361]: Could not generate persistent MAC address for veth04975dd: No such file or directory
Sep 18 23:42:11 sentry-docker00.cs.umd.edu systemd-udevd[3273362]: Could not generate persistent MAC address for vetha409637: No such file or directory
Sep 18 23:42:11 sentry-docker00.cs.umd.edu systemd-udevd[3273380]: Could not generate persistent MAC address for veth9b0d9bb: No such file or directory
Sep 18 23:42:11 sentry-docker00.cs.umd.edu systemd-udevd[3273370]: Could not generate persistent MAC address for veth1c4c977: No such file or directory
Sep 19 00:02:19 sentry-docker00.cs.umd.edu systemd-udevd[3282697]: link_config: could not get ethtool features for vethe0f0b78
Sep 19 00:02:19 sentry-docker00.cs.umd.edu systemd-udevd[3282697]: Could not set offload features of vethe0f0b78: No such device
Sep 19 00:02:19 sentry-docker00.cs.umd.edu systemd-udevd[3282730]: Could not generate persistent MAC address for veth26f97d7: No such file or directory
Sep 19 00:02:19 sentry-docker00.cs.umd.edu systemd-udevd[3282731]: Could not generate persistent MAC address for vethc533ded: No such file or directory
Sep 19 00:02:19 sentry-docker00.cs.umd.edu systemd-udevd[3282734]: Could not generate persistent MAC address for veth9bb9289: No such file or directory
Sep 19 00:02:19 sentry-docker00.cs.umd.edu systemd-udevd[3282735]: Could not generate persistent MAC address for vetha90facb: No such file or directory
... 6 more distinct messages not shown
== soul (2 distinct, 2 total) ==
Sep 18 23:50:12 soul krb5_child[3407384]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 18 23:52:00 soul sshd-session[3407875]: error: Protocol major versions differ: 2 vs. 1
== strawberry (7 distinct, 38 total) ==
Sep 18 23:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 18 23:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 18 23:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 18 23:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 18 23:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 18 23:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 18 23:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 4 total) ==
Sep 18 23:12:17 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f2 (1 distinct, 3 total) ==
Sep 18 23:08:53 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f3 (1 distinct, 2 total) ==
Sep 18 23:30:05 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f4 (1 distinct, 3 total) ==
Sep 18 23:22:04 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== wraith (2 distinct, 2 total) ==
Sep 19 00:00:00 wraith kernel: kauditd_printk_skb: 4 callbacks suppressed
Sep 19 00:00:00 wraith (nin-node)[699247]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== zwicker-computer (1 distinct, 1 total) ==
Sep 19 00:00:03 zwicker-computer kernel: kauditd_printk_skb: 2 callbacks suppressed
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0581s
Status : exited 0
Output :
Syslog digest — 2026-09-18 23:05 EDT
Processed 2,865 lines, filtered 2,282 (79%). 583 unknown (202 distinct) from 24 host(s).
== abadi-computer (2 distinct, 2 total) ==
Sep 18 22:18:33 abadi-computer systemd-tmpfiles[1238541]: Opening file "/tmp/code-d3f5f468-a541-4c48-86b8-68d2e40cb325" failed, ignoring: No such device or address
Sep 18 22:18:33 abadi-computer systemd-tmpfiles[1238541]: Opening file "/tmp/code-820064ef-588d-4ff0-b797-7ee04527a374" failed, ignoring: No such device or address
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 18 22:50:10 b0b02.cs.umd.edu rustdesk[2677642]: cannot open display:
== bale (5 distinct, 84 total) ==
Sep 18 22:05:39 bale setroubleshoot[677795]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 18 22:05:40 bale setroubleshoot[677795]: 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 18 22:05:42 bale setroubleshoot[677795]: 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 18 22:05:45 bale setroubleshoot[677795]: 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 18 22:05:57 bale setroubleshoot[678410]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x12]
== csfw00a (2 distinct, 152 total) ==
Sep 18 22:04:03 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x146]
Sep 18 22:37:04 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x6]
== idm00 (1 distinct, 1 total) ==
Sep 18 22:53:58 idm00 named[4166701]: client @0x7f11a402f3b8 10.73.240.42#61776: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 18 22:37:58 idmp0 named[1598691]: client @0x7f2d38010098 10.73.240.43#58052: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (3 distinct, 21 total) ==
Sep 18 22:05:58 inbound00.cs.umd.edu krb5_child[1622814]: Preauthentication failed [x8]
Sep 18 22:08:12 inbound00.cs.umd.edu krb5_child[1623408]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x12]
Sep 18 22:12:41 inbound00.cs.umd.edu krb5_child[1624626]: Client 'brenda(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 2 total) ==
Sep 18 22:08:10 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2]
== matrix (2 distinct, 3 total) ==
Sep 18 23:04:44 matrix krb5_child[1893718]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 18 23:04:46 matrix sshd[1893712]: error: PAM: Authentication failure for admin from 207.175.221.71
== mcstic (3 distinct, 6 total) ==
Sep 18 22:25:37 mcstic krb5_child[786667]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Sep 18 22:25:43 mcstic sshd[786662]: error: PAM: Authentication failure for admin from 34.34.148.123
Sep 18 22:31:41 mcstic sshd[786753]: error: Protocol major versions differ: 2 vs. 1
== munin (2 distinct, 12 total) ==
Sep 18 22:43:38 munin sudo[4169530]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6]
Sep 18 22:43:38 munin sudo[4169530]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6]
== newhonors.cs.umd.edu (1 distinct, 1 total) ==
Sep 18 22:57: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 18 22:13:02 newhonors2 dhcpcd[2832281]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 18 22:05:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 346) ***
Sep 18 22:05:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 346) ***
Sep 18 22:05:25 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 7810/7810, ET: 24) ***
Sep 18 22:05:25 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 61/61, ET: 24) ***
Sep 18 22:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 347) ***
Sep 18 22:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 7683/7683, ET: 0) ***
Sep 18 22:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 347) ***
Sep 18 22:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 59/59, ET: 0) ***
Sep 18 22:08:02 ntop00 setroubleshoot[523323]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12]
Sep 18 22:08:02 ntop00 setroubleshoot[523323]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12]
Sep 18 22:08:02 ntop00 setroubleshoot[523323]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 18 22:08:02 ntop00 setroubleshoot[523323]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12]
Sep 18 22:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) ***
Sep 18 22:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) ***
Sep 18 22:10:24 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 7697/7697, ET: 23) ***
Sep 18 22:10:24 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 60/60, ET: 23) ***
Sep 18 22:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 349) ***
Sep 18 22:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 7380/7380, ET: 0) ***
Sep 18 22:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 349) ***
Sep 18 22:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 67/67, ET: 0) ***
Sep 18 22:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) ***
Sep 18 22:15:02 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) ***
Sep 18 22:15:23 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 7433/7433, ET: 22) ***
Sep 18 22:15:23 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 66/66, ET: 21) ***
Sep 18 22:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 351) ***
Sep 18 22:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 61/61, ET: 0) ***
Sep 18 22:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 351) ***
Sep 18 22:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 7284/7284, ET: 0) ***
Sep 18 22:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) ***
Sep 18 22:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (4 distinct, 9 total) ==
Sep 18 22:05:21 outbound00.cs.umd.edu krb5_child[1494538]: Client 'backup(a)UMD.EDU' not found in Kerberos database
Sep 18 22:09:09 outbound00.cs.umd.edu python3[1495464]: ldapdb [x6]
Sep 18 22:11:56 outbound00.cs.umd.edu krb5_child[1496130]: Preauthentication failed
Sep 18 22:21:11 outbound00.cs.umd.edu krb5_child[1498298]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== outbound01.cs.umd.edu (2 distinct, 7 total) ==
Sep 18 22:13:06 outbound01.cs.umd.edu python3[3754178]: ldapdb [x6]
Sep 18 22:24:21 outbound01.cs.umd.edu krb5_child[3756490]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235619]: link_config: could not get ethtool features for veth4415fcf
Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235619]: Could not set offload features of veth4415fcf: No such device
Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235653]: Could not generate persistent MAC address for vethe3e0407: No such file or directory
Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235654]: Could not generate persistent MAC address for veth52d2037: No such file or directory
Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235657]: Could not generate persistent MAC address for vethe46109f: No such file or directory
Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235658]: Could not generate persistent MAC address for vethd611c1f: No such file or directory
Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235681]: Could not generate persistent MAC address for veth798d99e: No such file or directory
Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235682]: Could not generate persistent MAC address for veth7320007: No such file or directory
Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235682]: Could not generate persistent MAC address for veth12d6f69: No such file or directory
Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235689]: Could not generate persistent MAC address for vethc023c7f: No such file or directory
Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235742]: Could not generate persistent MAC address for veth6763bb4: No such file or directory
Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235748]: Could not generate persistent MAC address for veth9396cd1: No such file or directory
Sep 18 22:41:45 sentry-docker00.cs.umd.edu systemd-udevd[3244969]: link_config: could not get ethtool features for vethe46109f
Sep 18 22:41:45 sentry-docker00.cs.umd.edu systemd-udevd[3244969]: Could not set offload features of vethe46109f: No such device
Sep 18 22:41:45 sentry-docker00.cs.umd.edu systemd-udevd[3245045]: Could not generate persistent MAC address for veth290c308: No such file or directory
Sep 18 22:41:45 sentry-docker00.cs.umd.edu systemd-udevd[3245046]: Could not generate persistent MAC address for veth1fa5d3e: No such file or directory
Sep 18 22:41:45 sentry-docker00.cs.umd.edu systemd-udevd[3245071]: Could not generate persistent MAC address for vetha583529: No such file or directory
Sep 18 22:41:45 sentry-docker00.cs.umd.edu systemd-udevd[3245072]: Could not generate persistent MAC address for veth18b30c6: No such file or directory
Sep 18 22:41:46 sentry-docker00.cs.umd.edu systemd-udevd[3245101]: Could not generate persistent MAC address for vethc2204f4: No such file or directory
Sep 18 22:41:46 sentry-docker00.cs.umd.edu systemd-udevd[3245076]: Could not generate persistent MAC address for veth313c91b: No such file or directory
Sep 18 22:41:46 sentry-docker00.cs.umd.edu systemd-udevd[3245075]: Could not generate persistent MAC address for veth7236f39: No such file or directory
Sep 18 22:41:46 sentry-docker00.cs.umd.edu systemd-udevd[3245091]: Could not generate persistent MAC address for veth72d18de: No such file or directory
Sep 18 22:41:46 sentry-docker00.cs.umd.edu systemd-udevd[3245171]: Could not generate persistent MAC address for vethe2ac62f: No such file or directory
Sep 18 22:41:46 sentry-docker00.cs.umd.edu systemd-udevd[3245173]: Could not generate persistent MAC address for vetha4e8aee: No such file or directory
Sep 18 23:01:54 sentry-docker00.cs.umd.edu systemd-udevd[3254380]: link_config: could not get ethtool features for vethc2204f4
Sep 18 23:01:54 sentry-docker00.cs.umd.edu systemd-udevd[3254380]: Could not set offload features of vethc2204f4: No such device
Sep 18 23:01:54 sentry-docker00.cs.umd.edu systemd-udevd[3254493]: Could not generate persistent MAC address for vethfe09d09: No such file or directory
Sep 18 23:01:54 sentry-docker00.cs.umd.edu systemd-udevd[3254494]: Could not generate persistent MAC address for veth68da808: No such file or directory
Sep 18 23:01:54 sentry-docker00.cs.umd.edu systemd-udevd[3254503]: Could not generate persistent MAC address for veth0711688: No such file or directory
Sep 18 23:01:54 sentry-docker00.cs.umd.edu systemd-udevd[3254496]: Could not generate persistent MAC address for veth26d5a38: No such file or directory
... 6 more distinct messages not shown
== soul (1 distinct, 1 total) ==
Sep 18 22:05:35 soul krb5_child[3391301]: Preauthentication failed
== strawberry (7 distinct, 38 total) ==
Sep 18 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 18 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 18 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 18 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 18 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 18 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 18 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (11 distinct, 15 total) ==
Sep 18 22:17:59 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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 [x2]
Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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 [x2]
Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.LvJHDh/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.LvJHDh. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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 [x2]
Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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 [x2]
Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GXZqnU. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
== submit26-b9-f2 (10 distinct, 16 total) ==
Sep 18 22:06:48 submit26-b9-f2 setroubleshoot[1533678]: 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 18 22:06:48 submit26-b9-f2 setroubleshoot[1533678]: 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 18 22:06:48 submit26-b9-f2 setroubleshoot[1533678]: 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 18 22:06:48 submit26-b9-f2 setroubleshoot[1533678]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.q71MoX/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2]
Sep 18 22:06:48 submit26-b9-f2 setroubleshoot[1533678]: 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 18 22:06:49 submit26-b9-f2 setroubleshoot[1533678]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.q71MoX. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 18 22:06:49 submit26-b9-f2 setroubleshoot[1533678]: 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 18 22:06:49 submit26-b9-f2 setroubleshoot[1533678]: 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 18 22:06:49 submit26-b9-f2 setroubleshoot[1533678]: 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 18 22:33:07 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f4 (1 distinct, 2 total) ==
Sep 18 22:10:21 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== teaching-awards (1 distinct, 1 total) ==
Sep 18 23:02:05 teaching-awards sshd-session[1056971]: error: maximum authentication attempts exceeded for root from 80.180.212.218 port 54576 ssh2 [preauth]
== vacuum.cs.umd.edu (4 distinct, 4 total) ==
Sep 18 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[15218]: Process 10780 (driver) of user 33 killed by SIGABRT - dumping core
Sep 18 22:11:59 vacuum.cs.umd.edu abrt-server[15220]: Package 'amanda-backup_server' isn't signed with proper key
Sep 18 22:11:59 vacuum.cs.umd.edu abrt-server[15220]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-18-22:11:58-10780' exited with 1
Sep 18 22:11:59 vacuum.cs.umd.edu abrt-server[15220]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-18-22:11:58-10780'
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0542s
Status : exited 0
Output :
Syslog digest — 2026-09-18 22:05 EDT
Processed 2,596 lines, filtered 2,023 (77%). 573 unknown (190 distinct) from 22 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 18 21:50:06 b0b02.cs.umd.edu rustdesk[2662125]: cannot open display:
== bale (5 distinct, 87 total) ==
Sep 18 21:05:47 bale setroubleshoot[664853]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 18 21:05:47 bale setroubleshoot[664853]: 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 18 21:05:50 bale setroubleshoot[664853]: 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 18 21:05:53 bale setroubleshoot[664853]: 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 18 21:06:05 bale setroubleshoot[665467]: 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, 137 total) ==
Sep 18 21:03:56 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x137]
== idm00 (1 distinct, 1 total) ==
Sep 18 21:53:57 idm00 named[4166701]: client @0x7f11a4006dd8 10.73.240.42#64664: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 18 21:37:58 idmp0 named[1598691]: client @0x7f2d2401e448 10.73.240.43#60756: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (5 distinct, 29 total) ==
Sep 18 21:19:17 inbound00.cs.umd.edu krb5_child[1610304]: Preauthentication failed [x17]
Sep 18 21:22:02 inbound00.cs.umd.edu krb5_child[1611265]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x9]
Sep 18 21:57:39 inbound00.cs.umd.edu krb5_child[1620778]: Client 'george(a)UMD.EDU' not found in Kerberos database
Sep 18 21:59:18 inbound00.cs.umd.edu krb5_child[1621211]: Client 'anton(a)UMD.EDU' not found in Kerberos database
Sep 18 21:59:58 inbound00.cs.umd.edu krb5_child[1621341]: Client 'gitlab(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 2 total) ==
Sep 18 21:08:49 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2]
== krispykreme.cs.umd.edu (1 distinct, 2 total) ==
Sep 18 21:41:26 krispykreme.cs.umd.edu sshd-session[3845849]: pam_access(sshd:auth): access denied for user `rztao' from `52.119.65.102' [x2]
== munin (2 distinct, 28 total) ==
Sep 18 21:08:54 munin sudo[4135202]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x14]
Sep 18 21:08:54 munin sudo[4135202]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x14]
== netman.cs.umd.edu (1 distinct, 2 total) ==
Sep 18 21:08:38 netman.cs.umd.edu krb5_child[2142809]: Preauthentication failed [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 18 21:13:03 newhonors2 dhcpcd[2830440]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 18 21:05:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) ***
Sep 18 21:05:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) ***
Sep 18 21:05:38 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 12888/12888, ET: 37) ***
Sep 18 21:05:38 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 56/56, ET: 37) ***
Sep 18 21:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 323) ***
Sep 18 21:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 55/55, ET: 0) ***
Sep 18 21:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 323) ***
Sep 18 21:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 12946/12946, ET: 0) ***
Sep 18 21:08:02 ntop00 setroubleshoot[515285]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12]
Sep 18 21:08:02 ntop00 setroubleshoot[515285]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12]
Sep 18 21:08:02 ntop00 setroubleshoot[515285]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 18 21:08:02 ntop00 setroubleshoot[515285]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12]
Sep 18 21:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) ***
Sep 18 21:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) ***
Sep 18 21:10:40 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 13114/13114, ET: 39) ***
Sep 18 21:10:40 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 62/62, ET: 39) ***
Sep 18 21:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 325) ***
Sep 18 21:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 69/69, ET: 0) ***
Sep 18 21:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 325) ***
Sep 18 21:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 13069/13069, ET: 0) ***
Sep 18 21:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) ***
Sep 18 21:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) ***
Sep 18 21:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 65/65, ET: 0) ***
Sep 18 21:15:36 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 12799/12799, ET: 35) ***
Sep 18 21:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 327) ***
Sep 18 21:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 327) ***
Sep 18 21:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 65/65, ET: 0) ***
Sep 18 21:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 11811/11811, ET: 0) ***
Sep 18 21:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) ***
Sep 18 21:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (2 distinct, 7 total) ==
Sep 18 21:09:09 outbound00.cs.umd.edu python3[1481503]: ldapdb [x6]
Sep 18 22:01:23 outbound00.cs.umd.edu krb5_child[1494051]: Preauthentication failed
== outbound01.cs.umd.edu (2 distinct, 7 total) ==
Sep 18 21:13:06 outbound01.cs.umd.edu python3[3740033]: ldapdb [x6]
Sep 18 21:27:22 outbound01.cs.umd.edu krb5_child[3743721]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207098]: Could not generate persistent MAC address for veth399b566: No such file or directory
Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207099]: Could not generate persistent MAC address for vethc5dba78: No such file or directory
Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207123]: Could not generate persistent MAC address for veth1c2519f: No such file or directory
Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207117]: Could not generate persistent MAC address for veth2924a8d: No such file or directory
Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207126]: Could not generate persistent MAC address for vethe882141: No such file or directory
Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207127]: Could not generate persistent MAC address for veth0133c31: No such file or directory
Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207126]: Could not generate persistent MAC address for veth13791d1: No such file or directory
Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207146]: Could not generate persistent MAC address for veth4dc0625: No such file or directory
Sep 18 21:21:13 sentry-docker00.cs.umd.edu systemd-udevd[3207186]: Could not generate persistent MAC address for veth26d56b8: No such file or directory
Sep 18 21:21:13 sentry-docker00.cs.umd.edu systemd-udevd[3207190]: Could not generate persistent MAC address for vethc0968dd: No such file or directory
Sep 18 21:41:20 sentry-docker00.cs.umd.edu systemd-udevd[3216734]: link_config: could not get ethtool features for veth26d56b8
Sep 18 21:41:20 sentry-docker00.cs.umd.edu systemd-udevd[3216734]: Could not set offload features of veth26d56b8: No such device
Sep 18 21:41:20 sentry-docker00.cs.umd.edu systemd-udevd[3216758]: Could not generate persistent MAC address for vethbece149: No such file or directory
Sep 18 21:41:20 sentry-docker00.cs.umd.edu systemd-udevd[3216759]: Could not generate persistent MAC address for vethb6af48c: No such file or directory
Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216806]: Could not generate persistent MAC address for veth4edf6a8: No such file or directory
Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216807]: Could not generate persistent MAC address for veth2ea7a3c: No such file or directory
Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216818]: Could not generate persistent MAC address for vethe6d40f8: No such file or directory
Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216819]: Could not generate persistent MAC address for vethf45f226: No such file or directory
Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216849]: Could not generate persistent MAC address for veth258af61: No such file or directory
Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216851]: Could not generate persistent MAC address for vethb7a86bd: No such file or directory
Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216883]: Could not generate persistent MAC address for vetha230122: No such file or directory
Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216884]: Could not generate persistent MAC address for veth5aeb518: No such file or directory
Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226161]: link_config: could not get ethtool features for vetha230122
Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226161]: Could not set offload features of vetha230122: No such device
Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226231]: Could not generate persistent MAC address for veth4415fcf: No such file or directory
Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226232]: Could not generate persistent MAC address for vethc6ab66f: No such file or directory
Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226235]: Could not generate persistent MAC address for veth5f8d8e9: No such file or directory
Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226236]: Could not generate persistent MAC address for vethfc3a163: No such file or directory
Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226284]: Could not generate persistent MAC address for veth3761173: No such file or directory
Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226285]: Could not generate persistent MAC address for vethe499e41: No such file or directory
... 4 more distinct messages not shown
== soul (1 distinct, 1 total) ==
Sep 18 21:08:54 soul krb5_child[3382092]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== strawberry (7 distinct, 38 total) ==
Sep 18 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 18 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 18 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 18 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 18 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 18 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 18 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 3 total) ==
Sep 18 21:08:05 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f2 (1 distinct, 1 total) ==
Sep 18 21:28:06 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f3 (10 distinct, 12 total) ==
Sep 18 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 18 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 18 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 18 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.NPFxXF/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 18 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 18 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.NPFxXF. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 18 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 18 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 18 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 18 21:08:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f4 (10 distinct, 10 total) ==
Sep 18 21:08:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
Sep 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.8mcYH8/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.8mcYH8. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 (2 distinct, 2 total) ==
Sep 18 21:37:36 tma-0 sshd[29335]: error: maximum authentication attempts exceeded for root from 129.151.171.7 port 41164 ssh2 [preauth]
Sep 18 21:37:36 tma-0 sshd[29335]: PAM service(sshd) ignoring max retries; 6 > 3
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0536s
Status : exited 0
Output :
Syslog digest — 2026-09-18 21:05 EDT
Processed 2,595 lines, filtered 2,015 (77%). 580 unknown (180 distinct) from 21 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 18 20:50:02 b0b02.cs.umd.edu rustdesk[2646927]: cannot open display:
== bale (5 distinct, 84 total) ==
Sep 18 20:05:32 bale setroubleshoot[652135]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 18 20:05:33 bale setroubleshoot[652135]: 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 18 20:05:35 bale setroubleshoot[652135]: 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 18 20:05:38 bale setroubleshoot[652135]: 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 18 20:05:50 bale setroubleshoot[652758]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x12]
== csfw00a (1 distinct, 122 total) ==
Sep 18 20:05:27 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x122]
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Sep 18 20:05:58 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 18 20:05:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 18 20:05:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 18 20:05:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 18 20:05:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 18 20:05:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 18 20:05:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 18 20:05:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 18 20:05:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 18 20:05:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 18 20:05:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 18 20:53:57 idm00 named[4166701]: client @0x7f1198074538 10.73.240.42#58188: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 18 20:37:58 idmp0 named[1598691]: client @0x7f2d4803e0e8 10.73.240.43#57633: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 2 total) ==
Sep 18 20:14:08 inbound00.cs.umd.edu krb5_child[1595192]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
== itmon02 (1 distinct, 7 total) ==
Sep 18 20:08:34 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x7]
== munin (2 distinct, 16 total) ==
Sep 18 21:03:43 munin sudo[4133390]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x8]
Sep 18 21:03:43 munin sudo[4133390]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x8]
== newhonors2 (1 distinct, 24 total) ==
Sep 18 20:13:03 newhonors2 dhcpcd[2828501]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 18 20:05:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 298) ***
Sep 18 20:05:02 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 298) ***
Sep 18 20:05:38 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 13954/13954, ET: 37) ***
Sep 18 20:05:38 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 61/61, ET: 36) ***
Sep 18 20:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 299) ***
Sep 18 20:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 299) ***
Sep 18 20:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 68/68, ET: 0) ***
Sep 18 20:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 14933/14933, ET: 0) ***
Sep 18 20:08:02 ntop00 setroubleshoot[507410]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12]
Sep 18 20:08:02 ntop00 setroubleshoot[507410]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12]
Sep 18 20:08:02 ntop00 setroubleshoot[507410]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 18 20:08:02 ntop00 setroubleshoot[507410]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12]
Sep 18 20:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) ***
Sep 18 20:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) ***
Sep 18 20:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 70/70, ET: 0) ***
Sep 18 20:10:46 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 17070/17070, ET: 45) ***
Sep 18 20:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 301) ***
Sep 18 20:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 301) ***
Sep 18 20:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 66/66, ET: 0) ***
Sep 18 20:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 18302/18302, ET: 0) ***
Sep 18 20:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) ***
Sep 18 20:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) ***
Sep 18 20:15:49 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 18088/18088, ET: 48) ***
Sep 18 20:15:50 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 59/59, ET: 49) ***
Sep 18 20:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 303) ***
Sep 18 20:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 60/60, ET: 0) ***
Sep 18 20:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 303) ***
Sep 18 20:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 17693/17693, ET: 0) ***
Sep 18 20:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) ***
Sep 18 20:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 18 20:09:09 outbound00.cs.umd.edu python3[1467557]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 18 20:13:07 outbound01.cs.umd.edu python3[3726108]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (32 distinct, 32 total) ==
Sep 18 20:20:47 sentry-docker00.cs.umd.edu systemd-udevd[3178792]: link_config: could not get ethtool features for vethfa2f0fd
Sep 18 20:20:47 sentry-docker00.cs.umd.edu systemd-udevd[3178792]: Could not set offload features of vethfa2f0fd: No such device
Sep 18 20:20:47 sentry-docker00.cs.umd.edu systemd-udevd[3178865]: Could not generate persistent MAC address for vethe291b92: No such file or directory
Sep 18 20:20:47 sentry-docker00.cs.umd.edu systemd-udevd[3178866]: Could not generate persistent MAC address for veth14f1e6c: No such file or directory
Sep 18 20:20:47 sentry-docker00.cs.umd.edu systemd-udevd[3178882]: Could not generate persistent MAC address for veth4f32a8b: No such file or directory
Sep 18 20:20:47 sentry-docker00.cs.umd.edu systemd-udevd[3178866]: Could not generate persistent MAC address for veth8c3da92: No such file or directory
Sep 18 20:20:47 sentry-docker00.cs.umd.edu systemd-udevd[3178873]: Could not generate persistent MAC address for veth8637963: No such file or directory
Sep 18 20:20:47 sentry-docker00.cs.umd.edu systemd-udevd[3178875]: Could not generate persistent MAC address for veth05950fb: No such file or directory
Sep 18 20:20:47 sentry-docker00.cs.umd.edu systemd-udevd[3178873]: Could not generate persistent MAC address for vethcfbff1c: No such file or directory
Sep 18 20:20:47 sentry-docker00.cs.umd.edu systemd-udevd[3178875]: Could not generate persistent MAC address for vethdfcd196: No such file or directory
Sep 18 20:20:47 sentry-docker00.cs.umd.edu systemd-udevd[3178987]: Could not generate persistent MAC address for veth4945cec: No such file or directory
Sep 18 20:20:47 sentry-docker00.cs.umd.edu systemd-udevd[3178983]: Could not generate persistent MAC address for veth71629af: No such file or directory
Sep 18 20:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3188322]: Could not generate persistent MAC address for veth9c627ab: No such file or directory
Sep 18 20:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3188323]: Could not generate persistent MAC address for vethc9ce2e3: No such file or directory
Sep 18 20:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3188326]: Could not generate persistent MAC address for vethfa909f4: No such file or directory
Sep 18 20:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3188327]: Could not generate persistent MAC address for vethd99577a: No such file or directory
Sep 18 20:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3188350]: Could not generate persistent MAC address for veth2ea2c9e: No such file or directory
Sep 18 20:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3188351]: Could not generate persistent MAC address for veth266e306: No such file or directory
Sep 18 20:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3188360]: Could not generate persistent MAC address for vethad7db0c: No such file or directory
Sep 18 20:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3188355]: Could not generate persistent MAC address for veth889baf8: No such file or directory
Sep 18 20:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3188373]: Could not generate persistent MAC address for veth31bfca8: No such file or directory
Sep 18 20:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3188350]: Could not generate persistent MAC address for veth4636f6b: No such file or directory
Sep 18 21:01:04 sentry-docker00.cs.umd.edu systemd-udevd[3197725]: Could not generate persistent MAC address for vethd628ca5: No such file or directory
Sep 18 21:01:04 sentry-docker00.cs.umd.edu systemd-udevd[3197726]: Could not generate persistent MAC address for veth155d7ee: No such file or directory
Sep 18 21:01:04 sentry-docker00.cs.umd.edu systemd-udevd[3197729]: Could not generate persistent MAC address for veth0a329f4: No such file or directory
Sep 18 21:01:04 sentry-docker00.cs.umd.edu systemd-udevd[3197730]: Could not generate persistent MAC address for veth4206ccc: No such file or directory
Sep 18 21:01:04 sentry-docker00.cs.umd.edu systemd-udevd[3197726]: Could not generate persistent MAC address for veth167faff: No such file or directory
Sep 18 21:01:04 sentry-docker00.cs.umd.edu systemd-udevd[3197733]: Could not generate persistent MAC address for veth3ab8046: No such file or directory
Sep 18 21:01:04 sentry-docker00.cs.umd.edu systemd-udevd[3197750]: Could not generate persistent MAC address for veth0a096be: No such file or directory
Sep 18 21:01:04 sentry-docker00.cs.umd.edu systemd-udevd[3197749]: Could not generate persistent MAC address for veth4960cf4: No such file or directory
... 2 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 18 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 18 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 18 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 18 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 18 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 18 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 18 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 4 total) ==
Sep 18 20:08:40 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f2 (1 distinct, 6 total) ==
Sep 18 20:09:23 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f3 (1 distinct, 4 total) ==
Sep 18 20:13:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f4 (1 distinct, 4 total) ==
Sep 18 20:37:57 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-fclone (9 distinct, 11 total) ==
Sep 18 20:21:58 submit26-b9-fclone setroubleshoot[80900]: 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 18 20:21:58 submit26-b9-fclone setroubleshoot[80900]: 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 18 20:21:58 submit26-b9-fclone setroubleshoot[80900]: 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 18 20:21:58 submit26-b9-fclone setroubleshoot[80900]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.sSEW0J/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 18 20:21:58 submit26-b9-fclone setroubleshoot[80900]: 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 18 20:21:58 submit26-b9-fclone setroubleshoot[80900]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.sSEW0J. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 18 20:21:58 submit26-b9-fclone setroubleshoot[80900]: 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 18 20:21:58 submit26-b9-fclone setroubleshoot[80900]: 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 18 20:21:58 submit26-b9-fclone setroubleshoot[80900]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4
== teaching-awards (1 distinct, 1 total) ==
Sep 18 20:31:44 teaching-awards krb5_child[1049825]: Preauthentication failed
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0532s
Status : exited 0
Output :
Syslog digest — 2026-09-18 20:05 EDT
Processed 2,832 lines, filtered 2,337 (82%). 495 unknown (174 distinct) from 20 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 18 19:49:58 b0b02.cs.umd.edu rustdesk[2631589]: cannot open display:
== bachata (10 distinct, 10 total) ==
Sep 18 19:44:47 bachata smbd[767549]: [2026/09/18 19:44:47.739278, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service)
Sep 18 19:44:47 bachata smbd[767549]: chdir_current_service: vfs_ChDir(/fs/junkfood/nelson) failed: Permission denied. Current token: uid=20608, gid=20608, 19 groups: 20608 31006 30043 319050000 30736 30871 25274 15248 15206 25025 15294 15228 319000009 30872 25057 30742 25200 25038 25195
Sep 18 19:44:47 bachata smbd[767549]: [2026/09/18 19:44:47.741187, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect)
Sep 18 19:44:47 bachata smbd[767549]: smbXsrv_tcon_disconnect: disconnect(0xb897ceff, 'nelson'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR
Sep 18 19:44:47 bachata smbd[767549]: [2026/09/18 19:44:47.741518, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all)
Sep 18 19:44:47 bachata smbd[767549]: smbXsrv_tcon_disconnect_all: count[3] errors[1] first[NT_STATUS_INTERNAL_ERROR]
Sep 18 19:44:47 bachata smbd[767549]: [2026/09/18 19:44:47.741617, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff)
Sep 18 19:44:47 bachata smbd[767549]: smbXsrv_session_logoff: smbXsrv_session_logoff(0xf5efd630): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR
Sep 18 19:44:47 bachata smbd[767549]: [2026/09/18 19:44:47.741708, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done)
Sep 18 19:44:47 bachata smbd[767549]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(4126135856) failed: NT_STATUS_INTERNAL_ERROR
== bale (5 distinct, 88 total) ==
Sep 18 19:05:33 bale setroubleshoot[639413]: failed to retrieve rpm info for /dev/nvme0 [x38]
Sep 18 19:05:34 bale setroubleshoot[639413]: 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 18 19:05:36 bale setroubleshoot[639413]: 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 18 19:05:39 bale setroubleshoot[639413]: 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 18 19:05:51 bale setroubleshoot[640029]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x14]
== biggulp.cs.umd.edu (1 distinct, 2 total) ==
Sep 18 19:10:56 biggulp.cs.umd.edu sshd-session[2375525]: error: send_error: write: Connection reset by peer [x2]
== cheezit.cs.umd.edu (1 distinct, 1 total) ==
Sep 18 19:10:56 cheezit.cs.umd.edu sshd-session[655460]: error: send_error: write: Connection reset by peer
== csfw00a (1 distinct, 113 total) ==
Sep 18 19:04:24 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x113]
== idm00 (1 distinct, 1 total) ==
Sep 18 19:53:57 idm00 named[4166701]: client @0x7f11a9407128 10.73.240.42#52127: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 18 19:37:58 idmp0 named[1598691]: client @0x7f2d480360f8 10.73.240.43#64024: update '73.10.in-addr.arpa/IN' denied
== inbound01.cs.umd.edu (2 distinct, 3 total) ==
Sep 18 19:12:05 inbound01.cs.umd.edu krb5_child[3801214]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 18 19:43:51 inbound01.cs.umd.edu krb5_child[3808815]: Preauthentication failed [x2]
== itmon02 (1 distinct, 5 total) ==
Sep 18 19:08:22 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x5]
== munin (2 distinct, 10 total) ==
Sep 18 19:08:28 munin sudo[4092148]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x5]
Sep 18 19:08:28 munin sudo[4092148]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x5]
== newhonors2 (1 distinct, 24 total) ==
Sep 18 19:13:03 newhonors2 dhcpcd[2826628]: dhcpcd is not running [x24]
== ntop00 (99 distinct, 143 total) ==
Sep 18 19:05:02 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 274) ***
Sep 18 19:05:18 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 274, QN: 6229/6229, ET: 17) ***
Sep 18 19:05:18 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 274, QN: 59/59, ET: 16) ***
Sep 18 19:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 275) ***
Sep 18 19:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 275, QN: 6236/6236, ET: 0) ***
Sep 18 19:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 275) ***
Sep 18 19:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 275, QN: 49/49, ET: 0) ***
Sep 18 19:08:02 ntop00 setroubleshoot[499528]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12]
Sep 18 19:08:02 ntop00 setroubleshoot[499528]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12]
Sep 18 19:08:03 ntop00 setroubleshoot[499528]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 18 19:08:03 ntop00 setroubleshoot[499528]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12]
Sep 18 19:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 276) ***
Sep 18 19:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 276) ***
Sep 18 19:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 276, QN: 44/44, ET: 0) ***
Sep 18 19:10:19 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 276, QN: 6226/6226, ET: 18) ***
Sep 18 19:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 277) ***
Sep 18 19:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 277, QN: 53/53, ET: 0) ***
Sep 18 19:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 277) ***
Sep 18 19:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 277, QN: 6010/6010, ET: 0) ***
Sep 18 19:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 278) ***
Sep 18 19:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 278) ***
Sep 18 19:15:18 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 278, QN: 6068/6068, ET: 17) ***
Sep 18 19:15:18 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 278, QN: 51/51, ET: 17) ***
Sep 18 19:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 279) ***
Sep 18 19:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 279) ***
Sep 18 19:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 279, QN: 53/53, ET: 0) ***
Sep 18 19:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 279, QN: 6391/6391, ET: 0) ***
Sep 18 19:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 280) ***
Sep 18 19:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 280) ***
Sep 18 19:20:19 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 280, QN: 6451/6451, ET: 18) ***
... 69 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 18 19:09:09 outbound00.cs.umd.edu python3[1453634]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 18 19:13:06 outbound01.cs.umd.edu python3[3712184]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 18 19:20:22 sentry-docker00.cs.umd.edu systemd-udevd[3150212]: link_config: could not get ethtool features for veth47fd23f
Sep 18 19:20:22 sentry-docker00.cs.umd.edu systemd-udevd[3150212]: Could not set offload features of veth47fd23f: No such device
Sep 18 19:20:22 sentry-docker00.cs.umd.edu systemd-udevd[3150237]: Could not generate persistent MAC address for veth2303175: No such file or directory
Sep 18 19:20:22 sentry-docker00.cs.umd.edu systemd-udevd[3150236]: Could not generate persistent MAC address for veth4ece1f5: No such file or directory
Sep 18 19:20:22 sentry-docker00.cs.umd.edu systemd-udevd[3150263]: Could not generate persistent MAC address for veth6d313c8: No such file or directory
Sep 18 19:20:22 sentry-docker00.cs.umd.edu systemd-udevd[3150262]: Could not generate persistent MAC address for vethd54621a: No such file or directory
Sep 18 19:20:22 sentry-docker00.cs.umd.edu systemd-udevd[3150268]: Could not generate persistent MAC address for veth6abe661: No such file or directory
Sep 18 19:20:22 sentry-docker00.cs.umd.edu systemd-udevd[3150281]: Could not generate persistent MAC address for veth876e1fb: No such file or directory
Sep 18 19:20:22 sentry-docker00.cs.umd.edu systemd-udevd[3150268]: Could not generate persistent MAC address for veth0f40728: No such file or directory
Sep 18 19:20:22 sentry-docker00.cs.umd.edu systemd-udevd[3150278]: Could not generate persistent MAC address for veth3247af4: No such file or directory
Sep 18 19:20:22 sentry-docker00.cs.umd.edu systemd-udevd[3150332]: Could not generate persistent MAC address for veth56f10bd: No such file or directory
Sep 18 19:20:22 sentry-docker00.cs.umd.edu systemd-udevd[3150330]: Could not generate persistent MAC address for vethc5c50d8: No such file or directory
Sep 18 19:40:30 sentry-docker00.cs.umd.edu systemd-udevd[3159868]: link_config: could not get ethtool features for veth4ece1f5
Sep 18 19:40:30 sentry-docker00.cs.umd.edu systemd-udevd[3159868]: Could not set offload features of veth4ece1f5: No such device
Sep 18 19:40:31 sentry-docker00.cs.umd.edu systemd-udevd[3159962]: link_config: could not set ethtool features for vethd54621a
Sep 18 19:40:31 sentry-docker00.cs.umd.edu systemd-udevd[3159962]: Could not set offload features of vethd54621a: Operation not permitted
Sep 18 19:40:31 sentry-docker00.cs.umd.edu systemd-udevd[3159986]: Could not generate persistent MAC address for vethbca5b49: No such file or directory
Sep 18 19:40:31 sentry-docker00.cs.umd.edu systemd-udevd[3159987]: Could not generate persistent MAC address for vethdac20c7: No such file or directory
Sep 18 19:40:31 sentry-docker00.cs.umd.edu systemd-udevd[3160012]: Could not generate persistent MAC address for veth43d694f: No such file or directory
Sep 18 19:40:31 sentry-docker00.cs.umd.edu systemd-udevd[3160013]: Could not generate persistent MAC address for veth706cb4c: No such file or directory
Sep 18 19:40:31 sentry-docker00.cs.umd.edu systemd-udevd[3160016]: Could not generate persistent MAC address for veth469101f: No such file or directory
Sep 18 19:40:31 sentry-docker00.cs.umd.edu systemd-udevd[3160036]: Could not generate persistent MAC address for veth3397f44: No such file or directory
Sep 18 19:40:31 sentry-docker00.cs.umd.edu systemd-udevd[3160040]: Could not generate persistent MAC address for veth0c5a483: No such file or directory
Sep 18 19:40:31 sentry-docker00.cs.umd.edu systemd-udevd[3160041]: Could not generate persistent MAC address for veth3cf6404: No such file or directory
Sep 18 19:40:31 sentry-docker00.cs.umd.edu systemd-udevd[3160102]: Could not generate persistent MAC address for veth28d1955: No such file or directory
Sep 18 19:40:31 sentry-docker00.cs.umd.edu systemd-udevd[3160104]: Could not generate persistent MAC address for vethda1c11f: No such file or directory
Sep 18 20:00:39 sentry-docker00.cs.umd.edu systemd-udevd[3169454]: Could not generate persistent MAC address for vethc1c9cd4: No such file or directory
Sep 18 20:00:39 sentry-docker00.cs.umd.edu systemd-udevd[3169453]: Could not generate persistent MAC address for vethf03001e: No such file or directory
Sep 18 20:00:39 sentry-docker00.cs.umd.edu systemd-udevd[3169457]: Could not generate persistent MAC address for vethcc745aa: No such file or directory
Sep 18 20:00:39 sentry-docker00.cs.umd.edu systemd-udevd[3169464]: Could not generate persistent MAC address for vethb2a46e1: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 18 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 18 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 18 19:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 18 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 18 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 18 19:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 18 19:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 1 total) ==
Sep 18 19:13:56 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f2 (1 distinct, 2 total) ==
Sep 18 19:18:32 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f3 (1 distinct, 4 total) ==
Sep 18 19:08:53 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0540s
Status : exited 0
Output :
Syslog digest — 2026-09-18 19:05 EDT
Processed 2,674 lines, filtered 2,102 (78%). 572 unknown (200 distinct) from 21 host(s).
== b0b02.cs.umd.edu (4 distinct, 4 total) ==
Sep 18 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-18T22:10:59.426169188Z" level=info msg="PurgeUploads starting: olderThan=2026-09-11 22:10:59.426093279 +0000 UTC m=+3976620.186021594, actuallyDelete=true"
Sep 18 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-18T22:10:59.426681673Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1"
Sep 18 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-18T22:10:59.426714202Z" 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 18 18:49:54 b0b02.cs.umd.edu rustdesk[2616408]: cannot open display:
== bachata (10 distinct, 10 total) ==
Sep 18 18:26:09 bachata smbd[769012]: [2026/09/18 18:26:09.145502, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service)
Sep 18 18:26:09 bachata smbd[769012]: chdir_current_service: vfs_ChDir(/fs/junkfood/mount) failed: Permission denied. Current token: uid=11255, gid=11255, 12 groups: 11255 319000009 25038 15294 15229 755 25030 25025 30880 25029 770 15026
Sep 18 18:26:09 bachata smbd[769012]: [2026/09/18 18:26:09.147668, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect)
Sep 18 18:26:09 bachata smbd[769012]: smbXsrv_tcon_disconnect: disconnect(0x8367d2d0, 'mount'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR
Sep 18 18:26:09 bachata smbd[769012]: [2026/09/18 18:26:09.148032, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all)
Sep 18 18:26:09 bachata smbd[769012]: smbXsrv_tcon_disconnect_all: count[2] errors[1] first[NT_STATUS_INTERNAL_ERROR]
Sep 18 18:26:09 bachata smbd[769012]: [2026/09/18 18:26:09.148246, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff)
Sep 18 18:26:09 bachata smbd[769012]: smbXsrv_session_logoff: smbXsrv_session_logoff(0x2d903526): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR
Sep 18 18:26:09 bachata smbd[769012]: [2026/09/18 18:26:09.148422, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done)
Sep 18 18:26:09 bachata smbd[769012]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(764425510) failed: NT_STATUS_INTERNAL_ERROR
== bale (5 distinct, 87 total) ==
Sep 18 18:05:43 bale setroubleshoot[626708]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 18 18:05:44 bale setroubleshoot[626708]: 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 18 18:05:46 bale setroubleshoot[626708]: 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 18 18:05:49 bale setroubleshoot[626708]: 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 18 18:06:01 bale setroubleshoot[627324]: 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, 168 total) ==
Sep 18 18:03:47 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x168]
== idm00 (1 distinct, 1 total) ==
Sep 18 18:53:57 idm00 named[4166701]: client @0x7f11a8045438 10.73.240.42#54062: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 18 18:37:58 idmp0 named[1598691]: client @0x7f2d3c076558 10.73.240.43#51902: update '73.10.in-addr.arpa/IN' denied
== inbound01.cs.umd.edu (1 distinct, 1 total) ==
Sep 18 18:51:39 inbound01.cs.umd.edu krb5_child[3795968]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== irb2156 (1 distinct, 1 total) ==
Sep 18 18:08:39 irb2156 systemd-tmpfiles[432650]: Opening file "/tmp/org.chromium.Chromium.hbBl2V/SingletonSocket" failed, proceeding without lock: No such device or address
== itmon02 (1 distinct, 5 total) ==
Sep 18 18:23:04 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x5]
== munin (2 distinct, 4 total) ==
Sep 18 18:08:28 munin sudo[4070754]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 18 18:08:28 munin sudo[4070754]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 18 18:13:02 newhonors2 dhcpcd[2824784]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 18 18:05:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 250) ***
Sep 18 18:05:16 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 250, QN: 5920/5920, ET: 15) ***
Sep 18 18:05:16 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 250, QN: 46/46, ET: 15) ***
Sep 18 18:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 251) ***
Sep 18 18:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 251, QN: 6297/6297, ET: 0) ***
Sep 18 18:08:02 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 251) ***
Sep 18 18:08:02 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 251, QN: 47/47, ET: 0) ***
Sep 18 18:08:02 ntop00 setroubleshoot[491649]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12]
Sep 18 18:08:02 ntop00 setroubleshoot[491649]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12]
Sep 18 18:08:03 ntop00 setroubleshoot[491649]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 18 18:08:03 ntop00 setroubleshoot[491649]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12]
Sep 18 18:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 252) ***
Sep 18 18:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 252) ***
Sep 18 18:10:19 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 252, QN: 6386/6386, ET: 18) ***
Sep 18 18:10:19 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 252, QN: 53/53, ET: 18) ***
Sep 18 18:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 253) ***
Sep 18 18:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 253, QN: 6161/6161, ET: 0) ***
Sep 18 18:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 253) ***
Sep 18 18:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 253, QN: 58/58, ET: 0) ***
Sep 18 18:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 254) ***
Sep 18 18:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 254) ***
Sep 18 18:15:18 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 254, QN: 6317/6317, ET: 17) ***
Sep 18 18:15:18 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 254, QN: 55/55, ET: 17) ***
Sep 18 18:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 255) ***
Sep 18 18:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 255, QN: 59/59, ET: 0) ***
Sep 18 18:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 255) ***
Sep 18 18:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 255, QN: 6101/6101, ET: 0) ***
Sep 18 18:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 256) ***
Sep 18 18:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 256) ***
Sep 18 18:20:16 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 256, QN: 6053/6053, ET: 15) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (3 distinct, 8 total) ==
Sep 18 18:09:09 outbound00.cs.umd.edu python3[1439496]: ldapdb [x6]
Sep 18 18:15:17 outbound00.cs.umd.edu krb5_child[1440607]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 18 18:24:41 outbound00.cs.umd.edu krb5_child[1442685]: Preauthentication failed
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 18 18:13:06 outbound01.cs.umd.edu python3[3698236]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 18 18:19:57 sentry-docker00.cs.umd.edu systemd-udevd[3121769]: link_config: could not get ethtool features for vetha102897
Sep 18 18:19:57 sentry-docker00.cs.umd.edu systemd-udevd[3121769]: Could not set offload features of vetha102897: No such device
Sep 18 18:19:57 sentry-docker00.cs.umd.edu systemd-udevd[3121886]: Could not generate persistent MAC address for veth783807f: No such file or directory
Sep 18 18:19:57 sentry-docker00.cs.umd.edu systemd-udevd[3121887]: Could not generate persistent MAC address for veth31c9d9e: No such file or directory
Sep 18 18:19:57 sentry-docker00.cs.umd.edu systemd-udevd[3121890]: Could not generate persistent MAC address for veth976e625: No such file or directory
Sep 18 18:19:57 sentry-docker00.cs.umd.edu systemd-udevd[3121902]: Could not generate persistent MAC address for veth8ccff81: No such file or directory
Sep 18 18:19:57 sentry-docker00.cs.umd.edu systemd-udevd[3121901]: Could not generate persistent MAC address for vetheb96037: No such file or directory
Sep 18 18:19:57 sentry-docker00.cs.umd.edu systemd-udevd[3121907]: Could not generate persistent MAC address for vethf36d002: No such file or directory
Sep 18 18:19:57 sentry-docker00.cs.umd.edu systemd-udevd[3121962]: Could not generate persistent MAC address for veth4d29c76: No such file or directory
Sep 18 18:19:57 sentry-docker00.cs.umd.edu systemd-udevd[3121964]: Could not generate persistent MAC address for veth938ace4: No such file or directory
Sep 18 18:19:57 sentry-docker00.cs.umd.edu systemd-udevd[3121987]: Could not generate persistent MAC address for veth1f69293: No such file or directory
Sep 18 18:19:57 sentry-docker00.cs.umd.edu systemd-udevd[3121978]: Could not generate persistent MAC address for veth34a02fc: No such file or directory
Sep 18 18:40:06 sentry-docker00.cs.umd.edu systemd-udevd[3131323]: link_config: could not get ethtool features for veth4d29c76
Sep 18 18:40:06 sentry-docker00.cs.umd.edu systemd-udevd[3131323]: Could not set offload features of veth4d29c76: No such device
Sep 18 18:40:06 sentry-docker00.cs.umd.edu systemd-udevd[3131360]: Could not generate persistent MAC address for veth32ab543: No such file or directory
Sep 18 18:40:06 sentry-docker00.cs.umd.edu systemd-udevd[3131361]: Could not generate persistent MAC address for vethab52d55: No such file or directory
Sep 18 18:40:06 sentry-docker00.cs.umd.edu systemd-udevd[3131364]: Could not generate persistent MAC address for veth9904585: No such file or directory
Sep 18 18:40:06 sentry-docker00.cs.umd.edu systemd-udevd[3131386]: Could not generate persistent MAC address for veth7881259: No such file or directory
Sep 18 18:40:06 sentry-docker00.cs.umd.edu systemd-udevd[3131369]: Could not generate persistent MAC address for vethde7cb44: No such file or directory
Sep 18 18:40:06 sentry-docker00.cs.umd.edu systemd-udevd[3131375]: Could not generate persistent MAC address for vethb7f266e: No such file or directory
Sep 18 18:40:06 sentry-docker00.cs.umd.edu systemd-udevd[3131361]: Could not generate persistent MAC address for veth2936ec1: No such file or directory
Sep 18 18:40:06 sentry-docker00.cs.umd.edu systemd-udevd[3131374]: Could not generate persistent MAC address for veth95cb973: No such file or directory
Sep 18 18:40:06 sentry-docker00.cs.umd.edu systemd-udevd[3131481]: Could not generate persistent MAC address for veth628999d: No such file or directory
Sep 18 18:40:06 sentry-docker00.cs.umd.edu systemd-udevd[3131485]: Could not generate persistent MAC address for vethffa9475: No such file or directory
Sep 18 19:00:14 sentry-docker00.cs.umd.edu systemd-udevd[3140780]: link_config: could not get ethtool features for veth32ab543
Sep 18 19:00:14 sentry-docker00.cs.umd.edu systemd-udevd[3140780]: Could not set offload features of veth32ab543: No such device
Sep 18 19:00:14 sentry-docker00.cs.umd.edu systemd-udevd[3140874]: link_config: could not get ethtool features for veth2936ec1
Sep 18 19:00:14 sentry-docker00.cs.umd.edu systemd-udevd[3140874]: Could not set offload features of veth2936ec1: No such device
Sep 18 19:00:14 sentry-docker00.cs.umd.edu systemd-udevd[3140905]: Could not generate persistent MAC address for veth112e930: No such file or directory
Sep 18 19:00:14 sentry-docker00.cs.umd.edu systemd-udevd[3140906]: Could not generate persistent MAC address for veth4d0411c: No such file or directory
... 8 more distinct messages not shown
== soul (2 distinct, 2 total) ==
Sep 18 18:08:54 soul krb5_child[3353402]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 18 18:58:07 soul krb5_child[3361277]: Preauthentication failed
== strawberry (7 distinct, 38 total) ==
Sep 18 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 18 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 18 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 18 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 18 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 18 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 18 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (10 distinct, 14 total) ==
Sep 18 18:25:53 submit26-b9-f1 setroubleshoot[2372733]: 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 [x2]
Sep 18 18:25:53 submit26-b9-f1 setroubleshoot[2372733]: 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 [x2]
Sep 18 18:25:53 submit26-b9-f1 setroubleshoot[2372733]: 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 18 18:25:53 submit26-b9-f1 setroubleshoot[2372733]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.IlVxm5/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 18 18:25:53 submit26-b9-f1 setroubleshoot[2372733]: 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 18 18:25:53 submit26-b9-f1 setroubleshoot[2372733]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.IlVxm5. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 18 18:25:53 submit26-b9-f1 setroubleshoot[2372733]: 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 [x2]
Sep 18 18:25:53 submit26-b9-f1 setroubleshoot[2372733]: 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 18 18:25:53 submit26-b9-f1 setroubleshoot[2372733]: 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 [x2]
Sep 18 18:25:53 submit26-b9-f1 setroubleshoot[2372733]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.2GY1CO. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
== submit26-b9-f2 (9 distinct, 12 total) ==
Sep 18 18:06:48 submit26-b9-f2 setroubleshoot[1495716]: 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 18 18:06:48 submit26-b9-f2 setroubleshoot[1495716]: 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 18 18:06:48 submit26-b9-f2 setroubleshoot[1495716]: 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 18 18:06:48 submit26-b9-f2 setroubleshoot[1495716]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.03lRtp/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2]
Sep 18 18:06:48 submit26-b9-f2 setroubleshoot[1495716]: 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 18 18:06:48 submit26-b9-f2 setroubleshoot[1495716]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.03lRtp. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 18 18:06:48 submit26-b9-f2 setroubleshoot[1495716]: 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 18 18:06:49 submit26-b9-f2 setroubleshoot[1495716]: 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 18 18:06:49 submit26-b9-f2 setroubleshoot[1495716]: 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 18 18:48:14 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 18 18:38:06 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.0515s
Status : exited 0
Output :
Syslog digest — 2026-09-18 18:05 EDT
Processed 2,453 lines, filtered 1,940 (79%). 513 unknown (188 distinct) from 20 host(s).
== amoeba (6 distinct, 6 total) ==
Sep 18 17:16:00 amoeba firefox[1459102]: Couldn't map window 0x7f3d508530a0 as subsurface because its parent is not mapped.
Sep 18 17:16:00 amoeba firefox[1459102]: Couldn't map window 0x7f3d50856160 as subsurface because its parent is not mapped.
Sep 18 17:16:00 amoeba firefox[1459102]: Couldn't map window 0x7f3d50853240 as subsurface because its parent is not mapped.
Sep 18 17:16:00 amoeba firefox[1459102]: Couldn't map window 0x7f3d508533e0 as subsurface because its parent is not mapped.
Sep 18 17:16:00 amoeba firefox[1459102]: Couldn't map window 0x7f3d5deabae0 as subsurface because its parent is not mapped.
Sep 18 17:16:00 amoeba firefox[1459102]: Couldn't map window 0x7f3d3a0644a0 as subsurface because its parent is not mapped.
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 18 17:49:53 b0b02.cs.umd.edu rustdesk[2601222]: cannot open display:
== bale (5 distinct, 87 total) ==
Sep 18 17:05:20 bale setroubleshoot[613781]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 18 17:05:21 bale setroubleshoot[613781]: 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 18 17:05:23 bale setroubleshoot[613781]: 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 18 17:05:26 bale setroubleshoot[613781]: 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 18 17:05:38 bale setroubleshoot[614410]: 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, 123 total) ==
Sep 18 17:03:51 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x123]
== frozone (1 distinct, 1 total) ==
Sep 18 17:35:37 frozone systemd-tmpfiles[2008052]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted
== idm00 (1 distinct, 1 total) ==
Sep 18 17:53:57 idm00 named[4166701]: client @0x7f11a0053278 10.73.240.42#64481: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 18 17:37:58 idmp0 named[1598691]: client @0x7f2d3802f8f8 10.73.240.43#49911: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 1 total) ==
Sep 18 17:52:23 inbound00.cs.umd.edu krb5_child[1561555]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 7 total) ==
Sep 18 17:23:33 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x7]
== mcstic (2 distinct, 6 total) ==
Sep 18 17:05:10 mcstic krb5_child[776358]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 18 17:15:43 mcstic krb5_child[776729]: Preauthentication failed [x4]
== munin (2 distinct, 2 total) ==
Sep 18 18:03:14 munin sudo[4069239]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory
Sep 18 18:03:14 munin sudo[4069239]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order.
== newhonors2 (1 distinct, 24 total) ==
Sep 18 17:13:03 newhonors2 dhcpcd[2822943]: dhcpcd is not running [x24]
== ntop00 (99 distinct, 143 total) ==
Sep 18 17:05:21 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 226, QN: 7853/7853, ET: 20) ***
Sep 18 17:05:21 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 226, QN: 59/59, ET: 20) ***
Sep 18 17:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 227) ***
Sep 18 17:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 227, QN: 51/51, ET: 0) ***
Sep 18 17:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 227) ***
Sep 18 17:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 227, QN: 8496/8496, ET: 0) ***
Sep 18 17:08:02 ntop00 setroubleshoot[483612]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12]
Sep 18 17:08:02 ntop00 setroubleshoot[483612]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12]
Sep 18 17:08:03 ntop00 setroubleshoot[483612]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 18 17:08:03 ntop00 setroubleshoot[483612]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12]
Sep 18 17:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 228) ***
Sep 18 17:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 228) ***
Sep 18 17:10:26 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 228, QN: 8649/8649, ET: 25) ***
Sep 18 17:10:26 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 228, QN: 47/47, ET: 25) ***
Sep 18 17:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 229) ***
Sep 18 17:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 229, QN: 8612/8612, ET: 0) ***
Sep 18 17:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 229) ***
Sep 18 17:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 229, QN: 54/54, ET: 0) ***
Sep 18 17:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 230) ***
Sep 18 17:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 230) ***
Sep 18 17:15:24 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 230, QN: 8593/8593, ET: 23) ***
Sep 18 17:15:24 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 230, QN: 60/60, ET: 23) ***
Sep 18 17:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 231) ***
Sep 18 17:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 231, QN: 8251/8251, ET: 0) ***
Sep 18 17:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 231) ***
Sep 18 17:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 231, QN: 52/52, ET: 0) ***
Sep 18 17:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 232) ***
Sep 18 17:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 232) ***
Sep 18 17:20:23 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 232, QN: 8459/8459, ET: 22) ***
Sep 18 17:20:23 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 232, QN: 60/60, ET: 22) ***
... 69 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 18 17:09:09 outbound00.cs.umd.edu python3[1425562]: ldapdb [x6]
== outbound01.cs.umd.edu (3 distinct, 8 total) ==
Sep 18 17:13:06 outbound01.cs.umd.edu python3[3684057]: ldapdb [x6]
Sep 18 17:56:36 outbound01.cs.umd.edu krb5_child[3694777]: Client 'test1(a)UMD.EDU' not found in Kerberos database
Sep 18 17:59:20 outbound01.cs.umd.edu krb5_child[3695310]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 18 17:19:32 sentry-docker00.cs.umd.edu systemd-udevd[3093378]: Could not generate persistent MAC address for vetha9ed169: No such file or directory
Sep 18 17:19:32 sentry-docker00.cs.umd.edu systemd-udevd[3093379]: Could not generate persistent MAC address for veth049e346: No such file or directory
Sep 18 17:19:32 sentry-docker00.cs.umd.edu systemd-udevd[3093399]: Could not generate persistent MAC address for vethfc946cf: No such file or directory
Sep 18 17:19:32 sentry-docker00.cs.umd.edu systemd-udevd[3093388]: Could not generate persistent MAC address for veth86bc80d: No such file or directory
Sep 18 17:19:32 sentry-docker00.cs.umd.edu systemd-udevd[3093395]: Could not generate persistent MAC address for veth76281ee: No such file or directory
Sep 18 17:19:32 sentry-docker00.cs.umd.edu systemd-udevd[3093387]: Could not generate persistent MAC address for veth4759d77: No such file or directory
Sep 18 17:19:32 sentry-docker00.cs.umd.edu systemd-udevd[3093399]: Could not generate persistent MAC address for veth27cb915: No such file or directory
Sep 18 17:19:32 sentry-docker00.cs.umd.edu systemd-udevd[3093388]: Could not generate persistent MAC address for veth18082d0: No such file or directory
Sep 18 17:19:32 sentry-docker00.cs.umd.edu systemd-udevd[3093475]: Could not generate persistent MAC address for veth225e4bd: No such file or directory
Sep 18 17:19:32 sentry-docker00.cs.umd.edu systemd-udevd[3093477]: Could not generate persistent MAC address for veth2267896: No such file or directory
Sep 18 17:39:40 sentry-docker00.cs.umd.edu systemd-udevd[3102870]: link_config: could not get ethtool features for vethfc946cf
Sep 18 17:39:40 sentry-docker00.cs.umd.edu systemd-udevd[3102870]: Could not set offload features of vethfc946cf: No such device
Sep 18 17:39:41 sentry-docker00.cs.umd.edu systemd-udevd[3102989]: Could not generate persistent MAC address for veth5347b5f: No such file or directory
Sep 18 17:39:41 sentry-docker00.cs.umd.edu systemd-udevd[3102990]: Could not generate persistent MAC address for veth07d6f3a: No such file or directory
Sep 18 17:39:41 sentry-docker00.cs.umd.edu systemd-udevd[3103008]: Could not generate persistent MAC address for veth63af73d: No such file or directory
Sep 18 17:39:41 sentry-docker00.cs.umd.edu systemd-udevd[3103013]: Could not generate persistent MAC address for veth69153c4: No such file or directory
Sep 18 17:39:41 sentry-docker00.cs.umd.edu systemd-udevd[3103006]: Could not generate persistent MAC address for vethedf3e9f: No such file or directory
Sep 18 17:39:41 sentry-docker00.cs.umd.edu systemd-udevd[3103000]: Could not generate persistent MAC address for veth8060fcd: No such file or directory
Sep 18 17:39:41 sentry-docker00.cs.umd.edu systemd-udevd[3102997]: Could not generate persistent MAC address for veth6991576: No such file or directory
Sep 18 17:39:41 sentry-docker00.cs.umd.edu systemd-udevd[3102993]: Could not generate persistent MAC address for veth94e1d32: No such file or directory
Sep 18 17:39:41 sentry-docker00.cs.umd.edu systemd-udevd[3103006]: Could not generate persistent MAC address for veth8f243bc: No such file or directory
Sep 18 17:39:41 sentry-docker00.cs.umd.edu systemd-udevd[3103000]: Could not generate persistent MAC address for vetheaa6cf0: No such file or directory
Sep 18 17:59:49 sentry-docker00.cs.umd.edu systemd-udevd[3112396]: link_config: could not get ethtool features for veth5347b5f
Sep 18 17:59:49 sentry-docker00.cs.umd.edu systemd-udevd[3112396]: Could not set offload features of veth5347b5f: No such device
Sep 18 17:59:49 sentry-docker00.cs.umd.edu systemd-udevd[3112446]: Could not generate persistent MAC address for vethc3b9f3e: No such file or directory
Sep 18 17:59:49 sentry-docker00.cs.umd.edu systemd-udevd[3112447]: Could not generate persistent MAC address for vethb07bbb5: No such file or directory
Sep 18 17:59:49 sentry-docker00.cs.umd.edu systemd-udevd[3112472]: Could not generate persistent MAC address for vetha102897: No such file or directory
Sep 18 17:59:49 sentry-docker00.cs.umd.edu systemd-udevd[3112473]: Could not generate persistent MAC address for veth46fb293: No such file or directory
Sep 18 17:59:49 sentry-docker00.cs.umd.edu systemd-udevd[3112476]: Could not generate persistent MAC address for vethdac05d6: No such file or directory
Sep 18 17:59:49 sentry-docker00.cs.umd.edu systemd-udevd[3112477]: Could not generate persistent MAC address for veth1870af8: No such file or directory
... 4 more distinct messages not shown
== soul (1 distinct, 1 total) ==
Sep 18 17:45:15 soul krb5_child[3349621]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== strawberry (7 distinct, 38 total) ==
Sep 18 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 18 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 18 17:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 18 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 18 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 18 17:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 18 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (10 distinct, 10 total) ==
Sep 18 17:06:42 submit26-b9-f3 setroubleshoot[1831502]: 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 18 17:06:42 submit26-b9-f3 setroubleshoot[1831502]: 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 18 17:06:42 submit26-b9-f3 setroubleshoot[1831502]: 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 18 17:06:42 submit26-b9-f3 setroubleshoot[1831502]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.p8GXzZ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 18 17:06:42 submit26-b9-f3 setroubleshoot[1831502]: 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 18 17:06:42 submit26-b9-f3 setroubleshoot[1831502]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.p8GXzZ. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 18 17:06:42 submit26-b9-f3 setroubleshoot[1831502]: 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 18 17:06:42 submit26-b9-f3 setroubleshoot[1831502]: 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 18 17:06:42 submit26-b9-f3 setroubleshoot[1831502]: 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 18 17:25:05 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f4 (10 distinct, 13 total) ==
Sep 18 17:24:46 submit26-b9-f4 setroubleshoot[1333612]: 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 18 17:24:46 submit26-b9-f4 setroubleshoot[1333612]: 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 18 17:24:46 submit26-b9-f4 setroubleshoot[1333612]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d [x2]
Sep 18 17:24:46 submit26-b9-f4 setroubleshoot[1333612]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.RqTSWl/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 18 17:24:46 submit26-b9-f4 setroubleshoot[1333612]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e [x2]
Sep 18 17:24:46 submit26-b9-f4 setroubleshoot[1333612]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.RqTSWl. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 18 17:24:46 submit26-b9-f4 setroubleshoot[1333612]: 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 18 17:24:46 submit26-b9-f4 setroubleshoot[1333612]: 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 [x2]
Sep 18 17:24:46 submit26-b9-f4 setroubleshoot[1333612]: 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 18 17:24:46 submit26-b9-f4 setroubleshoot[1333612]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ZdjuTM/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
1
0