Command: /usr/local/sbin/syslog-digest.py Time : 0.5084s Status : exited 0 Output : Syslog digest — 2026-08-03 01:05 EDT Processed 4,325 lines, filtered 3,504 (81%). 821 unknown (113 distinct) from 29 host(s). == abuse (1 distinct, 347 total) == Aug 3 00:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x347] == b0b02.cs.umd.edu (1 distinct, 1 total) == Aug 3 00:42:47 b0b02.cs.umd.edu rustdesk[2306917]: cannot open display: == contest (1 distinct, 33 total) == Aug 3 00:06:24 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x33] == csfw00a (2 distinct, 238 total) == Aug 3 00:04:33 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x230] Aug 3 00:50:01 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x8] == cskayako (2 distinct, 2 total) == Aug 3 00:06:40 cskayako setroubleshoot[1855218]: SELinux is preventing /usr/bin/php from add_name access on the directory /var/www/html/(null). For complete SELinux messages run: sealert -l 5239c113-abc1-4953-a9c0-21d695a0d1bb Aug 3 00:06:40 cskayako setroubleshoot[1855218]: SELinux is preventing /usr/bin/php from create access on the file /var/www/html/(null). For complete SELinux messages run: sealert -l cacf8f36-45b0-4374-9a33-d15de767aae7 == grades01.cs.umd.edu (3 distinct, 4 total) == Aug 3 00:10:14 grades01.cs.umd.edu systemd[1]: New main PID 28327 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 3 00:10:37 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 3 00:10:53 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3737 which is not our child. We'll most likely not notice when it exits. == idm00 (1 distinct, 1 total) == Aug 3 00:51:15 idm00 named[1455]: client @0x7f33041f95f8 10.73.240.42#62269: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 3 00:36:01 idmp0 named[5198]: client @0x7f98fc0059e8 10.73.240.43#62342: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 30 total) == Aug 3 00:08:16 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x30] == jubjub.cs.umd.edu (3 distinct, 4 total) == Aug 3 00:10:13 jubjub.cs.umd.edu systemd[1]: New main PID 1380598 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 3 00:10:32 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 3 00:10:41 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1388106 which is not our child. We'll most likely not notice when it exits. == mirrors.cs.umd.edu (3 distinct, 4 total) == Aug 3 00:10:12 mirrors.cs.umd.edu systemd[1]: New main PID 27204 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 3 00:10:30 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 3 00:10:44 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1901 which is not our child. We'll most likely not notice when it exits. == misty.cs.umd.edu (3 distinct, 4 total) == Aug 3 00:10:14 misty.cs.umd.edu systemd[1]: New main PID 21671 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 3 00:10:34 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 3 00:10:50 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 29369 which is not our child. We'll most likely not notice when it exits. == netman.cs.umd.edu (6 distinct, 9 total) == Aug 3 00:08:40 netman.cs.umd.edu krb5_child[101731]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Aug 3 00:08:44 netman.cs.umd.edu sshd[101728]: error: PAM: Authentication failure for admin from 34.53.184.22 Aug 3 00:09:30 netman.cs.umd.edu sshd[101766]: error: Protocol major versions differ: 2 vs. 1 Aug 3 00:29:59 netman.cs.umd.edu setroubleshoot[107820]: SELinux is preventing /usr/bin/gpg from read access on the file gpg.conf. For complete SELinux messages run: sealert -l 019ad1da-a874-4814-8037-3b3e5f413ad2 Aug 3 00:30:00 netman.cs.umd.edu setroubleshoot[107820]: SELinux is preventing /usr/bin/gpg from open access on the file /root/.gnupg/gpg.conf. For complete SELinux messages run: sealert -l cb54177e-d44c-46a1-b246-5c0bbb8343be Aug 3 00:30:03 netman.cs.umd.edu setroubleshoot[107820]: SELinux is preventing /usr/bin/gpg from getattr access on the file /root/.gnupg/gpg.conf. For complete SELinux messages run: sealert -l fbba2e30-b7ab-491c-9ec6-f553e9ef72af == networkvm01.cs.umd.edu (10 distinct, 12 total) == Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from write access on the directory /(null). For complete SELinux messages run: sealert -l 8ead1354-ae8a-4a17-bb3f-146ebf6c892c Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from add_name access on the directory /(null). For complete SELinux messages run: sealert -l f9b51e91-5dbc-455f-88c2-f0746a2f0f4c Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from create access on the file /(null). For complete SELinux messages run: sealert -l af0a60e6-c449-4bdd-bfb8-c69b58472884 [x2] Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from link access on the file /(null). For complete SELinux messages run: sealert -l 3df452f6-4d9e-4e38-946b-ea8e1edd356c [x2] Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from remove_name access on the directory .#lk0x00005572abe56ed0.networkvm01.cs.umd.edu.3720625x. For complete SELinux messages run: sealert -l fcac71c9-c7c0-45a9-9dc2-a8dcbeccfc75 Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from unlink access on the file .#lk0x00005572abe56ed0.networkvm01.cs.umd.edu.3720625x. For complete SELinux messages run: sealert -l a672ebb7-fa69-419c-b1f0-fb386b8b48a6 Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from write access on the directory /(null). For complete SELinux messages run: sealert -l fec9104e-d27a-4fd4-9872-6b17088c2951 Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 26718b2a-493d-457d-818c-244bd8d4ec9d Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from remove_name access on the directory .#lk0x000055a87f760ee0.networkvm01.cs.umd.edu.3720673x. For complete SELinux messages run: sealert -l 80e6efe4-93f3-4219-8132-b2b52db1f517 Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from unlink access on the file .#lk0x000055a87f760ee0.networkvm01.cs.umd.edu.3720673x. For complete SELinux messages run: sealert -l a672ebb7-fa69-419c-b1f0-fb386b8b48a6 == newhonors2 (1 distinct, 24 total) == Aug 3 00:13:03 newhonors2 dhcpcd[656804]: dhcpcd is not running [x24] == openrepo (1 distinct, 1 total) == Aug 3 00:41:53 openrepo (nin-node)[1013822]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS == outbound00.cs.umd.edu (1 distinct, 6 total) == Aug 3 00:09:09 outbound00.cs.umd.edu python3[2309721]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 3 00:13:06 outbound01.cs.umd.edu python3[342927]: ldapdb [x6] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715535]: Could not generate persistent MAC address for veth68614a9: No such file or directory Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715536]: Could not generate persistent MAC address for veth30806ff: No such file or directory Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715539]: Could not generate persistent MAC address for veth126a2a4: No such file or directory Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715540]: Could not generate persistent MAC address for vethacef841: No such file or directory Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715535]: Could not generate persistent MAC address for veth8446906: No such file or directory Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715548]: Could not generate persistent MAC address for vetha7b861d: No such file or directory Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715565]: Could not generate persistent MAC address for veth7bbb21e: No such file or directory Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715566]: Could not generate persistent MAC address for veth1b29e05: No such file or directory Aug 3 00:17:13 sentry-docker00.cs.umd.edu systemd-udevd[716354]: Could not generate persistent MAC address for veth9aeeb54: No such file or directory Aug 3 00:17:13 sentry-docker00.cs.umd.edu systemd-udevd[716355]: Could not generate persistent MAC address for veth8276c9d: No such file or directory Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[724997]: Could not generate persistent MAC address for vetha6216c5: No such file or directory Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[724998]: Could not generate persistent MAC address for vethbe5de8b: No such file or directory Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[725001]: Could not generate persistent MAC address for vethf85b066: No such file or directory Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[725002]: Could not generate persistent MAC address for vethd80fae6: No such file or directory Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[725013]: Could not generate persistent MAC address for veth77b1ba2: No such file or directory Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[725003]: Could not generate persistent MAC address for veth7907498: No such file or directory Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[725027]: Could not generate persistent MAC address for veth18631fe: No such file or directory Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[725028]: Could not generate persistent MAC address for vethfec1efc: No such file or directory Aug 3 00:37:21 sentry-docker00.cs.umd.edu systemd-udevd[725826]: Could not generate persistent MAC address for veth1acd6d7: No such file or directory Aug 3 00:37:21 sentry-docker00.cs.umd.edu systemd-udevd[725827]: Could not generate persistent MAC address for veth444609e: No such file or directory Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734293]: link_config: could not get ethtool features for veth77b1ba2 Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734293]: Could not set offload features of veth77b1ba2: No such device Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734317]: link_config: could not get ethtool features for vetha6216c5 Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734317]: Could not set offload features of vetha6216c5: No such device Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734391]: Could not generate persistent MAC address for veth8e1edee: No such file or directory Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734392]: Could not generate persistent MAC address for vethb4d9f82: No such file or directory Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734410]: Could not generate persistent MAC address for veth541170d: No such file or directory Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734416]: Could not generate persistent MAC address for veth72fbff0: No such file or directory Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734419]: Could not generate persistent MAC address for veth3b2525c: No such file or directory Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734421]: Could not generate persistent MAC address for veth8c2b943: No such file or directory ... 4 more distinct messages not shown == strawberry (3 distinct, 9 total) == Aug 3 00:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6] Aug 3 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] Aug 3 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing. == submit10-cln25 (3 distinct, 4 total) == Aug 3 00:10:11 submit10-cln25 systemd: New main PID 27361 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 3 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing. Aug 3 00:10:36 submit10-cln25 systemd: pmlogger.service: Supervising process 1893 which is not our child. We'll most likely not notice when it exits. == submit26-b9-2 (1 distinct, 3 total) == Aug 3 00:20:18 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-4 (11 distinct, 20 total) == Aug 3 00:06:23 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a4e66030-8621-4da9-bd27-5988bb1bf8ad [x2] Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l c055e37d-bbf5-4800-9083-d606f792c8c1 [x2] Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l e5bc3a56-6d6f-4776-954f-ddde1579648f Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.7Rb8rz/repodata/repomd.xml. For complete SELinux messages run: sealert -l a8ec5e1b-49f9-4fbc-a8ae-22e800f7abf2 Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 945db714-d0c0-4402-911e-932978b8b036 Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.7Rb8rz. For complete SELinux messages run: sealert -l 463998a0-fb0d-463c-82b1-471135710a14 Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 473d2e21-15d8-407a-a9ee-2b842607fa00 [x2] Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 80c54d4f-bf4b-4501-addb-1627383587d0 Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l c63d3890-151e-49a0-83f0-3dfb69d051e5 [x2] Aug 3 00:15:29 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3HEze2. For complete SELinux messages run: sealert -l 463998a0-fb0d-463c-82b1-471135710a14 == tma-0 (4 distinct, 5 total) == Aug 3 00:10:13 tma-0 systemd[1]: New main PID 6726 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 3 00:10:30 tma-0 systemd[1]: Daemon never wrote its PID file. Failing. Aug 3 00:10:38 tma-0 systemd[1]: pmlogger.service: Supervising process 14365 which is not our child. We'll most likely not notice when it exits. Aug 3 00:30:25 tma-0 sshd[19119]: error: PAM: Authentication failure for admin from 91.35.78.34.bc.googleusercontent.com == uffish.cs.umd.edu (3 distinct, 4 total) == Aug 3 00:10:12 uffish.cs.umd.edu systemd[1]: New main PID 735477 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 3 00:10:34 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 3 00:10:51 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 743076 which is not our child. We'll most likely not notice when it exits. == updates00.cs.umd.edu (3 distinct, 4 total) == Aug 3 00:10:12 updates00.cs.umd.edu systemd[1]: New main PID 12088 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 3 00:10:30 updates00.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 3 00:10:36 updates00.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 19046 which is not our child. We'll most likely not notice when it exits. == vacuum.cs.umd.edu (3 distinct, 4 total) == Aug 3 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 21641 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 3 00:10:32 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 3 00:10:44 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 29042 which is not our child. We'll most likely not notice when it exits. == whiffle.cs.umd.edu (3 distinct, 4 total) == Aug 3 00:10:14 whiffle.cs.umd.edu systemd[1]: New main PID 540736 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 3 00:10:40 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 3 00:10:53 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 548402 which is not our child. We'll most likely not notice when it exits. == wraith (3 distinct, 3 total) == Aug 3 00:54:53 wraith kernel: nvme 10000:e1:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Aug 3 00:54:53 wraith kernel: nvme 10000:e1:00.0: device [15b7:5015] error status/mask=00000001/0000e000 Aug 3 00:54:53 wraith kernel: nvme 10000:e1:00.0: [ 0] RxErr (First)