Command: /usr/local/sbin/syslog-digest.py Time : 0.0518s Status : exited 0 Output : Syslog digest — 2026-09-20 03:05 EDT Processed 2,618 lines, filtered 2,111 (80%). 507 unknown (180 distinct) from 16 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 20 02:51:46 b0b02.cs.umd.edu rustdesk[3106834]: cannot open display: == bale (5 distinct, 91 total) == Sep 20 02:05:19 bale setroubleshoot[1037153]: failed to retrieve rpm info for /dev/nvme0 [x39] Sep 20 02:05:19 bale setroubleshoot[1037153]: 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 20 02:05:22 bale setroubleshoot[1037153]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13] Sep 20 02:05:25 bale setroubleshoot[1037153]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x11] Sep 20 02:05:37 bale setroubleshoot[1037781]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x15] == cheezit.cs.umd.edu (3 distinct, 4 total) == Sep 20 02:27:51 cheezit.cs.umd.edu sshd-session[1097677]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2] Sep 20 02:27:52 cheezit.cs.umd.edu sshd-session[1097677]: Error in Duo login for 'larry' from 71.191.93.172 Sep 20 02:27:52 cheezit.cs.umd.edu sshd-session[1097675]: error: PAM: Authentication failure for larry from 71.191.93.172 == csfw00a (1 distinct, 118 total) == Sep 20 02:04:33 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x118] == idm00 (1 distinct, 1 total) == Sep 20 02:53:59 idm00 named[4166701]: client @0x7f11a940bc18 10.73.240.42#50189: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 20 02:37:57 idmp0 named[1598691]: client @0x7f2d08d9fa18 10.73.240.43#53053: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 7 total) == Sep 20 02:14:04 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x7] == munin (2 distinct, 12 total) == Sep 20 02:08:48 munin sudo[572901]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Sep 20 02:08:48 munin sudo[572901]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == newhonors2 (1 distinct, 24 total) == Sep 20 02:13:02 newhonors2 dhcpcd[2885098]: dhcpcd is not running [x24] == ntop00 (101 distinct, 141 total) == Sep 20 02:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 442) *** Sep 20 02:05:22 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 5757/5757, ET: 21) *** Sep 20 02:05:22 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 49/49, ET: 21) *** Sep 20 02:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 20 02:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 5629/5629, ET: 0) *** Sep 20 02:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 20 02:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 49/49, ET: 0) *** Sep 20 02:08:02 ntop00 setroubleshoot[745959]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x11] Sep 20 02:08:02 ntop00 setroubleshoot[745959]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x11] Sep 20 02:08:02 ntop00 setroubleshoot[745959]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11] Sep 20 02:08:02 ntop00 setroubleshoot[745959]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x11] Sep 20 02:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 20 02:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 20 02:10:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 5564/5564, ET: 20) *** Sep 20 02:10:22 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 56/56, ET: 21) *** Sep 20 02:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 20 02:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 5625/5625, ET: 0) *** Sep 20 02:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 20 02:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 52/52, ET: 0) *** Sep 20 02:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 20 02:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 20 02:15:25 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 6415/6415, ET: 24) *** Sep 20 02:15:25 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 59/59, ET: 24) *** Sep 20 02:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 20 02:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 6410/6410, ET: 0) *** Sep 20 02:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 20 02:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 58/58, ET: 0) *** Sep 20 02:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) *** Sep 20 02:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) *** Sep 20 02:20:24 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 448, QN: 5744/5744, ET: 23) *** ... 71 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 20 02:09:09 outbound00.cs.umd.edu python3[1891156]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 20 02:13:07 outbound01.cs.umd.edu python3[4150586]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023052]: link_config: could not get ethtool features for vethea6ed10 Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023052]: Could not set offload features of vethea6ed10: No such device Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023076]: Could not generate persistent MAC address for vethc90f824: No such file or directory Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023077]: Could not generate persistent MAC address for vethf5d320c: No such file or directory Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023103]: Could not generate persistent MAC address for veth9f332ed: No such file or directory Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023102]: Could not generate persistent MAC address for veth8b62113: No such file or directory Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023106]: Could not generate persistent MAC address for vethe6f8718: No such file or directory Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023103]: Could not generate persistent MAC address for vethc3e4bac: No such file or directory Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023111]: Could not generate persistent MAC address for vethd15a99f: No such file or directory Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023128]: Could not generate persistent MAC address for vethf98393d: No such file or directory Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023166]: Could not generate persistent MAC address for veth0c9f9ef: No such file or directory Sep 20 02:13:08 sentry-docker00.cs.umd.edu systemd-udevd[4023171]: Could not generate persistent MAC address for veth47f5349: No such file or directory Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032760]: link_config: could not get ethtool features for veth8b62113 Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032760]: Could not set offload features of veth8b62113: No such device Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032793]: Could not generate persistent MAC address for veth66999bf: No such file or directory Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032794]: Could not generate persistent MAC address for veth4a6a482: No such file or directory Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032797]: Could not generate persistent MAC address for veth403e6e4: No such file or directory Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032798]: Could not generate persistent MAC address for veth1ebf4dc: No such file or directory Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032821]: Could not generate persistent MAC address for veth1a87588: No such file or directory Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032822]: Could not generate persistent MAC address for veth2d130fa: No such file or directory Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032831]: Could not generate persistent MAC address for veth8fde257: No such file or directory Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032839]: Could not generate persistent MAC address for vethe67695f: No such file or directory Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032861]: Could not generate persistent MAC address for vethe5523a8: No such file or directory Sep 20 02:33:16 sentry-docker00.cs.umd.edu systemd-udevd[4032862]: Could not generate persistent MAC address for vethf24ee46: No such file or directory Sep 20 02:53:24 sentry-docker00.cs.umd.edu systemd-udevd[4042411]: link_config: could not get ethtool features for vethe67695f Sep 20 02:53:24 sentry-docker00.cs.umd.edu systemd-udevd[4042411]: Could not set offload features of vethe67695f: No such device Sep 20 02:53:24 sentry-docker00.cs.umd.edu systemd-udevd[4042446]: Could not generate persistent MAC address for vethda77f66: No such file or directory Sep 20 02:53:24 sentry-docker00.cs.umd.edu systemd-udevd[4042447]: Could not generate persistent MAC address for veth7126878: No such file or directory Sep 20 02:53:24 sentry-docker00.cs.umd.edu systemd-udevd[4042450]: Could not generate persistent MAC address for vethf1fd103: No such file or directory Sep 20 02:53:24 sentry-docker00.cs.umd.edu systemd-udevd[4042451]: Could not generate persistent MAC address for vetha8813ef: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 20 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 20 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 20 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 20 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 20 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 20 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 20 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (9 distinct, 9 total) == Sep 20 02:25:53 submit26-b9-f1 setroubleshoot[2561421]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c Sep 20 02:25:53 submit26-b9-f1 setroubleshoot[2561421]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36 Sep 20 02:25:53 submit26-b9-f1 setroubleshoot[2561421]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6 Sep 20 02:25:54 submit26-b9-f1 setroubleshoot[2561421]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.aRSEiE/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 20 02:25:54 submit26-b9-f1 setroubleshoot[2561421]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee Sep 20 02:25:54 submit26-b9-f1 setroubleshoot[2561421]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.aRSEiE. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 20 02:25:54 submit26-b9-f1 setroubleshoot[2561421]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d Sep 20 02:25:54 submit26-b9-f1 setroubleshoot[2561421]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9 Sep 20 02:25:54 submit26-b9-f1 setroubleshoot[2561421]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848 == submit26-b9-f2 (9 distinct, 12 total) == Sep 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 Sep 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a Sep 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 [x2] Sep 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.lRft7C/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2] Sep 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 [x2] Sep 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.lRft7C. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885 Sep 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af Sep 20 02:06:49 submit26-b9-f2 setroubleshoot[1675309]: 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