Command: /usr/local/sbin/syslog-digest.py Time : 0.5109s Status : exited 0 Output : Syslog digest — 2026-08-05 01:05 EDT Processed 4,295 lines, filtered 3,417 (79%). 878 unknown (107 distinct) from 29 host(s). == abuse (1 distinct, 348 total) == Aug 5 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 ] [x348] == b0b02.cs.umd.edu (1 distinct, 1 total) == Aug 5 00:45:45 b0b02.cs.umd.edu rustdesk[3037076]: cannot open display: == cheezit.cs.umd.edu (7 distinct, 10 total) == Aug 5 00:13:38 cheezit.cs.umd.edu sshd-session[1159784]: pam_access(sshd:auth): access denied for user `admin' from `116.110.156.139' [x2] Aug 5 00:13:38 cheezit.cs.umd.edu krb5_child[1159786]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Aug 5 00:13:38 cheezit.cs.umd.edu sshd-session[1159767]: error: PAM: System error for admin from 116.110.156.139 [x2] Aug 5 00:14:22 cheezit.cs.umd.edu sshd-session[1159852]: pam_access(sshd:auth): access denied for user `root' from `116.110.16.43' Aug 5 00:14:24 cheezit.cs.umd.edu sshd-session[1159850]: error: PAM: Authentication failure for root from 116.110.16.43 Aug 5 00:32:43 cheezit.cs.umd.edu sshd-session[1164538]: pam_access(sshd:auth): access denied for user `root' from `116.110.156.139' Aug 5 00:32:44 cheezit.cs.umd.edu sshd-session[1164527]: error: PAM: Authentication failure for root from 116.110.156.139 == contest (1 distinct, 34 total) == Aug 5 00:06:00 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') [x34] == csfw00a (1 distinct, 274 total) == Aug 5 00:04:24 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x274] == cskayako (2 distinct, 2 total) == Aug 5 00:06:38 cskayako setroubleshoot[2166645]: 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 5 00:06:38 cskayako setroubleshoot[2166645]: 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 5 00:10:13 grades01.cs.umd.edu systemd[1]: New main PID 25353 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 5 00:10:37 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 5 00:10:55 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 521 which is not our child. We'll most likely not notice when it exits. == idm00 (1 distinct, 1 total) == Aug 5 00:51:18 idm00 named[1455]: client @0x7f331036a618 10.73.240.42#63303: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 5 00:36:01 idmp0 named[5198]: client @0x7f99040313a8 10.73.240.43#51484: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 45 total) == Aug 5 00:08:12 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x45] == jubjub.cs.umd.edu (3 distinct, 4 total) == Aug 5 00:10:12 jubjub.cs.umd.edu systemd[1]: New main PID 1996599 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 5 00:10:32 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 5 00:10:40 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 2004051 which is not our child. We'll most likely not notice when it exits. == mirrors.cs.umd.edu (3 distinct, 4 total) == Aug 5 00:10:19 mirrors.cs.umd.edu systemd[1]: New main PID 10591 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 5 00:10:38 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 5 00:10:52 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 17636 which is not our child. We'll most likely not notice when it exits. == misty.cs.umd.edu (3 distinct, 4 total) == Aug 5 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 36712 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 5 00:10:35 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 5 00:10:51 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3932 which is not our child. We'll most likely not notice when it exits. == netman.cs.umd.edu (4 distinct, 16 total) == Aug 5 00:12:15 netman.cs.umd.edu krb5_child[902568]: Client 'admin@UMD.EDU' not found in Kerberos database [x10] Aug 5 00:30:01 netman.cs.umd.edu setroubleshoot[907536]: 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 [x2] Aug 5 00:30:01 netman.cs.umd.edu setroubleshoot[907536]: 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 [x2] Aug 5 00:30:02 netman.cs.umd.edu setroubleshoot[907536]: 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 [x2] == newhonors2 (1 distinct, 24 total) == Aug 5 00:13:03 newhonors2 dhcpcd[748226]: dhcpcd is not running [x24] == openrepo (1 distinct, 1 total) == Aug 5 00:47:53 openrepo (nin-node)[1275770]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS == outbound00.cs.umd.edu (1 distinct, 6 total) == Aug 5 00:09:09 outbound00.cs.umd.edu python3[2984162]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 5 00:13:06 outbound01.cs.umd.edu python3[1018667]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Aug 5 00:15:32 sentry-docker00.cs.umd.edu systemd-udevd[2074490]: link_config: could not get ethtool features for vethcebb620 Aug 5 00:15:32 sentry-docker00.cs.umd.edu systemd-udevd[2074490]: Could not set offload features of vethcebb620: No such device Aug 5 00:15:32 sentry-docker00.cs.umd.edu systemd-udevd[2074527]: Could not generate persistent MAC address for vethc304c3e: No such file or directory Aug 5 00:15:32 sentry-docker00.cs.umd.edu systemd-udevd[2074528]: Could not generate persistent MAC address for vethea1545f: No such file or directory Aug 5 00:15:32 sentry-docker00.cs.umd.edu systemd-udevd[2074531]: Could not generate persistent MAC address for vethfa02b69: No such file or directory Aug 5 00:15:32 sentry-docker00.cs.umd.edu systemd-udevd[2074532]: Could not generate persistent MAC address for veth50632b5: No such file or directory Aug 5 00:15:32 sentry-docker00.cs.umd.edu systemd-udevd[2074555]: Could not generate persistent MAC address for veth9cb5207: No such file or directory Aug 5 00:15:32 sentry-docker00.cs.umd.edu systemd-udevd[2074557]: Could not generate persistent MAC address for veth3fdfc39: No such file or directory Aug 5 00:15:32 sentry-docker00.cs.umd.edu systemd-udevd[2074571]: Could not generate persistent MAC address for vethe1e77ba: No such file or directory Aug 5 00:15:32 sentry-docker00.cs.umd.edu systemd-udevd[2074560]: Could not generate persistent MAC address for vethea5fbbd: No such file or directory Aug 5 00:15:32 sentry-docker00.cs.umd.edu systemd-udevd[2074650]: Could not generate persistent MAC address for vethb188734: No such file or directory Aug 5 00:15:32 sentry-docker00.cs.umd.edu systemd-udevd[2074653]: Could not generate persistent MAC address for vethdcdb201: No such file or directory Aug 5 00:35:40 sentry-docker00.cs.umd.edu systemd-udevd[2083842]: link_config: could not get ethtool features for vethc304c3e Aug 5 00:35:40 sentry-docker00.cs.umd.edu systemd-udevd[2083842]: Could not set offload features of vethc304c3e: No such device Aug 5 00:35:41 sentry-docker00.cs.umd.edu systemd-udevd[2083912]: link_config: could not get ethtool features for vethb188734 Aug 5 00:35:41 sentry-docker00.cs.umd.edu systemd-udevd[2083912]: Could not set offload features of vethb188734: No such device Aug 5 00:35:41 sentry-docker00.cs.umd.edu systemd-udevd[2083935]: Could not generate persistent MAC address for veth6093c9b: No such file or directory Aug 5 00:35:41 sentry-docker00.cs.umd.edu systemd-udevd[2083936]: Could not generate persistent MAC address for vethcb92161: No such file or directory Aug 5 00:35:41 sentry-docker00.cs.umd.edu systemd-udevd[2083954]: Could not generate persistent MAC address for veth77b61de: No such file or directory Aug 5 00:35:41 sentry-docker00.cs.umd.edu systemd-udevd[2083947]: Could not generate persistent MAC address for vethb32e0bd: No such file or directory Aug 5 00:35:41 sentry-docker00.cs.umd.edu systemd-udevd[2083963]: Could not generate persistent MAC address for veth9627549: No such file or directory Aug 5 00:35:41 sentry-docker00.cs.umd.edu systemd-udevd[2083964]: Could not generate persistent MAC address for veth515cb82: No such file or directory Aug 5 00:35:41 sentry-docker00.cs.umd.edu systemd-udevd[2083967]: Could not generate persistent MAC address for veth8a0bd6c: No such file or directory Aug 5 00:35:41 sentry-docker00.cs.umd.edu systemd-udevd[2083972]: Could not generate persistent MAC address for veth80fbc83: No such file or directory Aug 5 00:35:41 sentry-docker00.cs.umd.edu systemd-udevd[2084016]: Could not generate persistent MAC address for vethd62aa83: No such file or directory Aug 5 00:35:41 sentry-docker00.cs.umd.edu systemd-udevd[2084018]: Could not generate persistent MAC address for veth1523a8a: No such file or directory Aug 5 00:55:49 sentry-docker00.cs.umd.edu systemd-udevd[2093349]: link_config: could not get ethtool features for vethd62aa83 Aug 5 00:55:49 sentry-docker00.cs.umd.edu systemd-udevd[2093349]: Could not set offload features of vethd62aa83: No such device Aug 5 00:55:49 sentry-docker00.cs.umd.edu systemd-udevd[2093374]: Could not generate persistent MAC address for veth345f8c3: No such file or directory Aug 5 00:55:49 sentry-docker00.cs.umd.edu systemd-udevd[2093375]: Could not generate persistent MAC address for veth4af105b: No such file or directory ... 8 more distinct messages not shown == soul (1 distinct, 3 total) == Aug 5 00:13:02 soul krb5_child[3648443]: Client 'admin@UMD.EDU' not found in Kerberos database [x3] == strawberry (3 distinct, 9 total) == Aug 5 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 5 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] Aug 5 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing. == submit10-cln25 (3 distinct, 4 total) == Aug 5 00:10:12 submit10-cln25 systemd: New main PID 3486 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 5 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing. Aug 5 00:10:36 submit10-cln25 systemd: pmlogger.service: Supervising process 10386 which is not our child. We'll most likely not notice when it exits. == submit26-b9-2 (1 distinct, 5 total) == Aug 5 00:10:06 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-4 (10 distinct, 14 total) == Aug 5 00:08:06 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] Aug 5 00:15:29 submit26-b9-4 setroubleshoot[1086303]: 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 Aug 5 00:15:29 submit26-b9-4 setroubleshoot[1086303]: 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 Aug 5 00:15:29 submit26-b9-4 setroubleshoot[1086303]: 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 5 00:15:29 submit26-b9-4 setroubleshoot[1086303]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.1LMsUf/repodata/repomd.xml. For complete SELinux messages run: sealert -l a8ec5e1b-49f9-4fbc-a8ae-22e800f7abf2 Aug 5 00:15:29 submit26-b9-4 setroubleshoot[1086303]: 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 5 00:15:29 submit26-b9-4 setroubleshoot[1086303]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.1LMsUf. For complete SELinux messages run: sealert -l 463998a0-fb0d-463c-82b1-471135710a14 Aug 5 00:15:29 submit26-b9-4 setroubleshoot[1086303]: 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 Aug 5 00:15:30 submit26-b9-4 setroubleshoot[1086303]: 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 5 00:15:30 submit26-b9-4 setroubleshoot[1086303]: 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 == tma-0 (3 distinct, 4 total) == Aug 5 00:10:12 tma-0 systemd[1]: New main PID 2931 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 5 00:10:29 tma-0 systemd[1]: Daemon never wrote its PID file. Failing. Aug 5 00:10:36 tma-0 systemd[1]: pmlogger.service: Supervising process 10549 which is not our child. We'll most likely not notice when it exits. == uffish.cs.umd.edu (3 distinct, 4 total) == Aug 5 00:10:13 uffish.cs.umd.edu systemd[1]: New main PID 1314653 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 5 00:10:35 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 5 00:10:52 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1322226 which is not our child. We'll most likely not notice when it exits. == updates00.cs.umd.edu (3 distinct, 4 total) == Aug 5 00:10:12 updates00.cs.umd.edu systemd[1]: New main PID 26966 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 5 00:10:30 updates00.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 5 00:10:36 updates00.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1559 which is not our child. We'll most likely not notice when it exits. == vacuum.cs.umd.edu (3 distinct, 4 total) == Aug 5 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 30938 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 5 00:10:33 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 5 00:10:44 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 6346 which is not our child. We'll most likely not notice when it exits. == whiffle.cs.umd.edu (3 distinct, 4 total) == Aug 5 00:10:14 whiffle.cs.umd.edu systemd[1]: New main PID 1108090 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 5 00:10:33 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 5 00:10:47 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1115647 which is not our child. We'll most likely not notice when it exits.