Command: /usr/local/sbin/syslog-digest.py Time : 0.5008s Status : exited 0 Output : Syslog digest — 2026-07-21 22:05 EDT Processed 4,431 lines, filtered 3,640 (82%). 791 unknown (86 distinct) from 20 host(s). == abadi-computer (3 distinct, 5 total) == Jul 21 21:08:05 abadi-computer falcon-sensor-bpf[529]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 [x2] Jul 21 21:08:05 abadi-computer falcon-sensor-bpf[529]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 [x2] Jul 21 21:08:16 abadi-computer kernel: kauditd_printk_skb: 512 callbacks suppressed == abuse (1 distinct, 347 total) == Jul 21 21: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) == Jul 21 21:10:18 b0b02.cs.umd.edu rustdesk[1449255]: cannot open display: == bac102 (10 distinct, 10 total) == Jul 21 20:01:14 bac102 puppet-agent[147547]: (/File[/opt/puppetlabs/puppet/cache/lib]) Failed to generate additional resources using 'eval_generate': Request to https://openvox08-cmp2.cs.umd.edu:8140/puppet/v3/file_metadatas/plugins?recu... timed out read operation after 54776.292 seconds Jul 21 20:01:14 bac102 puppet-agent[147547]: (/File[/opt/puppetlabs/puppet/cache/lib]) Wrapped exception: Jul 21 20:01:14 bac102 puppet-agent[147547]: (/File[/opt/puppetlabs/puppet/cache/lib]) Net::ReadTimeout with #<TCPSocket:(closed)> Jul 21 20:01:30 bac102 puppet-agent[147547]: (Facter) invalid or malformed lldp data: MalformedDataError: no lldp interface data found Jul 21 22:03:28 bac102 puppet-agent[147547]: Could not retrieve catalog from remote server: Request to https://openvox08-cmp0.cs.umd.edu:8140/puppet/v3/catalog/bac102.cs.umd.edu?e... timed out read operation after 7314.048 seconds Jul 21 22:03:28 bac102 puppet-agent[147547]: Wrapped exception: Jul 21 22:03:28 bac102 puppet-agent[147547]: Net::ReadTimeout with #<TCPSocket:(closed)> Jul 21 22:03:28 bac102 puppet-agent[147547]: Not using cache on failed catalog Jul 21 22:03:28 bac102 puppet-agent[147547]: Could not retrieve catalog; skipping run Jul 21 22:03:29 bac102 setroubleshoot[171336]: failed to retrieve rpm info for path '/etc/aliases.lmdb': == biggulp.cs.umd.edu (3 distinct, 3 total) == Jul 21 21:44:48 biggulp.cs.umd.edu sshd-session[3543250]: pam_access(sshd:auth): access denied for user `admin' from `45.154.244.149' Jul 21 21:44:48 biggulp.cs.umd.edu krb5_child[3543252]: Client 'admin@UMD.EDU' not found in Kerberos database Jul 21 21:44:48 biggulp.cs.umd.edu sshd-session[3543248]: error: PAM: System error for admin from 45.154.244.149 == contest (1 distinct, 34 total) == Jul 21 21:05:33 contest goferd[994]: [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, 224 total) == Jul 21 21:04:41 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x224] == hackerman (1 distinct, 1 total) == Jul 21 21:19:01 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.G8RDT3”: Permission denied == idm00 (1 distinct, 1 total) == Jul 21 21:51:02 idm00 named[1455]: client @0x7f330c5f12a8 10.73.240.42#65256: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Jul 21 21:34:57 idmp0 named[5198]: client @0x7f9930012608 10.73.240.43#59423: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 44 total) == Jul 21 21:12:57 itmon02 sshd[1904]: error: beginning MaxStartups throttling [x44] == netman.cs.umd.edu (1 distinct, 2 total) == Jul 21 21:47:50 netman.cs.umd.edu krb5_child[3005598]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == newhonors2 (1 distinct, 24 total) == Jul 21 21:13:03 newhonors2 dhcpcd[96463]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 21 21:09:09 outbound00.cs.umd.edu python3[2416777]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Jul 21 21:13:07 outbound01.cs.umd.edu python3[444666]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Jul 21 21:13:55 sentry-docker00.cs.umd.edu systemd-udevd[772336]: Could not generate persistent MAC address for vethdef62c2: No such file or directory Jul 21 21:13:55 sentry-docker00.cs.umd.edu systemd-udevd[772337]: Could not generate persistent MAC address for vethc405070: No such file or directory Jul 21 21:16:02 sentry-docker00.cs.umd.edu systemd-udevd[773355]: link_config: could not get ethtool features for veth88a6e37 Jul 21 21:16:02 sentry-docker00.cs.umd.edu systemd-udevd[773355]: Could not set offload features of veth88a6e37: No such device Jul 21 21:16:02 sentry-docker00.cs.umd.edu systemd-udevd[773424]: Could not generate persistent MAC address for vethc7492f9: No such file or directory Jul 21 21:16:02 sentry-docker00.cs.umd.edu systemd-udevd[773425]: Could not generate persistent MAC address for veth2f91b98: No such file or directory Jul 21 21:16:02 sentry-docker00.cs.umd.edu systemd-udevd[773428]: Could not generate persistent MAC address for veth7359775: No such file or directory Jul 21 21:16:02 sentry-docker00.cs.umd.edu systemd-udevd[773429]: Could not generate persistent MAC address for vethe796186: No such file or directory Jul 21 21:16:02 sentry-docker00.cs.umd.edu systemd-udevd[773452]: Could not generate persistent MAC address for veth10e85e6: No such file or directory Jul 21 21:16:02 sentry-docker00.cs.umd.edu systemd-udevd[773453]: Could not generate persistent MAC address for veth445a100: No such file or directory Jul 21 21:16:02 sentry-docker00.cs.umd.edu systemd-udevd[773471]: Could not generate persistent MAC address for veth16ccf49: No such file or directory Jul 21 21:16:02 sentry-docker00.cs.umd.edu systemd-udevd[773478]: Could not generate persistent MAC address for vethe51a428: No such file or directory Jul 21 21:33:59 sentry-docker00.cs.umd.edu systemd-udevd[781736]: Could not generate persistent MAC address for veth501bc05: No such file or directory Jul 21 21:33:59 sentry-docker00.cs.umd.edu systemd-udevd[781737]: Could not generate persistent MAC address for vethc1c9dc8: No such file or directory Jul 21 21:36:10 sentry-docker00.cs.umd.edu systemd-udevd[782797]: link_config: could not get ethtool features for vethc7492f9 Jul 21 21:36:10 sentry-docker00.cs.umd.edu systemd-udevd[782797]: Could not set offload features of vethc7492f9: No such device Jul 21 21:36:10 sentry-docker00.cs.umd.edu systemd-udevd[782829]: Could not generate persistent MAC address for veth9a8e42a: No such file or directory Jul 21 21:36:10 sentry-docker00.cs.umd.edu systemd-udevd[782830]: Could not generate persistent MAC address for veth69f5aef: No such file or directory Jul 21 21:36:10 sentry-docker00.cs.umd.edu systemd-udevd[782833]: Could not generate persistent MAC address for veth7232ab9: No such file or directory Jul 21 21:36:10 sentry-docker00.cs.umd.edu systemd-udevd[782834]: Could not generate persistent MAC address for vethc999152: No such file or directory Jul 21 21:36:10 sentry-docker00.cs.umd.edu systemd-udevd[782841]: Could not generate persistent MAC address for veth4cf9315: No such file or directory Jul 21 21:36:10 sentry-docker00.cs.umd.edu systemd-udevd[782850]: Could not generate persistent MAC address for veth07676e8: No such file or directory Jul 21 21:36:10 sentry-docker00.cs.umd.edu systemd-udevd[782841]: Could not generate persistent MAC address for veth7b4dd4b: No such file or directory Jul 21 21:36:10 sentry-docker00.cs.umd.edu systemd-udevd[782838]: Could not generate persistent MAC address for vetha547466: No such file or directory Jul 21 21:54:07 sentry-docker00.cs.umd.edu systemd-udevd[791221]: Could not generate persistent MAC address for veth1e30268: No such file or directory Jul 21 21:54:07 sentry-docker00.cs.umd.edu systemd-udevd[791222]: Could not generate persistent MAC address for vethf576611: No such file or directory Jul 21 21:56:19 sentry-docker00.cs.umd.edu systemd-udevd[792317]: link_config: could not get ethtool features for vetha547466 Jul 21 21:56:19 sentry-docker00.cs.umd.edu systemd-udevd[792317]: Could not set offload features of vetha547466: No such device Jul 21 21:56:19 sentry-docker00.cs.umd.edu systemd-udevd[792331]: Could not generate persistent MAC address for veth3861087: No such file or directory Jul 21 21:56:19 sentry-docker00.cs.umd.edu systemd-udevd[792332]: Could not generate persistent MAC address for vethad2a13c: No such file or directory ... 6 more distinct messages not shown == strawberry (2 distinct, 8 total) == Jul 21 21: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 21 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (1 distinct, 12 total) == Jul 21 21:08:06 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x12] == submit26-b9-3 (9 distinct, 12 total) == Jul 21 21:20:33 submit26-b9-3 setroubleshoot[494034]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 5b912a44-22fd-4560-b201-2a4e289b73f5 Jul 21 21:20:33 submit26-b9-3 setroubleshoot[494034]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 7f1df1e4-725e-4953-98eb-1079f908f543 Jul 21 21:20:33 submit26-b9-3 setroubleshoot[494034]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 40b8852a-f77b-44b4-affe-5f11fa33de43 [x2] Jul 21 21:20:33 submit26-b9-3 setroubleshoot[494034]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.iQ6mLv/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 [x2] Jul 21 21:20:33 submit26-b9-3 setroubleshoot[494034]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e9f0bfff-7784-4126-baa4-2bb06da56591 [x2] Jul 21 21:20:33 submit26-b9-3 setroubleshoot[494034]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.iQ6mLv. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 21 21:20:33 submit26-b9-3 setroubleshoot[494034]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 10e38c64-b65f-4cdd-901e-4375652d9a42 Jul 21 21:20:33 submit26-b9-3 setroubleshoot[494034]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 7fd9cf72-ef38-48e1-b6aa-b571b26a7b22 Jul 21 21:20:33 submit26-b9-3 setroubleshoot[494034]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l b9b11116-89bd-4a3c-980c-1d422c5dcee4 == submit26-clnb9 (10 distinct, 14 total) == Jul 21 21:31:51 submit26-clnb9 setroubleshoot[1112972]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 6783ed2b-5ae4-42b5-975a-4bf50eec4658 [x2] Jul 21 21:31:51 submit26-clnb9 setroubleshoot[1112972]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 9e7fa955-cc30-4804-ac8c-e1779e85946c [x2] Jul 21 21:31:51 submit26-clnb9 setroubleshoot[1112972]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 69bfa6e3-089c-40ff-9563-fd30787d0774 Jul 21 21:31:51 submit26-clnb9 setroubleshoot[1112972]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.7Er5pc/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Jul 21 21:31:51 submit26-clnb9 setroubleshoot[1112972]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l edacddcf-16ed-4dc3-8d82-7c597d5dee23 Jul 21 21:31:51 submit26-clnb9 setroubleshoot[1112972]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.7Er5pc. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 21 21:31:51 submit26-clnb9 setroubleshoot[1112972]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 81cb3698-78f8-440a-8e3c-e5d1041e6b78 [x2] Jul 21 21:31:51 submit26-clnb9 setroubleshoot[1112972]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 792b472a-115c-4799-9805-fc7436f916b9 Jul 21 21:31:51 submit26-clnb9 setroubleshoot[1112972]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 15c83a86-837b-41e2-b662-b39cd4e361cb [x2] Jul 21 21:31:51 submit26-clnb9 setroubleshoot[1112972]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GYF68Q. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c