Command: /usr/local/sbin/syslog-digest.py Time : 0.0446s Status : exited 0 Output : Syslog digest — 2026-09-15 14:05 EDT Processed 1,949 lines, filtered 1,576 (80%). 373 unknown (94 distinct) from 19 host(s). == abadi-computer (2 distinct, 2 total) == Sep 15 13:44:47 abadi-computer falcon-sensor-bpf[529]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 Sep 15 13:44:47 abadi-computer falcon-sensor-bpf[529]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 15 13:44:59 b0b02.cs.umd.edu rustdesk[1434944]: cannot open display: == bigtuna (7 distinct, 7 total) == Sep 15 13:50:21 bigtuna gsd-subman[2911593]: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Sep 15 13:50:21 bigtuna xdg-desktop-por[2911857]: Caught PipeWire error: connection error Sep 15 13:50:33 bigtuna systemd-coredump[2962133]: Process 2912080 (firefox) of user 119431696 dumped core.#012#012Stack trace of thread 2912102:#012#0 0x00007f65b1a8d38c n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Sep 15 13:50:37 bigtuna org.gnome.Shell.desktop[2962705] The XKEYBOARD keymap compiler (xkbcomp) reports: Sep 15 13:50:37 bigtuna org.gnome.Shell.desktop[2962705] > Warning: Unsupported maximum keycode 708, clipping. Sep 15 13:50:37 bigtuna org.gnome.Shell.desktop[2962705] > X11 cannot support keycodes above 255. Sep 15 13:50:37 bigtuna org.gnome.Shell.desktop[2962705] Errors from xkbcomp are not fatal to the X server == csfw00a (1 distinct, 109 total) == Sep 15 13:04:35 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x109] == gle-dind04 (2 distinct, 2 total) == Sep 15 13:54:50 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 Sep 15 13:54:50 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 == hazfs.cs.umd.edu (12 distinct, 68 total) == Sep 15 13:25:05 hazfs.cs.umd.edu pcp[1247260]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2] Sep 15 13:46:58 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Sep 15 13:46:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Sep 15 13:46:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Sep 15 13:46:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Sep 15 13:46:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Sep 15 13:46:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Sep 15 13:46:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Sep 15 13:46:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Sep 15 13:46:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Sep 15 13:46:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Sep 15 13:46:58 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Sep 15 13:53:55 idm00 named[4166701]: client @0x7f11a006da58 10.73.240.42#50250: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 15 13:37:38 idmp0 named[1598691]: client @0x7f2d3c076558 10.73.240.43#60983: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (1 distinct, 2 total) == Sep 15 13:22:11 inbound01.cs.umd.edu krb5_child[2687181]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == itmon02 (1 distinct, 50 total) == Sep 15 13:07:47 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x50] == neoavion (1 distinct, 1 total) == Sep 15 13:55:59 neoavion pipewire[2856737]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files == newhonors2 (1 distinct, 24 total) == Sep 15 13:13:03 newhonors2 dhcpcd[2678292]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 15 13:09:09 outbound00.cs.umd.edu python3[345938]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 15 13:13:06 outbound01.cs.umd.edu python3[2605004]: ldapdb [x6] == quiss (3 distinct, 3 total) == Sep 15 13:08:37 quiss gnome-software[191719]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/josephao/.config/dconf/user.YJSEV3”: Permission denied Sep 15 13:08:47 quiss packagekitd[206183]: Failed to get cache filename for perl Sep 15 13:08:47 quiss packagekitd[206183]: Failed to get cache filename for kernel == sentry-docker00.cs.umd.edu (32 distinct, 32 total) == Sep 15 13:08:04 sentry-docker00.cs.umd.edu systemd-udevd[936828]: Could not generate persistent MAC address for vethe12ada9: No such file or directory Sep 15 13:08:04 sentry-docker00.cs.umd.edu systemd-udevd[936829]: Could not generate persistent MAC address for vethed3c33b: No such file or directory Sep 15 13:08:04 sentry-docker00.cs.umd.edu systemd-udevd[936837]: Could not generate persistent MAC address for vethdbe423f: No such file or directory Sep 15 13:08:04 sentry-docker00.cs.umd.edu systemd-udevd[936835]: Could not generate persistent MAC address for vethcf9bce7: No such file or directory Sep 15 13:08:04 sentry-docker00.cs.umd.edu systemd-udevd[936837]: Could not generate persistent MAC address for vethdd4d628: No such file or directory Sep 15 13:08:04 sentry-docker00.cs.umd.edu systemd-udevd[936835]: Could not generate persistent MAC address for vethfddcdd9: No such file or directory Sep 15 13:08:04 sentry-docker00.cs.umd.edu systemd-udevd[936835]: Could not generate persistent MAC address for veth4fa2d63: No such file or directory Sep 15 13:08:04 sentry-docker00.cs.umd.edu systemd-udevd[936837]: Could not generate persistent MAC address for vethe4ea227: No such file or directory Sep 15 13:08:04 sentry-docker00.cs.umd.edu systemd-udevd[936862]: Could not generate persistent MAC address for veth9fe1f8b: No such file or directory Sep 15 13:08:04 sentry-docker00.cs.umd.edu systemd-udevd[936864]: Could not generate persistent MAC address for veth4042d74: No such file or directory Sep 15 13:28:12 sentry-docker00.cs.umd.edu systemd-udevd[947425]: Could not generate persistent MAC address for vetha920f71: No such file or directory Sep 15 13:28:12 sentry-docker00.cs.umd.edu systemd-udevd[947426]: Could not generate persistent MAC address for vethbeef8c3: No such file or directory Sep 15 13:28:12 sentry-docker00.cs.umd.edu systemd-udevd[947451]: Could not generate persistent MAC address for vethe557649: No such file or directory Sep 15 13:28:12 sentry-docker00.cs.umd.edu systemd-udevd[947452]: Could not generate persistent MAC address for vethfa287ae: No such file or directory Sep 15 13:28:12 sentry-docker00.cs.umd.edu systemd-udevd[947471]: Could not generate persistent MAC address for vetha081e0a: No such file or directory Sep 15 13:28:12 sentry-docker00.cs.umd.edu systemd-udevd[947473]: Could not generate persistent MAC address for veth179fc61: No such file or directory Sep 15 13:28:12 sentry-docker00.cs.umd.edu systemd-udevd[947479]: Could not generate persistent MAC address for veth410921b: No such file or directory Sep 15 13:28:12 sentry-docker00.cs.umd.edu systemd-udevd[947480]: Could not generate persistent MAC address for veth330d0ab: No such file or directory Sep 15 13:28:12 sentry-docker00.cs.umd.edu systemd-udevd[947501]: Could not generate persistent MAC address for vethf3596ca: No such file or directory Sep 15 13:28:12 sentry-docker00.cs.umd.edu systemd-udevd[947502]: Could not generate persistent MAC address for veth5d48b10: No such file or directory Sep 15 13:48:20 sentry-docker00.cs.umd.edu systemd-udevd[956872]: link_config: could not get ethtool features for vethf3596ca Sep 15 13:48:20 sentry-docker00.cs.umd.edu systemd-udevd[956872]: Could not set offload features of vethf3596ca: No such device Sep 15 13:48:20 sentry-docker00.cs.umd.edu systemd-udevd[956901]: Could not generate persistent MAC address for vetha05792f: No such file or directory Sep 15 13:48:20 sentry-docker00.cs.umd.edu systemd-udevd[956902]: Could not generate persistent MAC address for vethc157c8d: No such file or directory Sep 15 13:48:20 sentry-docker00.cs.umd.edu systemd-udevd[956920]: Could not generate persistent MAC address for veth0ddda47: No such file or directory Sep 15 13:48:20 sentry-docker00.cs.umd.edu systemd-udevd[956926]: Could not generate persistent MAC address for vethf95e072: No such file or directory Sep 15 13:48:20 sentry-docker00.cs.umd.edu systemd-udevd[956924]: Could not generate persistent MAC address for vetha8f276a: No such file or directory Sep 15 13:48:20 sentry-docker00.cs.umd.edu systemd-udevd[956917]: Could not generate persistent MAC address for vethc32517c: No such file or directory Sep 15 13:48:20 sentry-docker00.cs.umd.edu systemd-udevd[956931]: Could not generate persistent MAC address for vethc5259ab: No such file or directory Sep 15 13:48:20 sentry-docker00.cs.umd.edu systemd-udevd[956932]: Could not generate persistent MAC address for vethbf65b87: No such file or directory ... 2 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 15 13:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 15 13:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 15 13:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 15 13:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 15 13:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 15 13:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 15 13:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (10 distinct, 11 total) == Sep 15 13:06:41 submit26-b9-f3 setroubleshoot[1120291]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b Sep 15 13:06:41 submit26-b9-f3 setroubleshoot[1120291]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859 Sep 15 13:06:41 submit26-b9-f3 setroubleshoot[1120291]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033 Sep 15 13:06:41 submit26-b9-f3 setroubleshoot[1120291]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.2UdU0n/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 15 13:06:41 submit26-b9-f3 setroubleshoot[1120291]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba Sep 15 13:06:41 submit26-b9-f3 setroubleshoot[1120291]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.2UdU0n. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 15 13:06:41 submit26-b9-f3 setroubleshoot[1120291]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407 Sep 15 13:06:41 submit26-b9-f3 setroubleshoot[1120291]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65 Sep 15 13:06:41 submit26-b9-f3 setroubleshoot[1120291]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68 Sep 15 13:13:24 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f4 (9 distinct, 9 total) == Sep 15 13:24:45 submit26-b9-f4 setroubleshoot[853558]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb Sep 15 13:24:45 submit26-b9-f4 setroubleshoot[853558]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4 Sep 15 13:24:45 submit26-b9-f4 setroubleshoot[853558]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d Sep 15 13:24:45 submit26-b9-f4 setroubleshoot[853558]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.I5Sez0/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 15 13:24:45 submit26-b9-f4 setroubleshoot[853558]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e Sep 15 13:24:45 submit26-b9-f4 setroubleshoot[853558]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.I5Sez0. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 15 13:24:45 submit26-b9-f4 setroubleshoot[853558]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d Sep 15 13:24:45 submit26-b9-f4 setroubleshoot[853558]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74 Sep 15 13:24:45 submit26-b9-f4 setroubleshoot[853558]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915