Command: /usr/local/sbin/syslog-digest.py Time : 0.0516s Status : exited 0 Output : Syslog digest — 2026-09-23 02:05 EDT Processed 2,711 lines, filtered 2,319 (85%). 392 unknown (194 distinct) from 20 host(s). == atif01.cs.umd.edu (2 distinct, 2 total) == Sep 23 01:20:07 atif01.cs.umd.edu kernel: net_ratelimit: 11 callbacks suppressed Sep 23 01:20:08 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)! == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 23 01:56:17 b0b02.cs.umd.edu rustdesk[66826]: cannot open display: == bale (5 distinct, 86 total) == Sep 23 01:05:20 bale setroubleshoot[1975780]: failed to retrieve rpm info for /dev/nvme0 [x37] Sep 23 01:05:21 bale setroubleshoot[1975780]: 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 23 01:05:23 bale setroubleshoot[1975780]: 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 23 01:05:26 bale setroubleshoot[1975780]: 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 23 01:05:38 bale setroubleshoot[1976408]: 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] == galax (2 distinct, 7 total) == Sep 23 01:10:02 galax systemd[1]: sysstat-collect.service: Condition check process exited, code=dumped, status=11/SEGV [x6] Sep 23 01:19:29 galax systemd[1]: man-db.service: Main process exited, code=dumped, status=11/SEGV == idm00 (1 distinct, 1 total) == Sep 23 01:54:26 idm00 named[4166701]: client @0x7f11a406bb48 10.73.240.42#51549: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 23 01:37:54 idmp0 named[1598691]: client @0x7f2d2c0368e8 10.73.240.43#55896: update '73.10.in-addr.arpa/IN' denied == irb2156 (4 distinct, 4 total) == Sep 23 01:04:32 irb2156 systemd-resolved[3402]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 10.73.244.13. Sep 23 01:04:53 irb2156 systemd-resolved[3402]: Using degraded feature set TCP instead of UDP for DNS server 10.73.244.13. Sep 23 01:54:18 irb2156 systemd-resolved[3402]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 10.73.244.14. Sep 23 01:54:38 irb2156 systemd-resolved[3402]: Using degraded feature set TCP instead of UDP for DNS server 10.73.244.14. == itmon02 (1 distinct, 3 total) == Sep 23 01:28:22 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == krispykreme.cs.umd.edu (3 distinct, 4 total) == Sep 23 01:11:05 krispykreme.cs.umd.edu sshd-session[1431483]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2] Sep 23 01:11:07 krispykreme.cs.umd.edu sshd-session[1431483]: Error in Duo login for 'larry' from 71.191.93.172 Sep 23 01:11:07 krispykreme.cs.umd.edu sshd-session[1431481]: error: PAM: Authentication failure for larry from 71.191.93.172 == newhonors2 (1 distinct, 24 total) == Sep 23 01:13:03 newhonors2 dhcpcd[3020162]: dhcpcd is not running [x24] == ntop00 (98 distinct, 138 total) == Sep 23 01:06:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 11113/11113, ET: 60) *** Sep 23 01:06:02 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 73/73, ET: 61) *** Sep 23 01:08:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 23 01:08:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 11295/11295, ET: 0) *** Sep 23 01:08:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 23 01:08:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 86/86, ET: 0) *** Sep 23 01:08:02 ntop00 setroubleshoot[1311260]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l af369431-37df-4ac9-9292-5066d38787e5 [x11] Sep 23 01:08:02 ntop00 setroubleshoot[1311260]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 244a2465-7b27-44c9-bda6-9cd4f2dd6cbc [x11] Sep 23 01:08:02 ntop00 setroubleshoot[1311260]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11] Sep 23 01:08:02 ntop00 setroubleshoot[1311260]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l ba3a59c0-2cfe-4a84-9a21-86479d1517da [x11] Sep 23 01:10:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 23 01:10:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 23 01:11:04 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 11341/11341, ET: 63) *** Sep 23 01:11:05 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 83/83, ET: 64) *** Sep 23 01:13:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 23 01:13:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 55/55, ET: 0) *** Sep 23 01:13:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 23 01:13:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 10890/10890, ET: 0) *** Sep 23 01:15:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 23 01:15:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 23 01:16:05 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 10977/10977, ET: 64) *** Sep 23 01:16:05 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 71/71, ET: 64) *** Sep 23 01:18:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 23 01:18:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 9351/9351, ET: 0) *** Sep 23 01:18:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 23 01:18:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 86/86, ET: 0) *** Sep 23 01:20:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 23 01:20:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 23 01:20:44 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 7677/7677, ET: 43) *** Sep 23 01:20:44 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 72/72, ET: 43) *** ... 68 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 23 01:09:09 outbound00.cs.umd.edu python3[2897952]: ldapdb [x6] == outbound01.cs.umd.edu (3 distinct, 8 total) == Sep 23 01:10:52 outbound01.cs.umd.edu krb5_child[990816]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 23 01:13:06 outbound01.cs.umd.edu python3[991231]: ldapdb [x6] Sep 23 01:15:10 outbound01.cs.umd.edu sshd-session[991581]: error: Protocol major versions differ: 2 vs. 1 == sentry-docker00.cs.umd.edu (40 distinct, 40 total) == Sep 23 01:22:31 sentry-docker00.cs.umd.edu systemd-udevd[1860604]: link_config: could not get ethtool features for vetheb1c9ae Sep 23 01:22:31 sentry-docker00.cs.umd.edu systemd-udevd[1860604]: Could not set offload features of vetheb1c9ae: No such device Sep 23 01:22:31 sentry-docker00.cs.umd.edu systemd-udevd[1860698]: link_config: could not get ethtool features for veth1647e4c Sep 23 01:22:31 sentry-docker00.cs.umd.edu systemd-udevd[1860698]: Could not set offload features of veth1647e4c: No such device Sep 23 01:22:32 sentry-docker00.cs.umd.edu systemd-udevd[1860723]: Could not generate persistent MAC address for vethc6733c4: No such file or directory Sep 23 01:22:32 sentry-docker00.cs.umd.edu systemd-udevd[1860724]: Could not generate persistent MAC address for vetha292563: No such file or directory Sep 23 01:22:32 sentry-docker00.cs.umd.edu systemd-udevd[1860749]: Could not generate persistent MAC address for vethb93c44f: No such file or directory Sep 23 01:22:32 sentry-docker00.cs.umd.edu systemd-udevd[1860750]: Could not generate persistent MAC address for veth3c74f72: No such file or directory Sep 23 01:22:32 sentry-docker00.cs.umd.edu systemd-udevd[1860768]: Could not generate persistent MAC address for vethb2082fe: No such file or directory Sep 23 01:22:32 sentry-docker00.cs.umd.edu systemd-udevd[1860762]: Could not generate persistent MAC address for vetha7f93f6: No such file or directory Sep 23 01:22:32 sentry-docker00.cs.umd.edu systemd-udevd[1860778]: Could not generate persistent MAC address for veth742c578: No such file or directory Sep 23 01:22:32 sentry-docker00.cs.umd.edu systemd-udevd[1860777]: Could not generate persistent MAC address for veth939a9b0: No such file or directory Sep 23 01:22:32 sentry-docker00.cs.umd.edu systemd-udevd[1860826]: Could not generate persistent MAC address for veth4277ff6: No such file or directory Sep 23 01:22:32 sentry-docker00.cs.umd.edu systemd-udevd[1860827]: Could not generate persistent MAC address for vethd7d8a64: No such file or directory Sep 23 01:42:40 sentry-docker00.cs.umd.edu systemd-udevd[1870173]: link_config: could not get ethtool features for veth4277ff6 Sep 23 01:42:40 sentry-docker00.cs.umd.edu systemd-udevd[1870173]: Could not set offload features of veth4277ff6: No such device Sep 23 01:42:40 sentry-docker00.cs.umd.edu systemd-udevd[1870199]: Could not generate persistent MAC address for veth89cafb9: No such file or directory Sep 23 01:42:40 sentry-docker00.cs.umd.edu systemd-udevd[1870198]: Could not generate persistent MAC address for vethaf33028: No such file or directory Sep 23 01:42:40 sentry-docker00.cs.umd.edu systemd-udevd[1870202]: Could not generate persistent MAC address for veth217e668: No such file or directory Sep 23 01:42:40 sentry-docker00.cs.umd.edu systemd-udevd[1870215]: Could not generate persistent MAC address for veth3affe14: No such file or directory Sep 23 01:42:40 sentry-docker00.cs.umd.edu systemd-udevd[1870222]: Could not generate persistent MAC address for veth3c5bf4e: No such file or directory Sep 23 01:42:40 sentry-docker00.cs.umd.edu systemd-udevd[1870205]: Could not generate persistent MAC address for veth70f2e12: No such file or directory Sep 23 01:42:40 sentry-docker00.cs.umd.edu systemd-udevd[1870228]: Could not generate persistent MAC address for veth9a859d3: No such file or directory Sep 23 01:42:40 sentry-docker00.cs.umd.edu systemd-udevd[1870229]: Could not generate persistent MAC address for vethb57f498: No such file or directory Sep 23 01:42:40 sentry-docker00.cs.umd.edu systemd-udevd[1870260]: Could not generate persistent MAC address for veth12ee091: No such file or directory Sep 23 01:42:40 sentry-docker00.cs.umd.edu systemd-udevd[1870269]: Could not generate persistent MAC address for veth0fb164b: No such file or directory Sep 23 02:02:48 sentry-docker00.cs.umd.edu systemd-udevd[1879579]: link_config: could not get ethtool features for vethaf33028 Sep 23 02:02:48 sentry-docker00.cs.umd.edu systemd-udevd[1879579]: Could not set offload features of vethaf33028: No such device Sep 23 02:02:48 sentry-docker00.cs.umd.edu systemd-udevd[1879580]: link_config: could not set ethtool features for veth9a859d3 Sep 23 02:02:48 sentry-docker00.cs.umd.edu systemd-udevd[1879580]: Could not set offload features of veth9a859d3: Operation not permitted ... 10 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 23 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 23 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 23 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 23 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 23 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 23 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 23 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 2 total) == Sep 23 01:18:11 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f2 (1 distinct, 1 total) == Sep 23 01:18:08 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (10 distinct, 10 total) == Sep 23 01:06:44 submit26-b9-f3 setroubleshoot[2650450]: 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 23 01:06:44 submit26-b9-f3 setroubleshoot[2650450]: 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 23 01:06:44 submit26-b9-f3 setroubleshoot[2650450]: 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 23 01:06:44 submit26-b9-f3 setroubleshoot[2650450]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.xPP0l4/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 23 01:06:44 submit26-b9-f3 setroubleshoot[2650450]: 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 23 01:06:44 submit26-b9-f3 setroubleshoot[2650450]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xPP0l4. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 23 01:06:44 submit26-b9-f3 setroubleshoot[2650450]: 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 23 01:06:44 submit26-b9-f3 setroubleshoot[2650450]: 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 23 01:06:44 submit26-b9-f3 setroubleshoot[2650450]: 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 23 02:00:57 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f4 (11 distinct, 15 total) == Sep 23 01:13:09 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL Sep 23 01:24:49 submit26-b9-f4 setroubleshoot[1947179]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb [x2] Sep 23 01:24:49 submit26-b9-f4 setroubleshoot[1947179]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4 [x2] Sep 23 01:24:49 submit26-b9-f4 setroubleshoot[1947179]: 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 23 01:24:49 submit26-b9-f4 setroubleshoot[1947179]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.t0URFx/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 23 01:24:49 submit26-b9-f4 setroubleshoot[1947179]: 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 23 01:24:49 submit26-b9-f4 setroubleshoot[1947179]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.t0URFx. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 23 01:24:49 submit26-b9-f4 setroubleshoot[1947179]: 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 [x2] Sep 23 01:24:49 submit26-b9-f4 setroubleshoot[1947179]: 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 23 01:24:49 submit26-b9-f4 setroubleshoot[1947179]: 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 [x2] Sep 23 01:24:50 submit26-b9-f4 setroubleshoot[1947179]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.nbju4q. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c == teaching-awards (1 distinct, 1 total) == Sep 23 01:43:41 teaching-awards krb5_child[1387229]: Client 'admin@UMD.EDU' not found in Kerberos database