Command: /usr/local/sbin/syslog-digest.py
Time : 0.0552s
Status : exited 0
Output :
Syslog digest — 2026-09-22 07:05 EDT
Processed 2,697 lines, filtered 2,144 (79%). 553 unknown (227 distinct) from 36 host(s).
== ai-course (1 distinct, 1 total) ==
Sep 22 06:28:48 ai-course rsyslogd[1525878]: imjournal: filecreatemode is not set, using default 0644 [v8.2312.0 try https://www.rsyslog.com/e/2186 ]
== amoeba (1 distinct, 1 total) ==
Sep 22 06:39:14 amoeba gnome-software[1458418]: Only 0 apps for recent list, hiding
== atif01.cs.umd.edu (4 distinct, 4 total) ==
Sep 22 06:12:21 atif01.cs.umd.edu kernel: net_ratelimit: 13 callbacks suppressed
Sep 22 06:12:40 atif01.cs.umd.edu kernel: net_ratelimit: 10 callbacks suppressed
Sep 22 06:39:46 atif01.cs.umd.edu kernel: net_ratelimit: 9 callbacks suppressed
Sep 22 06:39:46 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)!
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 06:55:01 b0b02.cs.umd.edu rustdesk[3903188]: cannot open display:
== bale (5 distinct, 86 total) ==
Sep 22 06:05:30 bale setroubleshoot[1732843]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 22 06:05:31 bale setroubleshoot[1732843]: 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 22 06:05:33 bale setroubleshoot[1732843]: 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 22 06:05:36 bale setroubleshoot[1732843]: 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 22 06:05:48 bale setroubleshoot[1733472]: 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, 122 total) ==
Sep 22 06:04:02 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x122]
== galahad.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 06:19:12 galahad.cs.umd.edu gnome-software[2904800]: Only 0 apps for recent list, hiding
== gle-dind00.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 06:24:33 gle-dind00.cs.umd.edu systemd[1]: cgroup compatibility translation between legacy and unified hierarchy settings activated. See cgroup-compat debug messages for details.
== idm00 (1 distinct, 1 total) ==
Sep 22 06:54:04 idm00 named[4166701]: client @0x7f11a002d2d8 10.73.240.42#53321: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 22 06:37:55 idmp0 named[1598691]: client @0x7f2d200347e8 10.73.240.43#65154: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 2 total) ==
Sep 22 06:07:05 inbound00.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway. [x2]
== inbound01.cs.umd.edu (1 distinct, 2 total) ==
Sep 22 06:18:13 inbound01.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway. [x2]
== irb2156 (1 distinct, 1 total) ==
Sep 22 06:37:49 irb2156 systemd[1]: insights-client.service: Start request repeated too quickly.
== itmon02 (1 distinct, 2 total) ==
Sep 22 06:58:59 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2]
== kadath.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 06:14:30 kadath.cs.umd.edu gnome-software[589638]: Only 0 apps for recent list, hiding
== librenms (1 distinct, 1 total) ==
Sep 22 06:48:19 librenms puppet-agent[3094115]: The directory '/opt/librenms/rrd' contains 16517 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
== mcstic (1 distinct, 1 total) ==
Sep 22 06:41:58 mcstic rsyslogd[944412]: imjournal: filecreatemode is not set, using default 0644 [v8.2312.0 try https://www.rsyslog.com/e/2186 ]
== munin (2 distinct, 4 total) ==
Sep 22 06:18:10 munin sudo[1706657]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 22 06:18:10 munin sudo[1706657]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== neo-gizmonic (1 distinct, 1 total) ==
Sep 22 06:06:47 neo-gizmonic rsyslogd[2042193]: imjournal: filecreatemode is not set, using default 0644 [v8.2312.0 try https://www.rsyslog.com/e/2186 ]
== neoavion (1 distinct, 1 total) ==
Sep 22 06:32:35 neoavion krb5_child[4092468]: No credentials cache found
== neodontcare.cs.umd.edu (4 distinct, 4 total) ==
Sep 22 06:14:49 neodontcare.cs.umd.edu gnome-software[10171]: Only 0 apps for recent list, hiding
Sep 22 06:14:58 neodontcare.cs.umd.edu packagekitd[1504324]: Failed to get cache filename for gnu-free-mono-fonts
Sep 22 06:14:58 neodontcare.cs.umd.edu packagekitd[1504324]: Failed to get cache filename for gnu-free-serif-fonts
Sep 22 06:15:01 neodontcare.cs.umd.edu packagekitd[1504324]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release
== netman.cs.umd.edu (1 distinct, 2 total) ==
Sep 22 06:09:56 netman.cs.umd.edu krb5_child[3485926]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
== newhonors2 (2 distinct, 25 total) ==
Sep 22 06:13:03 newhonors2 dhcpcd[2983341]: dhcpcd is not running [x24]
Sep 22 06:41:09 newhonors2 rsyslogd[2984908]: imjournal: filecreatemode is not set, using default 0644 [v8.2312.0 try https://www.rsyslog.com/e/2186 ]
== ntop00 (101 distinct, 145 total) ==
Sep 22 06:05:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 538) ***
Sep 22 06:05:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 538) ***
Sep 22 06:05:21 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 538, QN: 3848/3848, ET: 20) ***
Sep 22 06:05:21 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 538, QN: 72/72, ET: 20) ***
Sep 22 06:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 539) ***
Sep 22 06:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 539, QN: 3844/3844, ET: 0) ***
Sep 22 06:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 539) ***
Sep 22 06:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 539, QN: 66/66, ET: 0) ***
Sep 22 06:08:02 ntop00 setroubleshoot[1159969]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12]
Sep 22 06:08:02 ntop00 setroubleshoot[1159969]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12]
Sep 22 06:08:02 ntop00 setroubleshoot[1159969]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 22 06:08:03 ntop00 setroubleshoot[1159969]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12]
Sep 22 06:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 540) ***
Sep 22 06:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 540) ***
Sep 22 06:10:21 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 540, QN: 3862/3862, ET: 20) ***
Sep 22 06:10:21 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 540, QN: 70/70, ET: 20) ***
Sep 22 06:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 541) ***
Sep 22 06:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 541, QN: 3744/3744, ET: 0) ***
Sep 22 06:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 541) ***
Sep 22 06:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 541, QN: 62/62, ET: 0) ***
Sep 22 06:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 542) ***
Sep 22 06:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 542) ***
Sep 22 06:15:20 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 542, QN: 3692/3692, ET: 19) ***
Sep 22 06:15:20 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 542, QN: 57/57, ET: 19) ***
Sep 22 06:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 543) ***
Sep 22 06:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 543, QN: 3905/3905, ET: 0) ***
Sep 22 06:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 543) ***
Sep 22 06:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 543, QN: 55/55, ET: 0) ***
Sep 22 06:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 544) ***
Sep 22 06:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 544) ***
... 71 more distinct messages not shown
== orchids (5 distinct, 6 total) ==
Sep 22 06:11:31 orchids gnome-software[1516991]: Only 0 apps for recent list, hiding
Sep 22 06:11:39 orchids packagekitd[2337445]: Failed to get cache filename for libreoffice
Sep 22 06:11:39 orchids packagekitd[2337445]: Failed to get cache filename for cups-filesystem
Sep 22 06:11:39 orchids packagekitd[2337445]: Failed to get cache filename for kernel
Sep 22 06:11:41 orchids packagekitd[2337445]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release [x2]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 22 06:09:09 outbound00.cs.umd.edu python3[2627579]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 22 06:13:06 outbound01.cs.umd.edu python3[723049]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 22 06:14:37 sentry-docker00.cs.umd.edu systemd-udevd[1301713]: link_config: could not get ethtool features for vethdf68c03
Sep 22 06:14:37 sentry-docker00.cs.umd.edu systemd-udevd[1301713]: Could not set offload features of vethdf68c03: No such device
Sep 22 06:14:37 sentry-docker00.cs.umd.edu systemd-udevd[1301772]: Could not generate persistent MAC address for veth91fe92b: No such file or directory
Sep 22 06:14:37 sentry-docker00.cs.umd.edu systemd-udevd[1301773]: Could not generate persistent MAC address for vetha6288cd: No such file or directory
Sep 22 06:14:37 sentry-docker00.cs.umd.edu systemd-udevd[1301773]: Could not generate persistent MAC address for veth9de6e4e: No such file or directory
Sep 22 06:14:37 sentry-docker00.cs.umd.edu systemd-udevd[1301772]: Could not generate persistent MAC address for veth2269571: No such file or directory
Sep 22 06:14:37 sentry-docker00.cs.umd.edu systemd-udevd[1301782]: Could not generate persistent MAC address for veth1d3dcf3: No such file or directory
Sep 22 06:14:37 sentry-docker00.cs.umd.edu systemd-udevd[1301777]: Could not generate persistent MAC address for veth878149b: No such file or directory
Sep 22 06:14:37 sentry-docker00.cs.umd.edu systemd-udevd[1301772]: Could not generate persistent MAC address for veth5afd165: No such file or directory
Sep 22 06:14:37 sentry-docker00.cs.umd.edu systemd-udevd[1301773]: Could not generate persistent MAC address for veth21d51b1: No such file or directory
Sep 22 06:14:37 sentry-docker00.cs.umd.edu systemd-udevd[1301870]: Could not generate persistent MAC address for veth5d52787: No such file or directory
Sep 22 06:14:37 sentry-docker00.cs.umd.edu systemd-udevd[1301874]: Could not generate persistent MAC address for vethc366022: No such file or directory
Sep 22 06:34:45 sentry-docker00.cs.umd.edu systemd-udevd[1311108]: link_config: could not get ethtool features for veth2269571
Sep 22 06:34:45 sentry-docker00.cs.umd.edu systemd-udevd[1311108]: Could not set offload features of veth2269571: No such device
Sep 22 06:34:46 sentry-docker00.cs.umd.edu systemd-udevd[1311181]: Could not generate persistent MAC address for veth87ccf20: No such file or directory
Sep 22 06:34:46 sentry-docker00.cs.umd.edu systemd-udevd[1311182]: Could not generate persistent MAC address for veth66e5946: No such file or directory
Sep 22 06:34:46 sentry-docker00.cs.umd.edu systemd-udevd[1311185]: Could not generate persistent MAC address for vethb9c780c: No such file or directory
Sep 22 06:34:46 sentry-docker00.cs.umd.edu systemd-udevd[1311186]: Could not generate persistent MAC address for veth332b995: No such file or directory
Sep 22 06:34:46 sentry-docker00.cs.umd.edu systemd-udevd[1311209]: Could not generate persistent MAC address for veth3de7470: No such file or directory
Sep 22 06:34:46 sentry-docker00.cs.umd.edu systemd-udevd[1311210]: Could not generate persistent MAC address for veth7fe9328: No such file or directory
Sep 22 06:34:46 sentry-docker00.cs.umd.edu systemd-udevd[1311213]: Could not generate persistent MAC address for vethccfa693: No such file or directory
Sep 22 06:34:46 sentry-docker00.cs.umd.edu systemd-udevd[1311227]: Could not generate persistent MAC address for vetha0a27af: No such file or directory
Sep 22 06:34:46 sentry-docker00.cs.umd.edu systemd-udevd[1311215]: Could not generate persistent MAC address for vethcdb65ae: No such file or directory
Sep 22 06:34:46 sentry-docker00.cs.umd.edu systemd-udevd[1311225]: Could not generate persistent MAC address for veth6e19f97: No such file or directory
Sep 22 06:54:54 sentry-docker00.cs.umd.edu systemd-udevd[1320513]: link_config: could not get ethtool features for vethb9c780c
Sep 22 06:54:54 sentry-docker00.cs.umd.edu systemd-udevd[1320513]: Could not set offload features of vethb9c780c: No such device
Sep 22 06:54:54 sentry-docker00.cs.umd.edu systemd-udevd[1320548]: Could not generate persistent MAC address for vethb928b03: No such file or directory
Sep 22 06:54:54 sentry-docker00.cs.umd.edu systemd-udevd[1320549]: Could not generate persistent MAC address for vethb136b48: No such file or directory
Sep 22 06:54:54 sentry-docker00.cs.umd.edu systemd-udevd[1320552]: Could not generate persistent MAC address for vethf89d1ed: No such file or directory
Sep 22 06:54:54 sentry-docker00.cs.umd.edu systemd-udevd[1320553]: Could not generate persistent MAC address for veth496ecb4: No such file or directory
... 6 more distinct messages not shown
== strawberry (9 distinct, 46 total) ==
Sep 22 06:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x7]
Sep 22 06:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x7]
Sep 22 06:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x7]
Sep 22 06:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x7]
Sep 22 06:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x7]
Sep 22 06:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x7]
Sep 22 06:31:04 strawberry nologin[3335921]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 22 06:31:04 strawberry pipewire[3335920]: 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 22 06:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (9 distinct, 9 total) ==
Sep 22 06:25:54 submit26-b9-f1 setroubleshoot[2876088]: 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 22 06:25:54 submit26-b9-f1 setroubleshoot[2876088]: 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 22 06:25:54 submit26-b9-f1 setroubleshoot[2876088]: 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 22 06:25:54 submit26-b9-f1 setroubleshoot[2876088]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Zf5gEj/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 22 06:25:54 submit26-b9-f1 setroubleshoot[2876088]: 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 22 06:25:55 submit26-b9-f1 setroubleshoot[2876088]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Zf5gEj. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 22 06:25:55 submit26-b9-f1 setroubleshoot[2876088]: 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 22 06:25:55 submit26-b9-f1 setroubleshoot[2876088]: 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 22 06:25:55 submit26-b9-f1 setroubleshoot[2876088]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848
== submit26-b9-f2 (11 distinct, 13 total) ==
Sep 22 06:06:50 submit26-b9-f2 setroubleshoot[1981505]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 [x2]
Sep 22 06:06:50 submit26-b9-f2 setroubleshoot[1981505]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a [x2]
Sep 22 06:06:50 submit26-b9-f2 setroubleshoot[1981505]: 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 22 06:06:50 submit26-b9-f2 setroubleshoot[1981505]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.QpwNDv/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 22 06:06:50 submit26-b9-f2 setroubleshoot[1981505]: 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 22 06:06:50 submit26-b9-f2 setroubleshoot[1981505]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.QpwNDv. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 22 06:06:50 submit26-b9-f2 setroubleshoot[1981505]: 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 22 06:06:50 submit26-b9-f2 setroubleshoot[1981505]: 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 22 06:06:50 submit26-b9-f2 setroubleshoot[1981505]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repodata. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885
Sep 22 06:06:50 submit26-b9-f2 setroubleshoot[1981505]: 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 22 06:06:50 submit26-b9-f2 setroubleshoot[1981505]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.2exWtB. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
== submit26-b9-f3 (1 distinct, 2 total) ==
Sep 22 06:51:13 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 22 06:56:07 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== tlsrpt (1 distinct, 1 total) ==
Sep 22 06:38:03 tlsrpt (httpd)[3026060]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== wraith (1 distinct, 1 total) ==
Sep 22 06:55:08 wraith rsyslogd[910684]: imjournal: filecreatemode is not set, using default 0644 [v8.2312.0 try https://www.rsyslog.com/e/2186 ]
== zwicker-computer (15 distinct, 15 total) ==
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/a98.icc.dpkg-new: No such file or directory
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/default_rgb.icc.dpkg-new: No such file or directory
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/default_gray.icc.dpkg-new: No such file or directory
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/esrgb.icc.dpkg-new: No such file or directory
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/gray_to_k.icc.dpkg-new: No such file or directory
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/default_cmyk.icc.dpkg-new: No such file or directory
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/ps_cmyk.icc.dpkg-new: No such file or directory
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/ps_rgb.icc.dpkg-new: No such file or directory
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/lab.icc.dpkg-new: No such file or directory
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/ps_gray.icc.dpkg-new: No such file or directory
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/scrgb.icc.dpkg-new: No such file or directory
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/rommrgb.icc.dpkg-new: No such file or directory
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/srgb.icc.dpkg-new: No such file or directory
Sep 22 06:24:36 zwicker-computer colord[2661]: failed to search file: failed to load file: Error opening file /usr/share/color/icc/ghostscript/sgray.icc.dpkg-new: No such file or directory
Sep 22 06:24:50 zwicker-computer rsyslogd[3155870]: imjournal: filecreatemode is not set, using default 0644 [v8.2312.0 try https://www.rsyslog.com/e/2186 ]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0526s
Status : exited 0
Output :
Syslog digest — 2026-09-22 06:05 EDT
Processed 2,604 lines, filtered 2,088 (80%). 516 unknown (186 distinct) from 23 host(s).
== atif01.cs.umd.edu (2 distinct, 2 total) ==
Sep 22 05:13:29 atif01.cs.umd.edu kernel: net_ratelimit: 9 callbacks suppressed
Sep 22 05:13:29 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)!
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 05:54:57 b0b02.cs.umd.edu rustdesk[3887743]: cannot open display:
== bale (5 distinct, 90 total) ==
Sep 22 05:05:15 bale setroubleshoot[1719940]: failed to retrieve rpm info for /dev/nvme0 [x39]
Sep 22 05:05:15 bale setroubleshoot[1719940]: 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 22 05:05:18 bale setroubleshoot[1719940]: 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 22 05:05:21 bale setroubleshoot[1719940]: 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 22 05:05:33 bale setroubleshoot[1720555]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x14]
== csfw00a (1 distinct, 121 total) ==
Sep 22 05:03:57 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x121]
== gle-dind02.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 05:37:40 gle-dind02.cs.umd.edu systemd[1]: cgroup compatibility translation between legacy and unified hierarchy settings activated. See cgroup-compat debug messages for details.
== grades01.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 05:48:23 grades01.cs.umd.edu puppet-agent[5647]: 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 22 05:54:03 idm00 named[4166701]: client @0x7f119804aea8 10.73.240.42#56650: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 22 05:37:55 idmp0 named[1598691]: client @0x7f2d2402e528 10.73.240.43#58002: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 2 total) ==
Sep 22 05:20:12 inbound00.cs.umd.edu cockpit-ws[2751225]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2]
== inbound01.cs.umd.edu (1 distinct, 3 total) ==
Sep 22 05:20:17 inbound01.cs.umd.edu cockpit-ws[774803]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x3]
== itmon02 (1 distinct, 3 total) ==
Sep 22 05:23:12 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== munin (2 distinct, 6 total) ==
Sep 22 05:08:08 munin sudo[1681959]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x3]
Sep 22 05:08:08 munin sudo[1681959]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x3]
== neodontcare.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 06:04:48 neodontcare.cs.umd.edu packagekitd[1501563]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release
== newhonors2 (1 distinct, 24 total) ==
Sep 22 05:13:02 newhonors2 dhcpcd[2981503]: dhcpcd is not running [x24]
== ntop00 (97 distinct, 141 total) ==
Sep 22 05:05:28 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 5349/5349, ET: 27) ***
Sep 22 05:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 515) ***
Sep 22 05:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 5463/5463, ET: 0) ***
Sep 22 05:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 515) ***
Sep 22 05:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 48/48, ET: 0) ***
Sep 22 05:08:02 ntop00 setroubleshoot[1151933]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12]
Sep 22 05:08:02 ntop00 setroubleshoot[1151933]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12]
Sep 22 05:08:02 ntop00 setroubleshoot[1151933]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 22 05:08:02 ntop00 setroubleshoot[1151933]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12]
Sep 22 05:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) ***
Sep 22 05:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) ***
Sep 22 05:10:28 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 5065/5065, ET: 27) ***
Sep 22 05:10:28 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 48/48, ET: 27) ***
Sep 22 05:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 517) ***
Sep 22 05:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 4806/4806, ET: 0) ***
Sep 22 05:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 517) ***
Sep 22 05:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 55/55, ET: 0) ***
Sep 22 05:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) ***
Sep 22 05:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) ***
Sep 22 05:15:27 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 4845/4845, ET: 26) ***
Sep 22 05:15:27 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 61/61, ET: 26) ***
Sep 22 05:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 519) ***
Sep 22 05:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 4652/4652, ET: 0) ***
Sep 22 05:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 519) ***
Sep 22 05:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 59/59, ET: 0) ***
Sep 22 05:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) ***
Sep 22 05:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) ***
Sep 22 05:20:25 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 4444/4444, ET: 24) ***
Sep 22 05:20:25 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 63/63, ET: 24) ***
Sep 22 05:23:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 521) ***
... 67 more distinct messages not shown
== outbound00.cs.umd.edu (2 distinct, 9 total) ==
Sep 22 05:09:09 outbound00.cs.umd.edu python3[2613212]: ldapdb [x6]
Sep 22 05:17:05 outbound00.cs.umd.edu cockpit-ws[2614794]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x3]
== outbound01.cs.umd.edu (3 distinct, 11 total) ==
Sep 22 05:08:33 outbound01.cs.umd.edu python3[678605]: ldapdb [x7]
Sep 22 05:09:40 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. [x2]
Sep 22 05:46:29 outbound01.cs.umd.edu cockpit-ws[716537]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273106]: link_config: could not get ethtool features for veth092efca
Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273106]: Could not set offload features of veth092efca: No such device
Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273140]: Could not generate persistent MAC address for veth3c53bc3: No such file or directory
Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273141]: Could not generate persistent MAC address for vetha2a5d78: No such file or directory
Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273144]: Could not generate persistent MAC address for veth06ae805: No such file or directory
Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273145]: Could not generate persistent MAC address for vethbfd1bd3: No such file or directory
Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273154]: Could not generate persistent MAC address for veth9004c64: No such file or directory
Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273144]: Could not generate persistent MAC address for veth87eb3c1: No such file or directory
Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273145]: Could not generate persistent MAC address for vethd3e513c: No such file or directory
Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273154]: Could not generate persistent MAC address for vetha8fefcd: No such file or directory
Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273183]: Could not generate persistent MAC address for veth3097d57: No such file or directory
Sep 22 05:14:12 sentry-docker00.cs.umd.edu systemd-udevd[1273192]: Could not generate persistent MAC address for vethd6b0791: No such file or directory
Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282697]: link_config: could not get ethtool features for veth3097d57
Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282697]: Could not set offload features of veth3097d57: No such device
Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282778]: Could not generate persistent MAC address for vetha399796: No such file or directory
Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282779]: Could not generate persistent MAC address for vethb2778ec: No such file or directory
Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282782]: Could not generate persistent MAC address for vetha76752e: No such file or directory
Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282783]: Could not generate persistent MAC address for veth04e8cf3: No such file or directory
Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282798]: Could not generate persistent MAC address for vethc6f3b1f: No such file or directory
Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282788]: Could not generate persistent MAC address for veth3a0c6e1: No such file or directory
Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282809]: Could not generate persistent MAC address for veth2613524: No such file or directory
Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282808]: Could not generate persistent MAC address for veth9b82d81: No such file or directory
Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282834]: Could not generate persistent MAC address for veth61443ac: No such file or directory
Sep 22 05:34:21 sentry-docker00.cs.umd.edu systemd-udevd[1282835]: Could not generate persistent MAC address for vetha49593e: No such file or directory
Sep 22 05:54:29 sentry-docker00.cs.umd.edu systemd-udevd[1292241]: link_config: could not get ethtool features for veth9b82d81
Sep 22 05:54:29 sentry-docker00.cs.umd.edu systemd-udevd[1292241]: Could not set offload features of veth9b82d81: No such device
Sep 22 05:54:29 sentry-docker00.cs.umd.edu systemd-udevd[1292280]: Could not generate persistent MAC address for veth445e0a2: No such file or directory
Sep 22 05:54:29 sentry-docker00.cs.umd.edu systemd-udevd[1292281]: Could not generate persistent MAC address for veth885dc41: No such file or directory
Sep 22 05:54:29 sentry-docker00.cs.umd.edu systemd-udevd[1292284]: Could not generate persistent MAC address for veth8fd5dd1: No such file or directory
Sep 22 05:54:29 sentry-docker00.cs.umd.edu systemd-udevd[1292285]: Could not generate persistent MAC address for vethb21f138: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 22 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 22 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 22 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 22 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 22 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 22 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 22 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 1 total) ==
Sep 22 05:10:05 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f2 (1 distinct, 1 total) ==
Sep 22 05:33:09 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f3 (10 distinct, 13 total) ==
Sep 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Aov9YK/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Aov9YK. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 22 05:06:43 submit26-b9-f3 setroubleshoot[2453409]: 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 22 05:13:07 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f4 (9 distinct, 9 total) ==
Sep 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.msu9Es/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.msu9Es. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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 22 05:24:47 submit26-b9-f4 setroubleshoot[1790919]: 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.0574s
Status : exited 0
Output :
Syslog digest — 2026-09-22 05:05 EDT
Processed 2,393 lines, filtered 1,758 (73%). 635 unknown (264 distinct) from 22 host(s).
== abadi-computer (14 distinct, 15 total) ==
Sep 22 02:29:07 abadi-computer falcon-sensor-bpf[529]: CrowdStrike(4): SSLSocket Disconnected from Cloud. [x2]
Sep 22 02:31:00 abadi-computer systemd[1]: resmon.service: Main process exited, code=killed, status=14/ALRM
Sep 22 02:31:01 abadi-computer systemd-resolved[2907024]: Failed to send hostname reply: Transport endpoint is not connected
Sep 22 02:31:01 abadi-computer systemd[1]: resmon.service: start operation timed out. Terminating.
Sep 22 02:31:01 abadi-computer systemctl[1844552]: Warning: The unit file, source configuration file or drop-ins of cups.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Sep 22 02:31:06 abadi-computer systemd[1]: resmon.service: Supervising process 1844622 which is not our child. We'll most likely not notice when it exits.
Sep 22 02:32:06 abadi-computer falcon-sensor-bpf[529]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 22 02:32:06 abadi-computer falcon-sensor-bpf[529]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
Sep 22 04:45:24 abadi-computer systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT
Sep 22 04:45:24 abadi-computer systemd-journald[1845845]: File /var/log/journal/eb1cc96a36ae4cc69eaaadf3c8558acf/system.journal corrupted or uncleanly shut down, renaming and replacing.
Sep 22 04:45:24 abadi-computer sshd[1824376]: fatal: login_init_entry: Cannot find user "poojan"
Sep 22 04:45:24 abadi-computer nologin[1845334]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 22 04:45:24 abadi-computer systemd[1]: systemd-journald.service: Watchdog timeout (limit 3min)!
Sep 22 04:45:24 abadi-computer pipewire[1845332]: 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
== atif01.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 04:40:10 atif01.cs.umd.edu kernel: net_ratelimit: 9 callbacks suppressed
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 04:54:53 b0b02.cs.umd.edu rustdesk[3872559]: cannot open display:
== bale (5 distinct, 86 total) ==
Sep 22 04:05:45 bale setroubleshoot[1678342]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 22 04:05:46 bale setroubleshoot[1678342]: 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 22 04:05:48 bale setroubleshoot[1678342]: 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 22 04:05:51 bale setroubleshoot[1678342]: 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 22 04:06:03 bale setroubleshoot[1678958]: 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, 130 total) ==
Sep 22 04:03:47 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x130]
== forge00 (1 distinct, 1 total) ==
Sep 22 04:09:02 forge00 (httpd)[649905]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== galax (59 distinct, 61 total) ==
Sep 22 04:21:22 galax puppet-agent[369155]: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install choria=0.29.4+resolute' returned 100: W: --force-yes is deprecated, use one of the options starting with --allow instead.
Sep 22 04:21:22 galax puppet-agent[369155]: E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 50156 (aptd) [x2]
Sep 22 04:21:22 galax puppet-agent[369155]: E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? [x2]
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Choria::Install/Package[choria]/ensure) change from 'absent' to '0.29.4+resolute' failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install choria=0.29.4+resolute' returned 100: W: --force-yes is deprecated, use one of the options starting with --allow instead.
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Choria::Install/Package[choria]/ensure) E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 50156 (aptd)
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Choria::Install/Package[choria]/ensure) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? (corrective)
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Choria::Config/File[/etc/choria]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Choria::Config/File[/etc/choria/policies]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Choria::Config/File[/etc/choria/policies/rego]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Choria::Config/File[/etc/choria/plugin.d]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Choria::Config/File[/etc/choria/overrides.json]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Choria::Config/File[/etc/choria/machine]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Choria::Config/File[/usr/bin/choria_mcollective_agent_compat.rb]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Choria::Config/File[/etc/choria/server.conf]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Mcollective::Config/File[/etc/choria/server.cfg]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Mcollective::Config/File[/etc/choria/client.cfg]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/choria_util.policy]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/rpcutil.policy]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/scout.policy]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/rego/default.rego]) Skipping because of failed dependencies
Sep 22 04:21:22 galax puppet-agent[369155]: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install openvox-agent=8.27.0-1+ubuntu26.04' returned 100: W: --force-yes is deprecated, use one of the options starting with --allow instead.
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Puppet::Agent::Install/Package[openvox-agent]/ensure) change from '8.29.0-1+ubuntu26.04' to '8.27.0-1+ubuntu26.04' failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install openvox-agent=8.27.0-1+ubuntu26.04' returned 100: W: --force-yes is deprecated, use one of the options starting with --allow instead.
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Puppet::Agent::Install/Package[openvox-agent]/ensure) E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 50156 (aptd)
Sep 22 04:21:22 galax puppet-agent[369155]: (/Stage[main]/Puppet::Agent::Install/Package[openvox-agent]/ensure) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? (corrective)
Sep 22 04:21:23 galax puppet-agent[369155]: (/Stage[main]/Choria::Config/Concat[/etc/choria/policies/groups]/Concat_file[/etc/choria/policies/groups]) Skipping because of failed dependencies
Sep 22 04:21:23 galax puppet-agent[369155]: (/Stage[main]/Choria::Config/Concat[/etc/choria/policies/groups]/File[/etc/choria/policies/groups]) Skipping because of failed dependencies
Sep 22 04:21:23 galax puppet-agent[369155]: (/Stage[main]/Mcollective::Config/Mcollective::Config_file[/etc/choria/client.conf]/File[/etc/choria/client.conf]) Skipping because of failed dependencies
Sep 22 04:21:23 galax puppet-agent[369155]: (/Stage[main]/Mcollective::Config/Mcollective::Config_file[/etc/choria/choria-shim.cfg]/File[/etc/choria/choria-shim.cfg]) Skipping because of failed dependencies
Sep 22 04:21:23 galax puppet-agent[369155]: (/Stage[main]/Mcollective::Facts/Exec[mcollective_facts_yaml_refresh]) Skipping because of failed dependencies
Sep 22 04:21:23 galax puppet-agent[369155]: (/Stage[main]/Mcollective_agent_puppet/Mcollective::Module_plugin[mcollective_agent_puppet]/File[/etc/choria/policies/puppet.policy]) Skipping because of failed dependencies
... 29 more distinct messages not shown
== idm00 (1 distinct, 1 total) ==
Sep 22 04:54:03 idm00 named[4166701]: client @0x7f11a403ce28 10.73.240.42#55532: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 22 04:37:55 idmp0 named[1598691]: client @0x7f2d0889dd48 10.73.240.43#53793: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 22 04:13:04 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== matrix (12 distinct, 13 total) ==
Sep 22 04:22:05 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 378068, but reception only permitted for main PID 720
Sep 22 04:22:05 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 378081, but reception only permitted for main PID 720
Sep 22 04:22:13 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 378173, but reception only permitted for main PID 720
Sep 22 04:22:13 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 378179, but reception only permitted for main PID 720
Sep 22 04:22:13 matrix networkctl[378189]: Interface "veth293c106" not found.
Sep 22 04:22:13 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 378189, but reception only permitted for main PID 720
Sep 22 04:22:13 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 378249, but reception only permitted for main PID 720
Sep 22 04:22:13 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 378259, but reception only permitted for main PID 720
Sep 22 04:25:39 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 379828, but reception only permitted for main PID 720
Sep 22 04:25:39 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 379834, but reception only permitted for main PID 720
Sep 22 04:25:39 matrix networkctl[379845]: Interface "veth4988be0" not found.
Sep 22 04:25:39 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 379845, but reception only permitted for main PID 720 [x2]
== munin (2 distinct, 46 total) ==
Sep 22 04:18:55 munin sudo[1662514]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x23]
Sep 22 04:18:55 munin sudo[1662514]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x23]
== newhonors2 (1 distinct, 24 total) ==
Sep 22 04:13:03 newhonors2 dhcpcd[2979640]: dhcpcd is not running [x24]
== ntop00 (102 distinct, 146 total) ==
Sep 22 04:05:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 490) ***
Sep 22 04:05:27 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 490, QN: 5149/5149, ET: 26) ***
Sep 22 04:05:28 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 490, QN: 62/62, ET: 27) ***
Sep 22 04:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 491) ***
Sep 22 04:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 491, QN: 5082/5082, ET: 0) ***
Sep 22 04:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 491) ***
Sep 22 04:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 491, QN: 56/56, ET: 0) ***
Sep 22 04:08:02 ntop00 setroubleshoot[1144004]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12]
Sep 22 04:08:02 ntop00 setroubleshoot[1144004]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12]
Sep 22 04:08:02 ntop00 setroubleshoot[1144004]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 22 04:08:02 ntop00 setroubleshoot[1144004]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12]
Sep 22 04:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 492) ***
Sep 22 04:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 492) ***
Sep 22 04:10:28 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 492, QN: 5275/5275, ET: 27) ***
Sep 22 04:10:28 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 492, QN: 64/64, ET: 27) ***
Sep 22 04:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 493) ***
Sep 22 04:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 493, QN: 5587/5587, ET: 0) ***
Sep 22 04:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 493) ***
Sep 22 04:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 493, QN: 71/71, ET: 0) ***
Sep 22 04:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 494) ***
Sep 22 04:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 494) ***
Sep 22 04:15:39 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 494, QN: 5465/5465, ET: 38) ***
Sep 22 04:15:39 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 494, QN: 62/62, ET: 38) ***
Sep 22 04:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 495) ***
Sep 22 04:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 495, QN: 6388/6388, ET: 0) ***
Sep 22 04:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 495) ***
Sep 22 04:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 495, QN: 64/64, ET: 0) ***
Sep 22 04:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 496) ***
Sep 22 04:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 496) ***
Sep 22 04:20:31 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 496, QN: 6400/6400, ET: 30) ***
... 72 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 22 04:09:09 outbound00.cs.umd.edu python3[2598607]: ldapdb [x6]
== outbound01.cs.umd.edu (2 distinct, 8 total) ==
Sep 22 04:13:06 outbound01.cs.umd.edu python3[665002]: ldapdb [x6]
Sep 22 04:19:36 outbound01.cs.umd.edu cockpit-ws[666226]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 22 04:13:47 sentry-docker00.cs.umd.edu systemd-udevd[1244643]: link_config: could not get ethtool features for veth0c74588
Sep 22 04:13:47 sentry-docker00.cs.umd.edu systemd-udevd[1244643]: Could not set offload features of veth0c74588: No such device
Sep 22 04:13:47 sentry-docker00.cs.umd.edu systemd-udevd[1244680]: Could not generate persistent MAC address for vethb666ca7: No such file or directory
Sep 22 04:13:47 sentry-docker00.cs.umd.edu systemd-udevd[1244679]: Could not generate persistent MAC address for vethf98ac52: No such file or directory
Sep 22 04:13:47 sentry-docker00.cs.umd.edu systemd-udevd[1244683]: Could not generate persistent MAC address for veth11b7b7f: No such file or directory
Sep 22 04:13:47 sentry-docker00.cs.umd.edu systemd-udevd[1244684]: Could not generate persistent MAC address for veth5148f49: No such file or directory
Sep 22 04:13:48 sentry-docker00.cs.umd.edu systemd-udevd[1244707]: Could not generate persistent MAC address for vetha42db36: No such file or directory
Sep 22 04:13:48 sentry-docker00.cs.umd.edu systemd-udevd[1244708]: Could not generate persistent MAC address for vetha3f21dc: No such file or directory
Sep 22 04:13:48 sentry-docker00.cs.umd.edu systemd-udevd[1244726]: Could not generate persistent MAC address for vethf57b44e: No such file or directory
Sep 22 04:13:48 sentry-docker00.cs.umd.edu systemd-udevd[1244729]: Could not generate persistent MAC address for veth7730510: No such file or directory
Sep 22 04:13:48 sentry-docker00.cs.umd.edu systemd-udevd[1244759]: Could not generate persistent MAC address for veth5d8b270: No such file or directory
Sep 22 04:13:48 sentry-docker00.cs.umd.edu systemd-udevd[1244760]: Could not generate persistent MAC address for veth46c121c: No such file or directory
Sep 22 04:33:56 sentry-docker00.cs.umd.edu systemd-udevd[1254265]: link_config: could not get ethtool features for vetha42db36
Sep 22 04:33:56 sentry-docker00.cs.umd.edu systemd-udevd[1254265]: Could not set offload features of vetha42db36: No such device
Sep 22 04:33:56 sentry-docker00.cs.umd.edu systemd-udevd[1254305]: Could not generate persistent MAC address for veth58779f0: No such file or directory
Sep 22 04:33:56 sentry-docker00.cs.umd.edu systemd-udevd[1254306]: Could not generate persistent MAC address for vethb3a406e: No such file or directory
Sep 22 04:33:56 sentry-docker00.cs.umd.edu systemd-udevd[1254309]: Could not generate persistent MAC address for vethaf182aa: No such file or directory
Sep 22 04:33:56 sentry-docker00.cs.umd.edu systemd-udevd[1254310]: Could not generate persistent MAC address for veth3803f10: No such file or directory
Sep 22 04:33:56 sentry-docker00.cs.umd.edu systemd-udevd[1254333]: Could not generate persistent MAC address for veth5bfa672: No such file or directory
Sep 22 04:33:56 sentry-docker00.cs.umd.edu systemd-udevd[1254334]: Could not generate persistent MAC address for veth030dc23: No such file or directory
Sep 22 04:33:56 sentry-docker00.cs.umd.edu systemd-udevd[1254353]: Could not generate persistent MAC address for veth0f44a00: No such file or directory
Sep 22 04:33:56 sentry-docker00.cs.umd.edu systemd-udevd[1254356]: Could not generate persistent MAC address for vetheb9f81c: No such file or directory
Sep 22 04:33:56 sentry-docker00.cs.umd.edu systemd-udevd[1254338]: Could not generate persistent MAC address for veth8559224: No such file or directory
Sep 22 04:33:56 sentry-docker00.cs.umd.edu systemd-udevd[1254353]: Could not generate persistent MAC address for veth32d10bc: No such file or directory
Sep 22 04:54:04 sentry-docker00.cs.umd.edu systemd-udevd[1263586]: link_config: could not get ethtool features for veth0f44a00
Sep 22 04:54:04 sentry-docker00.cs.umd.edu systemd-udevd[1263586]: Could not set offload features of veth0f44a00: No such device
Sep 22 04:54:04 sentry-docker00.cs.umd.edu systemd-udevd[1263682]: link_config: could not get ethtool features for veth8559224
Sep 22 04:54:04 sentry-docker00.cs.umd.edu systemd-udevd[1263682]: Could not set offload features of veth8559224: No such device
Sep 22 04:54:04 sentry-docker00.cs.umd.edu systemd-udevd[1263713]: Could not generate persistent MAC address for veth092efca: No such file or directory
Sep 22 04:54:04 sentry-docker00.cs.umd.edu systemd-udevd[1263714]: Could not generate persistent MAC address for veth90822e3: No such file or directory
... 8 more distinct messages not shown
== smokeping-slave (1 distinct, 1 total) ==
Sep 22 04:15:01 smokeping-slave nologin[2191530]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
== strawberry (9 distinct, 40 total) ==
Sep 22 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 22 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 22 04:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 22 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 22 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 22 04:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 22 04:15:04 strawberry nologin[3327451]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 22 04:15:04 strawberry pipewire[3327450]: 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 22 04:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (1 distinct, 2 total) ==
Sep 22 04:49:39 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 22 04:21:58 submit26-b9-fclone setroubleshoot[275709]: 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 22 04:21:58 submit26-b9-fclone setroubleshoot[275709]: 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 22 04:21:58 submit26-b9-fclone setroubleshoot[275709]: 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 22 04:21:58 submit26-b9-fclone setroubleshoot[275709]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.vwQ7uH/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 22 04:21:58 submit26-b9-fclone setroubleshoot[275709]: 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 22 04:21:58 submit26-b9-fclone setroubleshoot[275709]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.vwQ7uH. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 22 04:21:58 submit26-b9-fclone setroubleshoot[275709]: 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 22 04:21:58 submit26-b9-fclone setroubleshoot[275709]: 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 22 04:21:58 submit26-b9-fclone setroubleshoot[275709]: 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
== yogurt (1 distinct, 2 total) ==
Sep 22 04:37:24 yogurt systemd[1]: Configuration file /usr/lib/systemd/system/gpd.service is marked executable. Please remove executable permission bits. Proceeding anyway. [x2]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0571s
Status : exited 0
Output :
Syslog digest — 2026-09-22 04:05 EDT
Processed 3,214 lines, filtered 2,703 (84%). 511 unknown (178 distinct) from 23 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 03:54:49 b0b02.cs.umd.edu rustdesk[3857031]: cannot open display:
== bale (5 distinct, 86 total) ==
Sep 22 03:05:59 bale setroubleshoot[1665610]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 22 03:06:00 bale setroubleshoot[1665610]: 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 22 03:06:03 bale setroubleshoot[1665610]: 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 22 03:06:06 bale setroubleshoot[1665610]: 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 22 03:06:17 bale setroubleshoot[1666226]: 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, 134 total) ==
Sep 22 03:04:31 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x134]
== idm00 (1 distinct, 1 total) ==
Sep 22 03:54:03 idm00 named[4166701]: client @0x7f11a93f2098 10.73.240.42#52145: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 22 03:37:55 idmp0 named[1598691]: client @0x7f2d34041cc8 10.73.240.43#49244: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 2 total) ==
Sep 22 04:00:10 inbound00.cs.umd.edu cockpit-ws[2731852]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2]
== inbound01.cs.umd.edu (1 distinct, 3 total) ==
Sep 22 04:00:09 inbound01.cs.umd.edu cockpit-ws[755563]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x3]
== itmon02 (2 distinct, 5 total) ==
Sep 22 03:12:56 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
Sep 22 03:15:04 itmon02 (httpd)[3199994]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== kadath.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 03:47:31 kadath.cs.umd.edu puppet-agent[1487010]: (Facter) invalid or malformed lldp data: MalformedDataError: no lldp interface data found
== librenms (1 distinct, 1 total) ==
Sep 22 03:47:03 librenms (httpd)[2937247]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== munin (2 distinct, 4 total) ==
Sep 22 03:48:57 munin sudo[1651956]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 22 03:48:57 munin sudo[1651956]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== netbox (1 distinct, 1 total) ==
Sep 22 03:08:02 netbox (httpd)[128850]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== newhonors2 (1 distinct, 24 total) ==
Sep 22 03:13:03 newhonors2 dhcpcd[2977800]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 22 03:05:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 466) ***
Sep 22 03:05:27 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 466, QN: 4852/4852, ET: 26) ***
Sep 22 03:05:27 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 466, QN: 79/79, ET: 26) ***
Sep 22 03:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 467) ***
Sep 22 03:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 467, QN: 98/98, ET: 0) ***
Sep 22 03:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 467) ***
Sep 22 03:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 467, QN: 4954/4954, ET: 0) ***
Sep 22 03:08:02 ntop00 setroubleshoot[1136123]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12]
Sep 22 03:08:02 ntop00 setroubleshoot[1136123]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12]
Sep 22 03:08:02 ntop00 setroubleshoot[1136123]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 22 03:08:02 ntop00 setroubleshoot[1136123]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12]
Sep 22 03:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 468) ***
Sep 22 03:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 468) ***
Sep 22 03:10:26 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 468, QN: 4797/4797, ET: 25) ***
Sep 22 03:10:26 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 468, QN: 92/92, ET: 25) ***
Sep 22 03:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 469) ***
Sep 22 03:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 469, QN: 4880/4880, ET: 0) ***
Sep 22 03:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 469) ***
Sep 22 03:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 469, QN: 70/70, ET: 0) ***
Sep 22 03:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 470) ***
Sep 22 03:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 470) ***
Sep 22 03:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 470, QN: 71/71, ET: 0) ***
Sep 22 03:15:28 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 470, QN: 5159/5159, ET: 27) ***
Sep 22 03:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 471) ***
Sep 22 03:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 471, QN: 5494/5494, ET: 0) ***
Sep 22 03:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 471) ***
Sep 22 03:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 471, QN: 80/80, ET: 0) ***
Sep 22 03:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 472) ***
Sep 22 03:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 472) ***
Sep 22 03:20:29 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 472, QN: 5517/5517, ET: 28) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (3 distinct, 10 total) ==
Sep 22 03:09:08 outbound00.cs.umd.edu python3[2583622]: ldapdb [x7]
Sep 22 03:25:05 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.
Sep 22 03:58:52 outbound00.cs.umd.edu cockpit-ws[2595990]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2]
== outbound01.cs.umd.edu (2 distinct, 7 total) ==
Sep 22 03:13:06 outbound01.cs.umd.edu python3[650847]: ldapdb [x6]
Sep 22 03:58:56 outbound01.cs.umd.edu cockpit-ws[661989]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 22 03:13:22 sentry-docker00.cs.umd.edu systemd-udevd[1216313]: link_config: could not get ethtool features for veth8e1f277
Sep 22 03:13:22 sentry-docker00.cs.umd.edu systemd-udevd[1216313]: Could not set offload features of veth8e1f277: No such device
Sep 22 03:13:22 sentry-docker00.cs.umd.edu systemd-udevd[1216335]: Could not generate persistent MAC address for veth2f71607: No such file or directory
Sep 22 03:13:22 sentry-docker00.cs.umd.edu systemd-udevd[1216337]: Could not generate persistent MAC address for vethb768cce: No such file or directory
Sep 22 03:13:22 sentry-docker00.cs.umd.edu systemd-udevd[1216362]: Could not generate persistent MAC address for vethed12578: No such file or directory
Sep 22 03:13:22 sentry-docker00.cs.umd.edu systemd-udevd[1216363]: Could not generate persistent MAC address for veth51362a5: No such file or directory
Sep 22 03:13:22 sentry-docker00.cs.umd.edu systemd-udevd[1216381]: Could not generate persistent MAC address for veth66ce290: No such file or directory
Sep 22 03:13:22 sentry-docker00.cs.umd.edu systemd-udevd[1216387]: Could not generate persistent MAC address for vethaea4b09: No such file or directory
Sep 22 03:13:23 sentry-docker00.cs.umd.edu systemd-udevd[1216397]: Could not generate persistent MAC address for vetha9441a9: No such file or directory
Sep 22 03:13:23 sentry-docker00.cs.umd.edu systemd-udevd[1216398]: Could not generate persistent MAC address for vethfac7e76: No such file or directory
Sep 22 03:13:23 sentry-docker00.cs.umd.edu systemd-udevd[1216448]: Could not generate persistent MAC address for vethba71ec4: No such file or directory
Sep 22 03:13:23 sentry-docker00.cs.umd.edu systemd-udevd[1216449]: Could not generate persistent MAC address for vethbd3e12b: No such file or directory
Sep 22 03:33:31 sentry-docker00.cs.umd.edu systemd-udevd[1225762]: link_config: could not get ethtool features for veth66ce290
Sep 22 03:33:31 sentry-docker00.cs.umd.edu systemd-udevd[1225762]: Could not set offload features of veth66ce290: No such device
Sep 22 03:33:31 sentry-docker00.cs.umd.edu systemd-udevd[1225797]: Could not generate persistent MAC address for vethab5e9e1: No such file or directory
Sep 22 03:33:31 sentry-docker00.cs.umd.edu systemd-udevd[1225798]: Could not generate persistent MAC address for veth5e37293: No such file or directory
Sep 22 03:33:31 sentry-docker00.cs.umd.edu systemd-udevd[1225816]: Could not generate persistent MAC address for veth45ebc95: No such file or directory
Sep 22 03:33:31 sentry-docker00.cs.umd.edu systemd-udevd[1225801]: Could not generate persistent MAC address for veth40ffae3: No such file or directory
Sep 22 03:33:31 sentry-docker00.cs.umd.edu systemd-udevd[1225826]: Could not generate persistent MAC address for veth708df7b: No such file or directory
Sep 22 03:33:31 sentry-docker00.cs.umd.edu systemd-udevd[1225825]: Could not generate persistent MAC address for veth76a0ca4: No such file or directory
Sep 22 03:33:31 sentry-docker00.cs.umd.edu systemd-udevd[1225860]: Could not generate persistent MAC address for veth91d594b: No such file or directory
Sep 22 03:33:31 sentry-docker00.cs.umd.edu systemd-udevd[1225870]: Could not generate persistent MAC address for vethf72c7ad: No such file or directory
Sep 22 03:33:31 sentry-docker00.cs.umd.edu systemd-udevd[1225900]: Could not generate persistent MAC address for vethbadb8e5: No such file or directory
Sep 22 03:33:31 sentry-docker00.cs.umd.edu systemd-udevd[1225901]: Could not generate persistent MAC address for vethbcbc533: No such file or directory
Sep 22 03:53:39 sentry-docker00.cs.umd.edu systemd-udevd[1235223]: link_config: could not get ethtool features for veth45ebc95
Sep 22 03:53:39 sentry-docker00.cs.umd.edu systemd-udevd[1235223]: Could not set offload features of veth45ebc95: No such device
Sep 22 03:53:39 sentry-docker00.cs.umd.edu systemd-udevd[1235224]: link_config: could not get ethtool features for vethbadb8e5
Sep 22 03:53:39 sentry-docker00.cs.umd.edu systemd-udevd[1235224]: Could not set offload features of vethbadb8e5: No such device
Sep 22 03:53:39 sentry-docker00.cs.umd.edu systemd-udevd[1235256]: Could not generate persistent MAC address for vethb1792c2: No such file or directory
Sep 22 03:53:39 sentry-docker00.cs.umd.edu systemd-udevd[1235257]: Could not generate persistent MAC address for vethf5b64b9: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 22 03:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 22 03:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 22 03:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 22 03:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 22 03:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 22 03:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 22 03:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 1 total) ==
Sep 22 03:23:08 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f2 (1 distinct, 1 total) ==
Sep 22 03:20:05 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f3 (3 distinct, 3 total) ==
Sep 22 03:23:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
Sep 22 03:23:08 submit26-b9-f3 systemd-coredump[2448620]: Process 2448617 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2448617:#012#0 0x00007ffb9c48d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007ffb9c43fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007ffb9c429873 abort (libc.so.6 + 0x29873)#012#3 0x00007ffb9c42a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007ffb9c51d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007ffb9c51e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040159b main (grades + 0x159b)#012#7 0x00007ffb9c42a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#8 0x00007ffb9c42a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#9 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64
Sep 22 03:23:08 submit26-b9-f3 systemd-coredump[2448630]: Process 2448627 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2448627:#012#0 0x00007f1f3e48d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f1f3e43fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f1f3e429873 abort (libc.so.6 + 0x29873)#012#3 0x00007f1f3e42a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f1f3e51d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f1f3e51e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040159b main (grades + 0x159b)#012#7 0x00007f1f3e42a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#8 0x00007f1f3e42a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#9 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f4 (3 distinct, 4 total) ==
Sep 22 03:20:07 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
Sep 22 03:43:13 submit26-b9-f4 systemd-coredump[1786182]: Process 1786179 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1786179:#012#0 0x00007fa7ee48d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fa7ee43fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fa7ee429873 abort (libc.so.6 + 0x29873)#012#3 0x00007fa7ee42a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fa7ee51d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fa7ee51e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040159b main (grades + 0x159b)#012#7 0x00007fa7ee42a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#8 0x00007fa7ee42a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#9 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64
Sep 22 03:43:13 submit26-b9-f4 systemd-coredump[1786193]: Process 1786190 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1786190:#012#0 0x00007f59d248d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f59d243fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f59d2429873 abort (libc.so.6 + 0x29873)#012#3 0x00007f59d242a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f59d251d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f59d251e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040159b main (grades + 0x159b)#012#7 0x00007f59d242a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#8 0x00007f59d242a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#9 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64
== teaching-awards (1 distinct, 1 total) ==
Sep 22 03:07:24 teaching-awards krb5_child[1306790]: Client 'admin(a)UMD.EDU' not found in Kerberos database
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0515s
Status : exited 0
Output :
Syslog digest — 2026-09-22 03:05 EDT
Processed 2,201 lines, filtered 1,646 (74%). 555 unknown (198 distinct) from 21 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 02:54:46 b0b02.cs.umd.edu rustdesk[3841832]: cannot open display:
== bale (5 distinct, 84 total) ==
Sep 22 02:05:09 bale setroubleshoot[1652881]: failed to retrieve rpm info for /dev/nvme0 [x36]
Sep 22 02:05:09 bale setroubleshoot[1652881]: 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 22 02:05:12 bale setroubleshoot[1652881]: 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 22 02:05:15 bale setroubleshoot[1652881]: 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 22 02:05:27 bale setroubleshoot[1653497]: 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 (6 distinct, 6 total) ==
Sep 22 02:56:21 cheezit.cs.umd.edu sshd-session[1778133]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 22 02:56:21 cheezit.cs.umd.edu sshd-session[1778133]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 22 02:56:25 cheezit.cs.umd.edu sshd-session[1778133]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 22 02:56:25 cheezit.cs.umd.edu sshd-session[1778133]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 22 02:56:27 cheezit.cs.umd.edu sshd-session[1778133]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 22 02:56:27 cheezit.cs.umd.edu sshd-session[1778133]: error: kex_protocol_error: type 30 seq 7 [preauth]
== cmsc436-0101-redis (2 distinct, 2 total) ==
Sep 22 02:39:04 cmsc436-0101-redis krb5_child[3420339]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 22 02:39:07 cmsc436-0101-redis sshd-session[3420335]: error: PAM: Authentication failure for admin from 35.205.15.0
== csfw00a (2 distinct, 138 total) ==
Sep 22 02:03:56 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x134]
Sep 22 03:01:57 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x4]
== idm00 (1 distinct, 1 total) ==
Sep 22 02:54:03 idm00 named[4166701]: client @0x7f11a402f3b8 10.73.240.42#60694: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 22 02:37:55 idmp0 named[1598691]: client @0x7f2d2c050c58 10.73.240.43#60433: update '73.10.in-addr.arpa/IN' denied
== krispykreme.cs.umd.edu (6 distinct, 24 total) ==
Sep 22 02:54:41 krispykreme.cs.umd.edu sshd-session[961197]: error: kex_protocol_error: type 20 seq 2 [preauth] [x4]
Sep 22 02:54:41 krispykreme.cs.umd.edu sshd-session[961197]: error: kex_protocol_error: type 30 seq 3 [preauth] [x4]
Sep 22 02:54:43 krispykreme.cs.umd.edu sshd-session[961197]: error: kex_protocol_error: type 20 seq 4 [preauth] [x4]
Sep 22 02:54:43 krispykreme.cs.umd.edu sshd-session[961197]: error: kex_protocol_error: type 30 seq 5 [preauth] [x4]
Sep 22 02:54:45 krispykreme.cs.umd.edu sshd-session[961197]: error: kex_protocol_error: type 20 seq 6 [preauth] [x4]
Sep 22 02:54:45 krispykreme.cs.umd.edu sshd-session[961197]: error: kex_protocol_error: type 30 seq 7 [preauth] [x4]
== munin (2 distinct, 8 total) ==
Sep 22 02:23:30 munin sudo[1621666]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 22 02:23:30 munin sudo[1621666]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== netman.cs.umd.edu (3 distinct, 6 total) ==
Sep 22 02:56:50 netman.cs.umd.edu krb5_child[3432905]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Sep 22 02:56:55 netman.cs.umd.edu sshd[3432902]: error: PAM: Authentication failure for admin from 34.52.144.133
Sep 22 02:57:05 netman.cs.umd.edu sshd[3432917]: error: Protocol major versions differ: 2 vs. 1
== newhonors2 (1 distinct, 24 total) ==
Sep 22 02:13:02 newhonors2 dhcpcd[2975971]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 22 02:05:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 442) ***
Sep 22 02:05:30 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 5227/5227, ET: 29) ***
Sep 22 02:05:30 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 51/51, ET: 29) ***
Sep 22 02:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 443) ***
Sep 22 02:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 4905/4905, ET: 0) ***
Sep 22 02:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 443) ***
Sep 22 02:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 57/57, ET: 0) ***
Sep 22 02:08:02 ntop00 setroubleshoot[1128246]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12]
Sep 22 02:08:02 ntop00 setroubleshoot[1128246]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12]
Sep 22 02:08:02 ntop00 setroubleshoot[1128246]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 22 02:08:02 ntop00 setroubleshoot[1128246]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12]
Sep 22 02:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) ***
Sep 22 02:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) ***
Sep 22 02:10:29 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 4947/4947, ET: 28) ***
Sep 22 02:10:29 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 49/49, ET: 28) ***
Sep 22 02:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 445) ***
Sep 22 02:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 4752/4752, ET: 0) ***
Sep 22 02:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 445) ***
Sep 22 02:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 52/52, ET: 0) ***
Sep 22 02:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) ***
Sep 22 02:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) ***
Sep 22 02:15:26 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 4625/4625, ET: 25) ***
Sep 22 02:15:26 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 58/58, ET: 25) ***
Sep 22 02:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 447) ***
Sep 22 02:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 4837/4837, ET: 0) ***
Sep 22 02:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 447) ***
Sep 22 02:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 51/51, ET: 0) ***
Sep 22 02:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) ***
Sep 22 02:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) ***
Sep 22 02:20:30 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 448, QN: 5326/5326, ET: 29) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 22 02:09:09 outbound00.cs.umd.edu python3[2569481]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 22 02:13:06 outbound01.cs.umd.edu python3[636864]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 22 02:12:57 sentry-docker00.cs.umd.edu systemd-udevd[1187581]: link_config: could not get ethtool features for vethc5a6916
Sep 22 02:12:57 sentry-docker00.cs.umd.edu systemd-udevd[1187581]: Could not set offload features of vethc5a6916: No such device
Sep 22 02:12:58 sentry-docker00.cs.umd.edu systemd-udevd[1187653]: Could not generate persistent MAC address for vethb28958e: No such file or directory
Sep 22 02:12:58 sentry-docker00.cs.umd.edu systemd-udevd[1187654]: Could not generate persistent MAC address for veth895f798: No such file or directory
Sep 22 02:12:58 sentry-docker00.cs.umd.edu systemd-udevd[1187658]: Could not generate persistent MAC address for vethecff1fc: No such file or directory
Sep 22 02:12:58 sentry-docker00.cs.umd.edu systemd-udevd[1187657]: Could not generate persistent MAC address for vethdfda982: No such file or directory
Sep 22 02:12:58 sentry-docker00.cs.umd.edu systemd-udevd[1187681]: Could not generate persistent MAC address for veth449fbfa: No such file or directory
Sep 22 02:12:58 sentry-docker00.cs.umd.edu systemd-udevd[1187682]: Could not generate persistent MAC address for veth1ae8e65: No such file or directory
Sep 22 02:12:58 sentry-docker00.cs.umd.edu systemd-udevd[1187681]: Could not generate persistent MAC address for veth15b9566: No such file or directory
Sep 22 02:12:58 sentry-docker00.cs.umd.edu systemd-udevd[1187697]: Could not generate persistent MAC address for veth2ca8da6: No such file or directory
Sep 22 02:12:58 sentry-docker00.cs.umd.edu systemd-udevd[1187737]: Could not generate persistent MAC address for veth8a894fd: No such file or directory
Sep 22 02:12:58 sentry-docker00.cs.umd.edu systemd-udevd[1187750]: Could not generate persistent MAC address for vethe9e6af2: No such file or directory
Sep 22 02:33:06 sentry-docker00.cs.umd.edu systemd-udevd[1197217]: link_config: could not get ethtool features for veth449fbfa
Sep 22 02:33:06 sentry-docker00.cs.umd.edu systemd-udevd[1197217]: Could not set offload features of veth449fbfa: No such device
Sep 22 02:33:06 sentry-docker00.cs.umd.edu systemd-udevd[1197342]: Could not generate persistent MAC address for vethdd0cf35: No such file or directory
Sep 22 02:33:06 sentry-docker00.cs.umd.edu systemd-udevd[1197343]: Could not generate persistent MAC address for veth65d7496: No such file or directory
Sep 22 02:33:06 sentry-docker00.cs.umd.edu systemd-udevd[1197361]: Could not generate persistent MAC address for veth1eab758: No such file or directory
Sep 22 02:33:06 sentry-docker00.cs.umd.edu systemd-udevd[1197356]: Could not generate persistent MAC address for vethadebcf1: No such file or directory
Sep 22 02:33:06 sentry-docker00.cs.umd.edu systemd-udevd[1197349]: Could not generate persistent MAC address for veth600cc2f: No such file or directory
Sep 22 02:33:06 sentry-docker00.cs.umd.edu systemd-udevd[1197348]: Could not generate persistent MAC address for veth52d8e46: No such file or directory
Sep 22 02:33:06 sentry-docker00.cs.umd.edu systemd-udevd[1197372]: Could not generate persistent MAC address for veth2d59d8d: No such file or directory
Sep 22 02:33:06 sentry-docker00.cs.umd.edu systemd-udevd[1197373]: Could not generate persistent MAC address for vethda95d32: No such file or directory
Sep 22 02:33:06 sentry-docker00.cs.umd.edu systemd-udevd[1197425]: Could not generate persistent MAC address for veth81aa787: No such file or directory
Sep 22 02:33:06 sentry-docker00.cs.umd.edu systemd-udevd[1197426]: Could not generate persistent MAC address for veth42ac2bd: No such file or directory
Sep 22 02:53:14 sentry-docker00.cs.umd.edu systemd-udevd[1206932]: Could not generate persistent MAC address for veth3a54853: No such file or directory
Sep 22 02:53:14 sentry-docker00.cs.umd.edu systemd-udevd[1206933]: Could not generate persistent MAC address for vethc462316: No such file or directory
Sep 22 02:53:14 sentry-docker00.cs.umd.edu systemd-udevd[1206958]: Could not generate persistent MAC address for vethf0b96ea: No such file or directory
Sep 22 02:53:14 sentry-docker00.cs.umd.edu systemd-udevd[1206959]: Could not generate persistent MAC address for veth31d5ffe: No such file or directory
Sep 22 02:53:14 sentry-docker00.cs.umd.edu systemd-udevd[1206983]: Could not generate persistent MAC address for veth8e1f277: No such file or directory
Sep 22 02:53:14 sentry-docker00.cs.umd.edu systemd-udevd[1206985]: Could not generate persistent MAC address for veth3fdd744: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 22 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 22 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 22 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 22 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 22 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 22 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 22 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (10 distinct, 12 total) ==
Sep 22 02:10:07 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
Sep 22 02:25:54 submit26-b9-f1 setroubleshoot[2865739]: 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 22 02:25:54 submit26-b9-f1 setroubleshoot[2865739]: 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 22 02:25:54 submit26-b9-f1 setroubleshoot[2865739]: 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 22 02:25:54 submit26-b9-f1 setroubleshoot[2865739]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.0hRww7/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 22 02:25:54 submit26-b9-f1 setroubleshoot[2865739]: 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 22 02:25:54 submit26-b9-f1 setroubleshoot[2865739]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.0hRww7. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 22 02:25:54 submit26-b9-f1 setroubleshoot[2865739]: 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 22 02:25:55 submit26-b9-f1 setroubleshoot[2865739]: 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 22 02:25:55 submit26-b9-f1 setroubleshoot[2865739]: 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 (12 distinct, 13 total) ==
Sep 22 02:06:49 submit26-b9-f2 setroubleshoot[1971148]: 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 22 02:06:49 submit26-b9-f2 setroubleshoot[1971148]: 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 22 02:06:49 submit26-b9-f2 setroubleshoot[1971148]: 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 22 02:06:49 submit26-b9-f2 setroubleshoot[1971148]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.9oOAX1/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 22 02:06:49 submit26-b9-f2 setroubleshoot[1971148]: 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 22 02:06:49 submit26-b9-f2 setroubleshoot[1971148]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.9oOAX1. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 22 02:06:49 submit26-b9-f2 setroubleshoot[1971148]: 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 22 02:06:49 submit26-b9-f2 setroubleshoot[1971148]: 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 22 02:06:50 submit26-b9-f2 setroubleshoot[1971148]: 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 22 02:39:55 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
Sep 22 03:01:05 submit26-b9-f2 systemd-coredump[1973462]: Process 1973459 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1973459:#012#0 0x00007f82b608d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f82b603fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f82b6029873 abort (libc.so.6 + 0x29873)#012#3 0x00007f82b602a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f82b611d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f82b611e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040159b main (grades + 0x159b)#012#7 0x00007f82b602a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#8 0x00007f82b602a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#9 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64
Sep 22 03:01:05 submit26-b9-f2 systemd-coredump[1973473]: Process 1973469 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1973469:#012#0 0x00007fd6b588d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fd6b583fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fd6b5829873 abort (libc.so.6 + 0x29873)#012#3 0x00007fd6b582a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fd6b591d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fd6b591e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040159b main (grades + 0x159b)#012#7 0x00007fd6b582a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#8 0x00007fd6b582a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#9 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f3 (1 distinct, 5 total) ==
Sep 22 02:08:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 22 02:13:11 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== tma-0 (1 distinct, 1 total) ==
Sep 22 02:58:51 tma-0 sshd[16476]: error: PAM: Authentication failure for admin from 209.196.189.35.bc.googleusercontent.com
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0503s
Status : exited 0
Output :
Syslog digest — 2026-09-22 02:05 EDT
Processed 1,878 lines, filtered 1,339 (71%). 539 unknown (199 distinct) from 21 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 01:54:42 b0b02.cs.umd.edu rustdesk[3826632]: cannot open display:
== bachata (10 distinct, 10 total) ==
Sep 22 01:52:48 bachata smbd[951283]: [2026/09/22 01:52:48.248512, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service)
Sep 22 01:52:48 bachata smbd[951283]: chdir_current_service: vfs_ChDir(/fs/junkfood/mount) failed: Permission denied. Current token: uid=11255, gid=11255, 12 groups: 11255 319000009 25038 15294 15229 755 25030 25025 30880 25029 770 15026
Sep 22 01:52:48 bachata smbd[951283]: [2026/09/22 01:52:48.250108, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect)
Sep 22 01:52:48 bachata smbd[951283]: smbXsrv_tcon_disconnect: disconnect(0x3bcf4414, 'mount'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR
Sep 22 01:52:48 bachata smbd[951283]: [2026/09/22 01:52:48.250594, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all)
Sep 22 01:52:48 bachata smbd[951283]: smbXsrv_tcon_disconnect_all: count[2] errors[1] first[NT_STATUS_INTERNAL_ERROR]
Sep 22 01:52:48 bachata smbd[951283]: [2026/09/22 01:52:48.250693, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff)
Sep 22 01:52:48 bachata smbd[951283]: smbXsrv_session_logoff: smbXsrv_session_logoff(0x66970deb): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR
Sep 22 01:52:48 bachata smbd[951283]: [2026/09/22 01:52:48.250793, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done)
Sep 22 01:52:48 bachata smbd[951283]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(1721175531) failed: NT_STATUS_INTERNAL_ERROR
== bale (5 distinct, 87 total) ==
Sep 22 01:05:37 bale setroubleshoot[1639980]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 22 01:05:38 bale setroubleshoot[1639980]: 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 22 01:05:40 bale setroubleshoot[1639980]: 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 22 01:05:43 bale setroubleshoot[1639980]: 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 22 01:05:55 bale setroubleshoot[1640596]: 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]
== cheezit.cs.umd.edu (4 distinct, 4 total) ==
Sep 22 01:27:30 cheezit.cs.umd.edu sshd-session[1757776]: pam_access(sshd:auth): access denied for user `admin' from `34.52.144.133'
Sep 22 01:27:30 cheezit.cs.umd.edu krb5_child[1757778]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 22 01:27:30 cheezit.cs.umd.edu sshd-session[1757774]: error: PAM: System error for admin from 34.52.144.133
Sep 22 01:29:01 cheezit.cs.umd.edu sshd-session[1758075]: error: Protocol major versions differ: 2 vs. 1
== csfw00a (2 distinct, 131 total) ==
Sep 22 01:03:59 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x129]
Sep 22 01:14:40 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x2]
== idm00 (1 distinct, 1 total) ==
Sep 22 01:54:03 idm00 named[4166701]: client @0x7f11a0057bb8 10.73.240.42#63462: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 22 01:37:55 idmp0 named[1598691]: client @0x7f2d28029f68 10.73.240.43#64970: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 4 total) ==
Sep 22 01:23:03 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== munin (2 distinct, 14 total) ==
Sep 22 01:08:08 munin sudo[1594464]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x7]
Sep 22 01:08:08 munin sudo[1594464]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x7]
== newhonors2 (1 distinct, 24 total) ==
Sep 22 01:13:03 newhonors2 dhcpcd[2974078]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 144 total) ==
Sep 22 01:05:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 418) ***
Sep 22 01:05:32 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 6083/6083, ET: 31) ***
Sep 22 01:05:32 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 56/56, ET: 31) ***
Sep 22 01:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 419) ***
Sep 22 01:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 6043/6043, ET: 0) ***
Sep 22 01:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 419) ***
Sep 22 01:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 54/54, ET: 0) ***
Sep 22 01:08:02 ntop00 setroubleshoot[1120213]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12]
Sep 22 01:08:02 ntop00 setroubleshoot[1120213]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12]
Sep 22 01:08:02 ntop00 setroubleshoot[1120213]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 22 01:08:02 ntop00 setroubleshoot[1120213]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12]
Sep 22 01:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) ***
Sep 22 01:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) ***
Sep 22 01:10:31 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 5638/5638, ET: 30) ***
Sep 22 01:10:31 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 51/51, ET: 30) ***
Sep 22 01:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 421) ***
Sep 22 01:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 4789/4789, ET: 0) ***
Sep 22 01:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 421) ***
Sep 22 01:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 48/48, ET: 0) ***
Sep 22 01:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) ***
Sep 22 01:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) ***
Sep 22 01:15:25 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 4471/4471, ET: 24) ***
Sep 22 01:15:25 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 40/40, ET: 24) ***
Sep 22 01:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 423) ***
Sep 22 01:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 4680/4680, ET: 0) ***
Sep 22 01:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 423) ***
Sep 22 01:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 37/37, ET: 0) ***
Sep 22 01:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) ***
Sep 22 01:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) ***
Sep 22 01:20:27 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 4792/4792, ET: 26) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (3 distinct, 8 total) ==
Sep 22 01:09:09 outbound00.cs.umd.edu python3[2555481]: ldapdb [x6]
Sep 22 02:02:50 outbound00.cs.umd.edu krb5_child[2568197]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 22 02:02:56 outbound00.cs.umd.edu sshd-session[2568230]: error: Protocol major versions differ: 2 vs. 1
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 22 01:13:07 outbound01.cs.umd.edu python3[622735]: ldapdb [x6]
== sebatinsky.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 01:42:59 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 22 01:12:32 sentry-docker00.cs.umd.edu systemd-udevd[1159137]: link_config: could not get ethtool features for vethe0eb035
Sep 22 01:12:32 sentry-docker00.cs.umd.edu systemd-udevd[1159137]: Could not set offload features of vethe0eb035: No such device
Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159175]: Could not generate persistent MAC address for vethda633f2: No such file or directory
Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159176]: Could not generate persistent MAC address for vethc4cbce5: No such file or directory
Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159179]: Could not generate persistent MAC address for veth658a0ce: No such file or directory
Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159192]: Could not generate persistent MAC address for vethac85d33: No such file or directory
Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159176]: Could not generate persistent MAC address for vethdcbb6a1: No such file or directory
Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159180]: Could not generate persistent MAC address for veth5579e0d: No such file or directory
Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159191]: Could not generate persistent MAC address for veth66ea1c4: No such file or directory
Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159196]: Could not generate persistent MAC address for vethd42300e: No such file or directory
Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159304]: Could not generate persistent MAC address for vethfc18506: No such file or directory
Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159310]: Could not generate persistent MAC address for veth10bfdf7: No such file or directory
Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168713]: link_config: could not get ethtool features for vethfc18506
Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168713]: Could not set offload features of vethfc18506: No such device
Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168822]: Could not generate persistent MAC address for vethe849b9f: No such file or directory
Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168823]: Could not generate persistent MAC address for vethc3bf175: No such file or directory
Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168850]: Could not generate persistent MAC address for veth2997f75: No such file or directory
Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168851]: Could not generate persistent MAC address for veth2be485b: No such file or directory
Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168859]: Could not generate persistent MAC address for veth4593b36: No such file or directory
Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168867]: Could not generate persistent MAC address for vethb99dade: No such file or directory
Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168863]: Could not generate persistent MAC address for vetha878903: No such file or directory
Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168850]: Could not generate persistent MAC address for vethee335aa: No such file or directory
Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168850]: Could not generate persistent MAC address for veth5685369: No such file or directory
Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168863]: Could not generate persistent MAC address for veth63b06d1: No such file or directory
Sep 22 01:52:49 sentry-docker00.cs.umd.edu systemd-udevd[1178118]: link_config: could not get ethtool features for vethe849b9f
Sep 22 01:52:49 sentry-docker00.cs.umd.edu systemd-udevd[1178118]: Could not set offload features of vethe849b9f: No such device
Sep 22 01:52:49 sentry-docker00.cs.umd.edu systemd-udevd[1178236]: Could not generate persistent MAC address for vetha18968c: No such file or directory
Sep 22 01:52:49 sentry-docker00.cs.umd.edu systemd-udevd[1178237]: Could not generate persistent MAC address for veth1a67fe9: No such file or directory
Sep 22 01:52:49 sentry-docker00.cs.umd.edu systemd-udevd[1178255]: Could not generate persistent MAC address for vethe045dfd: No such file or directory
Sep 22 01:52:49 sentry-docker00.cs.umd.edu systemd-udevd[1178262]: Could not generate persistent MAC address for vetha1bf529: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 22 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 22 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 22 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 22 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 22 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 22 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 22 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 1 total) ==
Sep 22 01:59:00 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f2 (1 distinct, 5 total) ==
Sep 22 01:05:06 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f3 (10 distinct, 12 total) ==
Sep 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.1Ltup3/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.1Ltup3. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:15:05 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f4 (10 distinct, 10 total) ==
Sep 22 01:24:48 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:24:48 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:24:48 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:24:49 submit26-b9-f4 setroubleshoot[1777317]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.aRN0WU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 22 01:24:49 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:24:49 submit26-b9-f4 setroubleshoot[1777317]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.aRN0WU. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 22 01:24:49 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:24:49 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:24:49 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:53:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== teaching-awards (1 distinct, 1 total) ==
Sep 22 01:05:13 teaching-awards krb5_child[1299444]: Client 'admin(a)UMD.EDU' not found in Kerberos database
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0569s
Status : exited 0
Output :
Syslog digest — 2026-09-22 01:05 EDT
Processed 2,547 lines, filtered 1,889 (74%). 658 unknown (230 distinct) from 36 host(s).
== abuse (3 distinct, 4 total) ==
Sep 22 00:10:14 abuse systemd[1]: New main PID 16771 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 22 00:10:33 abuse systemd[1]: Daemon never wrote its PID file. Failing.
Sep 22 00:10:43 abuse systemd[1]: pmlogger.service: Supervising process 24145 which is not our child. We'll most likely not notice when it exits.
== atif01.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 00:55:35 atif01.cs.umd.edu kernel: net_ratelimit: 15 callbacks suppressed
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 22 00:54:38 b0b02.cs.umd.edu rustdesk[3811400]: cannot open display:
== bale (5 distinct, 87 total) ==
Sep 22 00:05:10 bale setroubleshoot[1626731]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 22 00:05:11 bale setroubleshoot[1626731]: 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 22 00:05:13 bale setroubleshoot[1626731]: 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 22 00:05:16 bale setroubleshoot[1626731]: 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 22 00:05:28 bale setroubleshoot[1627347]: 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 (4 distinct, 4 total) ==
Sep 22 00:25:56 biggulp.cs.umd.edu sshd-session[3182978]: pam_access(sshd:auth): access denied for user `admin' from `34.22.208.38'
Sep 22 00:25:56 biggulp.cs.umd.edu krb5_child[3182980]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 22 00:25:56 biggulp.cs.umd.edu sshd-session[3182973]: error: PAM: System error for admin from 34.22.208.38
Sep 22 00:26:16 biggulp.cs.umd.edu sshd-session[3182999]: error: Protocol major versions differ: 2 vs. 1
== cheezit.cs.umd.edu (3 distinct, 4 total) ==
Sep 22 00:52:18 cheezit.cs.umd.edu sshd-session[1749238]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2]
Sep 22 00:52:19 cheezit.cs.umd.edu sshd-session[1749238]: Error in Duo login for 'larry' from 71.191.93.172
Sep 22 00:52:19 cheezit.cs.umd.edu sshd-session[1749236]: error: PAM: Authentication failure for larry from 71.191.93.172
== csfw00a (1 distinct, 120 total) ==
Sep 22 00:03:58 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x120]
== galax (2 distinct, 2 total) ==
Sep 22 00:29:35 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 4099 times, consider switching to WQ_UNBOUND
Sep 22 00:30:13 galax systemctl[319133]: Warning: The unit file, source configuration file or drop-ins of cups.service changed on disk. Run 'systemctl daemon-reload' to reload units.
== grades01.cs.umd.edu (3 distinct, 4 total) ==
Sep 22 00:10:13 grades01.cs.umd.edu systemd[1]: New main PID 29680 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 22 00:10:34 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 22 00:10:49 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 5043 which is not our child. We'll most likely not notice when it exits.
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Sep 22 00:53:21 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 22 00:53:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 22 00:53:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 22 00:53:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 22 00:53:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 22 00:53:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 22 00:53:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 22 00:53:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 22 00:53:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 22 00:53:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 22 00:53:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 22 00:54:03 idm00 named[4166701]: client @0x7f11a403ce28 10.73.240.42#55766: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 22 00:37:55 idmp0 named[1598691]: client @0x7f2d2c03b838 10.73.240.43#50107: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 1 total) ==
Sep 22 00:43:36 itmon02 sshd[1483508]: error: beginning MaxStartups throttling
== jubjub.cs.umd.edu (3 distinct, 4 total) ==
Sep 22 00:10:11 jubjub.cs.umd.edu systemd[1]: New main PID 42560 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 22 00:10:31 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 22 00:10:39 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 50096 which is not our child. We'll most likely not notice when it exits.
== matrix (3 distinct, 4 total) ==
Sep 22 00:18:01 matrix krb5_child[236508]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 22 00:18:02 matrix sshd[236483]: error: PAM: Authentication failure for admin from 35.205.121.246
Sep 22 00:18:24 matrix sshd[236614]: error: Protocol major versions differ: 2 vs. 1
== mirrors.cs.umd.edu (4 distinct, 6 total) ==
Sep 22 00:10:34 mirrors.cs.umd.edu root[1207]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log
Sep 22 00:10:34 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. [x2]
Sep 22 00:10:37 mirrors.cs.umd.edu systemd[1]: New main PID 32531 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 22 00:11:38 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 16895 which is not our child. We'll most likely not notice when it exits.
== misty.cs.umd.edu (3 distinct, 4 total) ==
Sep 22 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 2747 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 22 00:10:35 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 22 00:10:51 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 10457 which is not our child. We'll most likely not notice when it exits.
== munin (2 distinct, 42 total) ==
Sep 22 00:13:08 munin sudo[1573810]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x21]
Sep 22 00:13:08 munin sudo[1573810]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x21]
== newhonors2 (1 distinct, 24 total) ==
Sep 22 00:13:03 newhonors2 dhcpcd[2972229]: dhcpcd is not running [x24]
== ntop00 (101 distinct, 145 total) ==
Sep 22 00:05:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 394) ***
Sep 22 00:05:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 394) ***
Sep 22 00:05:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 394, QN: 74/74, ET: 0) ***
Sep 22 00:05:31 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 394, QN: 6024/6024, ET: 30) ***
Sep 22 00:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 395) ***
Sep 22 00:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 395, QN: 5789/5789, ET: 0) ***
Sep 22 00:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 395) ***
Sep 22 00:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 395, QN: 56/56, ET: 0) ***
Sep 22 00:08:02 ntop00 setroubleshoot[1112305]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12]
Sep 22 00:08:02 ntop00 setroubleshoot[1112305]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12]
Sep 22 00:08:02 ntop00 setroubleshoot[1112305]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 22 00:08:02 ntop00 setroubleshoot[1112305]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12]
Sep 22 00:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 396) ***
Sep 22 00:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 396) ***
Sep 22 00:10:35 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 396, QN: 6072/6072, ET: 34) ***
Sep 22 00:10:35 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 396, QN: 52/52, ET: 34) ***
Sep 22 00:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 397) ***
Sep 22 00:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 397, QN: 6205/6205, ET: 0) ***
Sep 22 00:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 397) ***
Sep 22 00:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 397, QN: 61/61, ET: 0) ***
Sep 22 00:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 398) ***
Sep 22 00:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 398) ***
Sep 22 00:15:32 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 398, QN: 6089/6089, ET: 31) ***
Sep 22 00:15:33 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 398, QN: 63/63, ET: 32) ***
Sep 22 00:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 399) ***
Sep 22 00:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 399, QN: 7340/7340, ET: 0) ***
Sep 22 00:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 399) ***
Sep 22 00:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 399, QN: 48/48, ET: 0) ***
Sep 22 00:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 400) ***
Sep 22 00:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 400) ***
... 71 more distinct messages not shown
== openrepo (1 distinct, 1 total) ==
Sep 22 00:49:53 openrepo (nin-node)[3366206]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 22 00:09:09 outbound00.cs.umd.edu python3[2540930]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 22 00:13:06 outbound01.cs.umd.edu python3[608707]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 22 00:12:07 sentry-docker00.cs.umd.edu systemd-udevd[1130674]: link_config: could not get ethtool features for veth7f5c43a
Sep 22 00:12:07 sentry-docker00.cs.umd.edu systemd-udevd[1130674]: Could not set offload features of veth7f5c43a: No such device
Sep 22 00:12:07 sentry-docker00.cs.umd.edu systemd-udevd[1130764]: link_config: could not get ethtool features for veth8b050f9
Sep 22 00:12:07 sentry-docker00.cs.umd.edu systemd-udevd[1130764]: Could not set offload features of veth8b050f9: No such device
Sep 22 00:12:08 sentry-docker00.cs.umd.edu systemd-udevd[1130788]: Could not generate persistent MAC address for vethe21ec11: No such file or directory
Sep 22 00:12:08 sentry-docker00.cs.umd.edu systemd-udevd[1130789]: Could not generate persistent MAC address for veth07cd765: No such file or directory
Sep 22 00:12:08 sentry-docker00.cs.umd.edu systemd-udevd[1130807]: Could not generate persistent MAC address for vethb6ef5f6: No such file or directory
Sep 22 00:12:08 sentry-docker00.cs.umd.edu systemd-udevd[1130801]: Could not generate persistent MAC address for veth7b00051: No such file or directory
Sep 22 00:12:08 sentry-docker00.cs.umd.edu systemd-udevd[1130816]: Could not generate persistent MAC address for vethadb22b7: No such file or directory
Sep 22 00:12:08 sentry-docker00.cs.umd.edu systemd-udevd[1130817]: Could not generate persistent MAC address for vetha02d0e8: No such file or directory
Sep 22 00:12:08 sentry-docker00.cs.umd.edu systemd-udevd[1130826]: Could not generate persistent MAC address for veth6aea476: No such file or directory
Sep 22 00:12:08 sentry-docker00.cs.umd.edu systemd-udevd[1130839]: Could not generate persistent MAC address for veth18fc101: No such file or directory
Sep 22 00:12:08 sentry-docker00.cs.umd.edu systemd-udevd[1130864]: Could not generate persistent MAC address for veth0538af7: No such file or directory
Sep 22 00:12:08 sentry-docker00.cs.umd.edu systemd-udevd[1130867]: Could not generate persistent MAC address for veth5b024cb: No such file or directory
Sep 22 00:32:16 sentry-docker00.cs.umd.edu systemd-udevd[1140220]: Could not generate persistent MAC address for vethd9f0194: No such file or directory
Sep 22 00:32:16 sentry-docker00.cs.umd.edu systemd-udevd[1140221]: Could not generate persistent MAC address for vethb8d4113: No such file or directory
Sep 22 00:32:16 sentry-docker00.cs.umd.edu systemd-udevd[1140247]: Could not generate persistent MAC address for veth15a8ded: No such file or directory
Sep 22 00:32:16 sentry-docker00.cs.umd.edu systemd-udevd[1140251]: Could not generate persistent MAC address for vethee2a0f3: No such file or directory
Sep 22 00:32:16 sentry-docker00.cs.umd.edu systemd-udevd[1140285]: Could not generate persistent MAC address for vethba52ccc: No such file or directory
Sep 22 00:32:16 sentry-docker00.cs.umd.edu systemd-udevd[1140277]: Could not generate persistent MAC address for vethffb5524: No such file or directory
Sep 22 00:32:16 sentry-docker00.cs.umd.edu systemd-udevd[1140300]: Could not generate persistent MAC address for veth383d0ed: No such file or directory
Sep 22 00:32:16 sentry-docker00.cs.umd.edu systemd-udevd[1140299]: Could not generate persistent MAC address for veth5a1ec26: No such file or directory
Sep 22 00:32:16 sentry-docker00.cs.umd.edu systemd-udevd[1140358]: Could not generate persistent MAC address for vethe6239b8: No such file or directory
Sep 22 00:32:16 sentry-docker00.cs.umd.edu systemd-udevd[1140364]: Could not generate persistent MAC address for veth54bdd45: No such file or directory
Sep 22 00:52:24 sentry-docker00.cs.umd.edu systemd-udevd[1149648]: link_config: could not get ethtool features for vethd9f0194
Sep 22 00:52:24 sentry-docker00.cs.umd.edu systemd-udevd[1149648]: Could not set offload features of vethd9f0194: No such device
Sep 22 00:52:24 sentry-docker00.cs.umd.edu systemd-udevd[1149678]: Could not generate persistent MAC address for vethfac639d: No such file or directory
Sep 22 00:52:24 sentry-docker00.cs.umd.edu systemd-udevd[1149679]: Could not generate persistent MAC address for veth98dd84f: No such file or directory
Sep 22 00:52:24 sentry-docker00.cs.umd.edu systemd-udevd[1149697]: Could not generate persistent MAC address for vethe0eb035: No such file or directory
Sep 22 00:52:24 sentry-docker00.cs.umd.edu systemd-udevd[1149692]: Could not generate persistent MAC address for veth927b095: No such file or directory
... 6 more distinct messages not shown
== soul (1 distinct, 1 total) ==
Sep 22 00:40:57 soul krb5_child[4102457]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== strawberry (8 distinct, 39 total) ==
Sep 22 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 22 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 22 00:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 22 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 22 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 22 00:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 22 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Sep 22 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing.
== submit10-cln25 (3 distinct, 4 total) ==
Sep 22 00:10:11 submit10-cln25 systemd: New main PID 14597 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 22 00:10:29 submit10-cln25 systemd: Daemon never wrote its PID file. Failing.
Sep 22 00:10:35 submit10-cln25 systemd: pmlogger.service: Supervising process 21497 which is not our child. We'll most likely not notice when it exits.
== submit26-b9-f1 (1 distinct, 4 total) ==
Sep 22 00:13:08 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f2 (1 distinct, 5 total) ==
Sep 22 00:08:37 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f3 (1 distinct, 3 total) ==
Sep 22 00:13:11 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f4 (1 distinct, 3 total) ==
Sep 22 00:08:11 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 22 00:21:59 submit26-b9-fclone setroubleshoot[265919]: 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 22 00:21:59 submit26-b9-fclone setroubleshoot[265919]: 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 22 00:21:59 submit26-b9-fclone setroubleshoot[265919]: 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 22 00:21:59 submit26-b9-fclone setroubleshoot[265919]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.WQWEwF/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 22 00:21:59 submit26-b9-fclone setroubleshoot[265919]: 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 22 00:21:59 submit26-b9-fclone setroubleshoot[265919]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.WQWEwF. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 22 00:21:59 submit26-b9-fclone setroubleshoot[265919]: 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 22 00:21:59 submit26-b9-fclone setroubleshoot[265919]: 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 22 00:21:59 submit26-b9-fclone setroubleshoot[265919]: 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 22 00:10:13 tma-0 systemd[1]: New main PID 6521 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 22 00:10:31 tma-0 systemd[1]: Daemon never wrote its PID file. Failing.
Sep 22 00:10:38 tma-0 systemd[1]: pmlogger.service: Supervising process 13488 which is not our child. We'll most likely not notice when it exits.
== uffish.cs.umd.edu (3 distinct, 4 total) ==
Sep 22 00:10:14 uffish.cs.umd.edu systemd[1]: New main PID 2615169 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 22 00:10:40 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 22 00:10:55 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 2622437 which is not our child. We'll most likely not notice when it exits.
== vacuum.cs.umd.edu (3 distinct, 4 total) ==
Sep 22 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 11740 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 22 00:10:33 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 22 00:10:44 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 19317 which is not our child. We'll most likely not notice when it exits.
== whiffle.cs.umd.edu (3 distinct, 4 total) ==
Sep 22 00:10:13 whiffle.cs.umd.edu systemd[1]: New main PID 2166147 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 22 00:10:32 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 22 00:10:45 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 2173654 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.0509s
Status : exited 0
Output :
Syslog digest — 2026-09-22 00:05 EDT
Processed 1,984 lines, filtered 1,439 (72%). 545 unknown (181 distinct) from 23 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 23:54:35 b0b02.cs.umd.edu rustdesk[3795282]: cannot open display:
== bale (5 distinct, 87 total) ==
Sep 21 23:05:09 bale setroubleshoot[1614005]: failed to retrieve rpm info for /dev/nvme0 [x37]
Sep 21 23:05:10 bale setroubleshoot[1614005]: 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 23:05:12 bale setroubleshoot[1614005]: 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 23:05:15 bale setroubleshoot[1614005]: 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 23:05:27 bale setroubleshoot[1614621]: 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]
== cmsc436-0101-redis (1 distinct, 1 total) ==
Sep 21 23:23:57 cmsc436-0101-redis sshd-session[3413361]: error: PAM: Authentication failure for root from 193.187.110.214
== csfw00a (1 distinct, 124 total) ==
Sep 21 23:04:01 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x124]
== idm00 (1 distinct, 1 total) ==
Sep 21 23:54:03 idm00 named[4166701]: client @0x7f11a404b548 10.73.240.42#55053: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 21 23:37:55 idmp0 named[1598691]: client @0x7f2d4c005288 10.73.240.43#49281: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 21 23:13:54 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== krispykreme.cs.umd.edu (8 distinct, 11 total) ==
Sep 21 23:17:23 krispykreme.cs.umd.edu sshd-session[896166]: pam_access(sshd:auth): access denied for user `admin' from `104.155.100.207'
Sep 21 23:17:23 krispykreme.cs.umd.edu krb5_child[896168]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x3]
Sep 21 23:17:23 krispykreme.cs.umd.edu sshd-session[896160]: error: PAM: System error for admin from 104.155.100.207
Sep 21 23:17:40 krispykreme.cs.umd.edu sshd-session[896179]: error: Protocol major versions differ: 2 vs. 1 [x2]
Sep 21 23:28:04 krispykreme.cs.umd.edu sshd-session[899289]: pam_access(sshd:auth): access denied for user `admin' from `35.205.38.12'
Sep 21 23:28:04 krispykreme.cs.umd.edu sshd-session[899283]: error: PAM: System error for admin from 35.205.38.12
Sep 21 23:49:05 krispykreme.cs.umd.edu sshd-session[904432]: pam_access(sshd:auth): access denied for user `admin' from `193.187.110.214'
Sep 21 23:49:05 krispykreme.cs.umd.edu sshd-session[904423]: error: PAM: System error for admin from 193.187.110.214
== matrix (3 distinct, 4 total) ==
Sep 21 23:51:21 matrix krb5_child[221143]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 21 23:51:23 matrix sshd[221137]: error: PAM: Authentication failure for admin from 193.187.110.214
Sep 22 00:00:25 matrix (nin-node)[225085]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== munin (2 distinct, 24 total) ==
Sep 21 23:39:01 munin sudo[1561682]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x12]
Sep 21 23:39:01 munin sudo[1561682]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x12]
== neo-gizmonic (1 distinct, 1 total) ==
Sep 22 00:00:01 neo-gizmonic (nin-node)[2011013]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neoavion (1 distinct, 1 total) ==
Sep 22 00:00:20 neoavion (nin-node)[4041892]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== newhonors2 (2 distinct, 25 total) ==
Sep 21 23:13:03 newhonors2 dhcpcd[2970185]: dhcpcd is not running [x24]
Sep 22 00:00:16 newhonors2 (nin-node)[2971702]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== ntop00 (99 distinct, 143 total) ==
Sep 21 23:05:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 370) ***
Sep 21 23:05:29 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 370, QN: 5460/5460, ET: 28) ***
Sep 21 23:05:30 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 370, QN: 55/55, ET: 29) ***
Sep 21 23:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 371) ***
Sep 21 23:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 371, QN: 5638/5638, ET: 0) ***
Sep 21 23:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 371) ***
Sep 21 23:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 371, QN: 52/52, ET: 0) ***
Sep 21 23:08:02 ntop00 setroubleshoot[1104421]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12]
Sep 21 23:08:02 ntop00 setroubleshoot[1104421]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12]
Sep 21 23:08:02 ntop00 setroubleshoot[1104421]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 21 23:08:02 ntop00 setroubleshoot[1104421]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12]
Sep 21 23:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 372) ***
Sep 21 23:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 372) ***
Sep 21 23:10:32 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 372, QN: 5648/5648, ET: 31) ***
Sep 21 23:10:32 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 372, QN: 50/50, ET: 31) ***
Sep 21 23:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 373) ***
Sep 21 23:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 373, QN: 5524/5524, ET: 0) ***
Sep 21 23:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 373) ***
Sep 21 23:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 373, QN: 42/42, ET: 0) ***
Sep 21 23:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 374) ***
Sep 21 23:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 374) ***
Sep 21 23:15:30 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 374, QN: 5471/5471, ET: 29) ***
Sep 21 23:15:30 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 374, QN: 54/54, ET: 29) ***
Sep 21 23:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 375) ***
Sep 21 23:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 375, QN: 5619/5619, ET: 0) ***
Sep 21 23:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 375) ***
Sep 21 23:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 375, QN: 66/66, ET: 0) ***
Sep 21 23:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 376) ***
Sep 21 23:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 376) ***
Sep 21 23:20:30 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 376, QN: 5701/5701, ET: 29) ***
... 69 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 23:09:09 outbound00.cs.umd.edu python3[2526717]: ldapdb [x6]
== outbound01.cs.umd.edu (3 distinct, 8 total) ==
Sep 21 23:13:06 outbound01.cs.umd.edu python3[593888]: ldapdb [x6]
Sep 21 23:27:28 outbound01.cs.umd.edu krb5_child[597517]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 21 23:28:08 outbound01.cs.umd.edu sshd-session[597625]: error: Protocol major versions differ: 2 vs. 1
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 21 23:11:42 sentry-docker00.cs.umd.edu systemd-udevd[1102500]: link_config: could not get ethtool features for veth615fbdf
Sep 21 23:11:42 sentry-docker00.cs.umd.edu systemd-udevd[1102500]: Could not set offload features of veth615fbdf: No such device
Sep 21 23:11:43 sentry-docker00.cs.umd.edu systemd-udevd[1102589]: link_config: could not get ethtool features for vethb687fef
Sep 21 23:11:43 sentry-docker00.cs.umd.edu systemd-udevd[1102589]: Could not set offload features of vethb687fef: No such device
Sep 21 23:11:43 sentry-docker00.cs.umd.edu systemd-udevd[1102617]: Could not generate persistent MAC address for veth91779d3: No such file or directory
Sep 21 23:11:43 sentry-docker00.cs.umd.edu systemd-udevd[1102618]: Could not generate persistent MAC address for vethe9051f5: No such file or directory
Sep 21 23:11:43 sentry-docker00.cs.umd.edu systemd-udevd[1102621]: Could not generate persistent MAC address for vethcb7edb6: No such file or directory
Sep 21 23:11:43 sentry-docker00.cs.umd.edu systemd-udevd[1102622]: Could not generate persistent MAC address for vetha051cf7: No such file or directory
Sep 21 23:11:43 sentry-docker00.cs.umd.edu systemd-udevd[1102645]: Could not generate persistent MAC address for vethb577b25: No such file or directory
Sep 21 23:11:43 sentry-docker00.cs.umd.edu systemd-udevd[1102646]: Could not generate persistent MAC address for veth8011308: No such file or directory
Sep 21 23:11:43 sentry-docker00.cs.umd.edu systemd-udevd[1102668]: Could not generate persistent MAC address for veth48a7c0a: No such file or directory
Sep 21 23:11:43 sentry-docker00.cs.umd.edu systemd-udevd[1102646]: Could not generate persistent MAC address for veth6c126ef: No such file or directory
Sep 21 23:11:43 sentry-docker00.cs.umd.edu systemd-udevd[1102649]: Could not generate persistent MAC address for vethabb608e: No such file or directory
Sep 21 23:11:43 sentry-docker00.cs.umd.edu systemd-udevd[1102659]: Could not generate persistent MAC address for veth92ae76b: No such file or directory
Sep 21 23:31:51 sentry-docker00.cs.umd.edu systemd-udevd[1111964]: link_config: could not get ethtool features for veth92ae76b
Sep 21 23:31:51 sentry-docker00.cs.umd.edu systemd-udevd[1111964]: Could not set offload features of veth92ae76b: No such device
Sep 21 23:31:51 sentry-docker00.cs.umd.edu systemd-udevd[1112001]: Could not generate persistent MAC address for veth8c56cb1: No such file or directory
Sep 21 23:31:51 sentry-docker00.cs.umd.edu systemd-udevd[1112002]: Could not generate persistent MAC address for veth636a222: No such file or directory
Sep 21 23:31:51 sentry-docker00.cs.umd.edu systemd-udevd[1112005]: Could not generate persistent MAC address for vethbce670a: No such file or directory
Sep 21 23:31:51 sentry-docker00.cs.umd.edu systemd-udevd[1112014]: Could not generate persistent MAC address for vethdbf5a74: No such file or directory
Sep 21 23:31:51 sentry-docker00.cs.umd.edu systemd-udevd[1112027]: Could not generate persistent MAC address for veth303c4fb: No such file or directory
Sep 21 23:31:51 sentry-docker00.cs.umd.edu systemd-udevd[1112010]: Could not generate persistent MAC address for vethbc54b27: No such file or directory
Sep 21 23:31:51 sentry-docker00.cs.umd.edu systemd-udevd[1112031]: Could not generate persistent MAC address for vethe60407b: No such file or directory
Sep 21 23:31:51 sentry-docker00.cs.umd.edu systemd-udevd[1112032]: Could not generate persistent MAC address for vetha76fdf4: No such file or directory
Sep 21 23:31:51 sentry-docker00.cs.umd.edu systemd-udevd[1112039]: Could not generate persistent MAC address for veth3f6b3e9: No such file or directory
Sep 21 23:31:51 sentry-docker00.cs.umd.edu systemd-udevd[1112052]: Could not generate persistent MAC address for veth0ef8f22: No such file or directory
Sep 21 23:51:59 sentry-docker00.cs.umd.edu systemd-udevd[1121331]: link_config: could not get ethtool features for veth3f6b3e9
Sep 21 23:51:59 sentry-docker00.cs.umd.edu systemd-udevd[1121331]: Could not set offload features of veth3f6b3e9: No such device
Sep 21 23:51:59 sentry-docker00.cs.umd.edu systemd-udevd[1121371]: Could not generate persistent MAC address for veth7f5c43a: No such file or directory
Sep 21 23:51:59 sentry-docker00.cs.umd.edu systemd-udevd[1121372]: Could not generate persistent MAC address for veth339de48: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 21 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 21 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 21 23:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 21 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 21 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 21 23:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 21 23:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 6 total) ==
Sep 21 23:08:08 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f2 (1 distinct, 8 total) ==
Sep 21 23:08:19 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x8]
== submit26-b9-f3 (1 distinct, 2 total) ==
Sep 21 23:15:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f4 (1 distinct, 11 total) ==
Sep 21 23:09:00 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x11]
== wraith (1 distinct, 1 total) ==
Sep 22 00:00:00 wraith (nin-node)[890453]: 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.0545s
Status : exited 0
Output :
Syslog digest — 2026-09-21 23:05 EDT
Processed 2,495 lines, filtered 1,888 (75%). 607 unknown (260 distinct) from 26 host(s).
== abadi-computer (62 distinct, 62 total) ==
Sep 21 22:05:39 abadi-computer kernel: gsd-housekeepin invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0
Sep 21 22:05:39 abadi-computer kernel: CPU: 1 UID: 120 PID: 2148 Comm: gsd-housekeepin Not tainted 6.17.0-35-generic #35~24.04.1-Ubuntu PREEMPT(voluntary)
Sep 21 22:05:39 abadi-computer kernel: Hardware name: Dell Inc. Precision T3600/08HPGT, BIOS A09 05/03/2013
Sep 21 22:05:39 abadi-computer kernel: Call Trace:
Sep 21 22:05:39 abadi-computer kernel: <TASK>
Sep 21 22:05:39 abadi-computer kernel: dump_stack_lvl+0x76/0xa0
Sep 21 22:05:39 abadi-computer kernel: dump_stack+0x10/0x20
Sep 21 22:05:39 abadi-computer kernel: dump_header+0x48/0x210
Sep 21 22:05:39 abadi-computer kernel: oom_kill_process+0x118/0x290
Sep 21 22:05:39 abadi-computer kernel: ? oom_evaluate_task+0x15c/0x210
Sep 21 22:05:39 abadi-computer kernel: out_of_memory+0x101/0x340
Sep 21 22:05:39 abadi-computer kernel: __alloc_pages_may_oom+0x109/0x1d0
Sep 21 22:05:39 abadi-computer kernel: __alloc_pages_slowpath.constprop.0+0x623/0x9f0
Sep 21 22:05:39 abadi-computer kernel: ? get_page_from_freelist+0x4be/0x6d0
Sep 21 22:05:39 abadi-computer kernel: __alloc_frozen_pages_noprof+0x347/0x360
Sep 21 22:05:39 abadi-computer kernel: alloc_pages_mpol+0x7e/0x1a0
Sep 21 22:05:39 abadi-computer kernel: folio_alloc_noprof+0x65/0xf0
Sep 21 22:05:39 abadi-computer kernel: filemap_alloc_folio_noprof+0x102/0x110
Sep 21 22:05:39 abadi-computer kernel: __filemap_get_folio+0x1f2/0x340
Sep 21 22:05:39 abadi-computer kernel: filemap_fault+0x10c/0xd50
Sep 21 22:05:39 abadi-computer kernel: __do_fault+0x3d/0x190
Sep 21 22:05:39 abadi-computer kernel: do_read_fault+0x12e/0x230
Sep 21 22:05:39 abadi-computer kernel: do_fault+0x167/0x280
Sep 21 22:05:39 abadi-computer kernel: handle_pte_fault+0x15e/0x200
Sep 21 22:05:39 abadi-computer kernel: __handle_mm_fault+0x5ba/0x740
Sep 21 22:05:39 abadi-computer kernel: handle_mm_fault+0x120/0x370
Sep 21 22:05:39 abadi-computer kernel: do_user_addr_fault+0x1d2/0x8d0
Sep 21 22:05:39 abadi-computer kernel: exc_page_fault+0x7f/0x1b0
Sep 21 22:05:39 abadi-computer kernel: asm_exc_page_fault+0x27/0x30
Sep 21 22:05:39 abadi-computer kernel: RIP: 0033:0x79718a26c139
... 32 more distinct messages not shown
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 22:54:31 b0b02.cs.umd.edu rustdesk[3780088]: cannot open display:
== bale (5 distinct, 88 total) ==
Sep 21 22:05:10 bale setroubleshoot[1601279]: failed to retrieve rpm info for /dev/nvme0 [x38]
Sep 21 22:05:10 bale setroubleshoot[1601279]: 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 22:05:13 bale setroubleshoot[1601279]: 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 22:05:16 bale setroubleshoot[1601279]: 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 22:05:28 bale setroubleshoot[1601895]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x14]
== csfw00a (1 distinct, 125 total) ==
Sep 21 22:03:47 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x125]
== gle-dind04 (1 distinct, 1 total) ==
Sep 21 23:01:21 gle-dind04 lldpd[1171]: unable to send packet on real device for veth39773c1: No such device or address
== idm00 (1 distinct, 1 total) ==
Sep 21 22:54:03 idm00 named[4166701]: client @0x7f11a00475a8 10.73.240.42#53383: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 21 22:37:55 idmp0 named[1598691]: client @0x7f2d5002a688 10.73.240.43#61735: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 22:27:07 inbound00.cs.umd.edu krb5_child[2653081]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== inbound01.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 22:42:53 inbound01.cs.umd.edu krb5_child[680223]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 3 total) ==
Sep 21 22:18:19 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== krispykreme.cs.umd.edu (5 distinct, 5 total) ==
Sep 21 22:11:40 krispykreme.cs.umd.edu sshd-session[877961]: pam_access(sshd:auth): access denied for user `admin' from `193.187.110.214'
Sep 21 22:11:40 krispykreme.cs.umd.edu krb5_child[877963]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Sep 21 22:11:40 krispykreme.cs.umd.edu sshd-session[877959]: error: PAM: System error for admin from 193.187.110.214
Sep 21 22:54:25 krispykreme.cs.umd.edu sshd-session[889241]: pam_access(sshd:auth): access denied for user `root' from `193.187.110.214'
Sep 21 22:54:27 krispykreme.cs.umd.edu sshd-session[889239]: error: PAM: Authentication failure for root from 193.187.110.214
== matrix (3 distinct, 4 total) ==
Sep 21 22:14:07 matrix krb5_child[164437]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Sep 21 22:14:09 matrix sshd[164431]: error: PAM: Authentication failure for admin from 193.187.110.214
Sep 21 22:56:42 matrix sshd[189236]: error: PAM: Authentication failure for root from 193.187.110.214
== mcstic (3 distinct, 6 total) ==
Sep 21 22:30:27 mcstic krb5_child[927488]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Sep 21 22:30:33 mcstic sshd[927483]: error: PAM: Authentication failure for admin from 34.22.208.38
Sep 21 22:35:57 mcstic sshd[927740]: error: Protocol major versions differ: 2 vs. 1
== munin (2 distinct, 12 total) ==
Sep 21 22:18:34 munin sudo[1533143]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6]
Sep 21 22:18:34 munin sudo[1533143]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6]
== newhonors.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 23:00:01 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 21 22:13:02 newhonors2 dhcpcd[2968339]: dhcpcd is not running [x24]
== ntop00 (99 distinct, 143 total) ==
Sep 21 22:05:31 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 5851/5851, ET: 30) ***
Sep 21 22:05:31 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 51/51, ET: 30) ***
Sep 21 22:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 347) ***
Sep 21 22:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 5557/5557, ET: 0) ***
Sep 21 22:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 347) ***
Sep 21 22:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 60/60, ET: 0) ***
Sep 21 22:08:03 ntop00 setroubleshoot[1096537]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12]
Sep 21 22:08:03 ntop00 setroubleshoot[1096537]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12]
Sep 21 22:08:03 ntop00 setroubleshoot[1096537]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 21 22:08:03 ntop00 setroubleshoot[1096537]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12]
Sep 21 22:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) ***
Sep 21 22:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) ***
Sep 21 22:10:28 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 5542/5542, ET: 27) ***
Sep 21 22:10:28 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 51/51, ET: 27) ***
Sep 21 22:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 349) ***
Sep 21 22:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 55/55, ET: 0) ***
Sep 21 22:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 349) ***
Sep 21 22:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 5631/5631, ET: 0) ***
Sep 21 22:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) ***
Sep 21 22:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) ***
Sep 21 22:15:29 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 5657/5657, ET: 28) ***
Sep 21 22:15:29 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 60/60, ET: 28) ***
Sep 21 22:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 351) ***
Sep 21 22:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 5656/5656, ET: 0) ***
Sep 21 22:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 351) ***
Sep 21 22:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 62/62, ET: 0) ***
Sep 21 22:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) ***
Sep 21 22:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) ***
Sep 21 22:20:31 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 5872/5872, ET: 30) ***
Sep 21 22:20:31 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 67/67, ET: 30) ***
... 69 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 22:09:09 outbound00.cs.umd.edu python3[2512548]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 22:13:06 outbound01.cs.umd.edu python3[579870]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074300]: link_config: could not get ethtool features for vethcc9e33b
Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074300]: Could not set offload features of vethcc9e33b: No such device
Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074334]: Could not generate persistent MAC address for veth1a8e129: No such file or directory
Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074335]: Could not generate persistent MAC address for veth6eb2921: No such file or directory
Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074338]: Could not generate persistent MAC address for vethee3da76: No such file or directory
Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074339]: Could not generate persistent MAC address for vethcbf5ccd: No such file or directory
Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074362]: Could not generate persistent MAC address for vethafa6d9c: No such file or directory
Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074363]: Could not generate persistent MAC address for veth3b336e6: No such file or directory
Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074381]: Could not generate persistent MAC address for veth72a673e: No such file or directory
Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074388]: Could not generate persistent MAC address for veth10db9e3: No such file or directory
Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074390]: Could not generate persistent MAC address for vethffcfbb7: No such file or directory
Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074392]: Could not generate persistent MAC address for veth4000969: No such file or directory
Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083694]: link_config: could not get ethtool features for vethafa6d9c
Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083694]: Could not set offload features of vethafa6d9c: No such device
Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083781]: Could not generate persistent MAC address for veth435ee5d: No such file or directory
Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083782]: Could not generate persistent MAC address for veth77255ad: No such file or directory
Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083782]: Could not generate persistent MAC address for veth5e4506a: No such file or directory
Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083795]: Could not generate persistent MAC address for veth37811c0: No such file or directory
Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083827]: Could not generate persistent MAC address for vethe36577f: No such file or directory
Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083829]: Could not generate persistent MAC address for veth06ac276: No such file or directory
Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083855]: Could not generate persistent MAC address for veth3e15713: No such file or directory
Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083842]: Could not generate persistent MAC address for vethb2da7be: No such file or directory
Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083840]: Could not generate persistent MAC address for veth85202fd: No such file or directory
Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083852]: Could not generate persistent MAC address for vethed493ce: No such file or directory
Sep 21 22:51:34 sentry-docker00.cs.umd.edu systemd-udevd[1093147]: link_config: could not get ethtool features for vethed493ce
Sep 21 22:51:34 sentry-docker00.cs.umd.edu systemd-udevd[1093147]: Could not set offload features of vethed493ce: No such device
Sep 21 22:51:34 sentry-docker00.cs.umd.edu systemd-udevd[1093177]: Could not generate persistent MAC address for veth9e4bf9b: No such file or directory
Sep 21 22:51:34 sentry-docker00.cs.umd.edu systemd-udevd[1093178]: Could not generate persistent MAC address for vethd2bc272: No such file or directory
Sep 21 22:51:34 sentry-docker00.cs.umd.edu systemd-udevd[1093181]: Could not generate persistent MAC address for veth32afc0f: No such file or directory
Sep 21 22:51:34 sentry-docker00.cs.umd.edu systemd-udevd[1093182]: Could not generate persistent MAC address for veth1510200: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 21 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 21 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 21 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 21 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 21 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 21 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 21 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (10 distinct, 16 total) ==
Sep 21 22:10:56 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
Sep 21 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 21 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.DxVicq/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 21 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.DxVicq. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 21 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 21 22:06:49 submit26-b9-f2 setroubleshoot[1933624]: 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 22:06:49 submit26-b9-f2 setroubleshoot[1933624]: 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 22:06:49 submit26-b9-f2 setroubleshoot[1933624]: 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 22:06:49 submit26-b9-f2 setroubleshoot[1933624]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.OGAHug/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 21 22:06:49 submit26-b9-f2 setroubleshoot[1933624]: 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 22:06:50 submit26-b9-f2 setroubleshoot[1933624]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.OGAHug. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 21 22:06:50 submit26-b9-f2 setroubleshoot[1933624]: 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 22:06:50 submit26-b9-f2 setroubleshoot[1933624]: 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 22:06:50 submit26-b9-f2 setroubleshoot[1933624]: 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 22:15:21 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f3 (1 distinct, 8 total) ==
Sep 21 22:16:19 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x8]
== submit26-b9-f4 (1 distinct, 2 total) ==
Sep 21 22:19:12 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== vacuum.cs.umd.edu (4 distinct, 4 total) ==
Sep 21 22:11:57 vacuum.cs.umd.edu abrt-hook-ccpp[13500]: Process 9066 (driver) of user 33 killed by SIGABRT - dumping core
Sep 21 22:11:58 vacuum.cs.umd.edu abrt-server[13502]: Package 'amanda-backup_server' isn't signed with proper key
Sep 21 22:11:58 vacuum.cs.umd.edu abrt-server[13502]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-21-22:11:57-9066' exited with 1
Sep 21 22:11:58 vacuum.cs.umd.edu abrt-server[13502]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-21-22:11:57-9066'
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0505s
Status : exited 0
Output :
Syslog digest — 2026-09-21 22:05 EDT
Processed 1,896 lines, filtered 1,368 (72%). 528 unknown (194 distinct) from 21 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 21:54:28 b0b02.cs.umd.edu rustdesk[3764865]: cannot open display:
== bale (5 distinct, 90 total) ==
Sep 21 21:05:45 bale setroubleshoot[1588368]: failed to retrieve rpm info for /dev/nvme0 [x39]
Sep 21 21:05:45 bale setroubleshoot[1588368]: 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 21:05:48 bale setroubleshoot[1588368]: 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 21:05:51 bale setroubleshoot[1588368]: 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 21:06:03 bale setroubleshoot[1588983]: 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]
== csfw00a (1 distinct, 115 total) ==
Sep 21 21:04:41 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x115]
== gle-dind04 (1 distinct, 1 total) ==
Sep 21 21:27:09 gle-dind04 lldpd[1171]: unable to send packet on real device for veth66e027c: No such device or address
== idm00 (1 distinct, 1 total) ==
Sep 21 21:54:03 idm00 named[4166701]: client @0x7f11a00732a8 10.73.240.42#63661: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 21 21:37:55 idmp0 named[1598691]: client @0x7f2d44011478 10.73.240.43#60837: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 2 total) ==
Sep 21 21:48:23 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2]
== krispykreme.cs.umd.edu (4 distinct, 4 total) ==
Sep 21 21:14:21 krispykreme.cs.umd.edu sshd-session[861565]: pam_access(sshd:auth): access denied for user `nobody' from `193.187.110.214'
Sep 21 21:14:23 krispykreme.cs.umd.edu sshd-session[861563]: error: PAM: User not known to the underlying authentication module for nobody from 193.187.110.214
Sep 21 21:56:53 krispykreme.cs.umd.edu sshd-session[873797]: pam_access(sshd:auth): access denied for user `root' from `193.187.110.214'
Sep 21 21:56:55 krispykreme.cs.umd.edu sshd-session[873794]: error: PAM: Authentication failure for root from 193.187.110.214
== matrix (2 distinct, 2 total) ==
Sep 21 21:23:33 matrix sshd[135522]: error: PAM: Authentication failure for nobody from 193.187.110.214
Sep 21 21:59:20 matrix sshd[155631]: error: PAM: Authentication failure for root from 193.187.110.214
== munin (2 distinct, 20 total) ==
Sep 21 21:23:35 munin sudo[1513382]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x10]
Sep 21 21:23:35 munin sudo[1513382]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x10]
== newhonors2 (1 distinct, 24 total) ==
Sep 21 21:13:03 newhonors2 dhcpcd[2966496]: dhcpcd is not running [x24]
== ntop00 (102 distinct, 146 total) ==
Sep 21 21:05:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) ***
Sep 21 21:05:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) ***
Sep 21 21:05:32 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 6159/6159, ET: 31) ***
Sep 21 21:05:32 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 52/52, ET: 31) ***
Sep 21 21:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 323) ***
Sep 21 21:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 6446/6446, ET: 0) ***
Sep 21 21:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 323) ***
Sep 21 21:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 45/45, ET: 0) ***
Sep 21 21:08:02 ntop00 setroubleshoot[1088496]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12]
Sep 21 21:08:02 ntop00 setroubleshoot[1088496]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12]
Sep 21 21:08:02 ntop00 setroubleshoot[1088496]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12]
Sep 21 21:08:02 ntop00 setroubleshoot[1088496]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12]
Sep 21 21:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) ***
Sep 21 21:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) ***
Sep 21 21:10:32 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 6252/6252, ET: 31) ***
Sep 21 21:10:32 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 57/57, ET: 31) ***
Sep 21 21:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 325) ***
Sep 21 21:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 6179/6179, ET: 0) ***
Sep 21 21:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 325) ***
Sep 21 21:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 52/52, ET: 0) ***
Sep 21 21:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) ***
Sep 21 21:15:02 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) ***
Sep 21 21:15:32 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 6211/6211, ET: 31) ***
Sep 21 21:15:32 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 41/41, ET: 30) ***
Sep 21 21:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 327) ***
Sep 21 21:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 46/46, ET: 0) ***
Sep 21 21:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 327) ***
Sep 21 21:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 6407/6407, ET: 0) ***
Sep 21 21:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) ***
Sep 21 21:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) ***
... 72 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 21:09:09 outbound00.cs.umd.edu python3[2498580]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 21 21:13:06 outbound01.cs.umd.edu python3[565714]: ldapdb [x6]
== sebatinsky.cs.umd.edu (1 distinct, 1 total) ==
Sep 21 21:13:59 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts
== sentry-docker00.cs.umd.edu (40 distinct, 40 total) ==
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045693]: link_config: could not get ethtool features for veth1093b24
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045693]: Could not set offload features of veth1093b24: No such device
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045737]: link_config: could not set ethtool features for veth69d3675
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045737]: Could not set offload features of veth69d3675: Operation not permitted
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045771]: Could not generate persistent MAC address for veth3bb02cb: No such file or directory
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045772]: Could not generate persistent MAC address for veth8170379: No such file or directory
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045775]: Could not generate persistent MAC address for veth7772a67: No such file or directory
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045776]: Could not generate persistent MAC address for veth2393a8d: No such file or directory
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045799]: Could not generate persistent MAC address for veth750bc4f: No such file or directory
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045800]: Could not generate persistent MAC address for vethb0cd3e5: No such file or directory
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045818]: Could not generate persistent MAC address for veth061570d: No such file or directory
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045821]: Could not generate persistent MAC address for vethf297150: No such file or directory
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045838]: Could not generate persistent MAC address for vetha3396ef: No such file or directory
Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045841]: Could not generate persistent MAC address for veth9dac3db: No such file or directory
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055338]: link_config: could not get ethtool features for veth7772a67
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055338]: Could not set offload features of veth7772a67: No such device
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055426]: link_config: could not get ethtool features for veth750bc4f
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055426]: Could not set offload features of veth750bc4f: No such device
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055450]: Could not generate persistent MAC address for vethd3e061e: No such file or directory
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055451]: Could not generate persistent MAC address for veth88c5e91: No such file or directory
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055456]: Could not generate persistent MAC address for veth34ba79e: No such file or directory
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055469]: Could not generate persistent MAC address for vethd6f29f8: No such file or directory
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055479]: Could not generate persistent MAC address for veth860ce71: No such file or directory
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055480]: Could not generate persistent MAC address for vethd7deeae: No such file or directory
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055516]: Could not generate persistent MAC address for veth91c308b: No such file or directory
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055513]: Could not generate persistent MAC address for veth3a61427: No such file or directory
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055514]: Could not generate persistent MAC address for veth938f3e5: No such file or directory
Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055524]: Could not generate persistent MAC address for vethfa0293d: No such file or directory
Sep 21 21:51:09 sentry-docker00.cs.umd.edu systemd-udevd[1064818]: link_config: could not get ethtool features for veth34ba79e
Sep 21 21:51:09 sentry-docker00.cs.umd.edu systemd-udevd[1064818]: Could not set offload features of veth34ba79e: No such device
... 10 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 21 21:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 21 21:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 21 21:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 21 21:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 21 21:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 21 21:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 21 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 3 total) ==
Sep 21 21:09:51 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f2 (1 distinct, 1 total) ==
Sep 21 22:03:06 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f3 (10 distinct, 14 total) ==
Sep 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.qRyYjg/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.qRyYjg. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 21 21:22:00 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f4 (10 distinct, 12 total) ==
Sep 21 21:18:11 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
Sep 21 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.qNTrBE/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 21 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.qNTrBE. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 21 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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