Command: /usr/local/sbin/syslog-digest.py
Time : 0.0485s
Status : exited 0
Output :
Syslog digest — 2026-09-21 06:05 EDT
Processed 1,825 lines, filtered 1,329 (72%). 496 unknown (175 distinct) from 16 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 05:53:27 b0b02.cs.umd.edu rustdesk[3520111]: cannot open display:
== bale (5 distinct, 84 total) ==
Sep 21 05:05:10 bale setroubleshoot[1384075]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 21 05:05:10 bale setroubleshoot[1384075]: 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 21 05:05:13 bale setroubleshoot[1384075]: 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 21 05:05:16 bale setroubleshoot[1384075]: 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 21 05:05:28 bale setroubleshoot[1384691]: 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, 118 total) ==
Sep 21 05:04:02 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x118]
== grades01.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 05:48:27 grades01.cs.umd.edu puppet-agent[5295]: The directory '/srv/grades' contains 2471 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees
== idm00 (1 distinct, 1 total) ==
Sep 21 05:54:01 idm00 named[4166701]: client @0x7f11a429b368 10.73.240.42#64009: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 21 05:37:56 idmp0 named[1598691]: client @0x7f2d280332b8 10.73.240.43#60614: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 4 total) ==
Sep 21 05:08:01 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x4]
== munin (2 distinct, 12 total) ==
Sep 21 05:08:12 munin sudo[1160012]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6]
Sep 21 05:08:12 munin sudo[1160012]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6]
== newhonors2 (1 distinct, 24 total) ==
Sep 21 05:13:03 newhonors2 dhcpcd[2936136]: dhcpcd is not running [x24]
== ntop00 (99 distinct, 143 total) ==
Sep 21 05:05:27 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 5322/5322, ET: 26) ***
Sep 21 05:05:27 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 48/48, ET: 26) ***
Sep 21 05:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 515) ***
Sep 21 05:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 40/40, ET: 0) ***
Sep 21 05:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 515) ***
Sep 21 05:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 5462/5462, ET: 0) ***
Sep 21 05:08:02 ntop00 setroubleshoot[960715]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x12]
Sep 21 05:08:02 ntop00 setroubleshoot[960715]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x12]
Sep 21 05:08:02 ntop00 setroubleshoot[960715]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 21 05:08:02 ntop00 setroubleshoot[960715]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x12]
Sep 21 05:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) ***
Sep 21 05:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) ***
Sep 21 05:10:28 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 5614/5614, ET: 27) ***
Sep 21 05:10:28 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 37/37, ET: 27) ***
Sep 21 05:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 517) ***
Sep 21 05:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 5661/5661, ET: 0) ***
Sep 21 05:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 517) ***
Sep 21 05:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 48/48, ET: 0) ***
Sep 21 05:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) ***
Sep 21 05:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) ***
Sep 21 05:15:27 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 5620/5620, ET: 26) ***
Sep 21 05:15:27 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 54/54, ET: 26) ***
Sep 21 05:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 519) ***
Sep 21 05:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 519) ***
Sep 21 05:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 48/48, ET: 0) ***
Sep 21 05:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 5358/5358, ET: 0) ***
Sep 21 05:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) ***
Sep 21 05:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) ***
Sep 21 05:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 46/46, ET: 0) ***
Sep 21 05:20:24 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 5029/5029, ET: 23) ***
... 69 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 05:09:09 outbound00.cs.umd.edu python3[2273430]: ldapdb [x6]
== outbound01.cs.umd.edu (2 distinct, 8 total) ==
Sep 21 05:08:33 outbound01.cs.umd.edu python3[338371]: ldapdb [x7]
Sep 21 05:09:41 outbound01.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway.
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599245]: link_config: could not get ethtool features for veth4273c1b
Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599245]: Could not set offload features of veth4273c1b: No such device
Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599282]: Could not generate persistent MAC address for veth54bac89: No such file or directory
Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599283]: Could not generate persistent MAC address for veth22c806b: No such file or directory
Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599286]: Could not generate persistent MAC address for veth9e271f8: No such file or directory
Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599287]: Could not generate persistent MAC address for veth78b58f7: No such file or directory
Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599310]: Could not generate persistent MAC address for veth193a7b3: No such file or directory
Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599311]: Could not generate persistent MAC address for veth45f5af6: No such file or directory
Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599329]: Could not generate persistent MAC address for veth0855e6f: No such file or directory
Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599331]: Could not generate persistent MAC address for veth0fd0f54: No such file or directory
Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599317]: Could not generate persistent MAC address for vethc8dae42: No such file or directory
Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599316]: Could not generate persistent MAC address for veth28b2b73: No such file or directory
Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608760]: Could not generate persistent MAC address for vethf9fecbe: No such file or directory
Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608759]: Could not generate persistent MAC address for vethadc78c3: No such file or directory
Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608785]: Could not generate persistent MAC address for veth2919437: No such file or directory
Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608786]: Could not generate persistent MAC address for veth5a41864: No such file or directory
Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608804]: Could not generate persistent MAC address for veth3aabfe0: No such file or directory
Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608793]: Could not generate persistent MAC address for veth635bd94: No such file or directory
Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608833]: Could not generate persistent MAC address for veth5351b51: No such file or directory
Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608839]: Could not generate persistent MAC address for veth6b25e7e: No such file or directory
Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608902]: Could not generate persistent MAC address for vethb83feca: No such file or directory
Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608890]: Could not generate persistent MAC address for veth9b47cfc: No such file or directory
Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618163]: link_config: could not get ethtool features for veth5351b51
Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618163]: Could not set offload features of veth5351b51: No such device
Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618236]: Could not generate persistent MAC address for veth8ec0c93: No such file or directory
Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618235]: Could not generate persistent MAC address for veth3d0d1bb: No such file or directory
Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618235]: Could not generate persistent MAC address for vethdcc6535: No such file or directory
Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618252]: Could not generate persistent MAC address for veth00b3a78: No such file or directory
Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618236]: Could not generate persistent MAC address for veth03447fd: No such file or directory
Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618255]: Could not generate persistent MAC address for vetha5ac0b0: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 21 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 21 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 21 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 21 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 21 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 21 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 21 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (9 distinct, 9 total) ==
Sep 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: 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 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: 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 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: 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 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.5PoudU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: 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 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.5PoudU. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: 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 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: 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 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68
== submit26-b9-f4 (9 distinct, 12 total) ==
Sep 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: 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 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: 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 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: 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 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.iHUiXb/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2]
Sep 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: 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 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.iHUiXb. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: 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 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: 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 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0503s
Status : exited 0
Output :
Syslog digest — 2026-09-21 05:05 EDT
Processed 1,945 lines, filtered 1,400 (71%). 545 unknown (181 distinct) from 21 host(s).
== abadi-computer (2 distinct, 2 total) ==
Sep 21 04:15:00 abadi-computer nologin[1632033]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 21 04:15:00 abadi-computer pipewire[1632031]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 04:53:23 b0b02.cs.umd.edu rustdesk[3504928]: cannot open display:
== bale (5 distinct, 84 total) ==
Sep 21 04:05:18 bale setroubleshoot[1370467]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 21 04:05:19 bale setroubleshoot[1370467]: 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 21 04:05:21 bale setroubleshoot[1370467]: 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 21 04:05:24 bale setroubleshoot[1370467]: 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 21 04:05:36 bale setroubleshoot[1371098]: 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]
== cmsc436-0101-redis (2 distinct, 2 total) ==
Sep 21 04:22:50 cmsc436-0101-redis krb5_child[3371138]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 21 04:22:52 cmsc436-0101-redis sshd-session[3371134]: error: PAM: Authentication failure for admin from 193.187.110.214
== csfw00a (1 distinct, 136 total) ==
Sep 21 04:04:13 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x136]
== forge00 (1 distinct, 1 total) ==
Sep 21 04:09:03 forge00 (httpd)[509737]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== idm00 (1 distinct, 1 total) ==
Sep 21 04:54:01 idm00 named[4166701]: client @0x7f11980abff8 10.73.240.42#63137: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 21 04:37:56 idmp0 named[1598691]: client @0x7f2d4c005288 10.73.240.43#61016: update '73.10.in-addr.arpa/IN' denied
== inbound01.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 04:23:57 inbound01.cs.umd.edu krb5_child[419556]: Preauthentication failed
== itmon02 (1 distinct, 4 total) ==
Sep 21 04:08:29 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x4]
== krispykreme.cs.umd.edu (3 distinct, 3 total) ==
Sep 21 04:38:30 krispykreme.cs.umd.edu sshd-session[577529]: pam_access(sshd:auth): access denied for user `admin' from `193.187.110.214'
Sep 21 04:38:30 krispykreme.cs.umd.edu krb5_child[577531]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 21 04:38:30 krispykreme.cs.umd.edu sshd-session[577527]: error: PAM: System error for admin from 193.187.110.214
== matrix (2 distinct, 3 total) ==
Sep 21 04:39:12 matrix krb5_child[3750050]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 21 04:39:14 matrix sshd[3750044]: error: PAM: Authentication failure for admin from 193.187.110.214
== munin (2 distinct, 44 total) ==
Sep 21 04:18:46 munin sudo[1140312]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x22]
Sep 21 04:18:46 munin sudo[1140312]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x22]
== newhonors2 (1 distinct, 24 total) ==
Sep 21 04:13:02 newhonors2 dhcpcd[2934274]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 140 total) ==
Sep 21 04:05:24 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 490, QN: 5329/5329, ET: 23) ***
Sep 21 04:05:24 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 490, QN: 45/45, ET: 23) ***
Sep 21 04:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 491) ***
Sep 21 04:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 491, QN: 63/63, ET: 0) ***
Sep 21 04:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 491) ***
Sep 21 04:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 491, QN: 5480/5480, ET: 0) ***
Sep 21 04:08:02 ntop00 setroubleshoot[952823]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x11]
Sep 21 04:08:02 ntop00 setroubleshoot[952823]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x11]
Sep 21 04:08:02 ntop00 setroubleshoot[952823]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11]
Sep 21 04:08:02 ntop00 setroubleshoot[952823]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x11]
Sep 21 04:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 492) ***
Sep 21 04:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 492) ***
Sep 21 04:10:26 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 492, QN: 5307/5307, ET: 25) ***
Sep 21 04:10:26 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 492, QN: 55/55, ET: 25) ***
Sep 21 04:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 493) ***
Sep 21 04:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 493, QN: 5230/5230, ET: 0) ***
Sep 21 04:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 493) ***
Sep 21 04:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 493, QN: 41/41, ET: 0) ***
Sep 21 04:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 494) ***
Sep 21 04:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 494) ***
Sep 21 04:15:32 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 494, QN: 5010/5010, ET: 31) ***
Sep 21 04:15:32 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 494, QN: 43/43, ET: 31) ***
Sep 21 04:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 495) ***
Sep 21 04:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 495, QN: 5681/5681, ET: 0) ***
Sep 21 04:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 495) ***
Sep 21 04:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 495, QN: 49/49, ET: 0) ***
Sep 21 04:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 496) ***
Sep 21 04:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 496) ***
Sep 21 04:20:26 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 496, QN: 6054/6054, ET: 25) ***
Sep 21 04:20:26 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 496, QN: 51/51, ET: 25) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 04:09:09 outbound00.cs.umd.edu python3[2259436]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 04:13:06 outbound01.cs.umd.edu python3[325108]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 21 04:23:57 sentry-docker00.cs.umd.edu systemd-udevd[570691]: link_config: could not get ethtool features for vethe717cbd
Sep 21 04:23:57 sentry-docker00.cs.umd.edu systemd-udevd[570691]: Could not set offload features of vethe717cbd: No such device
Sep 21 04:23:57 sentry-docker00.cs.umd.edu systemd-udevd[570770]: Could not generate persistent MAC address for veth429d9c3: No such file or directory
Sep 21 04:23:57 sentry-docker00.cs.umd.edu systemd-udevd[570771]: Could not generate persistent MAC address for veth9e05f81: No such file or directory
Sep 21 04:23:57 sentry-docker00.cs.umd.edu systemd-udevd[570774]: Could not generate persistent MAC address for vethf6d1196: No such file or directory
Sep 21 04:23:57 sentry-docker00.cs.umd.edu systemd-udevd[570775]: Could not generate persistent MAC address for vethe753e25: No such file or directory
Sep 21 04:23:57 sentry-docker00.cs.umd.edu systemd-udevd[570774]: Could not generate persistent MAC address for vethf0b0e4e: No such file or directory
Sep 21 04:23:57 sentry-docker00.cs.umd.edu systemd-udevd[570794]: Could not generate persistent MAC address for veth046c03a: No such file or directory
Sep 21 04:23:57 sentry-docker00.cs.umd.edu systemd-udevd[570776]: Could not generate persistent MAC address for vethf5fe06e: No such file or directory
Sep 21 04:23:57 sentry-docker00.cs.umd.edu systemd-udevd[570783]: Could not generate persistent MAC address for vethce8c8a6: No such file or directory
Sep 21 04:23:57 sentry-docker00.cs.umd.edu systemd-udevd[570774]: Could not generate persistent MAC address for veth3d67d98: No such file or directory
Sep 21 04:23:57 sentry-docker00.cs.umd.edu systemd-udevd[570794]: Could not generate persistent MAC address for vethec53244: No such file or directory
Sep 21 04:44:05 sentry-docker00.cs.umd.edu systemd-udevd[580138]: link_config: could not get ethtool features for veth429d9c3
Sep 21 04:44:05 sentry-docker00.cs.umd.edu systemd-udevd[580138]: Could not set offload features of veth429d9c3: No such device
Sep 21 04:44:05 sentry-docker00.cs.umd.edu systemd-udevd[580224]: Could not generate persistent MAC address for veth4002ce1: No such file or directory
Sep 21 04:44:05 sentry-docker00.cs.umd.edu systemd-udevd[580225]: Could not generate persistent MAC address for vethd2affa6: No such file or directory
Sep 21 04:44:05 sentry-docker00.cs.umd.edu systemd-udevd[580228]: Could not generate persistent MAC address for veth038a8ab: No such file or directory
Sep 21 04:44:05 sentry-docker00.cs.umd.edu systemd-udevd[580229]: Could not generate persistent MAC address for veth04e5632: No such file or directory
Sep 21 04:44:05 sentry-docker00.cs.umd.edu systemd-udevd[580231]: Could not generate persistent MAC address for veth4f5c729: No such file or directory
Sep 21 04:44:05 sentry-docker00.cs.umd.edu systemd-udevd[580239]: Could not generate persistent MAC address for veth868bf46: No such file or directory
Sep 21 04:44:05 sentry-docker00.cs.umd.edu systemd-udevd[580241]: Could not generate persistent MAC address for veth80bda43: No such file or directory
Sep 21 04:44:05 sentry-docker00.cs.umd.edu systemd-udevd[580239]: Could not generate persistent MAC address for veth6bea9b1: No such file or directory
Sep 21 04:44:05 sentry-docker00.cs.umd.edu systemd-udevd[580236]: Could not generate persistent MAC address for veth0f5b628: No such file or directory
Sep 21 04:44:05 sentry-docker00.cs.umd.edu systemd-udevd[580239]: Could not generate persistent MAC address for vethb4f5e7a: No such file or directory
Sep 21 05:04:13 sentry-docker00.cs.umd.edu systemd-udevd[589623]: link_config: could not get ethtool features for veth038a8ab
Sep 21 05:04:13 sentry-docker00.cs.umd.edu systemd-udevd[589623]: Could not set offload features of veth038a8ab: No such device
Sep 21 05:04:13 sentry-docker00.cs.umd.edu systemd-udevd[589644]: Could not generate persistent MAC address for vethaf33d39: No such file or directory
Sep 21 05:04:13 sentry-docker00.cs.umd.edu systemd-udevd[589645]: Could not generate persistent MAC address for veth4d55012: No such file or directory
Sep 21 05:04:13 sentry-docker00.cs.umd.edu systemd-udevd[589701]: Could not generate persistent MAC address for veth0aaac01: No such file or directory
Sep 21 05:04:13 sentry-docker00.cs.umd.edu systemd-udevd[589702]: Could not generate persistent MAC address for veth70dddbd: No such file or directory
... 6 more distinct messages not shown
== smokeping-slave (1 distinct, 1 total) ==
Sep 21 04:15:01 smokeping-slave nologin[2076430]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
== strawberry (9 distinct, 40 total) ==
Sep 21 04:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 21 04:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 21 04:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 21 04:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 21 04:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 21 04:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 21 04:15:04 strawberry nologin[3235231]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 21 04:15:04 strawberry pipewire[3235230]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files
Sep 21 04:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 21 04:21:57 submit26-b9-fclone setroubleshoot[217265]: 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 21 04:21:57 submit26-b9-fclone setroubleshoot[217265]: 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 21 04:21:57 submit26-b9-fclone setroubleshoot[217265]: 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 21 04:21:57 submit26-b9-fclone setroubleshoot[217265]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.mAFLVR/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 21 04:21:57 submit26-b9-fclone setroubleshoot[217265]: 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 21 04:21:57 submit26-b9-fclone setroubleshoot[217265]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.mAFLVR. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 21 04:21:57 submit26-b9-fclone setroubleshoot[217265]: 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 21 04:21:57 submit26-b9-fclone setroubleshoot[217265]: 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 21 04:21:57 submit26-b9-fclone setroubleshoot[217265]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0489s
Status : exited 0
Output :
Syslog digest — 2026-09-21 04:05 EDT
Processed 1,975 lines, filtered 1,458 (73%). 517 unknown (175 distinct) from 19 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 03:53:19 b0b02.cs.umd.edu rustdesk[3489453]: cannot open display:
== bale (5 distinct, 84 total) ==
Sep 21 03:06:04 bale setroubleshoot[1357738]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 21 03:06:04 bale setroubleshoot[1357738]: 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 21 03:06:07 bale setroubleshoot[1357738]: 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 21 03:06:10 bale setroubleshoot[1357738]: 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 21 03:06:22 bale setroubleshoot[1358352]: 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, 138 total) ==
Sep 21 03:05:03 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x132]
Sep 21 03:31:32 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x6]
== idm00 (1 distinct, 1 total) ==
Sep 21 03:54:01 idm00 named[4166701]: client @0x7f11980696f8 10.73.240.42#60455: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 21 03:37:56 idmp0 named[1598691]: client @0x7f2d08898fa8 10.73.240.43#59529: update '73.10.in-addr.arpa/IN' denied
== itmon02 (2 distinct, 3 total) ==
Sep 21 03:15:04 itmon02 (httpd)[1172893]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
Sep 21 03:53:24 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2]
== kadath.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 03:47:30 kadath.cs.umd.edu puppet-agent[1246699]: (Facter) invalid or malformed lldp data: MalformedDataError: no lldp interface data found
== librenms (1 distinct, 1 total) ==
Sep 21 03:47:03 librenms (httpd)[1650388]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== matrix (10 distinct, 12 total) ==
Sep 21 04:00:18 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3727151, but reception only permitted for main PID 720
Sep 21 04:00:18 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3727164, but reception only permitted for main PID 720
Sep 21 04:00:26 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3727232, but reception only permitted for main PID 720
Sep 21 04:00:26 matrix networkctl[3727250]: Interface "vethdc6095f" not found.
Sep 21 04:00:26 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3727250, but reception only permitted for main PID 720 [x2]
Sep 21 04:00:26 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3727309, but reception only permitted for main PID 720
Sep 21 04:00:26 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3727322, but reception only permitted for main PID 720
Sep 21 04:03:52 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3730119, but reception only permitted for main PID 720
Sep 21 04:03:52 matrix networkctl[3730129]: Interface "vetheb82970" not found.
Sep 21 04:03:52 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3730129, but reception only permitted for main PID 720 [x2]
== munin (2 distinct, 16 total) ==
Sep 21 03:23:37 munin sudo[1121040]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x8]
Sep 21 03:23:37 munin sudo[1121040]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x8]
== netbox (1 distinct, 1 total) ==
Sep 21 03:08:03 netbox (httpd)[4180522]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== newhonors2 (1 distinct, 24 total) ==
Sep 21 03:13:03 newhonors2 dhcpcd[2932402]: dhcpcd is not running [x24]
== ntop00 (101 distinct, 145 total) ==
Sep 21 03:05:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 466) ***
Sep 21 03:05:52 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 466, QN: 11757/11757, ET: 51) ***
Sep 21 03:05:52 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 466, QN: 59/59, ET: 51) ***
Sep 21 03:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 467) ***
Sep 21 03:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 467, QN: 12033/12033, ET: 0) ***
Sep 21 03:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 467) ***
Sep 21 03:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 467, QN: 58/58, ET: 0) ***
Sep 21 03:08:02 ntop00 setroubleshoot[944941]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x12]
Sep 21 03:08:02 ntop00 setroubleshoot[944941]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x12]
Sep 21 03:08:02 ntop00 setroubleshoot[944941]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 21 03:08:02 ntop00 setroubleshoot[944941]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x12]
Sep 21 03:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 468) ***
Sep 21 03:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 468) ***
Sep 21 03:10:52 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 468, QN: 12104/12104, ET: 51) ***
Sep 21 03:10:53 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 468, QN: 62/62, ET: 52) ***
Sep 21 03:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 469) ***
Sep 21 03:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 469, QN: 11660/11660, ET: 0) ***
Sep 21 03:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 469) ***
Sep 21 03:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 469, QN: 42/42, ET: 0) ***
Sep 21 03:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 470) ***
Sep 21 03:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 470) ***
Sep 21 03:15:43 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 470, QN: 9751/9751, ET: 42) ***
Sep 21 03:15:44 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 470, QN: 46/46, ET: 43) ***
Sep 21 03:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 471) ***
Sep 21 03:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 471, QN: 7738/7738, ET: 0) ***
Sep 21 03:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 471) ***
Sep 21 03:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 471, QN: 72/72, ET: 0) ***
Sep 21 03:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 472) ***
Sep 21 03:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 472) ***
Sep 21 03:20:35 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 472, QN: 7768/7768, ET: 34) ***
... 71 more distinct messages not shown
== outbound00.cs.umd.edu (2 distinct, 8 total) ==
Sep 21 03:09:09 outbound00.cs.umd.edu python3[2244718]: ldapdb [x7]
Sep 21 03:24:14 outbound00.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway.
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 03:13:07 outbound01.cs.umd.edu python3[311103]: ldapdb [x6]
== sebatinsky.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 03:31:58 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 21 03:23:32 sentry-docker00.cs.umd.edu systemd-udevd[542389]: link_config: could not get ethtool features for veth35c8a83
Sep 21 03:23:32 sentry-docker00.cs.umd.edu systemd-udevd[542389]: Could not set offload features of veth35c8a83: No such device
Sep 21 03:23:32 sentry-docker00.cs.umd.edu systemd-udevd[542410]: Could not generate persistent MAC address for veth12e3f4d: No such file or directory
Sep 21 03:23:32 sentry-docker00.cs.umd.edu systemd-udevd[542411]: Could not generate persistent MAC address for veth1404040: No such file or directory
Sep 21 03:23:32 sentry-docker00.cs.umd.edu systemd-udevd[542429]: Could not generate persistent MAC address for veth25c4f55: No such file or directory
Sep 21 03:23:32 sentry-docker00.cs.umd.edu systemd-udevd[542424]: Could not generate persistent MAC address for vethb7682e9: No such file or directory
Sep 21 03:23:32 sentry-docker00.cs.umd.edu systemd-udevd[542410]: Could not generate persistent MAC address for veth883980d: No such file or directory
Sep 21 03:23:32 sentry-docker00.cs.umd.edu systemd-udevd[542417]: Could not generate persistent MAC address for vethb842340: No such file or directory
Sep 21 03:23:32 sentry-docker00.cs.umd.edu systemd-udevd[542417]: Could not generate persistent MAC address for veth02ebf2f: No such file or directory
Sep 21 03:23:32 sentry-docker00.cs.umd.edu systemd-udevd[542410]: Could not generate persistent MAC address for veth5004d51: No such file or directory
Sep 21 03:23:32 sentry-docker00.cs.umd.edu systemd-udevd[542457]: Could not generate persistent MAC address for veth1545b6e: No such file or directory
Sep 21 03:23:32 sentry-docker00.cs.umd.edu systemd-udevd[542464]: Could not generate persistent MAC address for veth7265020: No such file or directory
Sep 21 03:43:40 sentry-docker00.cs.umd.edu systemd-udevd[551877]: Could not generate persistent MAC address for vethed1ce85: No such file or directory
Sep 21 03:43:40 sentry-docker00.cs.umd.edu systemd-udevd[551878]: Could not generate persistent MAC address for veth03591f4: No such file or directory
Sep 21 03:43:40 sentry-docker00.cs.umd.edu systemd-udevd[551881]: Could not generate persistent MAC address for veth0e5ca75: No such file or directory
Sep 21 03:43:40 sentry-docker00.cs.umd.edu systemd-udevd[551899]: Could not generate persistent MAC address for veth05400f1: No such file or directory
Sep 21 03:43:40 sentry-docker00.cs.umd.edu systemd-udevd[551878]: Could not generate persistent MAC address for vethbc03819: No such file or directory
Sep 21 03:43:40 sentry-docker00.cs.umd.edu systemd-udevd[551881]: Could not generate persistent MAC address for vethe837f57: No such file or directory
Sep 21 03:43:40 sentry-docker00.cs.umd.edu systemd-udevd[551899]: Could not generate persistent MAC address for vethb3fc765: No such file or directory
Sep 21 03:43:40 sentry-docker00.cs.umd.edu systemd-udevd[551878]: Could not generate persistent MAC address for veth7becc3a: No such file or directory
Sep 21 03:43:40 sentry-docker00.cs.umd.edu systemd-udevd[551878]: Could not generate persistent MAC address for veth808a53c: No such file or directory
Sep 21 03:43:40 sentry-docker00.cs.umd.edu systemd-udevd[551899]: Could not generate persistent MAC address for vethaf7a3d2: No such file or directory
Sep 21 04:03:48 sentry-docker00.cs.umd.edu systemd-udevd[561239]: link_config: could not get ethtool features for vethed1ce85
Sep 21 04:03:48 sentry-docker00.cs.umd.edu systemd-udevd[561239]: Could not set offload features of vethed1ce85: No such device
Sep 21 04:03:48 sentry-docker00.cs.umd.edu systemd-udevd[561271]: Could not generate persistent MAC address for veth7a3d06b: No such file or directory
Sep 21 04:03:48 sentry-docker00.cs.umd.edu systemd-udevd[561272]: Could not generate persistent MAC address for veth7fcddb4: No such file or directory
Sep 21 04:03:48 sentry-docker00.cs.umd.edu systemd-udevd[561275]: Could not generate persistent MAC address for veth36a2269: No such file or directory
Sep 21 04:03:48 sentry-docker00.cs.umd.edu systemd-udevd[561276]: Could not generate persistent MAC address for veth3287e95: No such file or directory
Sep 21 04:03:48 sentry-docker00.cs.umd.edu systemd-udevd[561281]: Could not generate persistent MAC address for veth6cfb99d: No such file or directory
Sep 21 04:03:48 sentry-docker00.cs.umd.edu systemd-udevd[561298]: Could not generate persistent MAC address for veth7851394: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 21 03:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 21 03:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 21 03:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 21 03:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 21 03:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 21 03:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 21 03:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f2 (1 distinct, 2 total) ==
Sep 21 03:08:08 submit26-b9-f2 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.0513s
Status : exited 0
Output :
Syslog digest — 2026-09-21 03:05 EDT
Processed 2,152 lines, filtered 1,608 (74%). 544 unknown (197 distinct) from 20 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 02:53:15 b0b02.cs.umd.edu rustdesk[3474254]: cannot open display:
== bale (5 distinct, 93 total) ==
Sep 21 02:05:23 bale setroubleshoot[1344989]: failed to retrieve rpm info for /dev/nvme0 [x40]
Sep 21 02:05:24 bale setroubleshoot[1344989]: 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 21 02:05:26 bale setroubleshoot[1344989]: 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 21 02:05:29 bale setroubleshoot[1344989]: 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 21 02:05:41 bale setroubleshoot[1345616]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x16]
== cheezit.cs.umd.edu (6 distinct, 6 total) ==
Sep 21 03:03:45 cheezit.cs.umd.edu sshd-session[1441483]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 21 03:03:45 cheezit.cs.umd.edu sshd-session[1441483]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 21 03:03:47 cheezit.cs.umd.edu sshd-session[1441483]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 21 03:03:47 cheezit.cs.umd.edu sshd-session[1441483]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 21 03:03:51 cheezit.cs.umd.edu sshd-session[1441483]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 21 03:03:51 cheezit.cs.umd.edu sshd-session[1441483]: error: kex_protocol_error: type 30 seq 7 [preauth]
== csfw00a (1 distinct, 139 total) ==
Sep 21 02:03:57 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x139]
== idm00 (1 distinct, 1 total) ==
Sep 21 02:54:01 idm00 named[4166701]: client @0x7f11a0062908 10.73.240.42#64426: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 21 02:37:56 idmp0 named[1598691]: client @0x7f2d34049808 10.73.240.43#52449: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 2 total) ==
Sep 21 02:13:58 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2]
== krispykreme.cs.umd.edu (9 distinct, 10 total) ==
Sep 21 02:08:09 krispykreme.cs.umd.edu sshd-session[536092]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2]
Sep 21 02:08:10 krispykreme.cs.umd.edu sshd-session[536092]: Error in Duo login for 'larry' from 71.191.93.172
Sep 21 02:08:10 krispykreme.cs.umd.edu sshd-session[536090]: error: PAM: Authentication failure for larry from 71.191.93.172
Sep 21 03:03:42 krispykreme.cs.umd.edu sshd-session[551306]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 21 03:03:42 krispykreme.cs.umd.edu sshd-session[551306]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 21 03:03:46 krispykreme.cs.umd.edu sshd-session[551306]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 21 03:03:46 krispykreme.cs.umd.edu sshd-session[551306]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 21 03:03:48 krispykreme.cs.umd.edu sshd-session[551306]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 21 03:03:48 krispykreme.cs.umd.edu sshd-session[551306]: error: kex_protocol_error: type 30 seq 7 [preauth]
== matrix (2 distinct, 3 total) ==
Sep 21 02:51:34 matrix krb5_child[3687972]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 21 02:51:36 matrix sshd[3687966]: error: PAM: Authentication failure for admin from 104.199.98.110
== munin (2 distinct, 8 total) ==
Sep 21 02:53:43 munin sudo[1110625]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 21 02:53:43 munin sudo[1110625]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== newhonors2 (1 distinct, 24 total) ==
Sep 21 02:13:03 newhonors2 dhcpcd[2930551]: dhcpcd is not running [x24]
== ntop00 (101 distinct, 145 total) ==
Sep 21 02:05:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 442) ***
Sep 21 02:05:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 442) ***
Sep 21 02:05:47 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 10855/10855, ET: 46) ***
Sep 21 02:05:47 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 66/66, ET: 46) ***
Sep 21 02:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 443) ***
Sep 21 02:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 10859/10859, ET: 0) ***
Sep 21 02:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 443) ***
Sep 21 02:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 60/60, ET: 0) ***
Sep 21 02:08:02 ntop00 setroubleshoot[937036]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x12]
Sep 21 02:08:02 ntop00 setroubleshoot[937036]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x12]
Sep 21 02:08:02 ntop00 setroubleshoot[937036]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 21 02:08:02 ntop00 setroubleshoot[937036]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x12]
Sep 21 02:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) ***
Sep 21 02:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) ***
Sep 21 02:10:51 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 11171/11171, ET: 50) ***
Sep 21 02:10:51 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 54/54, ET: 50) ***
Sep 21 02:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 445) ***
Sep 21 02:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 11584/11584, ET: 0) ***
Sep 21 02:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 445) ***
Sep 21 02:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 61/61, ET: 0) ***
Sep 21 02:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) ***
Sep 21 02:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) ***
Sep 21 02:15:52 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 11434/11434, ET: 51) ***
Sep 21 02:15:52 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 62/62, ET: 51) ***
Sep 21 02:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 447) ***
Sep 21 02:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 11123/11123, ET: 0) ***
Sep 21 02:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 447) ***
Sep 21 02:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 65/65, ET: 0) ***
Sep 21 02:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) ***
Sep 21 02:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) ***
... 71 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 02:09:09 outbound00.cs.umd.edu python3[2230633]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 02:13:06 outbound01.cs.umd.edu python3[297149]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513614]: link_config: could not get ethtool features for veth8f92d0b
Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513614]: Could not set offload features of veth8f92d0b: No such device
Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513620]: Could not generate persistent MAC address for vethbbf43a2: No such file or directory
Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513614]: Could not generate persistent MAC address for veth16820e3: No such file or directory
Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513662]: Could not generate persistent MAC address for veth725441e: No such file or directory
Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513663]: Could not generate persistent MAC address for veth3428f23: No such file or directory
Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513666]: Could not generate persistent MAC address for veth9fcb719: No such file or directory
Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513671]: Could not generate persistent MAC address for veth1b40c0f: No such file or directory
Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513686]: Could not generate persistent MAC address for veth81eacfa: No such file or directory
Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513667]: Could not generate persistent MAC address for vethfd69725: No such file or directory
Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513727]: Could not generate persistent MAC address for vetha3f1aee: No such file or directory
Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513720]: Could not generate persistent MAC address for vetha8d4201: No such file or directory
Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523030]: link_config: could not get ethtool features for veth9fcb719
Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523030]: Could not set offload features of veth9fcb719: No such device
Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523066]: Could not generate persistent MAC address for vethb94c51d: No such file or directory
Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523067]: Could not generate persistent MAC address for vethc2a1ef0: No such file or directory
Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523070]: Could not generate persistent MAC address for veth13cab11: No such file or directory
Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523071]: Could not generate persistent MAC address for vethbaf54c2: No such file or directory
Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523087]: Could not generate persistent MAC address for veth2e71221: No such file or directory
Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523081]: Could not generate persistent MAC address for veth86e279f: No such file or directory
Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523071]: Could not generate persistent MAC address for veth6f2896c: No such file or directory
Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523087]: Could not generate persistent MAC address for vethc8e073d: No such file or directory
Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523087]: Could not generate persistent MAC address for veth2a6b149: No such file or directory
Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523089]: Could not generate persistent MAC address for vetha2cfbdd: No such file or directory
Sep 21 03:03:23 sentry-docker00.cs.umd.edu systemd-udevd[532856]: link_config: could not get ethtool features for vetha2cfbdd
Sep 21 03:03:23 sentry-docker00.cs.umd.edu systemd-udevd[532856]: Could not set offload features of vetha2cfbdd: No such device
Sep 21 03:03:24 sentry-docker00.cs.umd.edu systemd-udevd[532899]: Could not generate persistent MAC address for veth35c8a83: No such file or directory
Sep 21 03:03:24 sentry-docker00.cs.umd.edu systemd-udevd[532900]: Could not generate persistent MAC address for vethecda9dc: No such file or directory
Sep 21 03:03:24 sentry-docker00.cs.umd.edu systemd-udevd[532903]: Could not generate persistent MAC address for vethc0b87c8: No such file or directory
Sep 21 03:03:24 sentry-docker00.cs.umd.edu systemd-udevd[532904]: Could not generate persistent MAC address for veth39130cb: No such file or directory
... 6 more distinct messages not shown
== soul (1 distinct, 1 total) ==
Sep 21 02:48:51 soul krb5_child[3893543]: Client 'terry(a)UMD.EDU' not found in Kerberos database
== strawberry (7 distinct, 38 total) ==
Sep 21 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 21 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 21 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 21 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 21 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 21 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 21 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (9 distinct, 11 total) ==
Sep 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: 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 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: 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 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6 [x2]
Sep 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.veJuER/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d [x2]
Sep 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: 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 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.veJuER. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: 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 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: 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 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848
== submit26-b9-f2 (10 distinct, 10 total) ==
Sep 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: 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 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: 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 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: 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 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.zGNCBw/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: 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 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.zGNCBw. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: 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 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: 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 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: 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 21 02:55:07 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f3 (1 distinct, 3 total) ==
Sep 21 02:27:36 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0558s
Status : exited 0
Output :
Syslog digest — 2026-09-21 02:05 EDT
Processed 3,142 lines, filtered 2,554 (81%). 588 unknown (203 distinct) from 23 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 01:53:12 b0b02.cs.umd.edu rustdesk[3459018]: cannot open display:
== bale (5 distinct, 86 total) ==
Sep 21 01:05:15 bale setroubleshoot[1332102]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 21 01:05:16 bale setroubleshoot[1332102]: 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 21 01:05:18 bale setroubleshoot[1332102]: 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 21 01:05:21 bale setroubleshoot[1332102]: 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 21 01:05:33 bale setroubleshoot[1332719]: 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 (3 distinct, 3 total) ==
Sep 21 01:57:57 biggulp.cs.umd.edu sshd-session[2949804]: pam_access(sshd:auth): access denied for user `admin' from `193.187.110.214'
Sep 21 01:57:58 biggulp.cs.umd.edu krb5_child[2949822]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 21 01:57:58 biggulp.cs.umd.edu sshd-session[2949802]: error: PAM: System error for admin from 193.187.110.214
== cmsc436-0101-redis (1 distinct, 1 total) ==
Sep 21 01:15:55 cmsc436-0101-redis sshd-session[3364158]: error: PAM: Authentication failure for operator from 193.187.110.214
== csfw00a (1 distinct, 127 total) ==
Sep 21 01:03:48 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x127]
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 21 01:54:01 idm00 named[4166701]: client @0x7f1198079d88 10.73.240.42#52035: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 21 01:37:56 idmp0 named[1598691]: client @0x7f2d2c0368e8 10.73.240.43#60956: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (2 distinct, 2 total) ==
Sep 21 01:11:10 inbound00.cs.umd.edu krb5_child[2350790]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 21 01:11:39 inbound00.cs.umd.edu sshd-session[2350826]: error: Protocol major versions differ: 2 vs. 1
== inbound01.cs.umd.edu (2 distinct, 2 total) ==
Sep 21 01:22:46 inbound01.cs.umd.edu krb5_child[377095]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 21 01:23:06 inbound01.cs.umd.edu sshd-session[377104]: error: Protocol major versions differ: 2 vs. 1
== itmon02 (1 distinct, 7 total) ==
Sep 21 01:14:00 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x7]
== munin (2 distinct, 8 total) ==
Sep 21 01:18:09 munin sudo[1075241]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 21 01:18:09 munin sudo[1075241]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== newhonors2 (1 distinct, 24 total) ==
Sep 21 01:13:03 newhonors2 dhcpcd[2928706]: dhcpcd is not running [x24]
== ntop00 (99 distinct, 143 total) ==
Sep 21 01:05:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 418) ***
Sep 21 01:05:32 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 7248/7248, ET: 31) ***
Sep 21 01:05:32 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 42/42, ET: 31) ***
Sep 21 01:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 419) ***
Sep 21 01:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 7315/7315, ET: 0) ***
Sep 21 01:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 419) ***
Sep 21 01:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 40/40, ET: 0) ***
Sep 21 01:08:02 ntop00 setroubleshoot[928991]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x12]
Sep 21 01:08:02 ntop00 setroubleshoot[928991]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x12]
Sep 21 01:08:02 ntop00 setroubleshoot[928991]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 21 01:08:02 ntop00 setroubleshoot[928991]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x12]
Sep 21 01:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) ***
Sep 21 01:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) ***
Sep 21 01:10:35 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 7580/7580, ET: 34) ***
Sep 21 01:10:35 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 52/52, ET: 34) ***
Sep 21 01:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 421) ***
Sep 21 01:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 7635/7635, ET: 0) ***
Sep 21 01:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 421) ***
Sep 21 01:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 44/44, ET: 0) ***
Sep 21 01:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) ***
Sep 21 01:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) ***
Sep 21 01:15:35 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 7296/7296, ET: 34) ***
Sep 21 01:15:35 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 36/36, ET: 34) ***
Sep 21 01:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 423) ***
Sep 21 01:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 35/35, ET: 0) ***
Sep 21 01:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 423) ***
Sep 21 01:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 7553/7553, ET: 0) ***
Sep 21 01:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) ***
Sep 21 01:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) ***
Sep 21 01:20:37 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 7850/7850, ET: 36) ***
... 69 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 01:09:09 outbound00.cs.umd.edu python3[2216669]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 01:13:06 outbound01.cs.umd.edu python3[283029]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (40 distinct, 40 total) ==
Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485315]: link_config: could not get ethtool features for vetheadb795
Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485315]: Could not set offload features of vetheadb795: No such device
Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485379]: Could not generate persistent MAC address for veth7561f77: No such file or directory
Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485380]: Could not generate persistent MAC address for veth779dadb: No such file or directory
Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485383]: Could not generate persistent MAC address for veth8641e88: No such file or directory
Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485384]: Could not generate persistent MAC address for veth4f86a53: No such file or directory
Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485407]: Could not generate persistent MAC address for vethdbdeaf6: No such file or directory
Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485408]: Could not generate persistent MAC address for veth47a2a63: No such file or directory
Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485426]: Could not generate persistent MAC address for veth88c53d0: No such file or directory
Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485433]: Could not generate persistent MAC address for vethf3b2e4e: No such file or directory
Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485440]: Could not generate persistent MAC address for vethb671a97: No such file or directory
Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485446]: Could not generate persistent MAC address for veth4ed4f22: No such file or directory
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494790]: link_config: could not get ethtool features for veth7561f77
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494790]: Could not set offload features of veth7561f77: No such device
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494792]: link_config: could not get ethtool features for veth8641e88
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494792]: Could not set offload features of veth8641e88: No such device
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494833]: Could not generate persistent MAC address for vethc8a6ab4: No such file or directory
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494834]: Could not generate persistent MAC address for veth44af3e2: No such file or directory
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494837]: Could not generate persistent MAC address for vethad21fb4: No such file or directory
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494838]: Could not generate persistent MAC address for vethb5f3226: No such file or directory
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494861]: Could not generate persistent MAC address for veth32f2656: No such file or directory
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494862]: Could not generate persistent MAC address for veth4862a45: No such file or directory
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494885]: Could not generate persistent MAC address for vethab0f164: No such file or directory
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494871]: Could not generate persistent MAC address for veth3689c81: No such file or directory
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494869]: Could not generate persistent MAC address for veth0fbc5af: No such file or directory
Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494861]: Could not generate persistent MAC address for veth6b91818: No such file or directory
Sep 21 02:02:58 sentry-docker00.cs.umd.edu systemd-udevd[504140]: link_config: could not get ethtool features for veth3689c81
Sep 21 02:02:58 sentry-docker00.cs.umd.edu systemd-udevd[504140]: Could not set offload features of veth3689c81: No such device
Sep 21 02:02:58 sentry-docker00.cs.umd.edu systemd-udevd[504171]: link_config: could not set ethtool features for vethc8a6ab4
Sep 21 02:02:58 sentry-docker00.cs.umd.edu systemd-udevd[504171]: Could not set offload features of vethc8a6ab4: Operation not permitted
... 10 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 21 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 21 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 21 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 21 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 21 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 21 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 21 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 2 total) ==
Sep 21 01:08:07 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f2 (1 distinct, 2 total) ==
Sep 21 01:23:06 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f3 (10 distinct, 11 total) ==
Sep 21 01:05:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
Sep 21 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: 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 21 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: 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 21 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: 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 21 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.OIYCwp/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 21 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: 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 21 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.OIYCwp. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 21 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: 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 21 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: 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 21 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68
== submit26-b9-f4 (10 distinct, 10 total) ==
Sep 21 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: 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 21 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: 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 21 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: 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 21 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.DBMvD3/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 21 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: 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 21 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.DBMvD3. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 21 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: 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 21 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: 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 21 01:24:48 submit26-b9-f4 setroubleshoot[1592053]: 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 21 01:43:08 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== tma-0 (1 distinct, 1 total) ==
Sep 21 01:12:53 tma-0 sshd[13127]: error: PAM: Authentication failure for admin from 79.62.62.34.bc.googleusercontent.com
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0526s
Status : exited 0
Output :
Syslog digest — 2026-09-21 01:05 EDT
Processed 1,985 lines, filtered 1,386 (69%). 599 unknown (220 distinct) from 34 host(s).
== abuse (3 distinct, 4 total) ==
Sep 21 00:10:14 abuse systemd[1]: New main PID 26280 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 21 00:10:33 abuse systemd[1]: Daemon never wrote its PID file. Failing.
Sep 21 00:10:43 abuse systemd[1]: pmlogger.service: Supervising process 1046 which is not our child. We'll most likely not notice when it exits.
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 00:53:08 b0b02.cs.umd.edu rustdesk[3443845]: cannot open display:
== bale (5 distinct, 84 total) ==
Sep 21 00:06:05 bale setroubleshoot[1318904]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 21 00:06:06 bale setroubleshoot[1318904]: 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 21 00:06:08 bale setroubleshoot[1318904]: 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 21 00:06:11 bale setroubleshoot[1318904]: 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 21 00:06:23 bale setroubleshoot[1319518]: 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 (4 distinct, 4 total) ==
Sep 21 00:37:54 biggulp.cs.umd.edu sshd-session[2936346]: pam_access(sshd:auth): access denied for user `admin' from `130.211.97.92'
Sep 21 00:37:54 biggulp.cs.umd.edu krb5_child[2936348]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 21 00:37:54 biggulp.cs.umd.edu sshd-session[2936344]: error: PAM: System error for admin from 130.211.97.92
Sep 21 00:38:19 biggulp.cs.umd.edu sshd-session[2936415]: error: Protocol major versions differ: 2 vs. 1
== cheezit.cs.umd.edu (3 distinct, 3 total) ==
Sep 21 00:39:50 cheezit.cs.umd.edu sshd-session[1408301]: pam_access(sshd:auth): access denied for user `admin' from `130.211.97.92'
Sep 21 00:39:50 cheezit.cs.umd.edu krb5_child[1408303]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 21 00:39:50 cheezit.cs.umd.edu sshd-session[1408299]: error: PAM: System error for admin from 130.211.97.92
== csfw00a (1 distinct, 130 total) ==
Sep 21 00:04:56 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x130]
== grades01.cs.umd.edu (3 distinct, 4 total) ==
Sep 21 00:10:13 grades01.cs.umd.edu systemd[1]: New main PID 29529 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 21 00:10:34 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 21 00:10:49 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 4527 which is not our child. We'll most likely not notice when it exits.
== idm00 (1 distinct, 1 total) ==
Sep 21 00:54:01 idm00 named[4166701]: client @0x7f11a4036798 10.73.240.42#62867: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 21 00:37:56 idmp0 named[1598691]: client @0x7f2d1c0104c8 10.73.240.43#63077: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 2 total) ==
Sep 21 00:43:52 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2]
== jubjub.cs.umd.edu (3 distinct, 4 total) ==
Sep 21 00:10:12 jubjub.cs.umd.edu systemd[1]: New main PID 3928319 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 21 00:10:32 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 21 00:10:40 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3935403 which is not our child. We'll most likely not notice when it exits.
== krispykreme.cs.umd.edu (3 distinct, 3 total) ==
Sep 21 00:44:27 krispykreme.cs.umd.edu sshd-session[512891]: pam_access(sshd:auth): access denied for user `admin' from `104.199.98.110'
Sep 21 00:44:27 krispykreme.cs.umd.edu krb5_child[512893]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 21 00:44:27 krispykreme.cs.umd.edu sshd-session[512889]: error: PAM: System error for admin from 104.199.98.110
== mirrors.cs.umd.edu (4 distinct, 6 total) ==
Sep 21 00:10:33 mirrors.cs.umd.edu root[13216]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log
Sep 21 00:10:33 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. [x2]
Sep 21 00:10:37 mirrors.cs.umd.edu systemd[1]: New main PID 12147 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 21 00:11:51 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 28955 which is not our child. We'll most likely not notice when it exits.
== misty.cs.umd.edu (3 distinct, 4 total) ==
Sep 21 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 15396 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 21 00:10:35 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 21 00:10:51 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 22722 which is not our child. We'll most likely not notice when it exits.
== munin (2 distinct, 44 total) ==
Sep 21 00:13:05 munin sudo[1051211]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x22]
Sep 21 00:13:05 munin sudo[1051211]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x22]
== netman.cs.umd.edu (3 distinct, 6 total) ==
Sep 21 00:45:43 netman.cs.umd.edu krb5_child[2999775]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Sep 21 00:45:48 netman.cs.umd.edu sshd[2999764]: error: PAM: Authentication failure for admin from 207.175.19.96
Sep 21 00:45:59 netman.cs.umd.edu sshd[2999788]: error: Protocol major versions differ: 2 vs. 1
== newhonors2 (1 distinct, 24 total) ==
Sep 21 00:13:02 newhonors2 dhcpcd[2926864]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 21 00:05:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 394) ***
Sep 21 00:05:31 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 394, QN: 6524/6524, ET: 30) ***
Sep 21 00:05:31 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 394, QN: 44/44, ET: 30) ***
Sep 21 00:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 395) ***
Sep 21 00:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 395, QN: 6913/6913, ET: 0) ***
Sep 21 00:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 395) ***
Sep 21 00:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 395, QN: 41/41, ET: 0) ***
Sep 21 00:08:02 ntop00 setroubleshoot[921096]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x12]
Sep 21 00:08:02 ntop00 setroubleshoot[921096]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x12]
Sep 21 00:08:02 ntop00 setroubleshoot[921096]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 21 00:08:02 ntop00 setroubleshoot[921096]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x12]
Sep 21 00:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 396) ***
Sep 21 00:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 396) ***
Sep 21 00:10:34 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 396, QN: 6791/6791, ET: 33) ***
Sep 21 00:10:34 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 396, QN: 41/41, ET: 33) ***
Sep 21 00:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 397) ***
Sep 21 00:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 397, QN: 6594/6594, ET: 0) ***
Sep 21 00:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 397) ***
Sep 21 00:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 397, QN: 37/37, ET: 0) ***
Sep 21 00:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 398) ***
Sep 21 00:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 398) ***
Sep 21 00:15:32 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 398, QN: 6749/6749, ET: 31) ***
Sep 21 00:15:33 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 398, QN: 36/36, ET: 32) ***
Sep 21 00:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 399) ***
Sep 21 00:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 399, QN: 6805/6805, ET: 0) ***
Sep 21 00:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 399) ***
Sep 21 00:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 399, QN: 43/43, ET: 0) ***
Sep 21 00:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 400) ***
Sep 21 00:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 400) ***
Sep 21 00:20:32 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 400, QN: 6763/6763, ET: 31) ***
... 70 more distinct messages not shown
== openrepo (1 distinct, 1 total) ==
Sep 21 00:05:53 openrepo (nin-node)[3231015]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== outbound00.cs.umd.edu (3 distinct, 8 total) ==
Sep 21 00:09:09 outbound00.cs.umd.edu python3[2202145]: ldapdb [x6]
Sep 21 00:11:21 outbound00.cs.umd.edu krb5_child[2203191]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 21 00:11:55 outbound00.cs.umd.edu sshd-session[2203349]: error: Protocol major versions differ: 2 vs. 1
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 00:13:07 outbound01.cs.umd.edu python3[269064]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 21 00:22:17 sentry-docker00.cs.umd.edu systemd-udevd[456707]: link_config: could not get ethtool features for veth16874e8
Sep 21 00:22:17 sentry-docker00.cs.umd.edu systemd-udevd[456707]: Could not set offload features of veth16874e8: No such device
Sep 21 00:22:17 sentry-docker00.cs.umd.edu systemd-udevd[456781]: Could not generate persistent MAC address for veth995b502: No such file or directory
Sep 21 00:22:17 sentry-docker00.cs.umd.edu systemd-udevd[456782]: Could not generate persistent MAC address for vethe1bbaad: No such file or directory
Sep 21 00:22:17 sentry-docker00.cs.umd.edu systemd-udevd[456785]: Could not generate persistent MAC address for veth005cba0: No such file or directory
Sep 21 00:22:17 sentry-docker00.cs.umd.edu systemd-udevd[456786]: Could not generate persistent MAC address for veth99cec5e: No such file or directory
Sep 21 00:22:17 sentry-docker00.cs.umd.edu systemd-udevd[456810]: Could not generate persistent MAC address for veth5af871e: No such file or directory
Sep 21 00:22:17 sentry-docker00.cs.umd.edu systemd-udevd[456809]: Could not generate persistent MAC address for vethca01728: No such file or directory
Sep 21 00:22:17 sentry-docker00.cs.umd.edu systemd-udevd[456859]: Could not generate persistent MAC address for vethb9f0bdf: No such file or directory
Sep 21 00:22:17 sentry-docker00.cs.umd.edu systemd-udevd[456861]: Could not generate persistent MAC address for vethe69c6f3: No such file or directory
Sep 21 00:22:17 sentry-docker00.cs.umd.edu systemd-udevd[456896]: Could not generate persistent MAC address for veth9589ead: No such file or directory
Sep 21 00:22:17 sentry-docker00.cs.umd.edu systemd-udevd[456898]: Could not generate persistent MAC address for veth2d0b712: No such file or directory
Sep 21 00:42:25 sentry-docker00.cs.umd.edu systemd-udevd[466227]: link_config: could not get ethtool features for veth9589ead
Sep 21 00:42:25 sentry-docker00.cs.umd.edu systemd-udevd[466227]: Could not set offload features of veth9589ead: No such device
Sep 21 00:42:26 sentry-docker00.cs.umd.edu systemd-udevd[466267]: Could not generate persistent MAC address for vethe03bced: No such file or directory
Sep 21 00:42:26 sentry-docker00.cs.umd.edu systemd-udevd[466268]: Could not generate persistent MAC address for veth0f9fda7: No such file or directory
Sep 21 00:42:26 sentry-docker00.cs.umd.edu systemd-udevd[466271]: Could not generate persistent MAC address for veth4ae5136: No such file or directory
Sep 21 00:42:26 sentry-docker00.cs.umd.edu systemd-udevd[466272]: Could not generate persistent MAC address for veth8a20ed6: No such file or directory
Sep 21 00:42:26 sentry-docker00.cs.umd.edu systemd-udevd[466282]: Could not generate persistent MAC address for veth56036c9: No such file or directory
Sep 21 00:42:26 sentry-docker00.cs.umd.edu systemd-udevd[466292]: Could not generate persistent MAC address for veth278b962: No such file or directory
Sep 21 00:42:26 sentry-docker00.cs.umd.edu systemd-udevd[466272]: Could not generate persistent MAC address for vethb1efa9c: No such file or directory
Sep 21 00:42:26 sentry-docker00.cs.umd.edu systemd-udevd[466293]: Could not generate persistent MAC address for veth89feda2: No such file or directory
Sep 21 00:42:26 sentry-docker00.cs.umd.edu systemd-udevd[466282]: Could not generate persistent MAC address for vethafac709: No such file or directory
Sep 21 00:42:26 sentry-docker00.cs.umd.edu systemd-udevd[466292]: Could not generate persistent MAC address for vethc7c1793: No such file or directory
Sep 21 01:02:33 sentry-docker00.cs.umd.edu systemd-udevd[475643]: link_config: could not get ethtool features for veth4ae5136
Sep 21 01:02:33 sentry-docker00.cs.umd.edu systemd-udevd[475643]: Could not set offload features of veth4ae5136: No such device
Sep 21 01:02:34 sentry-docker00.cs.umd.edu systemd-udevd[475696]: Could not generate persistent MAC address for vetheadb795: No such file or directory
Sep 21 01:02:34 sentry-docker00.cs.umd.edu systemd-udevd[475697]: Could not generate persistent MAC address for veth04b034f: No such file or directory
Sep 21 01:02:34 sentry-docker00.cs.umd.edu systemd-udevd[475740]: Could not generate persistent MAC address for veth78969ab: No such file or directory
Sep 21 01:02:34 sentry-docker00.cs.umd.edu systemd-udevd[475741]: Could not generate persistent MAC address for vethb0dfeeb: No such file or directory
... 6 more distinct messages not shown
== soul (1 distinct, 1 total) ==
Sep 21 00:27:43 soul krb5_child[3871402]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== strawberry (8 distinct, 39 total) ==
Sep 21 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 21 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 21 00:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 21 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 21 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 21 00:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 21 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Sep 21 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing.
== submit10-cln25 (3 distinct, 4 total) ==
Sep 21 00:10:11 submit10-cln25 systemd: New main PID 26437 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 21 00:10:31 submit10-cln25 systemd: Daemon never wrote its PID file. Failing.
Sep 21 00:10:37 submit10-cln25 systemd: pmlogger.service: Supervising process 985 which is not our child. We'll most likely not notice when it exits.
== submit26-b9-f1 (1 distinct, 3 total) ==
Sep 21 00:12:18 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f2 (1 distinct, 2 total) ==
Sep 21 00:18:07 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 21 00:25:05 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 21 00:39:20 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 21 00:21:57 submit26-b9-fclone setroubleshoot[207433]: 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 21 00:21:57 submit26-b9-fclone setroubleshoot[207433]: 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 21 00:21:57 submit26-b9-fclone setroubleshoot[207433]: 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 21 00:21:57 submit26-b9-fclone setroubleshoot[207433]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.0dNKJH/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 21 00:21:57 submit26-b9-fclone setroubleshoot[207433]: 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 21 00:21:57 submit26-b9-fclone setroubleshoot[207433]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.0dNKJH. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 21 00:21:57 submit26-b9-fclone setroubleshoot[207433]: 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 21 00:21:57 submit26-b9-fclone setroubleshoot[207433]: 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 21 00:21:57 submit26-b9-fclone setroubleshoot[207433]: 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 21 00:10:13 tma-0 systemd[1]: New main PID 24886 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 21 00:10:31 tma-0 systemd[1]: Daemon never wrote its PID file. Failing.
Sep 21 00:10:39 tma-0 systemd[1]: pmlogger.service: Supervising process 32469 which is not our child. We'll most likely not notice when it exits.
== uffish.cs.umd.edu (3 distinct, 4 total) ==
Sep 21 00:10:14 uffish.cs.umd.edu systemd[1]: New main PID 2327203 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 21 00:10:40 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 21 00:10:57 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 2334839 which is not our child. We'll most likely not notice when it exits.
== vacuum.cs.umd.edu (3 distinct, 4 total) ==
Sep 21 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 23083 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 21 00:10:33 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 21 00:10:44 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 30187 which is not our child. We'll most likely not notice when it exits.
== whiffle.cs.umd.edu (3 distinct, 4 total) ==
Sep 21 00:10:13 whiffle.cs.umd.edu systemd[1]: New main PID 1882501 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 21 00:10:38 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 21 00:10:52 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1889773 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.0488s
Status : exited 0
Output :
Syslog digest — 2026-09-21 00:05 EDT
Processed 1,974 lines, filtered 1,472 (74%). 502 unknown (164 distinct) from 22 host(s).
== abadi-computer (1 distinct, 1 total) ==
Sep 21 00:00:00 abadi-computer systemctl[1611468]: Warning: The unit file, source configuration file or drop-ins of cups.service changed on disk. Run 'systemctl daemon-reload' to reload units.
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 20 23:53:04 b0b02.cs.umd.edu rustdesk[3427732]: cannot open display:
== bale (5 distinct, 85 total) ==
Sep 20 23:05:55 bale setroubleshoot[1306205]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 20 23:05:56 bale setroubleshoot[1306205]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12]
Sep 20 23:05:58 bale setroubleshoot[1306205]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13]
Sep 20 23:06:01 bale setroubleshoot[1306205]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x11]
Sep 20 23:06:13 bale setroubleshoot[1306819]: 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, 145 total) ==
Sep 20 23:04:54 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x145]
== idm00 (1 distinct, 1 total) ==
Sep 20 23:54:01 idm00 named[4166701]: client @0x7f11a9430488 10.73.240.42#60642: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 20 23:37:56 idmp0 named[1598691]: client @0x7f2d48000cc8 10.73.240.43#58896: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 1 total) ==
Sep 20 23:08:55 itmon02 sshd[1750555]: error: beginning MaxStartups throttling
== matrix (1 distinct, 1 total) ==
Sep 21 00:00:25 matrix (nin-node)[3588685]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== mcstic (2 distinct, 5 total) ==
Sep 20 23:49:06 mcstic krb5_child[883152]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Sep 20 23:49:12 mcstic sshd[883147]: error: PAM: Authentication failure for admin from 34.38.229.202
== neo-gizmonic (1 distinct, 1 total) ==
Sep 21 00:00:01 neo-gizmonic (nin-node)[1895724]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neoavion (1 distinct, 1 total) ==
Sep 21 00:00:09 neoavion (nin-node)[3857075]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== newhonors2 (2 distinct, 25 total) ==
Sep 20 23:13:03 newhonors2 dhcpcd[2924820]: dhcpcd is not running [x24]
Sep 21 00:00:16 newhonors2 (nin-node)[2926335]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== ntop00 (100 distinct, 144 total) ==
Sep 20 23:05:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 370) ***
Sep 20 23:05:26 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 370, QN: 5967/5967, ET: 25) ***
Sep 20 23:05:26 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 370, QN: 42/42, ET: 25) ***
Sep 20 23:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 371) ***
Sep 20 23:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 371, QN: 6072/6072, ET: 0) ***
Sep 20 23:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 371) ***
Sep 20 23:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 371, QN: 47/47, ET: 0) ***
Sep 20 23:08:02 ntop00 setroubleshoot[913209]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x12]
Sep 20 23:08:02 ntop00 setroubleshoot[913209]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x12]
Sep 20 23:08:02 ntop00 setroubleshoot[913209]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 20 23:08:02 ntop00 setroubleshoot[913209]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x12]
Sep 20 23:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 372) ***
Sep 20 23:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 372) ***
Sep 20 23:10:27 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 372, QN: 6301/6301, ET: 26) ***
Sep 20 23:10:27 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 372, QN: 51/51, ET: 26) ***
Sep 20 23:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 373) ***
Sep 20 23:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 373, QN: 6074/6074, ET: 0) ***
Sep 20 23:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 373) ***
Sep 20 23:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 373, QN: 63/63, ET: 0) ***
Sep 20 23:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 374) ***
Sep 20 23:15:02 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 374) ***
Sep 20 23:15:25 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 374, QN: 5910/5910, ET: 24) ***
Sep 20 23:15:25 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 374, QN: 55/55, ET: 23) ***
Sep 20 23:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 375) ***
Sep 20 23:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 375, QN: 6149/6149, ET: 0) ***
Sep 20 23:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 375) ***
Sep 20 23:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 375, QN: 38/38, ET: 0) ***
Sep 20 23:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 376) ***
Sep 20 23:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 376) ***
Sep 20 23:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 376, QN: 41/41, ET: 0) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 20 23:09:09 outbound00.cs.umd.edu python3[2187950]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 20 23:13:06 outbound01.cs.umd.edu python3[254283]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (32 distinct, 32 total) ==
Sep 20 23:21:52 sentry-docker00.cs.umd.edu systemd-udevd[428347]: link_config: could not get ethtool features for veth76b01be
Sep 20 23:21:52 sentry-docker00.cs.umd.edu systemd-udevd[428347]: Could not set offload features of veth76b01be: No such device
Sep 20 23:21:52 sentry-docker00.cs.umd.edu systemd-udevd[428432]: Could not generate persistent MAC address for vethc833a44: No such file or directory
Sep 20 23:21:52 sentry-docker00.cs.umd.edu systemd-udevd[428433]: Could not generate persistent MAC address for vethf4c153d: No such file or directory
Sep 20 23:21:52 sentry-docker00.cs.umd.edu systemd-udevd[428436]: Could not generate persistent MAC address for vethfe0f4be: No such file or directory
Sep 20 23:21:52 sentry-docker00.cs.umd.edu systemd-udevd[428437]: Could not generate persistent MAC address for veth37e0e14: No such file or directory
Sep 20 23:21:52 sentry-docker00.cs.umd.edu systemd-udevd[428453]: Could not generate persistent MAC address for vethdb28c7b: No such file or directory
Sep 20 23:21:52 sentry-docker00.cs.umd.edu systemd-udevd[428449]: Could not generate persistent MAC address for veth86857e8: No such file or directory
Sep 20 23:21:52 sentry-docker00.cs.umd.edu systemd-udevd[428453]: Could not generate persistent MAC address for veth9b0da49: No such file or directory
Sep 20 23:21:52 sentry-docker00.cs.umd.edu systemd-udevd[428448]: Could not generate persistent MAC address for veth7370ac4: No such file or directory
Sep 20 23:21:52 sentry-docker00.cs.umd.edu systemd-udevd[428453]: Could not generate persistent MAC address for veth4385a62: No such file or directory
Sep 20 23:21:52 sentry-docker00.cs.umd.edu systemd-udevd[428437]: Could not generate persistent MAC address for veth3fca32b: No such file or directory
Sep 20 23:42:01 sentry-docker00.cs.umd.edu systemd-udevd[437898]: Could not generate persistent MAC address for vethea296ea: No such file or directory
Sep 20 23:42:01 sentry-docker00.cs.umd.edu systemd-udevd[437899]: Could not generate persistent MAC address for vethde7a261: No such file or directory
Sep 20 23:42:01 sentry-docker00.cs.umd.edu systemd-udevd[437917]: Could not generate persistent MAC address for vethe06a6a8: No such file or directory
Sep 20 23:42:01 sentry-docker00.cs.umd.edu systemd-udevd[437909]: Could not generate persistent MAC address for veth1245985: No such file or directory
Sep 20 23:42:01 sentry-docker00.cs.umd.edu systemd-udevd[437920]: Could not generate persistent MAC address for vethad215ac: No such file or directory
Sep 20 23:42:01 sentry-docker00.cs.umd.edu systemd-udevd[437919]: Could not generate persistent MAC address for veth5b456f8: No such file or directory
Sep 20 23:42:01 sentry-docker00.cs.umd.edu systemd-udevd[437909]: Could not generate persistent MAC address for vethab8270a: No such file or directory
Sep 20 23:42:01 sentry-docker00.cs.umd.edu systemd-udevd[437919]: Could not generate persistent MAC address for veth88196e0: No such file or directory
Sep 20 23:42:01 sentry-docker00.cs.umd.edu systemd-udevd[437930]: Could not generate persistent MAC address for veth5f302ce: No such file or directory
Sep 20 23:42:01 sentry-docker00.cs.umd.edu systemd-udevd[437931]: Could not generate persistent MAC address for vetha81bbf1: No such file or directory
Sep 21 00:02:09 sentry-docker00.cs.umd.edu systemd-udevd[447337]: Could not generate persistent MAC address for veth2511f31: No such file or directory
Sep 21 00:02:09 sentry-docker00.cs.umd.edu systemd-udevd[447338]: Could not generate persistent MAC address for veth794c511: No such file or directory
Sep 21 00:02:09 sentry-docker00.cs.umd.edu systemd-udevd[447341]: Could not generate persistent MAC address for veth9ca3162: No such file or directory
Sep 21 00:02:09 sentry-docker00.cs.umd.edu systemd-udevd[447342]: Could not generate persistent MAC address for vethf593b51: No such file or directory
Sep 21 00:02:09 sentry-docker00.cs.umd.edu systemd-udevd[447366]: Could not generate persistent MAC address for veth4a23615: No such file or directory
Sep 21 00:02:09 sentry-docker00.cs.umd.edu systemd-udevd[447365]: Could not generate persistent MAC address for vethe34f5bd: No such file or directory
Sep 21 00:02:09 sentry-docker00.cs.umd.edu systemd-udevd[447384]: Could not generate persistent MAC address for veth16874e8: No such file or directory
Sep 21 00:02:09 sentry-docker00.cs.umd.edu systemd-udevd[447369]: Could not generate persistent MAC address for veth36ffb5f: No such file or directory
... 2 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 20 23:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 20 23:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 20 23:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 20 23:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 20 23:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 20 23:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 20 23:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 1 total) ==
Sep 20 23:13:07 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 20 23:22:50 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f3 (1 distinct, 2 total) ==
Sep 20 23:05:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f4 (1 distinct, 2 total) ==
Sep 20 23:25:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== wraith (1 distinct, 1 total) ==
Sep 21 00:00:00 wraith (nin-node)[826982]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0512s
Status : exited 0
Output :
Syslog digest — 2026-09-20 23:05 EDT
Processed 2,088 lines, filtered 1,530 (73%). 558 unknown (193 distinct) from 22 host(s).
== atif01.cs.umd.edu (2 distinct, 2 total) ==
Sep 20 22:13:29 atif01.cs.umd.edu kernel: net_ratelimit: 6 callbacks suppressed
Sep 20 22:40:29 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)!
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 20 22:53:00 b0b02.cs.umd.edu rustdesk[3412508]: cannot open display:
== bale (5 distinct, 88 total) ==
Sep 20 22:05:31 bale setroubleshoot[1293442]: failed to retrieve rpm info for /dev/nvme0 [x38]
Sep 20 22:05:31 bale setroubleshoot[1293442]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12]
Sep 20 22:05:34 bale setroubleshoot[1293442]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12]
Sep 20 22:05:37 bale setroubleshoot[1293442]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12]
Sep 20 22:05:49 bale setroubleshoot[1294080]: 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 (2 distinct, 2 total) ==
Sep 20 22:51:29 biggulp.cs.umd.edu sshd-session[2916301]: pam_access(sshd:auth): access denied for user `operator' from `193.187.110.214'
Sep 20 22:51:31 biggulp.cs.umd.edu sshd-session[2916295]: error: PAM: Authentication failure for operator from 193.187.110.214
== cmsc436-0101-redis (3 distinct, 3 total) ==
Sep 20 22:10:08 cmsc436-0101-redis sshd-session[3357493]: error: PAM: Authentication failure for root from 193.187.110.214
Sep 20 22:34:15 cmsc436-0101-redis krb5_child[3358346]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 20 22:34:17 cmsc436-0101-redis sshd-session[3358342]: error: PAM: Authentication failure for admin from 34.156.126.241
== csfw00a (2 distinct, 140 total) ==
Sep 20 22:03:49 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x138]
Sep 20 22:54:21 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x2]
== idm00 (1 distinct, 1 total) ==
Sep 20 22:54:01 idm00 named[4166701]: client @0x7f11986ceb28 10.73.240.42#53770: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 20 22:37:56 idmp0 named[1598691]: client @0x7f2d3002f808 10.73.240.43#49191: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 20 22:08:07 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3]
== munin (2 distinct, 28 total) ==
Sep 20 22:43:33 munin sudo[1019808]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x14]
Sep 20 22:43:33 munin sudo[1019808]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x14]
== newhonors.cs.umd.edu (1 distinct, 1 total) ==
Sep 20 22:59: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 20 22:13:03 newhonors2 dhcpcd[2922976]: dhcpcd is not running [x24]
== ntop00 (99 distinct, 143 total) ==
Sep 20 22:05:28 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 6458/6458, ET: 27) ***
Sep 20 22:05:28 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 56/56, ET: 27) ***
Sep 20 22:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 347) ***
Sep 20 22:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 5966/5966, ET: 0) ***
Sep 20 22:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 347) ***
Sep 20 22:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 61/61, ET: 0) ***
Sep 20 22:08:02 ntop00 setroubleshoot[905324]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x12]
Sep 20 22:08:02 ntop00 setroubleshoot[905324]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x12]
Sep 20 22:08:02 ntop00 setroubleshoot[905324]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 20 22:08:02 ntop00 setroubleshoot[905324]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x12]
Sep 20 22:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) ***
Sep 20 22:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) ***
Sep 20 22:10:25 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 5864/5864, ET: 24) ***
Sep 20 22:10:26 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 60/60, ET: 25) ***
Sep 20 22:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 349) ***
Sep 20 22:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 6461/6461, ET: 0) ***
Sep 20 22:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 349) ***
Sep 20 22:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 69/69, ET: 0) ***
Sep 20 22:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) ***
Sep 20 22:15:02 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) ***
Sep 20 22:15:28 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 6625/6625, ET: 27) ***
Sep 20 22:15:28 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 68/68, ET: 26) ***
Sep 20 22:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 351) ***
Sep 20 22:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 6410/6410, ET: 0) ***
Sep 20 22:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 351) ***
Sep 20 22:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 84/84, ET: 0) ***
Sep 20 22:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) ***
Sep 20 22:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) ***
Sep 20 22:20:27 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 6172/6172, ET: 26) ***
Sep 20 22:20:27 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 77/77, ET: 26) ***
... 69 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 20 22:09:09 outbound00.cs.umd.edu python3[2173321]: ldapdb [x6]
== outbound01.cs.umd.edu (3 distinct, 8 total) ==
Sep 20 22:13:07 outbound01.cs.umd.edu python3[239672]: ldapdb [x6]
Sep 20 22:13:30 outbound01.cs.umd.edu krb5_child[239844]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 20 22:20:30 outbound01.cs.umd.edu sshd-session[240980]: error: Protocol major versions differ: 2 vs. 1
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[399967]: link_config: could not get ethtool features for vethce0bb98
Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[399967]: Could not set offload features of vethce0bb98: No such device
Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400002]: Could not generate persistent MAC address for veth85f034d: No such file or directory
Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400003]: Could not generate persistent MAC address for vethb3a3e11: No such file or directory
Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400006]: Could not generate persistent MAC address for vethbe17271: No such file or directory
Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400007]: Could not generate persistent MAC address for veth11b2042: No such file or directory
Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400011]: Could not generate persistent MAC address for vetha2e2eb4: No such file or directory
Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400019]: Could not generate persistent MAC address for veth8ba3604: No such file or directory
Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400019]: Could not generate persistent MAC address for veth224563b: No such file or directory
Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400011]: Could not generate persistent MAC address for veth310e414: No such file or directory
Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400014]: Could not generate persistent MAC address for veth2381731: No such file or directory
Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400013]: Could not generate persistent MAC address for veth1d9d829: No such file or directory
Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409464]: Could not generate persistent MAC address for vetha18ac36: No such file or directory
Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409465]: Could not generate persistent MAC address for veth605402f: No such file or directory
Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409468]: Could not generate persistent MAC address for veth41eb912: No such file or directory
Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409469]: Could not generate persistent MAC address for vethe149c0f: No such file or directory
Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409484]: Could not generate persistent MAC address for veth7e5c7dc: No such file or directory
Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409471]: Could not generate persistent MAC address for veth2e54722: No such file or directory
Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409494]: Could not generate persistent MAC address for veth763e633: No such file or directory
Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409495]: Could not generate persistent MAC address for veth52b4004: No such file or directory
Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409511]: Could not generate persistent MAC address for vethd997755: No such file or directory
Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409517]: Could not generate persistent MAC address for veth44f7944: No such file or directory
Sep 20 23:01:43 sentry-docker00.cs.umd.edu systemd-udevd[418861]: link_config: could not get ethtool features for veth763e633
Sep 20 23:01:43 sentry-docker00.cs.umd.edu systemd-udevd[418861]: Could not set offload features of veth763e633: No such device
Sep 20 23:01:44 sentry-docker00.cs.umd.edu systemd-udevd[418895]: Could not generate persistent MAC address for vethf86a822: No such file or directory
Sep 20 23:01:44 sentry-docker00.cs.umd.edu systemd-udevd[418896]: Could not generate persistent MAC address for veth73dff1a: No such file or directory
Sep 20 23:01:44 sentry-docker00.cs.umd.edu systemd-udevd[418899]: Could not generate persistent MAC address for veth902b1c2: No such file or directory
Sep 20 23:01:44 sentry-docker00.cs.umd.edu systemd-udevd[418900]: Could not generate persistent MAC address for veth4879303: No such file or directory
Sep 20 23:01:44 sentry-docker00.cs.umd.edu systemd-udevd[418923]: Could not generate persistent MAC address for veth76b01be: No such file or directory
Sep 20 23:01:44 sentry-docker00.cs.umd.edu systemd-udevd[418924]: Could not generate persistent MAC address for vethad4f364: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 20 22:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 20 22:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 20 22:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 20 22:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 20 22:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 20 22:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 20 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (10 distinct, 14 total) ==
Sep 20 22:10:08 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
Sep 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c
Sep 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36
Sep 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6
Sep 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.h0ESKV/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee
Sep 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.h0ESKV. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d
Sep 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9
Sep 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848
== submit26-b9-f2 (10 distinct, 12 total) ==
Sep 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6
Sep 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a
Sep 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: 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 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.CcGYzx/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: 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 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.CcGYzx. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885
Sep 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af
Sep 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: 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 20 22:15:07 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f3 (1 distinct, 3 total) ==
Sep 20 22:15:04 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== teaching-awards (2 distinct, 2 total) ==
Sep 20 22:23:35 teaching-awards krb5_child[1202557]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 20 22:30:20 teaching-awards sshd-session[1203046]: error: Protocol major versions differ: 2 vs. 1
== vacuum.cs.umd.edu (4 distinct, 4 total) ==
Sep 20 22:12:00 vacuum.cs.umd.edu abrt-hook-ccpp[24837]: Process 20422 (driver) of user 33 killed by SIGABRT - dumping core
Sep 20 22:12:00 vacuum.cs.umd.edu abrt-server[24838]: Package 'amanda-backup_server' isn't signed with proper key
Sep 20 22:12:00 vacuum.cs.umd.edu abrt-server[24838]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-20-22:12:00-20422' exited with 1
Sep 20 22:12:00 vacuum.cs.umd.edu abrt-server[24838]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-20-22:12:00-20422'
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0512s
Status : exited 0
Output :
Syslog digest — 2026-09-20 22:05 EDT
Processed 1,995 lines, filtered 1,450 (72%). 545 unknown (198 distinct) from 21 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 20 21:52:56 b0b02.cs.umd.edu rustdesk[3397319]: cannot open display:
== bale (5 distinct, 90 total) ==
Sep 20 21:05:53 bale setroubleshoot[1280569]: failed to retrieve rpm info for /dev/nvme0 [x39]
Sep 20 21:05:53 bale setroubleshoot[1280569]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12]
Sep 20 21:05:56 bale setroubleshoot[1280569]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12]
Sep 20 21:05:59 bale setroubleshoot[1280569]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12]
Sep 20 21:06:11 bale setroubleshoot[1281185]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x15]
== cheezit.cs.umd.edu (6 distinct, 6 total) ==
Sep 20 21:46:07 cheezit.cs.umd.edu sshd-session[1367147]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 20 21:46:07 cheezit.cs.umd.edu sshd-session[1367147]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 20 21:46:09 cheezit.cs.umd.edu sshd-session[1367147]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 20 21:46:09 cheezit.cs.umd.edu sshd-session[1367147]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 20 21:46:11 cheezit.cs.umd.edu sshd-session[1367147]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 20 21:46:11 cheezit.cs.umd.edu sshd-session[1367147]: error: kex_protocol_error: type 30 seq 7 [preauth]
== csfw00a (1 distinct, 140 total) ==
Sep 20 21:04:49 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x140]
== idm00 (1 distinct, 1 total) ==
Sep 20 21:54:00 idm00 named[4166701]: client @0x7f11a0062908 10.73.240.42#49275: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 20 21:37:56 idmp0 named[1598691]: client @0x7f2d3802f8f8 10.73.240.43#54734: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 1 total) ==
Sep 20 21:34:52 inbound00.cs.umd.edu krb5_child[2298408]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 2 total) ==
Sep 20 21:38:16 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2]
== krispykreme.cs.umd.edu (9 distinct, 9 total) ==
Sep 20 21:18:12 krispykreme.cs.umd.edu sshd-session[452223]: pam_access(sshd:auth): access denied for user `admin' from `193.187.110.214'
Sep 20 21:18:12 krispykreme.cs.umd.edu krb5_child[452225]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 20 21:18:12 krispykreme.cs.umd.edu sshd-session[452221]: error: PAM: System error for admin from 193.187.110.214
Sep 20 21:58:20 krispykreme.cs.umd.edu sshd-session[464903]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 20 21:58:20 krispykreme.cs.umd.edu sshd-session[464903]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 20 21:58:21 krispykreme.cs.umd.edu sshd-session[464903]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 20 21:58:21 krispykreme.cs.umd.edu sshd-session[464903]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 20 21:58:23 krispykreme.cs.umd.edu sshd-session[464903]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 20 21:58:23 krispykreme.cs.umd.edu sshd-session[464903]: error: kex_protocol_error: type 30 seq 7 [preauth]
== matrix (2 distinct, 3 total) ==
Sep 20 21:25:39 matrix krb5_child[3498994]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 20 21:25:41 matrix sshd[3498969]: error: PAM: Authentication failure for admin from 193.187.110.214
== munin (2 distinct, 8 total) ==
Sep 20 21:33:20 munin sudo[993998]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 20 21:33:20 munin sudo[993998]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== newhonors2 (1 distinct, 24 total) ==
Sep 20 21:13:02 newhonors2 dhcpcd[2921039]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 140 total) ==
Sep 20 21:05:31 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 7176/7176, ET: 30) ***
Sep 20 21:05:31 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 88/88, ET: 30) ***
Sep 20 21:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 323) ***
Sep 20 21:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 7322/7322, ET: 0) ***
Sep 20 21:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 323) ***
Sep 20 21:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 52/52, ET: 0) ***
Sep 20 21:08:02 ntop00 setroubleshoot[897288]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x11]
Sep 20 21:08:02 ntop00 setroubleshoot[897288]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x11]
Sep 20 21:08:02 ntop00 setroubleshoot[897288]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11]
Sep 20 21:08:02 ntop00 setroubleshoot[897288]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x11]
Sep 20 21:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) ***
Sep 20 21:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) ***
Sep 20 21:10:29 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 7033/7033, ET: 28) ***
Sep 20 21:10:30 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 50/50, ET: 29) ***
Sep 20 21:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 325) ***
Sep 20 21:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 6743/6743, ET: 0) ***
Sep 20 21:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 325) ***
Sep 20 21:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 42/42, ET: 0) ***
Sep 20 21:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) ***
Sep 20 21:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) ***
Sep 20 21:15:30 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 6711/6711, ET: 29) ***
Sep 20 21:15:30 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 49/49, ET: 29) ***
Sep 20 21:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 327) ***
Sep 20 21:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 7282/7282, ET: 0) ***
Sep 20 21:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 327) ***
Sep 20 21:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 56/56, ET: 0) ***
Sep 20 21:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) ***
Sep 20 21:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) ***
Sep 20 21:20:37 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 328, QN: 7369/7369, ET: 36) ***
Sep 20 21:20:38 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 328, QN: 56/56, ET: 37) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 20 21:09:09 outbound00.cs.umd.edu python3[2159290]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 20 21:13:06 outbound01.cs.umd.edu python3[225448]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371254]: link_config: could not get ethtool features for vethdae63ea
Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371254]: Could not set offload features of vethdae63ea: No such device
Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371283]: Could not generate persistent MAC address for vethe3db1ab: No such file or directory
Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371284]: Could not generate persistent MAC address for veth764c61a: No such file or directory
Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371287]: Could not generate persistent MAC address for veth8fa5827: No such file or directory
Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371288]: Could not generate persistent MAC address for veth1341e5d: No such file or directory
Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371288]: Could not generate persistent MAC address for veth0b14eb0: No such file or directory
Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371300]: Could not generate persistent MAC address for veth39e0e50: No such file or directory
Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371283]: Could not generate persistent MAC address for vethbc14b63: No such file or directory
Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371303]: Could not generate persistent MAC address for veth2719d2b: No such file or directory
Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371377]: Could not generate persistent MAC address for vethd0f618e: No such file or directory
Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371378]: Could not generate persistent MAC address for vethed3ac50: No such file or directory
Sep 20 21:41:10 sentry-docker00.cs.umd.edu systemd-udevd[380895]: link_config: could not get ethtool features for vethbc14b63
Sep 20 21:41:10 sentry-docker00.cs.umd.edu systemd-udevd[380895]: Could not set offload features of vethbc14b63: No such device
Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380929]: Could not generate persistent MAC address for vethcd5c892: No such file or directory
Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380930]: Could not generate persistent MAC address for vethbc08448: No such file or directory
Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380933]: Could not generate persistent MAC address for veth4bd5303: No such file or directory
Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380935]: Could not generate persistent MAC address for veth44c9cbe: No such file or directory
Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380944]: Could not generate persistent MAC address for veth95cf018: No such file or directory
Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380940]: Could not generate persistent MAC address for veth180ebcd: No such file or directory
Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380946]: Could not generate persistent MAC address for veth9827b60: No such file or directory
Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380945]: Could not generate persistent MAC address for veth83b4502: No such file or directory
Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380955]: Could not generate persistent MAC address for veth2200e39: No such file or directory
Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380937]: Could not generate persistent MAC address for veth89d4c33: No such file or directory
Sep 20 22:01:19 sentry-docker00.cs.umd.edu systemd-udevd[390519]: link_config: could not get ethtool features for veth9827b60
Sep 20 22:01:19 sentry-docker00.cs.umd.edu systemd-udevd[390519]: Could not set offload features of veth9827b60: No such device
Sep 20 22:01:19 sentry-docker00.cs.umd.edu systemd-udevd[390544]: Could not generate persistent MAC address for vethd17332f: No such file or directory
Sep 20 22:01:19 sentry-docker00.cs.umd.edu systemd-udevd[390545]: Could not generate persistent MAC address for veth6c0b4d0: No such file or directory
Sep 20 22:01:19 sentry-docker00.cs.umd.edu systemd-udevd[390548]: Could not generate persistent MAC address for veth6316cfc: No such file or directory
Sep 20 22:01:19 sentry-docker00.cs.umd.edu systemd-udevd[390549]: Could not generate persistent MAC address for vethff53c67: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 20 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 20 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 20 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 20 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 20 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 20 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 20 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 1 total) ==
Sep 20 21:54:35 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f2 (1 distinct, 3 total) ==
Sep 20 21:08:08 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f3 (10 distinct, 15 total) ==
Sep 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b [x2]
Sep 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859 [x2]
Sep 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: 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 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.yphl3N/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: 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 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.yphl3N. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407
Sep 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65
Sep 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: 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 20 21:12:26 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f4 (10 distinct, 14 total) ==
Sep 20 21:15:06 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
Sep 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb
Sep 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4
Sep 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d
Sep 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.csCqFH/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e
Sep 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.csCqFH. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d
Sep 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74
Sep 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0519s
Status : exited 0
Output :
Syslog digest — 2026-09-20 21:05 EDT
Processed 2,019 lines, filtered 1,470 (72%). 549 unknown (175 distinct) from 19 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 20 20:52:52 b0b02.cs.umd.edu rustdesk[3382164]: cannot open display:
== bale (5 distinct, 84 total) ==
Sep 20 20:05:57 bale setroubleshoot[1267865]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 20 20:05:57 bale setroubleshoot[1267865]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12]
Sep 20 20:06:00 bale setroubleshoot[1267865]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12]
Sep 20 20:06:03 bale setroubleshoot[1267865]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12]
Sep 20 20:06:15 bale setroubleshoot[1268479]: 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]
== cheezit.cs.umd.edu (2 distinct, 2 total) ==
Sep 20 20:18:54 cheezit.cs.umd.edu sshd-session[1345854]: pam_access(sshd:auth): access denied for user `lin' from `74.96.151.253'
Sep 20 21:02:47 cheezit.cs.umd.edu sshd-session[1356825]: pam_access(sshd:auth): access denied for user `asriniv1' from `108.40.120.8'
== csfw00a (1 distinct, 149 total) ==
Sep 20 20:04:04 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x149]
== idm00 (1 distinct, 1 total) ==
Sep 20 20:54:00 idm00 named[4166701]: client @0x7f11a4059f88 10.73.240.42#62494: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 20 20:37:56 idmp0 named[1598691]: client @0x7f2d28029f68 10.73.240.43#58975: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 2 total) ==
Sep 20 20:43:35 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2]
== munin (2 distinct, 32 total) ==
Sep 20 20:13:45 munin sudo[964348]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x16]
Sep 20 20:13:45 munin sudo[964348]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x16]
== newhonors2 (1 distinct, 24 total) ==
Sep 20 20:13:03 newhonors2 dhcpcd[2919213]: dhcpcd is not running [x24]
== ntop00 (102 distinct, 146 total) ==
Sep 20 20:05:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 298) ***
Sep 20 20:05:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 298) ***
Sep 20 20:05:24 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 5717/5717, ET: 23) ***
Sep 20 20:05:24 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 57/57, ET: 23) ***
Sep 20 20:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 299) ***
Sep 20 20:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 5775/5775, ET: 0) ***
Sep 20 20:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 299) ***
Sep 20 20:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 54/54, ET: 0) ***
Sep 20 20:08:02 ntop00 setroubleshoot[889408]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x12]
Sep 20 20:08:02 ntop00 setroubleshoot[889408]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x12]
Sep 20 20:08:02 ntop00 setroubleshoot[889408]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 20 20:08:02 ntop00 setroubleshoot[889408]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x12]
Sep 20 20:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) ***
Sep 20 20:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) ***
Sep 20 20:10:25 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 6000/6000, ET: 24) ***
Sep 20 20:10:25 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 58/58, ET: 24) ***
Sep 20 20:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 301) ***
Sep 20 20:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 5891/5891, ET: 0) ***
Sep 20 20:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 301) ***
Sep 20 20:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 69/69, ET: 0) ***
Sep 20 20:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) ***
Sep 20 20:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) ***
Sep 20 20:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 62/62, ET: 0) ***
Sep 20 20:15:24 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 5744/5744, ET: 23) ***
Sep 20 20:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 303) ***
Sep 20 20:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 5696/5696, ET: 0) ***
Sep 20 20:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 303) ***
Sep 20 20:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 58/58, ET: 0) ***
Sep 20 20:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) ***
Sep 20 20:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) ***
... 72 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 20 20:09:09 outbound00.cs.umd.edu python3[2145387]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 20 20:13:06 outbound01.cs.umd.edu python3[211448]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343376]: link_config: could not get ethtool features for veth6879fff
Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343376]: Could not set offload features of veth6879fff: No such device
Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343410]: Could not generate persistent MAC address for vethae3a394: No such file or directory
Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343411]: Could not generate persistent MAC address for veth8a087b1: No such file or directory
Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343414]: Could not generate persistent MAC address for vethc832288: No such file or directory
Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343431]: Could not generate persistent MAC address for veth3fbccc5: No such file or directory
Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343436]: Could not generate persistent MAC address for veth1b26cb4: No such file or directory
Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343433]: Could not generate persistent MAC address for veth327eb02: No such file or directory
Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343427]: Could not generate persistent MAC address for veth1c84c4e: No such file or directory
Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343425]: Could not generate persistent MAC address for vethf08f76d: No such file or directory
Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343427]: Could not generate persistent MAC address for vethe26db3e: No such file or directory
Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343431]: Could not generate persistent MAC address for veth74fde09: No such file or directory
Sep 20 20:40:45 sentry-docker00.cs.umd.edu systemd-udevd[352732]: link_config: could not get ethtool features for vethc832288
Sep 20 20:40:45 sentry-docker00.cs.umd.edu systemd-udevd[352732]: Could not set offload features of vethc832288: No such device
Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352761]: Could not generate persistent MAC address for vethe20f63b: No such file or directory
Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352762]: Could not generate persistent MAC address for veth0d0bf39: No such file or directory
Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352765]: Could not generate persistent MAC address for veth95df242: No such file or directory
Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352766]: Could not generate persistent MAC address for veth94e8c3f: No such file or directory
Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352789]: Could not generate persistent MAC address for vethcbb4577: No such file or directory
Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352790]: Could not generate persistent MAC address for veth8038274: No such file or directory
Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352814]: Could not generate persistent MAC address for veth8ca72c6: No such file or directory
Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352799]: Could not generate persistent MAC address for veth8d944af: No such file or directory
Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352800]: Could not generate persistent MAC address for veth171eac8: No such file or directory
Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352799]: Could not generate persistent MAC address for veth49a6517: No such file or directory
Sep 20 21:00:54 sentry-docker00.cs.umd.edu systemd-udevd[362109]: link_config: could not get ethtool features for vethcbb4577
Sep 20 21:00:54 sentry-docker00.cs.umd.edu systemd-udevd[362109]: Could not set offload features of vethcbb4577: No such device
Sep 20 21:00:54 sentry-docker00.cs.umd.edu systemd-udevd[362142]: Could not generate persistent MAC address for vethf2fb91e: No such file or directory
Sep 20 21:00:54 sentry-docker00.cs.umd.edu systemd-udevd[362143]: Could not generate persistent MAC address for veth3a8c089: No such file or directory
Sep 20 21:00:54 sentry-docker00.cs.umd.edu systemd-udevd[362146]: Could not generate persistent MAC address for veth740b9d8: No such file or directory
Sep 20 21:00:54 sentry-docker00.cs.umd.edu systemd-udevd[362147]: Could not generate persistent MAC address for vetha7f69a5: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 20 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 20 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 20 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 20 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 20 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 20 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 20 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 2 total) ==
Sep 20 20:34:32 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f2 (1 distinct, 4 total) ==
Sep 20 20:08:51 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f3 (1 distinct, 4 total) ==
Sep 20 20:18:05 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f4 (1 distinct, 2 total) ==
Sep 20 20:33:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: 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 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: 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 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8
Sep 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.QimYga/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566
Sep 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.QimYga. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: 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 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c
Sep 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4
1
0