Command: /usr/local/sbin/syslog-digest.py Time : 0.0468s Status : exited 0 Output : Syslog digest — 2026-10-02 06:05 EDT Processed 1,758 lines, filtered 1,378 (78%). 380 unknown (171 distinct) from 17 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 2 05:09:41 b0b02.cs.umd.edu rustdesk[3489956]: cannot open display: == biggulp.cs.umd.edu (4 distinct, 4 total) == Oct 2 05:27:27 biggulp.cs.umd.edu sshd-session[1762946]: error: kex_protocol_error: type 20 seq 2 [preauth] Oct 2 05:27:27 biggulp.cs.umd.edu sshd-session[1762946]: error: kex_protocol_error: type 30 seq 3 [preauth] Oct 2 05:27:29 biggulp.cs.umd.edu sshd-session[1762946]: error: kex_protocol_error: type 20 seq 4 [preauth] Oct 2 05:27:29 biggulp.cs.umd.edu sshd-session[1762946]: error: kex_protocol_error: type 30 seq 5 [preauth] == grades01.cs.umd.edu (1 distinct, 1 total) == Oct 2 05:48:39 grades01.cs.umd.edu puppet-agent[10125]: 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) == Oct 2 05:54:25 idm00 named[4166701]: client @0x7f11a40662f8 10.73.240.42#51350: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 2 05:39:27 idmp0 named[1598691]: client @0x7f2d09240c38 10.73.240.43#58850: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Oct 2 05:12:58 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 72 total) == Oct 2 05:18:11 munin sudo[2718816]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x36] Oct 2 05:18:11 munin sudo[2718816]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x36] == netman.cs.umd.edu (1 distinct, 1 total) == Oct 2 05:50:33 netman.cs.umd.edu sshd[3441402]: fatal: userauth_pubkey: parse request failed: incomplete message [preauth] == newhonors2 (1 distinct, 24 total) == Oct 2 05:13:03 newhonors2 dhcpcd[3444614]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Oct 2 05:05:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1666, QN: 4393/4393, ET: 6) *** Oct 2 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1667) *** Oct 2 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1667, QN: 4304/4304, ET: 0) *** Oct 2 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1667) *** Oct 2 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1667, QN: 75/75, ET: 0) *** Oct 2 05:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1668) *** Oct 2 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1668) *** Oct 2 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1668, QN: 73/73, ET: 0) *** Oct 2 05:10:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1668, QN: 4366/4366, ET: 6) *** Oct 2 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1669) *** Oct 2 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1669, QN: 4217/4217, ET: 0) *** Oct 2 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1669) *** Oct 2 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1669, QN: 56/56, ET: 0) *** Oct 2 05:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1670) *** Oct 2 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1670) *** Oct 2 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1670, QN: 66/66, ET: 0) *** Oct 2 05:15:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1670, QN: 4123/4123, ET: 5) *** Oct 2 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1671) *** Oct 2 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1671, QN: 4215/4215, ET: 0) *** Oct 2 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1671) *** Oct 2 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1671, QN: 49/49, ET: 0) *** Oct 2 05:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1672) *** Oct 2 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1672) *** Oct 2 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1672, QN: 38/38, ET: 0) *** Oct 2 05:20:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1672, QN: 4394/4394, ET: 6) *** Oct 2 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1673) *** Oct 2 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1673, QN: 4587/4587, ET: 0) *** Oct 2 05:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1673) *** Oct 2 05:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1673, QN: 53/53, ET: 0) *** Oct 2 05:25:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1674) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 9 total) == Oct 2 05:09:09 outbound00.cs.umd.edu python3[1875961]: ldapdb [x6] Oct 2 05:22:13 outbound00.cs.umd.edu krb5_child[1878693]: Client 'admin@UMD.EDU' not found in Kerberos database [x3] == outbound01.cs.umd.edu (2 distinct, 8 total) == Oct 2 05:08:18 outbound01.cs.umd.edu python3[4139450]: ldapdb [x7] Oct 2 05:10:25 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. == portal (1 distinct, 72 total) == Oct 2 05:05:31 portal setroubleshoot[97477]: SELinux is preventing /usr/local/bin/traefik from connectto access on the unix_stream_socket /run/podman/podman.sock. For complete SELinux messages run: sealert -l e0a307a3-2c22-4320-8f9d-6a166c45222d [x72] == sentry-docker00.cs.umd.edu (32 distinct, 32 total) == Oct 2 05:13:41 sentry-docker00.cs.umd.edu systemd-udevd[3885094]: link_config: could not get ethtool features for vethe471e7e Oct 2 05:13:41 sentry-docker00.cs.umd.edu systemd-udevd[3885094]: Could not set offload features of vethe471e7e: No such device Oct 2 05:13:42 sentry-docker00.cs.umd.edu systemd-udevd[3885145]: Could not generate persistent MAC address for veth1dba4cf: No such file or directory Oct 2 05:13:42 sentry-docker00.cs.umd.edu systemd-udevd[3885146]: Could not generate persistent MAC address for vetha49bec2: No such file or directory Oct 2 05:13:42 sentry-docker00.cs.umd.edu systemd-udevd[3885149]: Could not generate persistent MAC address for vethb2d20ab: No such file or directory Oct 2 05:13:42 sentry-docker00.cs.umd.edu systemd-udevd[3885150]: Could not generate persistent MAC address for vethb8b3872: No such file or directory Oct 2 05:13:42 sentry-docker00.cs.umd.edu systemd-udevd[3885161]: Could not generate persistent MAC address for veth57a40e0: No such file or directory Oct 2 05:13:42 sentry-docker00.cs.umd.edu systemd-udevd[3885146]: Could not generate persistent MAC address for veth33d7c4d: No such file or directory Oct 2 05:13:42 sentry-docker00.cs.umd.edu systemd-udevd[3885149]: Could not generate persistent MAC address for veth200bc0f: No such file or directory Oct 2 05:13:42 sentry-docker00.cs.umd.edu systemd-udevd[3885145]: Could not generate persistent MAC address for veth7d476cf: No such file or directory Oct 2 05:13:42 sentry-docker00.cs.umd.edu systemd-udevd[3885145]: Could not generate persistent MAC address for veth853fc9c: No such file or directory Oct 2 05:13:42 sentry-docker00.cs.umd.edu systemd-udevd[3885155]: Could not generate persistent MAC address for vethbdfec43: No such file or directory Oct 2 05:33:50 sentry-docker00.cs.umd.edu systemd-udevd[3894713]: Could not generate persistent MAC address for veth9abbb13: No such file or directory Oct 2 05:33:50 sentry-docker00.cs.umd.edu systemd-udevd[3894714]: Could not generate persistent MAC address for vethf9df859: No such file or directory Oct 2 05:33:50 sentry-docker00.cs.umd.edu systemd-udevd[3894739]: Could not generate persistent MAC address for veth1de87f4: No such file or directory Oct 2 05:33:50 sentry-docker00.cs.umd.edu systemd-udevd[3894740]: Could not generate persistent MAC address for vethe27f9fb: No such file or directory Oct 2 05:33:50 sentry-docker00.cs.umd.edu systemd-udevd[3894758]: Could not generate persistent MAC address for vetha45f204: No such file or directory Oct 2 05:33:50 sentry-docker00.cs.umd.edu systemd-udevd[3894756]: Could not generate persistent MAC address for veth59832c0: No such file or directory Oct 2 05:33:50 sentry-docker00.cs.umd.edu systemd-udevd[3894767]: Could not generate persistent MAC address for veth33b710a: No such file or directory Oct 2 05:33:50 sentry-docker00.cs.umd.edu systemd-udevd[3894768]: Could not generate persistent MAC address for veth1bc8901: No such file or directory Oct 2 05:33:50 sentry-docker00.cs.umd.edu systemd-udevd[3894817]: Could not generate persistent MAC address for vethfb1b850: No such file or directory Oct 2 05:33:50 sentry-docker00.cs.umd.edu systemd-udevd[3894818]: Could not generate persistent MAC address for veth62ca774: No such file or directory Oct 2 05:53:58 sentry-docker00.cs.umd.edu systemd-udevd[3904134]: Could not generate persistent MAC address for veth54d227a: No such file or directory Oct 2 05:53:58 sentry-docker00.cs.umd.edu systemd-udevd[3904133]: Could not generate persistent MAC address for vetha08980c: No such file or directory Oct 2 05:53:59 sentry-docker00.cs.umd.edu systemd-udevd[3904159]: Could not generate persistent MAC address for vethca4476b: No such file or directory Oct 2 05:53:59 sentry-docker00.cs.umd.edu systemd-udevd[3904160]: Could not generate persistent MAC address for veth6d362b5: No such file or directory Oct 2 05:53:59 sentry-docker00.cs.umd.edu systemd-udevd[3904179]: Could not generate persistent MAC address for veth8224975: No such file or directory Oct 2 05:53:59 sentry-docker00.cs.umd.edu systemd-udevd[3904178]: Could not generate persistent MAC address for vethadfd839: No such file or directory Oct 2 05:53:59 sentry-docker00.cs.umd.edu systemd-udevd[3904159]: Could not generate persistent MAC address for vethbd7f197: No such file or directory Oct 2 05:53:59 sentry-docker00.cs.umd.edu systemd-udevd[3904180]: Could not generate persistent MAC address for veth8ddd2cc: No such file or directory ... 2 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 2 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 2 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 2 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 2 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 2 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 2 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 2 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 9 total) == Oct 2 05:06:47 submit26-b9-f3 setroubleshoot[535484]: 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 Oct 2 05:06:47 submit26-b9-f3 setroubleshoot[535484]: 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 Oct 2 05:06:47 submit26-b9-f3 setroubleshoot[535484]: 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 Oct 2 05:06:47 submit26-b9-f3 setroubleshoot[535484]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.mPBRNr/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 2 05:06:47 submit26-b9-f3 setroubleshoot[535484]: 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 Oct 2 05:06:47 submit26-b9-f3 setroubleshoot[535484]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.mPBRNr. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 2 05:06:47 submit26-b9-f3 setroubleshoot[535484]: 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 Oct 2 05:06:47 submit26-b9-f3 setroubleshoot[535484]: 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 Oct 2 05:06:47 submit26-b9-f3 setroubleshoot[535484]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68 == submit26-b9-f4 (9 distinct, 9 total) == Oct 2 05:24:50 submit26-b9-f4 setroubleshoot[3421201]: 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 Oct 2 05:24:50 submit26-b9-f4 setroubleshoot[3421201]: 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 Oct 2 05:24:50 submit26-b9-f4 setroubleshoot[3421201]: 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 Oct 2 05:24:51 submit26-b9-f4 setroubleshoot[3421201]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.hzhBop/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 2 05:24:51 submit26-b9-f4 setroubleshoot[3421201]: 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 Oct 2 05:24:51 submit26-b9-f4 setroubleshoot[3421201]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.hzhBop. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 2 05:24:51 submit26-b9-f4 setroubleshoot[3421201]: 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 Oct 2 05:24:51 submit26-b9-f4 setroubleshoot[3421201]: 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 Oct 2 05:24:51 submit26-b9-f4 setroubleshoot[3421201]: 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