Command: /usr/local/sbin/syslog-digest.py Time : 0.5149s Status : exited 0 Output : Syslog digest — 2026-08-06 01:05 EDT Processed 4,297 lines, filtered 3,424 (79%). 873 unknown (126 distinct) from 31 host(s). == abuse (1 distinct, 347 total) == Aug 6 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 6 00:47:08 b0b02.cs.umd.edu rustdesk[3401768]: cannot open display: == biggulp.cs.umd.edu (4 distinct, 4 total) == Aug 6 00:23:19 biggulp.cs.umd.edu sshd-session[3262847]: pam_access(sshd:auth): access denied for user `admin' from `35.241.231.49' Aug 6 00:23:19 biggulp.cs.umd.edu krb5_child[3262849]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 6 00:23:19 biggulp.cs.umd.edu sshd-session[3262845]: error: PAM: System error for admin from 35.241.231.49 Aug 6 00:23:30 biggulp.cs.umd.edu sshd-session[3262864]: error: Protocol major versions differ: 2 vs. 1 == cheezit.cs.umd.edu (11 distinct, 15 total) == Aug 6 01:02:33 cheezit.cs.umd.edu setroubleshoot[1521032]: failed to retrieve rpm info for path '/var/lib/sss/pipes/nss': [x3] Aug 6 01:02:34 cheezit.cs.umd.edu setroubleshoot[1521032]: SELinux is preventing /usr/bin/lsof from write access on the sock_file /var/lib/sss/pipes/nss. For complete SELinux messages run: sealert -l f570494d-54d2-4dac-97e2-28395659abf1 [x3] Aug 6 01:02:49 cheezit.cs.umd.edu setroubleshoot[1521614]: failed to retrieve rpm info for path '/var/log/falconctl.log': Aug 6 01:02:50 cheezit.cs.umd.edu setroubleshoot[1521614]: SELinux is preventing /opt/CrowdStrike/falconctl18708 from append access on the file /var/log/falconctl.log. For complete SELinux messages run: sealert -l 63f66d53-fcfc-44da-a79e-c789b1ce2ce8 Aug 6 01:02:52 cheezit.cs.umd.edu setroubleshoot[1521614]: SELinux is preventing /opt/CrowdStrike/falconctl18708 from write access on the file falconstore. For complete SELinux messages run: sealert -l 386506af-597f-4357-89de-bc382f369a6e Aug 6 01:03:05 cheezit.cs.umd.edu setroubleshoot[1522013]: SELinux is preventing /usr/bin/lsof from write access on the sock_file socket. For complete SELinux messages run: sealert -l 9ff2383b-9e1d-44ff-b8ae-af91637450ae Aug 6 01:03:44 cheezit.cs.umd.edu setroubleshoot[1522447]: SELinux is preventing /usr/bin/python3.9 from read access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs_dist. For complete SELinux messages run: sealert -l 679eb260-cf5d-4783-99f4-ce308edb3295 Aug 6 01:03:44 cheezit.cs.umd.edu setroubleshoot[1522447]: SELinux is preventing /usr/bin/python3.9 from open access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs_dist. For complete SELinux messages run: sealert -l 77caba8a-5cd0-4e18-b188-6e35c461772d Aug 6 01:03:44 cheezit.cs.umd.edu setroubleshoot[1522447]: SELinux is preventing /usr/bin/python3.9 from read access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs. For complete SELinux messages run: sealert -l d9c6dd0d-0a34-4430-a5ff-e985c55cb064 Aug 6 01:03:44 cheezit.cs.umd.edu setroubleshoot[1522447]: SELinux is preventing /usr/bin/python3.9 from open access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs. For complete SELinux messages run: sealert -l 8edbce57-8212-4ac8-af50-3fe403231eda Aug 6 01:03:44 cheezit.cs.umd.edu setroubleshoot[1522447]: SELinux is preventing /usr/bin/python3.9 from map access on the file /etc/selinux/targeted/contexts/files/file_contexts.bin. For complete SELinux messages run: sealert -l 4a0cbe3b-6f49-4c7e-95c6-380f7aef806e == contest (1 distinct, 33 total) == Aug 6 00:06:47 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 (1 distinct, 264 total) == Aug 6 00:04:25 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x264] == grades01.cs.umd.edu (3 distinct, 4 total) == Aug 6 00:10:13 grades01.cs.umd.edu systemd[1]: New main PID 24276 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 6 00:10:37 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 6 00:10:52 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 31879 which is not our child. We'll most likely not notice when it exits. == idm00 (1 distinct, 1 total) == Aug 6 00:51:18 idm00 named[1455]: client @0x7f3315c6a838 10.73.240.42#52786: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 6 00:36:07 idmp0 named[5198]: client @0x7f990c058998 10.73.240.43#58797: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 47 total) == Aug 6 00:07:48 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x47] == jubjub.cs.umd.edu (3 distinct, 4 total) == Aug 6 00:10:13 jubjub.cs.umd.edu systemd[1]: New main PID 2304600 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 6 00:10:32 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 6 00:10:40 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 2312112 which is not our child. We'll most likely not notice when it exits. == matrix (3 distinct, 4 total) == Aug 6 00:29:16 matrix krb5_child[3124563]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Aug 6 00:29:19 matrix sshd[3124557]: error: PAM: Authentication failure for admin from 34.52.168.223 Aug 6 00:29:36 matrix sshd[3124652]: error: Protocol major versions differ: 2 vs. 1 == mirrors.cs.umd.edu (3 distinct, 4 total) == Aug 6 00:10:12 mirrors.cs.umd.edu systemd[1]: New main PID 18388 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 6 00:10:30 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 6 00:10:56 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 25429 which is not our child. We'll most likely not notice when it exits. == misty.cs.umd.edu (3 distinct, 4 total) == Aug 6 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 23804 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 6 00:10:35 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 6 00:10:50 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 31602 which is not our child. We'll most likely not notice when it exits. == netman.cs.umd.edu (3 distinct, 6 total) == Aug 6 00:30:01 netman.cs.umd.edu setroubleshoot[1307983]: 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 6 00:30:01 netman.cs.umd.edu setroubleshoot[1307983]: 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 6 00:30:02 netman.cs.umd.edu setroubleshoot[1307983]: 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] == networkvm01.cs.umd.edu (9 distinct, 9 total) == Aug 6 00:52:20 networkvm01.cs.umd.edu setroubleshoot[1293153]: 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 6 00:52:20 networkvm01.cs.umd.edu setroubleshoot[1293153]: 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 6 00:52:20 networkvm01.cs.umd.edu setroubleshoot[1293153]: 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 6 00:52:20 networkvm01.cs.umd.edu setroubleshoot[1293153]: 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 6 00:52:20 networkvm01.cs.umd.edu setroubleshoot[1293153]: SELinux is preventing /usr/bin/gpg from remove_name access on the directory .#lk0x000055a184046ed0.networkvm01.cs.umd.edu.1293152x. For complete SELinux messages run: sealert -l fcac71c9-c7c0-45a9-9dc2-a8dcbeccfc75 Aug 6 00:52:20 networkvm01.cs.umd.edu setroubleshoot[1293153]: SELinux is preventing /usr/bin/gpg from unlink access on the file .#lk0x000055a184046ed0.networkvm01.cs.umd.edu.1293152x. For complete SELinux messages run: sealert -l a672ebb7-fa69-419c-b1f0-fb386b8b48a6 Aug 6 00:52:20 networkvm01.cs.umd.edu setroubleshoot[1293153]: 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 6 00:52:20 networkvm01.cs.umd.edu setroubleshoot[1293153]: 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 6 00:52:21 networkvm01.cs.umd.edu setroubleshoot[1293153]: SELinux is preventing /usr/bin/gpg from remove_name access on the directory .#lk0x000055d9d7fc6ee0.networkvm01.cs.umd.edu.1293170x. For complete SELinux messages run: sealert -l 80e6efe4-93f3-4219-8132-b2b52db1f517 == newhonors2 (1 distinct, 24 total) == Aug 6 00:13:03 newhonors2 dhcpcd[793942]: dhcpcd is not running [x24] == openrepo (1 distinct, 1 total) == Aug 6 00:45:27 openrepo (nin-node)[1406479]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS == outbound00.cs.umd.edu (3 distinct, 8 total) == Aug 6 00:09:08 outbound00.cs.umd.edu python3[3320785]: ldapdb [x6] Aug 6 00:49:11 outbound00.cs.umd.edu krb5_child[3330356]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 6 00:49:29 outbound00.cs.umd.edu sshd-session[3330387]: error: Protocol major versions differ: 2 vs. 1 == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 6 00:13:06 outbound01.cs.umd.edu python3[1355960]: ldapdb [x6] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Aug 6 00:08:54 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Aug 6 00:05:23 sentry-docker00.cs.umd.edu systemd-udevd[2748153]: link_config: could not get ethtool features for veth20fe184 Aug 6 00:05:23 sentry-docker00.cs.umd.edu systemd-udevd[2748153]: Could not set offload features of veth20fe184: No such device Aug 6 00:05:23 sentry-docker00.cs.umd.edu systemd-udevd[2748182]: Could not generate persistent MAC address for vethe6874da: No such file or directory Aug 6 00:05:23 sentry-docker00.cs.umd.edu systemd-udevd[2748183]: Could not generate persistent MAC address for veth64dd713: No such file or directory Aug 6 00:05:23 sentry-docker00.cs.umd.edu systemd-udevd[2748201]: Could not generate persistent MAC address for vethe16fe3f: No such file or directory Aug 6 00:05:23 sentry-docker00.cs.umd.edu systemd-udevd[2748186]: Could not generate persistent MAC address for veth18eecd9: No such file or directory Aug 6 00:05:23 sentry-docker00.cs.umd.edu systemd-udevd[2748208]: Could not generate persistent MAC address for vetha750ecc: No such file or directory Aug 6 00:05:23 sentry-docker00.cs.umd.edu systemd-udevd[2748190]: Could not generate persistent MAC address for vethbdd06de: No such file or directory Aug 6 00:05:23 sentry-docker00.cs.umd.edu systemd-udevd[2748190]: Could not generate persistent MAC address for veth71f6afe: No such file or directory Aug 6 00:05:23 sentry-docker00.cs.umd.edu systemd-udevd[2748204]: Could not generate persistent MAC address for veth5aa9f41: No such file or directory Aug 6 00:05:23 sentry-docker00.cs.umd.edu systemd-udevd[2748227]: Could not generate persistent MAC address for vethaf98dae: No such file or directory Aug 6 00:05:23 sentry-docker00.cs.umd.edu systemd-udevd[2748229]: Could not generate persistent MAC address for veth35f905a: No such file or directory Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757577]: link_config: could not get ethtool features for vethaf98dae Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757577]: Could not set offload features of vethaf98dae: No such device Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757672]: link_config: could not get ethtool features for veth71f6afe Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757672]: Could not set offload features of veth71f6afe: No such device Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757704]: Could not generate persistent MAC address for veth4a41b05: No such file or directory Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757705]: Could not generate persistent MAC address for veth12bd218: No such file or directory Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757710]: Could not generate persistent MAC address for veth8c9c7e4: No such file or directory Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757711]: Could not generate persistent MAC address for vethfb8e8e9: No such file or directory Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757735]: Could not generate persistent MAC address for veth7112267: No such file or directory Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757736]: Could not generate persistent MAC address for veth56663ab: No such file or directory Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757757]: Could not generate persistent MAC address for veth4bdac74: No such file or directory Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757747]: Could not generate persistent MAC address for veth4dadca6: No such file or directory Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757736]: Could not generate persistent MAC address for vethd52a0cb: No such file or directory Aug 6 00:25:31 sentry-docker00.cs.umd.edu systemd-udevd[2757757]: Could not generate persistent MAC address for vethd9cd37e: No such file or directory Aug 6 00:45:40 sentry-docker00.cs.umd.edu systemd-udevd[2767297]: link_config: could not get ethtool features for veth7112267 Aug 6 00:45:40 sentry-docker00.cs.umd.edu systemd-udevd[2767297]: Could not set offload features of veth7112267: No such device Aug 6 00:45:40 sentry-docker00.cs.umd.edu systemd-udevd[2767391]: Could not generate persistent MAC address for vethb43232b: No such file or directory Aug 6 00:45:40 sentry-docker00.cs.umd.edu systemd-udevd[2767392]: Could not generate persistent MAC address for vethcd5039a: No such file or directory ... 8 more distinct messages not shown == strawberry (3 distinct, 9 total) == Aug 6 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 6 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] Aug 6 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing. == submit10-cln25 (3 distinct, 4 total) == Aug 6 00:10:11 submit10-cln25 systemd: New main PID 23956 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 6 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing. Aug 6 00:10:36 submit10-cln25 systemd: pmlogger.service: Supervising process 30854 which is not our child. We'll most likely not notice when it exits. == submit26-b9-2 (1 distinct, 2 total) == Aug 6 00:10:05 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-4 (10 distinct, 12 total) == Aug 6 00:05:05 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Aug 6 00:15:30 submit26-b9-4 setroubleshoot[1153080]: 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 6 00:15:30 submit26-b9-4 setroubleshoot[1153080]: 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 6 00:15:30 submit26-b9-4 setroubleshoot[1153080]: 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 6 00:15:30 submit26-b9-4 setroubleshoot[1153080]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.wzgoje/repodata/repomd.xml. For complete SELinux messages run: sealert -l a8ec5e1b-49f9-4fbc-a8ae-22e800f7abf2 Aug 6 00:15:30 submit26-b9-4 setroubleshoot[1153080]: 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 6 00:15:30 submit26-b9-4 setroubleshoot[1153080]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.wzgoje. For complete SELinux messages run: sealert -l 463998a0-fb0d-463c-82b1-471135710a14 Aug 6 00:15:30 submit26-b9-4 setroubleshoot[1153080]: 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 6 00:15:30 submit26-b9-4 setroubleshoot[1153080]: 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 6 00:15:30 submit26-b9-4 setroubleshoot[1153080]: 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 6 00:10:12 tma-0 systemd[1]: New main PID 17118 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 6 00:10:29 tma-0 systemd[1]: Daemon never wrote its PID file. Failing. Aug 6 00:10:37 tma-0 systemd[1]: pmlogger.service: Supervising process 24739 which is not our child. We'll most likely not notice when it exits. == uffish.cs.umd.edu (3 distinct, 4 total) == Aug 6 00:10:12 uffish.cs.umd.edu systemd[1]: New main PID 1604259 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 6 00:10:34 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 6 00:10:51 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1611848 which is not our child. We'll most likely not notice when it exits. == updates00.cs.umd.edu (3 distinct, 4 total) == Aug 6 00:10:12 updates00.cs.umd.edu systemd[1]: New main PID 18216 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 6 00:10:30 updates00.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 6 00:10:37 updates00.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 25171 which is not our child. We'll most likely not notice when it exits. == vacuum.cs.umd.edu (3 distinct, 4 total) == Aug 6 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 19561 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 6 00:10:34 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 6 00:10:45 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 27190 which is not our child. We'll most likely not notice when it exits. == whiffle.cs.umd.edu (3 distinct, 4 total) == Aug 6 00:10:13 whiffle.cs.umd.edu systemd[1]: New main PID 1391860 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 6 00:10:32 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 6 00:10:46 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1399234 which is not our child. We'll most likely not notice when it exits.