Command: /usr/local/sbin/syslog-digest.py Time : 0.1123s Status : exited 0 Output : Syslog digest — 2026-08-30 01:05 EDT Processed 2,993 lines, filtered 1,415 (47%). 1,578 unknown (1325 distinct) from 34 host(s). == abuse (3 distinct, 4 total) == Aug 30 00:10:14 abuse systemd[1]: New main PID 7930 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 30 00:10:32 abuse systemd[1]: Daemon never wrote its PID file. Failing. Aug 30 00:10:43 abuse systemd[1]: pmlogger.service: Supervising process 15016 which is not our child. We'll most likely not notice when it exits. == ar102 (1193 distinct, 1193 total) == Aug 24 04:50:52 ar102 cosmic-session[6072]: [2026-08-24T08:50:52Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:50:55 ar102 cosmic-session[6072]: [2026-08-24T08:50:55Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:50:58 ar102 cosmic-session[6072]: [2026-08-24T08:50:58Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:01 ar102 cosmic-session[6072]: [2026-08-24T08:51:01Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:04 ar102 cosmic-session[6072]: [2026-08-24T08:51:04Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:07 ar102 cosmic-session[6072]: [2026-08-24T08:51:07Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:10 ar102 cosmic-session[6072]: [2026-08-24T08:51:10Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:13 ar102 cosmic-session[6072]: [2026-08-24T08:51:13Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:16 ar102 cosmic-session[6072]: [2026-08-24T08:51:16Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:19 ar102 cosmic-session[6072]: [2026-08-24T08:51:19Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:22 ar102 cosmic-session[6072]: [2026-08-24T08:51:22Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:25 ar102 cosmic-session[6072]: [2026-08-24T08:51:25Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:28 ar102 cosmic-session[6072]: [2026-08-24T08:51:28Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:31 ar102 cosmic-session[6072]: [2026-08-24T08:51:31Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:34 ar102 cosmic-session[6072]: [2026-08-24T08:51:34Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:37 ar102 cosmic-session[6072]: [2026-08-24T08:51:37Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:40 ar102 cosmic-session[6072]: [2026-08-24T08:51:40Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:43 ar102 cosmic-session[6072]: [2026-08-24T08:51:43Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:46 ar102 cosmic-session[6072]: [2026-08-24T08:51:46Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:49 ar102 cosmic-session[6072]: [2026-08-24T08:51:49Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:52 ar102 cosmic-session[6072]: [2026-08-24T08:51:52Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:55 ar102 cosmic-session[6072]: [2026-08-24T08:51:55Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:51:58 ar102 cosmic-session[6072]: [2026-08-24T08:51:58Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:52:01 ar102 cosmic-session[6072]: [2026-08-24T08:52:01Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:52:04 ar102 cosmic-session[6072]: [2026-08-24T08:52:04Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:52:07 ar102 cosmic-session[6072]: [2026-08-24T08:52:07Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:52:10 ar102 cosmic-session[6072]: [2026-08-24T08:52:10Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:52:13 ar102 cosmic-session[6072]: [2026-08-24T08:52:13Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:52:16 ar102 cosmic-session[6072]: [2026-08-24T08:52:16Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Aug 24 04:52:19 ar102 cosmic-session[6072]: [2026-08-24T08:52:19Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) ... 1163 more distinct messages not shown == b0b02.cs.umd.edu (1 distinct, 1 total) == Aug 30 00:20:28 b0b02.cs.umd.edu rustdesk[3753628]: cannot open display: == csfw00a (1 distinct, 128 total) == Aug 30 00:04:19 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x128] == forge00 (1 distinct, 1 total) == Aug 30 00:31:51 forge00 (httpd)[1490110]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS == grades01.cs.umd.edu (3 distinct, 4 total) == Aug 30 00:10:14 grades01.cs.umd.edu systemd[1]: New main PID 31808 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 30 00:10:34 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 30 00:10:49 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 6866 which is not our child. We'll most likely not notice when it exits. == haproxy02.cs.umd.edu (6 distinct, 6 total) == Aug 30 00:05:23 haproxy02.cs.umd.edu setroubleshoot[2825136]: SELinux is preventing /usr/bin/bash from getattr access on the file /usr/bin/hostname. For complete SELinux messages run: sealert -l 10c1167c-7d7f-4bd0-9c34-edfa11939b35 Aug 30 00:05:23 haproxy02.cs.umd.edu setroubleshoot[2825136]: SELinux is preventing /usr/bin/bash from execute access on the file /usr/bin/hostname. For complete SELinux messages run: sealert -l fc05f98c-7192-4468-a71f-e33cf64eb035 Aug 30 00:05:23 haproxy02.cs.umd.edu setroubleshoot[2825136]: SELinux is preventing /usr/bin/bash from read access on the file /usr/bin/hostname. For complete SELinux messages run: sealert -l 20a4e6dc-92c1-4b4a-9902-f54f9e41d67b Aug 30 00:05:23 haproxy02.cs.umd.edu setroubleshoot[2825136]: SELinux is preventing /usr/bin/hostname from open access on the file /usr/bin/hostname. For complete SELinux messages run: sealert -l be87c564-7565-4633-89a4-82ad56551851 Aug 30 00:05:23 haproxy02.cs.umd.edu setroubleshoot[2825136]: SELinux is preventing /usr/bin/hostname from execute_no_trans access on the file /usr/bin/hostname. For complete SELinux messages run: sealert -l aa0111b6-a4d2-4cdb-ab95-38eec3930593 Aug 30 00:05:28 haproxy02.cs.umd.edu setroubleshoot[2825136]: SELinux is preventing /usr/bin/send_gearman from name_connect access on the tcp_socket port 4730. For complete SELinux messages run: sealert -l 4714d70b-5732-42da-8cd9-18959d539b6a == haproxy03.cs.umd.edu (7 distinct, 7 total) == Aug 30 00:33:31 haproxy03.cs.umd.edu setroubleshoot[2103092]: SELinux is preventing /usr/bin/bash from getattr access on the file /usr/bin/hostname. For complete SELinux messages run: sealert -l 493c4d93-23ee-4305-8d4d-1528f4fd1a00 Aug 30 00:33:31 haproxy03.cs.umd.edu setroubleshoot[2103092]: SELinux is preventing /usr/bin/bash from execute access on the file /usr/bin/hostname. For complete SELinux messages run: sealert -l e777f6d2-6f70-44c5-97fd-bd8d5ce86737 Aug 30 00:33:31 haproxy03.cs.umd.edu setroubleshoot[2103092]: SELinux is preventing /usr/bin/bash from read access on the file /usr/bin/hostname. For complete SELinux messages run: sealert -l 91254efb-48e1-4e26-87fb-a872862442a5 Aug 30 00:33:31 haproxy03.cs.umd.edu setroubleshoot[2103092]: SELinux is preventing /usr/bin/hostname from open access on the file /usr/bin/hostname. For complete SELinux messages run: sealert -l dd71b97f-ee67-4cdb-9d1e-b2b7ae5b7603 Aug 30 00:33:31 haproxy03.cs.umd.edu setroubleshoot[2103092]: SELinux is preventing /usr/bin/hostname from execute_no_trans access on the file /usr/bin/hostname. For complete SELinux messages run: sealert -l b96fcf6a-949b-4b1c-abc3-af377594be3e Aug 30 00:33:31 haproxy03.cs.umd.edu setroubleshoot[2103092]: SELinux is preventing /usr/bin/hostname from map access on the file /usr/bin/hostname. For complete SELinux messages run: sealert -l 24f63a86-1b04-42cb-9828-f551b74c97a3 Aug 30 00:33:33 haproxy03.cs.umd.edu setroubleshoot[2103092]: SELinux is preventing /usr/bin/send_gearman from name_connect access on the tcp_socket port 4730. For complete SELinux messages run: sealert -l d724ceba-d2b9-455e-813d-a1ea395e23e2 == hazfs.cs.umd.edu (2 distinct, 3 total) == Aug 30 00:10:02 hazfs.cs.umd.edu pcp[1966083]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily.log Aug 30 00:25:01 hazfs.cs.umd.edu pcp[2044848]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2] == idm00 (1 distinct, 1 total) == Aug 30 00:51:47 idm00 named[3810278]: client @0x7f48cc097e88 10.73.240.42#61240: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 30 00:36:26 idmp0 named[1121900]: client @0x7fe414011348 10.73.240.43#56678: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (20 distinct, 48 total) == Aug 30 00:56:24 inbound00.cs.umd.edu sshd-session[3218215]: error: maximum authentication attempts exceeded for root from 58.187.163.20 port 47324 ssh2 [preauth] Aug 30 00:56:51 inbound00.cs.umd.edu sshd-session[3218324]: error: maximum authentication attempts exceeded for root from 58.187.163.20 port 48304 ssh2 [preauth] Aug 30 00:57:14 inbound00.cs.umd.edu sshd-session[3218342]: error: maximum authentication attempts exceeded for root from 58.187.163.20 port 42136 ssh2 [preauth] Aug 30 00:57:27 inbound00.cs.umd.edu krb5_child[3218455]: Client 'admin@UMD.EDU' not found in Kerberos database [x16] Aug 30 00:57:47 inbound00.cs.umd.edu sshd-session[3218452]: error: maximum authentication attempts exceeded for admin from 58.187.163.20 port 49902 ssh2 [preauth] Aug 30 00:58:15 inbound00.cs.umd.edu sshd-session[3218477]: error: maximum authentication attempts exceeded for admin from 58.187.163.20 port 60014 ssh2 [preauth] Aug 30 00:58:54 inbound00.cs.umd.edu sshd-session[3218811]: error: maximum authentication attempts exceeded for invalid user oracle from 58.187.163.20 port 40770 ssh2 [preauth] Aug 30 00:59:15 inbound00.cs.umd.edu sshd-session[3218818]: error: maximum authentication attempts exceeded for invalid user oracle from 58.187.163.20 port 58342 ssh2 [preauth] Aug 30 00:59:48 inbound00.cs.umd.edu sshd-session[3218924]: error: maximum authentication attempts exceeded for invalid user usuario from 58.187.163.20 port 48862 ssh2 [preauth] Aug 30 01:00:11 inbound00.cs.umd.edu sshd-session[3218931]: error: maximum authentication attempts exceeded for invalid user usuario from 58.187.163.20 port 58882 ssh2 [preauth] Aug 30 01:00:46 inbound00.cs.umd.edu sshd-session[3219324]: error: maximum authentication attempts exceeded for invalid user test from 58.187.163.20 port 47372 ssh2 [preauth] Aug 30 01:01:14 inbound00.cs.umd.edu sshd-session[3219371]: error: maximum authentication attempts exceeded for invalid user test from 58.187.163.20 port 46024 ssh2 [preauth] Aug 30 01:01:51 inbound00.cs.umd.edu sshd-session[3219747]: error: maximum authentication attempts exceeded for invalid user user from 58.187.163.20 port 43042 ssh2 [preauth] Aug 30 01:02:17 inbound00.cs.umd.edu sshd-session[3219761]: error: maximum authentication attempts exceeded for invalid user user from 58.187.163.20 port 57706 ssh2 [preauth] Aug 30 01:02:58 inbound00.cs.umd.edu sshd-session[3219867]: error: maximum authentication attempts exceeded for invalid user ftpuser from 58.187.163.20 port 52326 ssh2 [preauth] Aug 30 01:03:24 inbound00.cs.umd.edu sshd-session[3219889]: error: maximum authentication attempts exceeded for invalid user ftpuser from 58.187.163.20 port 43802 ssh2 [preauth] Aug 30 01:03:47 inbound00.cs.umd.edu krb5_child[3220009]: Client 'test1@UMD.EDU' not found in Kerberos database [x14] Aug 30 01:04:04 inbound00.cs.umd.edu sshd-session[3220006]: error: maximum authentication attempts exceeded for test1 from 58.187.163.20 port 58144 ssh2 [preauth] Aug 30 01:04:28 inbound00.cs.umd.edu sshd-session[3220074]: error: maximum authentication attempts exceeded for test1 from 58.187.163.20 port 35262 ssh2 [preauth] Aug 30 01:04:57 inbound00.cs.umd.edu sshd-session[3220146]: error: maximum authentication attempts exceeded for invalid user test2 from 58.187.163.20 port 59232 ssh2 [preauth] == itmon02 (2 distinct, 48 total) == Aug 30 00:08:11 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x47] Aug 30 00:58:16 itmon02 (httpd)[3119446]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS == jubjub.cs.umd.edu (3 distinct, 4 total) == Aug 30 00:10:13 jubjub.cs.umd.edu systemd[1]: New main PID 1320240 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 30 00:10:32 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 30 00:10:40 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1327792 which is not our child. We'll most likely not notice when it exits. == librenms (1 distinct, 1 total) == Aug 30 00:56:15 librenms (httpd)[2547379]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS == mirrors.cs.umd.edu (4 distinct, 6 total) == Aug 30 00:10:34 mirrors.cs.umd.edu root[15258]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log Aug 30 00:10:34 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. [x2] Aug 30 00:10:37 mirrors.cs.umd.edu systemd[1]: New main PID 14201 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 30 00:11:47 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 30960 which is not our child. We'll most likely not notice when it exits. == misty.cs.umd.edu (3 distinct, 4 total) == Aug 30 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 7352 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 30 00:10:35 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 30 00:10:50 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 15147 which is not our child. We'll most likely not notice when it exits. == netbox (1 distinct, 1 total) == Aug 30 00:33:08 netbox (httpd)[1045197]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS == networkvm01.cs.umd.edu (9 distinct, 9 total) == Aug 30 00:30:44 networkvm01.cs.umd.edu setroubleshoot[2854476]: 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 30 00:30:44 networkvm01.cs.umd.edu setroubleshoot[2854476]: 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 30 00:30:45 networkvm01.cs.umd.edu setroubleshoot[2854476]: 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 30 00:30:45 networkvm01.cs.umd.edu setroubleshoot[2854476]: 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 30 00:30:45 networkvm01.cs.umd.edu setroubleshoot[2854476]: SELinux is preventing /usr/bin/gpg from remove_name access on the directory .#lk0x000056387dc5aed0.networkvm01.cs.umd.edu.2854475x. For complete SELinux messages run: sealert -l fcac71c9-c7c0-45a9-9dc2-a8dcbeccfc75 Aug 30 00:30:45 networkvm01.cs.umd.edu setroubleshoot[2854476]: SELinux is preventing /usr/bin/gpg from unlink access on the file .#lk0x000056387dc5aed0.networkvm01.cs.umd.edu.2854475x. For complete SELinux messages run: sealert -l a672ebb7-fa69-419c-b1f0-fb386b8b48a6 Aug 30 00:30:45 networkvm01.cs.umd.edu setroubleshoot[2854476]: 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 30 00:30:45 networkvm01.cs.umd.edu setroubleshoot[2854476]: 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 30 00:30:45 networkvm01.cs.umd.edu setroubleshoot[2854476]: SELinux is preventing /usr/bin/gpg from remove_name access on the directory .#lk0x000055a467194ee0.networkvm01.cs.umd.edu.2854493x. For complete SELinux messages run: sealert -l 80e6efe4-93f3-4219-8132-b2b52db1f517 == newhonors2 (1 distinct, 24 total) == Aug 30 00:13:03 newhonors2 dhcpcd[1914262]: dhcpcd is not running [x24] == openrepo (1 distinct, 1 total) == Aug 30 00:51:27 openrepo (nin-node)[352931]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS == openvox08-board (1 distinct, 1 total) == Aug 30 00:05:32 openvox08-board (httpd)[506198]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS == outbound00.cs.umd.edu (2 distinct, 7 total) == Aug 30 00:09:09 outbound00.cs.umd.edu python3[3117212]: ldapdb [x6] Aug 30 00:11:57 outbound00.cs.umd.edu krb5_child[3118436]: Client 'admin@UMD.EDU' not found in Kerberos database == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 30 00:13:06 outbound01.cs.umd.edu python3[1172240]: ldapdb [x6] == quiss (1 distinct, 2 total) == Aug 30 00:41:24 quiss setroubleshoot[1193530]: SELinux is preventing /usr/libexec/openssh/sshd-session from search access on the directory josephao. For complete SELinux messages run: sealert -l bf7a29ff-cb56-4adb-bf14-f887aed82b80 [x2] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Aug 30 00:23:41 sentry-docker00.cs.umd.edu systemd-udevd[2287256]: link_config: could not set ethtool features for vethc48ce16 Aug 30 00:23:41 sentry-docker00.cs.umd.edu systemd-udevd[2287256]: Could not set offload features of vethc48ce16: Operation not permitted Aug 30 00:23:41 sentry-docker00.cs.umd.edu systemd-udevd[2287371]: Could not generate persistent MAC address for vethdd33fd0: No such file or directory Aug 30 00:23:41 sentry-docker00.cs.umd.edu systemd-udevd[2287372]: Could not generate persistent MAC address for veth491ef78: No such file or directory Aug 30 00:23:41 sentry-docker00.cs.umd.edu systemd-udevd[2287375]: Could not generate persistent MAC address for veth0b0182f: No such file or directory Aug 30 00:23:41 sentry-docker00.cs.umd.edu systemd-udevd[2287376]: Could not generate persistent MAC address for veth9285814: No such file or directory Aug 30 00:23:41 sentry-docker00.cs.umd.edu systemd-udevd[2287390]: Could not generate persistent MAC address for veth3560ec7: No such file or directory Aug 30 00:23:41 sentry-docker00.cs.umd.edu systemd-udevd[2287376]: Could not generate persistent MAC address for veth90ab959: No such file or directory Aug 30 00:23:41 sentry-docker00.cs.umd.edu systemd-udevd[2287394]: Could not generate persistent MAC address for vethb6b6cd2: No such file or directory Aug 30 00:23:41 sentry-docker00.cs.umd.edu systemd-udevd[2287371]: Could not generate persistent MAC address for veth7ac4931: No such file or directory Aug 30 00:23:41 sentry-docker00.cs.umd.edu systemd-udevd[2287459]: Could not generate persistent MAC address for vethc4c5e4a: No such file or directory Aug 30 00:23:41 sentry-docker00.cs.umd.edu systemd-udevd[2287461]: Could not generate persistent MAC address for veth42f4ceb: No such file or directory Aug 30 00:43:49 sentry-docker00.cs.umd.edu systemd-udevd[2296758]: link_config: could not get ethtool features for veth0b0182f Aug 30 00:43:49 sentry-docker00.cs.umd.edu systemd-udevd[2296758]: Could not set offload features of veth0b0182f: No such device Aug 30 00:43:49 sentry-docker00.cs.umd.edu systemd-udevd[2296795]: Could not generate persistent MAC address for vethcdfae29: No such file or directory Aug 30 00:43:49 sentry-docker00.cs.umd.edu systemd-udevd[2296796]: Could not generate persistent MAC address for veth101a17e: No such file or directory Aug 30 00:43:49 sentry-docker00.cs.umd.edu systemd-udevd[2296799]: Could not generate persistent MAC address for vethb019579: No such file or directory Aug 30 00:43:49 sentry-docker00.cs.umd.edu systemd-udevd[2296800]: Could not generate persistent MAC address for veth20b893e: No such file or directory Aug 30 00:43:49 sentry-docker00.cs.umd.edu systemd-udevd[2296818]: Could not generate persistent MAC address for veth94507ee: No such file or directory Aug 30 00:43:49 sentry-docker00.cs.umd.edu systemd-udevd[2296815]: Could not generate persistent MAC address for veth0d12ffd: No such file or directory Aug 30 00:43:49 sentry-docker00.cs.umd.edu systemd-udevd[2296804]: Could not generate persistent MAC address for veth63bc231: No such file or directory Aug 30 00:43:49 sentry-docker00.cs.umd.edu systemd-udevd[2296820]: Could not generate persistent MAC address for vetha1ba3f4: No such file or directory Aug 30 00:43:49 sentry-docker00.cs.umd.edu systemd-udevd[2296804]: Could not generate persistent MAC address for vethfd68a29: No such file or directory Aug 30 00:43:49 sentry-docker00.cs.umd.edu systemd-udevd[2296820]: Could not generate persistent MAC address for veth40dbdb0: No such file or directory Aug 30 01:03:57 sentry-docker00.cs.umd.edu systemd-udevd[2306135]: link_config: could not get ethtool features for vethfd68a29 Aug 30 01:03:57 sentry-docker00.cs.umd.edu systemd-udevd[2306135]: Could not set offload features of vethfd68a29: No such device Aug 30 01:03:57 sentry-docker00.cs.umd.edu systemd-udevd[2306204]: Could not generate persistent MAC address for vethed81864: No such file or directory Aug 30 01:03:57 sentry-docker00.cs.umd.edu systemd-udevd[2306205]: Could not generate persistent MAC address for veth1186123: No such file or directory Aug 30 01:03:57 sentry-docker00.cs.umd.edu systemd-udevd[2306208]: Could not generate persistent MAC address for veth3994c77: No such file or directory Aug 30 01:03:58 sentry-docker00.cs.umd.edu systemd-udevd[2306209]: Could not generate persistent MAC address for veth5d424d6: No such file or directory ... 6 more distinct messages not shown == strawberry (3 distinct, 9 total) == Aug 30 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 30 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] Aug 30 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing. == submit10-cln25 (3 distinct, 4 total) == Aug 30 00:10:11 submit10-cln25 systemd: New main PID 29328 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 30 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing. Aug 30 00:10:36 submit10-cln25 systemd: pmlogger.service: Supervising process 3863 which is not our child. We'll most likely not notice when it exits. == syslog01 (1 distinct, 1 total) == Aug 30 00:12:21 syslog01 rsyslogd: imrelp[2514]: error 'error when receiving data, session broken', object 'lstn 2514: conn to clt 128.8.127.53/haproxy03.cs.umd.edu' - input may not work as intended [v8.2510.0-5.el10 try https://www.rsyslog.com/e/2353 ] == tlsrpt (1 distinct, 1 total) == Aug 30 00:32:19 tlsrpt (httpd)[1898730]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS == tma-0 (3 distinct, 4 total) == Aug 30 00:10:13 tma-0 systemd[1]: New main PID 4526 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 30 00:10:31 tma-0 systemd[1]: Daemon never wrote its PID file. Failing. Aug 30 00:10:39 tma-0 systemd[1]: pmlogger.service: Supervising process 12157 which is not our child. We'll most likely not notice when it exits. == uffish.cs.umd.edu (3 distinct, 4 total) == Aug 30 00:10:13 uffish.cs.umd.edu systemd[1]: New main PID 162294 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 30 00:10:39 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 30 00:10:55 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 169767 which is not our child. We'll most likely not notice when it exits. == vacuum.cs.umd.edu (3 distinct, 4 total) == Aug 30 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 10876 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 30 00:10:33 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 30 00:10:44 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 18546 which is not our child. We'll most likely not notice when it exits. == whiffle.cs.umd.edu (3 distinct, 4 total) == Aug 30 00:10:14 whiffle.cs.umd.edu systemd[1]: New main PID 4016363 does not belong to service, and PID file is not owned by root. Refusing. [x2] Aug 30 00:10:33 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Aug 30 00:10:46 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 4023891 which is not our child. We'll most likely not notice when it exits.