Command: /usr/local/sbin/syslog-digest.py Time : 0.0417s Status : exited 0 Output : Syslog digest — 2026-09-24 22:05 EDT Processed 1,506 lines, filtered 1,241 (82%). 265 unknown (179 distinct) from 17 host(s). == abadi-computer (2 distinct, 3 total) == Sep 24 21:47:11 abadi-computer krb5_child[648070]: Preauthentication failed [x2] Sep 24 21:47:14 abadi-computer sshd[648033]: error: PAM: Authentication failure for poojan from 10.206.17.253 == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 24 21:59:09 b0b02.cs.umd.edu rustdesk[740960]: cannot open display: == cheezit.cs.umd.edu (5 distinct, 9 total) == Sep 24 21:07:44 cheezit.cs.umd.edu sshd-session[2795609]: pam_access(sshd:auth): access denied for user `heng' from `173.73.25.237' Sep 24 21:57:46 cheezit.cs.umd.edu sshd-session[2807096]: pam_access(sshd:auth): access denied for user `bahar' from `173.66.227.191' [x5] Sep 24 21:57:55 cheezit.cs.umd.edu krb5_child[2807114]: Preauthentication failed Sep 24 21:57:55 cheezit.cs.umd.edu sshd-session[2807094]: error: PAM: Authentication failure for bahar from 173.66.227.191 Sep 24 21:59:04 cheezit.cs.umd.edu sshd-session[2807117]: Failed Duo login for 'bahar' from 173.66.227.191 == idm00 (1 distinct, 1 total) == Sep 24 21:54:06 idm00 named[4166701]: client @0x7f11a93cbc38 10.73.240.42#54979: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 24 21:39:51 idmp0 named[1598691]: client @0x7f2d304493e8 10.73.240.43#54146: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Sep 24 21:18:08 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == krispykreme.cs.umd.edu (1 distinct, 1 total) == Sep 24 21:54:27 krispykreme.cs.umd.edu sshd-session[2191693]: pam_access(sshd:auth): access denied for user `amchilds' from `108.56.227.155' == newhonors2 (1 distinct, 24 total) == Sep 24 21:13:03 newhonors2 dhcpcd[3110059]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Sep 24 21:05:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) *** Sep 24 21:05:02 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 52/52, ET: 1) *** Sep 24 21:05:09 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 5323/5323, ET: 8) *** Sep 24 21:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 24 21:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 5465/5465, ET: 0) *** Sep 24 21:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 24 21:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 49/49, ET: 0) *** Sep 24 21:10:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 24 21:10:02 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 24 21:10:02 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 53/53, ET: 0) *** Sep 24 21:10:09 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 5798/5798, ET: 8) *** Sep 24 21:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 24 21:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 57/57, ET: 0) *** Sep 24 21:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 24 21:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 5188/5188, ET: 0) *** Sep 24 21:15:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 24 21:15:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 50/50, ET: 0) *** Sep 24 21:15:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 24 21:15:08 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 4946/4946, ET: 7) *** Sep 24 21:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 24 21:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 52/52, ET: 0) *** Sep 24 21:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 24 21:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 4762/4762, ET: 0) *** Sep 24 21:20:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** Sep 24 21:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** Sep 24 21:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 328, QN: 52/52, ET: 0) *** Sep 24 21:20:08 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 328, QN: 4749/4749, ET: 7) *** Sep 24 21:23:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 329) *** Sep 24 21:23:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 329, QN: 48/48, ET: 0) *** Sep 24 21:23:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 329) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 24 21:09:09 outbound00.cs.umd.edu python3[3547095]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 24 21:13:06 outbound01.cs.umd.edu python3[1613775]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 24 21:20:45 sentry-docker00.cs.umd.edu systemd-udevd[3104844]: link_config: could not get ethtool features for vethd62ad16 Sep 24 21:20:45 sentry-docker00.cs.umd.edu systemd-udevd[3104844]: Could not set offload features of vethd62ad16: No such device Sep 24 21:20:45 sentry-docker00.cs.umd.edu systemd-udevd[3104846]: link_config: could not get ethtool features for veth486e8d4 Sep 24 21:20:45 sentry-docker00.cs.umd.edu systemd-udevd[3104846]: Could not set offload features of veth486e8d4: No such device Sep 24 21:20:46 sentry-docker00.cs.umd.edu systemd-udevd[3104876]: Could not generate persistent MAC address for vethb91daa5: No such file or directory Sep 24 21:20:46 sentry-docker00.cs.umd.edu systemd-udevd[3104877]: Could not generate persistent MAC address for vethc335cee: No such file or directory Sep 24 21:20:46 sentry-docker00.cs.umd.edu systemd-udevd[3104896]: Could not generate persistent MAC address for veth23ee1de: No such file or directory Sep 24 21:20:46 sentry-docker00.cs.umd.edu systemd-udevd[3104883]: Could not generate persistent MAC address for veth9798c8b: No such file or directory Sep 24 21:20:46 sentry-docker00.cs.umd.edu systemd-udevd[3104904]: Could not generate persistent MAC address for vetha7bdbdb: No such file or directory Sep 24 21:20:46 sentry-docker00.cs.umd.edu systemd-udevd[3104905]: Could not generate persistent MAC address for veth2aa0574: No such file or directory Sep 24 21:20:46 sentry-docker00.cs.umd.edu systemd-udevd[3104930]: Could not generate persistent MAC address for vethc12a02a: No such file or directory Sep 24 21:20:46 sentry-docker00.cs.umd.edu systemd-udevd[3104931]: Could not generate persistent MAC address for vetha6c55a3: No such file or directory Sep 24 21:20:46 sentry-docker00.cs.umd.edu systemd-udevd[3104956]: Could not generate persistent MAC address for veth20b6b98: No such file or directory Sep 24 21:20:46 sentry-docker00.cs.umd.edu systemd-udevd[3104957]: Could not generate persistent MAC address for veth91540cd: No such file or directory Sep 24 21:40:54 sentry-docker00.cs.umd.edu systemd-udevd[3114502]: link_config: could not get ethtool features for vethb91daa5 Sep 24 21:40:54 sentry-docker00.cs.umd.edu systemd-udevd[3114502]: Could not set offload features of vethb91daa5: No such device Sep 24 21:40:54 sentry-docker00.cs.umd.edu systemd-udevd[3114568]: Could not generate persistent MAC address for vetha8871b4: No such file or directory Sep 24 21:40:54 sentry-docker00.cs.umd.edu systemd-udevd[3114569]: Could not generate persistent MAC address for veth0be14cb: No such file or directory Sep 24 21:40:54 sentry-docker00.cs.umd.edu systemd-udevd[3114572]: Could not generate persistent MAC address for veth1fe7bd9: No such file or directory Sep 24 21:40:54 sentry-docker00.cs.umd.edu systemd-udevd[3114573]: Could not generate persistent MAC address for veth68f670c: No such file or directory Sep 24 21:40:54 sentry-docker00.cs.umd.edu systemd-udevd[3114590]: Could not generate persistent MAC address for veth185bd39: No such file or directory Sep 24 21:40:54 sentry-docker00.cs.umd.edu systemd-udevd[3114577]: Could not generate persistent MAC address for vethd0bf963: No such file or directory Sep 24 21:40:54 sentry-docker00.cs.umd.edu systemd-udevd[3114568]: Could not generate persistent MAC address for vethf830deb: No such file or directory Sep 24 21:40:54 sentry-docker00.cs.umd.edu systemd-udevd[3114581]: Could not generate persistent MAC address for veth23f392a: No such file or directory Sep 24 21:40:54 sentry-docker00.cs.umd.edu systemd-udevd[3114577]: Could not generate persistent MAC address for vethf2cfd00: No such file or directory Sep 24 21:40:54 sentry-docker00.cs.umd.edu systemd-udevd[3114568]: Could not generate persistent MAC address for veth74ae08d: No such file or directory Sep 24 22:01:02 sentry-docker00.cs.umd.edu systemd-udevd[3123594]: link_config: could not get ethtool features for veth185bd39 Sep 24 22:01:02 sentry-docker00.cs.umd.edu systemd-udevd[3123594]: Could not set offload features of veth185bd39: No such device Sep 24 22:01:02 sentry-docker00.cs.umd.edu systemd-udevd[3123666]: Could not generate persistent MAC address for vethddc7173: No such file or directory Sep 24 22:01:02 sentry-docker00.cs.umd.edu systemd-udevd[3123667]: Could not generate persistent MAC address for vethb8a1144: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 24 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 24 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 24 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 24 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 24 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 24 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 24 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 24 21:19:56 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f2 (1 distinct, 3 total) == Sep 24 21:25:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f3 (10 distinct, 18 total) == Sep 24 21:05:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Sep 24 21:06:45 submit26-b9-f3 setroubleshoot[3244297]: 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 24 21:06:45 submit26-b9-f3 setroubleshoot[3244297]: 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 24 21:06:45 submit26-b9-f3 setroubleshoot[3244297]: 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 [x2] Sep 24 21:06:45 submit26-b9-f3 setroubleshoot[3244297]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.b41lI4/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f [x2] Sep 24 21:06:45 submit26-b9-f3 setroubleshoot[3244297]: 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 [x2] Sep 24 21:06:45 submit26-b9-f3 setroubleshoot[3244297]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.b41lI4. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 24 21:06:45 submit26-b9-f3 setroubleshoot[3244297]: 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 24 21:06:45 submit26-b9-f3 setroubleshoot[3244297]: 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 24 21:06:45 submit26-b9-f3 setroubleshoot[3244297]: 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 (11 distinct, 15 total) == Sep 24 21:20:42 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Sep 24 21:24:48 submit26-b9-f4 setroubleshoot[2358530]: 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 24 21:24:48 submit26-b9-f4 setroubleshoot[2358530]: 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 24 21:24:48 submit26-b9-f4 setroubleshoot[2358530]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d [x2] Sep 24 21:24:48 submit26-b9-f4 setroubleshoot[2358530]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.RY1Y7h/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 24 21:24:48 submit26-b9-f4 setroubleshoot[2358530]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e [x2] Sep 24 21:24:48 submit26-b9-f4 setroubleshoot[2358530]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.RY1Y7h. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 24 21:24:48 submit26-b9-f4 setroubleshoot[2358530]: 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 24 21:24:48 submit26-b9-f4 setroubleshoot[2358530]: 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 [x2] Sep 24 21:24:48 submit26-b9-f4 setroubleshoot[2358530]: 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 24 21:24:48 submit26-b9-f4 setroubleshoot[2358530]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.UbzAFT/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0