Command: /usr/local/sbin/syslog-digest.py Time : 0.4975s Status : exited 0 Output : Syslog digest — 2026-08-02 01:05 EDT Processed 3,994 lines, filtered 3,198 (80%). 796 unknown (118 distinct) from 33 host(s). == abuse (1 distinct, 348 total) == Aug 2 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 2 00:41:21 b0b02.cs.umd.edu rustdesk[1942406]: cannot open display: == contest (1 distinct, 34 total) == Aug 2 00:05:42 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, 214 total) == Aug 2 00:04:32 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x214] == cskayako (4 distinct, 6 total) == Aug 2 00:06:39 cskayako setroubleshoot[1694289]: 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 [x2] Aug 2 00:06:39 cskayako setroubleshoot[1694289]: 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 [x2] Aug 2 00:30:31 cskayako setroubleshoot[1696779]: failed to retrieve rpm info for path '/var/www/html/__swift/logs/log.cache_02_Aug_2026_eb2657f2e6.txt': Aug 2 00:30:31 cskayako setroubleshoot[1696779]: SELinux is preventing /usr/sbin/sendmail.postfix from append access on the file /var/www/html/__swift/logs/log.cache_02_Aug_2026_eb2657f2e6.txt. For complete SELinux messages run: sealert -l c566b62c-2773-4bf0-808b-10f832f1eafb == forge00 (1 distinct, 1 total) == Aug 2 00:35:52 forge00 (httpd)[1457003]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS == grades01.cs.umd.edu (3 distinct, 4 total) == Aug 2 00:10:13 grades01.cs.umd.edu systemd[1]: New main PID 30552 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 2 00:10:37 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 2 00:10:52 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 5979 which is not our child. We'll most likely not notice when it exits. == idm00 (1 distinct, 1 total) == Aug 2 00:51:13 idm00 named[1455]: client @0x7f33041b1a78 10.73.240.42#52182: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 2 00:36:02 idmp0 named[5198]: client @0x7f98f4021ea8 10.73.240.43#55593: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 1 total) == Aug 2 00:39:56 inbound00.cs.umd.edu krb5_child[2014791]: Preauthentication failed == itmon02 (1 distinct, 32 total) == Aug 2 00:08:15 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x32] == jubjub.cs.umd.edu (3 distinct, 4 total) == Aug 2 00:10:13 jubjub.cs.umd.edu systemd[1]: New main PID 1072720 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 2 00:10:32 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 2 00:10:40 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1079996 which is not our child. We'll most likely not notice when it exits. == mirrors.cs.umd.edu (3 distinct, 4 total) == Aug 2 00:10:12 mirrors.cs.umd.edu systemd[1]: New main PID 19329 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 2 00:10:30 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 2 00:10:44 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 26374 which is not our child. We'll most likely not notice when it exits. == misty.cs.umd.edu (3 distinct, 4 total) == Aug 2 00:10:14 misty.cs.umd.edu systemd[1]: New main PID 34264 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 2 00:10:35 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 2 00:10:50 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1516 which is not our child. We'll most likely not notice when it exits. == munin (1 distinct, 1 total) == Aug 2 00:58:21 munin (httpd)[374748]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS == netbox (1 distinct, 1 total) == Aug 2 00:32:21 netbox (httpd)[1314800]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS == netman.cs.umd.edu (3 distinct, 3 total) == Aug 2 00:30:00 netman.cs.umd.edu setroubleshoot[3901353]: 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 2 00:30:01 netman.cs.umd.edu setroubleshoot[3901353]: 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 2 00:30:09 netman.cs.umd.edu setroubleshoot[3901353]: 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 (9 distinct, 9 total) == Aug 2 00:35:55 networkvm01.cs.umd.edu setroubleshoot[3128092]: 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 2 00:35:55 networkvm01.cs.umd.edu setroubleshoot[3128092]: 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 2 00:35:55 networkvm01.cs.umd.edu setroubleshoot[3128092]: 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 Aug 2 00:35:55 networkvm01.cs.umd.edu setroubleshoot[3128092]: 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 Aug 2 00:35:55 networkvm01.cs.umd.edu setroubleshoot[3128092]: SELinux is preventing /usr/bin/gpg from remove_name access on the directory .#lk0x00005589ef81ded0.networkvm01.cs.umd.edu.3128091x. For complete SELinux messages run: sealert -l fcac71c9-c7c0-45a9-9dc2-a8dcbeccfc75 Aug 2 00:35:55 networkvm01.cs.umd.edu setroubleshoot[3128092]: SELinux is preventing /usr/bin/gpg from unlink access on the file .#lk0x00005589ef81ded0.networkvm01.cs.umd.edu.3128091x. For complete SELinux messages run: sealert -l a672ebb7-fa69-419c-b1f0-fb386b8b48a6 Aug 2 00:35:55 networkvm01.cs.umd.edu setroubleshoot[3128092]: 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 2 00:35:55 networkvm01.cs.umd.edu setroubleshoot[3128092]: 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 2 00:35:55 networkvm01.cs.umd.edu setroubleshoot[3128092]: SELinux is preventing /usr/bin/gpg from remove_name access on the directory .#lk0x000055fa5ea38ee0.networkvm01.cs.umd.edu.3128109x. For complete SELinux messages run: sealert -l 80e6efe4-93f3-4219-8132-b2b52db1f517 == newhonors2 (1 distinct, 24 total) == Aug 2 00:13:02 newhonors2 dhcpcd[610726]: dhcpcd is not running [x24] == openrepo (1 distinct, 1 total) == Aug 2 00:23:26 openrepo (nin-node)[881266]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS == outbound00.cs.umd.edu (1 distinct, 6 total) == Aug 2 00:09:09 outbound00.cs.umd.edu python3[1973297]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 2 00:13:06 outbound01.cs.umd.edu python3[6477]: ldapdb [x6] == sentry-docker00.cs.umd.edu (40 distinct, 40 total) == Aug 2 00:05:43 sentry-docker00.cs.umd.edu systemd-udevd[29196]: link_config: could not get ethtool features for veth837fcbd Aug 2 00:05:43 sentry-docker00.cs.umd.edu systemd-udevd[29196]: Could not set offload features of veth837fcbd: No such device Aug 2 00:05:44 sentry-docker00.cs.umd.edu systemd-udevd[29230]: Could not generate persistent MAC address for veth981406c: No such file or directory Aug 2 00:05:44 sentry-docker00.cs.umd.edu systemd-udevd[29231]: Could not generate persistent MAC address for veth568f0c2: No such file or directory Aug 2 00:05:44 sentry-docker00.cs.umd.edu systemd-udevd[29234]: Could not generate persistent MAC address for veth5fe84cf: No such file or directory Aug 2 00:05:44 sentry-docker00.cs.umd.edu systemd-udevd[29235]: Could not generate persistent MAC address for vethe261b97: No such file or directory Aug 2 00:05:44 sentry-docker00.cs.umd.edu systemd-udevd[29258]: Could not generate persistent MAC address for vethf5628be: No such file or directory Aug 2 00:05:44 sentry-docker00.cs.umd.edu systemd-udevd[29259]: Could not generate persistent MAC address for vethc9b4523: No such file or directory Aug 2 00:05:44 sentry-docker00.cs.umd.edu systemd-udevd[29262]: Could not generate persistent MAC address for veth8e62fda: No such file or directory Aug 2 00:05:44 sentry-docker00.cs.umd.edu systemd-udevd[29271]: Could not generate persistent MAC address for veth51ce3ef: No such file or directory Aug 2 00:08:31 sentry-docker00.cs.umd.edu systemd-udevd[31430]: Could not generate persistent MAC address for veth4ee29f3: No such file or directory Aug 2 00:08:31 sentry-docker00.cs.umd.edu systemd-udevd[31431]: Could not generate persistent MAC address for veth39666b4: No such file or directory Aug 2 00:25:52 sentry-docker00.cs.umd.edu systemd-udevd[38593]: link_config: could not get ethtool features for veth8e62fda Aug 2 00:25:52 sentry-docker00.cs.umd.edu systemd-udevd[38593]: Could not set offload features of veth8e62fda: No such device Aug 2 00:25:52 sentry-docker00.cs.umd.edu systemd-udevd[38669]: link_config: could not get ethtool features for veth981406c Aug 2 00:25:52 sentry-docker00.cs.umd.edu systemd-udevd[38669]: Could not set offload features of veth981406c: No such device Aug 2 00:25:52 sentry-docker00.cs.umd.edu systemd-udevd[38694]: Could not generate persistent MAC address for veth5667503: No such file or directory Aug 2 00:25:52 sentry-docker00.cs.umd.edu systemd-udevd[38695]: Could not generate persistent MAC address for veth4b10fa9: No such file or directory Aug 2 00:25:52 sentry-docker00.cs.umd.edu systemd-udevd[38724]: Could not generate persistent MAC address for veth6a2ad35: No such file or directory Aug 2 00:25:52 sentry-docker00.cs.umd.edu systemd-udevd[38725]: Could not generate persistent MAC address for veth0be797f: No such file or directory Aug 2 00:25:52 sentry-docker00.cs.umd.edu systemd-udevd[38761]: Could not generate persistent MAC address for veth3efd8c5: No such file or directory Aug 2 00:25:52 sentry-docker00.cs.umd.edu systemd-udevd[38756]: Could not generate persistent MAC address for vethb604904: No such file or directory Aug 2 00:25:52 sentry-docker00.cs.umd.edu systemd-udevd[38757]: Could not generate persistent MAC address for vetha790e52: No such file or directory Aug 2 00:25:52 sentry-docker00.cs.umd.edu systemd-udevd[38725]: Could not generate persistent MAC address for veth2ed2509: No such file or directory Aug 2 00:28:40 sentry-docker00.cs.umd.edu systemd-udevd[40852]: Could not generate persistent MAC address for veth22f731f: No such file or directory Aug 2 00:28:40 sentry-docker00.cs.umd.edu systemd-udevd[40853]: Could not generate persistent MAC address for vethee80de5: No such file or directory Aug 2 00:46:00 sentry-docker00.cs.umd.edu systemd-udevd[47993]: link_config: could not get ethtool features for vetha790e52 Aug 2 00:46:00 sentry-docker00.cs.umd.edu systemd-udevd[47993]: Could not set offload features of vetha790e52: No such device Aug 2 00:46:00 sentry-docker00.cs.umd.edu systemd-udevd[48085]: Could not generate persistent MAC address for veth6638325: No such file or directory Aug 2 00:46:00 sentry-docker00.cs.umd.edu systemd-udevd[48084]: Could not generate persistent MAC address for vethf80562f: No such file or directory ... 10 more distinct messages not shown == strawberry (3 distinct, 9 total) == Aug 2 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 2 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] Aug 2 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing. == submit10-cln25 (3 distinct, 4 total) == Aug 2 00:10:12 submit10-cln25 systemd: New main PID 6970 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 2 00:10:31 submit10-cln25 systemd: Daemon never wrote its PID file. Failing. Aug 2 00:10:37 submit10-cln25 systemd: pmlogger.service: Supervising process 13895 which is not our child. We'll most likely not notice when it exits. == submit26-b9-4 (11 distinct, 14 total) == Aug 2 00:15:28 submit26-b9-4 setroubleshoot[844504]: 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 2 00:15:28 submit26-b9-4 setroubleshoot[844504]: 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 2 00:15:28 submit26-b9-4 setroubleshoot[844504]: 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 [x2] Aug 2 00:15:28 submit26-b9-4 setroubleshoot[844504]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.sZFxHD/repodata/repomd.xml. For complete SELinux messages run: sealert -l a8ec5e1b-49f9-4fbc-a8ae-22e800f7abf2 Aug 2 00:15:28 submit26-b9-4 setroubleshoot[844504]: 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 [x2] Aug 2 00:15:28 submit26-b9-4 setroubleshoot[844504]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.sZFxHD. For complete SELinux messages run: sealert -l 463998a0-fb0d-463c-82b1-471135710a14 Aug 2 00:15:28 submit26-b9-4 setroubleshoot[844504]: 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 2 00:15:28 submit26-b9-4 setroubleshoot[844504]: 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 [x2] Aug 2 00:15:28 submit26-b9-4 setroubleshoot[844504]: 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 Aug 2 00:15:28 submit26-b9-4 setroubleshoot[844504]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.oMzqSl/repodata/repomd.xml. For complete SELinux messages run: sealert -l a8ec5e1b-49f9-4fbc-a8ae-22e800f7abf2 Aug 2 00:57:10 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == teaching-awards (2 distinct, 2 total) == Aug 2 00:52:27 teaching-awards krb5_child[1735631]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 2 00:52:50 teaching-awards sshd-session[1735645]: error: Protocol major versions differ: 2 vs. 1 == tlsrpt (1 distinct, 1 total) == Aug 2 00:18:25 tlsrpt (httpd)[547426]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS == tma-0 (3 distinct, 4 total) == Aug 2 00:10:13 tma-0 systemd[1]: New main PID 24858 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 2 00:10:30 tma-0 systemd[1]: Daemon never wrote its PID file. Failing. Aug 2 00:10:38 tma-0 systemd[1]: pmlogger.service: Supervising process 32492 which is not our child. We'll most likely not notice when it exits. == uffish.cs.umd.edu (3 distinct, 4 total) == Aug 2 00:10:13 uffish.cs.umd.edu systemd[1]: New main PID 445897 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 2 00:10:35 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 2 00:10:51 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 453480 which is not our child. We'll most likely not notice when it exits. == updates00.cs.umd.edu (3 distinct, 4 total) == Aug 2 00:10:12 updates00.cs.umd.edu systemd[1]: New main PID 20778 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 2 00:10:30 updates00.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 2 00:10:37 updates00.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 27746 which is not our child. We'll most likely not notice when it exits. == vacuum.cs.umd.edu (3 distinct, 4 total) == Aug 2 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 32714 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 2 00:10:33 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 2 00:10:44 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 8155 which is not our child. We'll most likely not notice when it exits. == whiffle.cs.umd.edu (3 distinct, 4 total) == Aug 2 00:10:13 whiffle.cs.umd.edu systemd[1]: New main PID 256995 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 2 00:10:39 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 2 00:10:52 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 264669 which is not our child. We'll most likely not notice when it exits.
participants (1)
-
cron/zfs00.cs.umd.edu