Command: /usr/local/sbin/syslog-digest.py Time : 0.5020s Status : exited 0 Output : Syslog digest — 2026-07-30 19:05 EDT Processed 4,349 lines, filtered 3,509 (80%). 840 unknown (73 distinct) from 20 host(s). == abadi-computer (3 distinct, 5 total) == Jul 30 18:52:33 abadi-computer sudo[345829]: pam_unix(sudo:auth): conversation failed [x2] Jul 30 18:52:33 abadi-computer sudo[345829]: pam_unix(sudo:auth): auth could not identify password for [poojan] [x2] Jul 30 19:01:28 abadi-computer kernel: kauditd_printk_skb: 2 callbacks suppressed == abuse (1 distinct, 347 total) == Jul 30 18: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] == alec.cs.umd.edu (6 distinct, 63 total) == Jul 30 18:05:12 alec.cs.umd.edu setroubleshoot[609135]: failed to retrieve rpm info for path '/run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3': [x12] Jul 30 18:05:13 alec.cs.umd.edu sedispatch[1526]: AVC Message regarding setroubleshoot, ignoring message [x24] Jul 30 18:05:13 alec.cs.umd.edu setroubleshoot[609135]: SELinux is preventing /usr/bin/df from getattr access on the file /run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3. For complete SELinux messages run: sealert -l 23f93208-3063-4aac-b78a-bb0fcb40740c [x24] Jul 30 18:58:01 alec.cs.umd.edu setroubleshoot[622393]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l b1c8012b-94a9-4ce7-92c3-ad6749526f5a Jul 30 18:58:03 alec.cs.umd.edu setroubleshoot[622393]: SELinux is preventing /usr/bin/python3.9 from read access on the directory repodata. For complete SELinux messages run: sealert -l 3512da42-a4b7-4b60-a694-c798abba8d51 Jul 30 18:58:05 alec.cs.umd.edu setroubleshoot[622393]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 5b52098c-4bab-47f9-909d-e2ac52f4f3dd == b0b02.cs.umd.edu (4 distinct, 4 total) == Jul 30 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-07-30T22:10:59.388567525Z" level=info msg="PurgeUploads starting: olderThan=2026-07-23 22:10:59.388476935 +0000 UTC m=-343379.851594740, actuallyDelete=true" Jul 30 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-07-30T22:10:59.389077562Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Jul 30 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-07-30T22:10:59.389096669Z" level=info msg="Starting upload purge in 24h0m0s" go.version=go1.11.2 instance.id=68469aa4-7857-4a69-bf12-c2190b4f96d8 service=registry version=v2.7.1 Jul 30 18:38:07 b0b02.cs.umd.edu rustdesk[1121003]: cannot open display: == contest (1 distinct, 34 total) == Jul 30 18:05:27 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, 236 total) == Jul 30 18:04:37 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x236] == hackerman (6 distinct, 11 total) == Jul 30 18:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4] Jul 30 18:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding Jul 30 18:20:28 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.VUJ7S3”: Permission denied Jul 30 18:20:28 hackerman packagekitd[2243181]: Failed to get cache filename for libreoffice [x2] Jul 30 18:20:28 hackerman packagekitd[2243181]: Failed to get cache filename for kernel [x2] Jul 30 18:20:38 hackerman packagekitd[2243181]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == idm00 (1 distinct, 1 total) == Jul 30 18:51:11 idm00 named[1455]: client @0x7f331578b7f8 10.73.240.42#64358: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Jul 30 18:36:01 idmp0 named[5198]: client @0x7f992002e6d8 10.73.240.43#52723: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (1 distinct, 1 total) == Jul 30 18:41:07 inbound01.cs.umd.edu krb5_child[3463775]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 44 total) == Jul 30 18:08:10 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x44] == mcstic (1 distinct, 2 total) == Jul 30 18:53:31 mcstic krb5_child[1882848]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == newhonors2 (1 distinct, 24 total) == Jul 30 18:13:03 newhonors2 dhcpcd[507544]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 30 18:09:08 outbound00.cs.umd.edu python3[1214240]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Jul 30 18:13:06 outbound01.cs.umd.edu python3[3440536]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Jul 30 18:08:39 sentry-docker00.cs.umd.edu systemd-udevd[2693609]: link_config: could not get ethtool features for vethaf7ed35 Jul 30 18:08:39 sentry-docker00.cs.umd.edu systemd-udevd[2693609]: Could not set offload features of vethaf7ed35: No such device Jul 30 18:08:39 sentry-docker00.cs.umd.edu systemd-udevd[2693627]: Could not generate persistent MAC address for veth8d120ea: No such file or directory Jul 30 18:08:39 sentry-docker00.cs.umd.edu systemd-udevd[2693628]: Could not generate persistent MAC address for vethd2d92a3: No such file or directory Jul 30 18:23:32 sentry-docker00.cs.umd.edu systemd-udevd[2699824]: link_config: could not get ethtool features for vethc561ef2 Jul 30 18:23:32 sentry-docker00.cs.umd.edu systemd-udevd[2699824]: Could not set offload features of vethc561ef2: No such device Jul 30 18:23:33 sentry-docker00.cs.umd.edu systemd-udevd[2699849]: Could not generate persistent MAC address for vethbf0a6a0: No such file or directory Jul 30 18:23:33 sentry-docker00.cs.umd.edu systemd-udevd[2699850]: Could not generate persistent MAC address for veth1b923a6: No such file or directory Jul 30 18:23:33 sentry-docker00.cs.umd.edu systemd-udevd[2699853]: Could not generate persistent MAC address for vethd8057ce: No such file or directory Jul 30 18:23:33 sentry-docker00.cs.umd.edu systemd-udevd[2699854]: Could not generate persistent MAC address for vethf85e53b: No such file or directory Jul 30 18:23:33 sentry-docker00.cs.umd.edu systemd-udevd[2699859]: Could not generate persistent MAC address for vethef97e78: No such file or directory Jul 30 18:23:33 sentry-docker00.cs.umd.edu systemd-udevd[2699861]: Could not generate persistent MAC address for veth2f810d5: No such file or directory Jul 30 18:23:33 sentry-docker00.cs.umd.edu systemd-udevd[2699879]: Could not generate persistent MAC address for vethc6348bc: No such file or directory Jul 30 18:23:33 sentry-docker00.cs.umd.edu systemd-udevd[2699880]: Could not generate persistent MAC address for veth93630c5: No such file or directory Jul 30 18:28:44 sentry-docker00.cs.umd.edu systemd-udevd[2703042]: Could not generate persistent MAC address for veth0eb165a: No such file or directory Jul 30 18:28:44 sentry-docker00.cs.umd.edu systemd-udevd[2703043]: Could not generate persistent MAC address for vethff125b9: No such file or directory Jul 30 18:43:41 sentry-docker00.cs.umd.edu systemd-udevd[2709340]: Could not generate persistent MAC address for vethd759fc9: No such file or directory Jul 30 18:43:41 sentry-docker00.cs.umd.edu systemd-udevd[2709341]: Could not generate persistent MAC address for veth212b86c: No such file or directory Jul 30 18:43:41 sentry-docker00.cs.umd.edu systemd-udevd[2709366]: Could not generate persistent MAC address for vethdbcb815: No such file or directory Jul 30 18:43:41 sentry-docker00.cs.umd.edu systemd-udevd[2709367]: Could not generate persistent MAC address for vethe444e58: No such file or directory Jul 30 18:43:41 sentry-docker00.cs.umd.edu systemd-udevd[2709370]: Could not generate persistent MAC address for veth890142a: No such file or directory Jul 30 18:43:41 sentry-docker00.cs.umd.edu systemd-udevd[2709372]: Could not generate persistent MAC address for vethba301e7: No such file or directory Jul 30 18:43:41 sentry-docker00.cs.umd.edu systemd-udevd[2709418]: Could not generate persistent MAC address for vethdb8d2cb: No such file or directory Jul 30 18:43:41 sentry-docker00.cs.umd.edu systemd-udevd[2709422]: Could not generate persistent MAC address for vethb2ff376: No such file or directory Jul 30 18:48:52 sentry-docker00.cs.umd.edu systemd-udevd[2712496]: link_config: could not get ethtool features for veth0eb165a Jul 30 18:48:52 sentry-docker00.cs.umd.edu systemd-udevd[2712496]: Could not set offload features of veth0eb165a: No such device Jul 30 18:48:52 sentry-docker00.cs.umd.edu systemd-udevd[2712514]: Could not generate persistent MAC address for veth09c0fd2: No such file or directory Jul 30 18:48:52 sentry-docker00.cs.umd.edu systemd-udevd[2712515]: Could not generate persistent MAC address for veth1405456: No such file or directory Jul 30 19:03:49 sentry-docker00.cs.umd.edu systemd-udevd[2718752]: link_config: could not get ethtool features for veth890142a Jul 30 19:03:49 sentry-docker00.cs.umd.edu systemd-udevd[2718752]: Could not set offload features of veth890142a: No such device ... 8 more distinct messages not shown == strawberry (2 distinct, 8 total) == Jul 30 18: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] Jul 30 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (1 distinct, 3 total) == Jul 30 18:40:44 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-4 (1 distinct, 5 total) == Jul 30 18:24:58 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == unknown (1 distinct, 1 total) == using-explainable-ai