Command: /usr/local/sbin/syslog-digest.py Time : 0.5331s Status : exited 0 Output : Syslog digest — 2026-07-31 02:05 EDT Processed 4,286 lines, filtered 3,331 (77%). 955 unknown (123 distinct) from 24 host(s). == abuse (1 distinct, 346 total) == Jul 31 01: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 ] [x346] == alec.cs.umd.edu (3 distinct, 61 total) == Jul 31 01:05:23 alec.cs.umd.edu setroubleshoot[714366]: failed to retrieve rpm info for path '/run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3': [x12] Jul 31 01:05:23 alec.cs.umd.edu sedispatch[1526]: AVC Message regarding setroubleshoot, ignoring message [x24] Jul 31 01:05:23 alec.cs.umd.edu setroubleshoot[714366]: 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 [x25] == b0b02.cs.umd.edu (1 distinct, 1 total) == Jul 31 01:38:31 b0b02.cs.umd.edu rustdesk[1227497]: cannot open display: == contest (9 distinct, 41 total) == Jul 31 01:06:46 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] Jul 31 01:48:15 contest setroubleshoot[370083]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.ZdIr96. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Jul 31 01:48:15 contest setroubleshoot[370083]: SELinux is preventing /usr/bin/gpgconf from add_name access on the directory repodata. For complete SELinux messages run: sealert -l 41cf7b1b-0f34-4609-98f2-b66e7825fef7 Jul 31 01:48:15 contest setroubleshoot[370083]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file mirrorlist. For complete SELinux messages run: sealert -l fc20ff92-ea83-4f38-a24b-ddfd737a3141 Jul 31 01:48:16 contest setroubleshoot[370083]: SELinux is preventing /usr/libexec/platform-python3.6 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l ac675631-fa35-4e93-adc9-b692b18e53e5 Jul 31 01:48:16 contest setroubleshoot[370083]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.ZdIr96. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Jul 31 01:48:20 contest setroubleshoot[370083]: SELinux is preventing /usr/libexec/platform-python3.6 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 7e499113-2fd7-4f67-bec6-3521efbe3637 Jul 31 01:48:23 contest setroubleshoot[370083]: SELinux is preventing rhsmcertd-worke from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 22835727-7fef-4cfb-b3b5-881f66888317 Jul 31 01:48:36 contest setroubleshoot[370135]: SELinux is preventing /usr/libexec/platform-python3.6 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3928930b-a1ed-448d-950b-0665ac2adef8 == csfw00a (2 distinct, 256 total) == Jul 31 01:04:52 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x248] Jul 31 01:09:22 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x8] == hackerman (1 distinct, 1 total) == Jul 31 01: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.MM3US3”: Permission denied == hazfs.cs.umd.edu (11 distinct, 66 total) == Jul 31 01:51:21 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Jul 31 01:51:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Jul 31 01:51:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Jul 31 01:51:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Jul 31 01:51:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Jul 31 01:51:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Jul 31 01:51:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Jul 31 01:51:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Jul 31 01:51:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Jul 31 01:51:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Jul 31 01:51:21 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Jul 31 01:51:12 idm00 named[1455]: client @0x7f331587f1d8 10.73.240.42#50279: update '73.10.in-addr.arpa/IN' denied == idmp0 (2 distinct, 2 total) == Jul 31 01:24:04 idmp0 named[5198]: client @0x7f992002e6d8 10.73.245.12#55144: update '73.10.in-addr.arpa/IN' denied Jul 31 01:36:02 idmp0 named[5198]: client @0x7f99300523f8 10.73.240.43#57038: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (3 distinct, 6 total) == Jul 31 01:26:01 inbound01.cs.umd.edu krb5_child[3560277]: Client 'admin@UMD.EDU' not found in Kerberos database Jul 31 02:02:11 inbound01.cs.umd.edu cockpit-ws[3568460]: Received unexpected TLS connection; use cockpit-tls for TLS termination [x3] Jul 31 02:03:57 inbound01.cs.umd.edu sshd-session[3569001]: error: Protocol major versions differ: 2 vs. 1 [x2] == irb2156 (3 distinct, 3 total) == Jul 31 01:34:45 irb2156 cosmic-greeter[4753]: Failed to create watcher for com.system76.CosmicTk Jul 31 01:34:45 irb2156 cosmic-greeter[4753]: Failed to create watcher for com.system76.CosmicTheme.Mode Jul 31 01:34:45 irb2156 cosmic-greeter[4753]: Failed to create watcher for com.system76.CosmicTheme.Dark == itmon02 (1 distinct, 44 total) == Jul 31 01:07:48 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x44] == krispykreme.cs.umd.edu (4 distinct, 4 total) == Jul 31 01:06:07 krispykreme.cs.umd.edu sshd-session[1408658]: pam_access(sshd:auth): access denied for user `admin' from `34.140.157.205' Jul 31 01:06:07 krispykreme.cs.umd.edu krb5_child[1408660]: Client 'admin@UMD.EDU' not found in Kerberos database Jul 31 01:06:07 krispykreme.cs.umd.edu sshd-session[1408656]: error: PAM: System error for admin from 34.140.157.205 Jul 31 01:06:12 krispykreme.cs.umd.edu sshd-session[1408662]: error: Protocol major versions differ: 2 vs. 1 == netman.cs.umd.edu (3 distinct, 6 total) == Jul 31 01:55:23 netman.cs.umd.edu krb5_child[3125814]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Jul 31 01:55:28 netman.cs.umd.edu sshd[3125811]: error: PAM: Authentication failure for admin from 34.77.183.14 Jul 31 01:56:43 netman.cs.umd.edu sshd[3126344]: error: Protocol major versions differ: 2 vs. 1 == newhonors2 (1 distinct, 24 total) == Jul 31 01:13:03 newhonors2 dhcpcd[520671]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 31 01:09:09 outbound00.cs.umd.edu python3[1312995]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Jul 31 01:13:06 outbound01.cs.umd.edu python3[3539423]: ldapdb [x6] == peach.cs.umd.edu (2 distinct, 2 total) == Jul 31 02:02:08 peach.cs.umd.edu setroubleshoot[1781784]: SELinux is preventing /usr/bin/qemu-ga from search access on the directory /var/lib/containers/storage/overlay. For complete SELinux messages run: sealert -l ba415951-a2c6-424e-b17d-305c5300b9f3 Jul 31 02:02:08 peach.cs.umd.edu setroubleshoot[1781784]: SELinux is preventing /usr/bin/qemu-ga from search access on the directory /var/lib/containers/storage/overlay. For complete SELinux messages run: sealert -l 6aeb0956-fcf2-462a-ae4d-439b912c16d0 == sentry-docker00.cs.umd.edu (42 distinct, 42 total) == Jul 31 01:06:19 sentry-docker00.cs.umd.edu systemd-udevd[2889727]: link_config: could not get ethtool features for veth3f4f1a2 Jul 31 01:06:19 sentry-docker00.cs.umd.edu systemd-udevd[2889727]: Could not set offload features of veth3f4f1a2: No such device Jul 31 01:06:19 sentry-docker00.cs.umd.edu systemd-udevd[2889753]: Could not generate persistent MAC address for veth766b0c7: No such file or directory Jul 31 01:06:19 sentry-docker00.cs.umd.edu systemd-udevd[2889754]: Could not generate persistent MAC address for veth37e1695: No such file or directory Jul 31 01:06:19 sentry-docker00.cs.umd.edu systemd-udevd[2889757]: Could not generate persistent MAC address for veth291aaed: No such file or directory Jul 31 01:06:19 sentry-docker00.cs.umd.edu systemd-udevd[2889758]: Could not generate persistent MAC address for veth2eb6c5c: No such file or directory Jul 31 01:06:19 sentry-docker00.cs.umd.edu systemd-udevd[2889781]: Could not generate persistent MAC address for vethdc8c36b: No such file or directory Jul 31 01:06:19 sentry-docker00.cs.umd.edu systemd-udevd[2889782]: Could not generate persistent MAC address for veth0f4fbc4: No such file or directory Jul 31 01:06:19 sentry-docker00.cs.umd.edu systemd-udevd[2889800]: Could not generate persistent MAC address for vetha4d6646: No such file or directory Jul 31 01:06:19 sentry-docker00.cs.umd.edu systemd-udevd[2889796]: Could not generate persistent MAC address for vethfd39e82: No such file or directory Jul 31 01:11:13 sentry-docker00.cs.umd.edu systemd-udevd[2892775]: link_config: could not get ethtool features for vethb763bbb Jul 31 01:11:13 sentry-docker00.cs.umd.edu systemd-udevd[2892775]: Could not set offload features of vethb763bbb: No such device Jul 31 01:11:14 sentry-docker00.cs.umd.edu systemd-udevd[2892791]: Could not generate persistent MAC address for vethb4b5fd4: No such file or directory Jul 31 01:11:14 sentry-docker00.cs.umd.edu systemd-udevd[2892792]: Could not generate persistent MAC address for vethdef985b: No such file or directory Jul 31 01:26:27 sentry-docker00.cs.umd.edu systemd-udevd[2899380]: link_config: could not get ethtool features for vetha4d6646 Jul 31 01:26:27 sentry-docker00.cs.umd.edu systemd-udevd[2899380]: Could not set offload features of vetha4d6646: No such device Jul 31 01:26:27 sentry-docker00.cs.umd.edu systemd-udevd[2899408]: Could not generate persistent MAC address for veth9c43a45: No such file or directory Jul 31 01:26:27 sentry-docker00.cs.umd.edu systemd-udevd[2899409]: Could not generate persistent MAC address for veth709ff3a: No such file or directory Jul 31 01:26:27 sentry-docker00.cs.umd.edu systemd-udevd[2899412]: Could not generate persistent MAC address for vetha8c89ce: No such file or directory Jul 31 01:26:27 sentry-docker00.cs.umd.edu systemd-udevd[2899413]: Could not generate persistent MAC address for veth612922d: No such file or directory Jul 31 01:26:27 sentry-docker00.cs.umd.edu systemd-udevd[2899431]: Could not generate persistent MAC address for vethe128178: No such file or directory Jul 31 01:26:27 sentry-docker00.cs.umd.edu systemd-udevd[2899422]: Could not generate persistent MAC address for veth5ac0797: No such file or directory Jul 31 01:26:27 sentry-docker00.cs.umd.edu systemd-udevd[2899438]: Could not generate persistent MAC address for vethcd1fc4e: No such file or directory Jul 31 01:26:27 sentry-docker00.cs.umd.edu systemd-udevd[2899440]: Could not generate persistent MAC address for vethf39c945: No such file or directory Jul 31 01:31:22 sentry-docker00.cs.umd.edu systemd-udevd[2902481]: link_config: could not get ethtool features for vethb4b5fd4 Jul 31 01:31:22 sentry-docker00.cs.umd.edu systemd-udevd[2902481]: Could not set offload features of vethb4b5fd4: No such device Jul 31 01:31:22 sentry-docker00.cs.umd.edu systemd-udevd[2902490]: Could not generate persistent MAC address for veth58557a7: No such file or directory Jul 31 01:31:22 sentry-docker00.cs.umd.edu systemd-udevd[2902491]: Could not generate persistent MAC address for veth9c791ab: No such file or directory Jul 31 01:46:35 sentry-docker00.cs.umd.edu systemd-udevd[2908757]: link_config: could not get ethtool features for vethe128178 Jul 31 01:46:35 sentry-docker00.cs.umd.edu systemd-udevd[2908757]: Could not set offload features of vethe128178: No such device ... 12 more distinct messages not shown == strawberry (2 distinct, 8 total) == Jul 31 01: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 31 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (9 distinct, 9 total) == Jul 31 01:12:50 submit26-b9-2 setroubleshoot[686484]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l d506243c-d61e-48f3-b42a-4592c913deb0 Jul 31 01:12:50 submit26-b9-2 setroubleshoot[686484]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3b4752ac-1b9a-4af9-a05b-32e4c2eb13ab Jul 31 01:12:50 submit26-b9-2 setroubleshoot[686484]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 29e5adbd-4381-4467-b40d-a2219101e096 Jul 31 01:12:50 submit26-b9-2 setroubleshoot[686484]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.lzUFMI/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Jul 31 01:12:50 submit26-b9-2 setroubleshoot[686484]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e5f9af40-1f63-4924-b012-27ab2a7b2266 Jul 31 01:12:50 submit26-b9-2 setroubleshoot[686484]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.lzUFMI. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Jul 31 01:12:51 submit26-b9-2 setroubleshoot[686484]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 63cd60e1-1e61-4276-afea-dd8526ffe8b2 Jul 31 01:12:51 submit26-b9-2 setroubleshoot[686484]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 81c7e9ec-e023-4c6d-b1ad-c02a242e655e Jul 31 01:12:51 submit26-b9-2 setroubleshoot[686484]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 6ae9a597-e123-4d74-8eec-a8ebe0f5e4d0 == submit26-b9-3 (9 distinct, 9 total) == Jul 31 01:20:37 submit26-b9-3 setroubleshoot[719851]: 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 31 01:20:37 submit26-b9-3 setroubleshoot[719851]: 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 31 01:20:37 submit26-b9-3 setroubleshoot[719851]: 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 Jul 31 01:20:37 submit26-b9-3 setroubleshoot[719851]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Fo5POm/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Jul 31 01:20:37 submit26-b9-3 setroubleshoot[719851]: 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 Jul 31 01:20:37 submit26-b9-3 setroubleshoot[719851]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Fo5POm. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 31 01:20:37 submit26-b9-3 setroubleshoot[719851]: 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 31 01:20:37 submit26-b9-3 setroubleshoot[719851]: 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 31 01:20:37 submit26-b9-3 setroubleshoot[719851]: 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 (9 distinct, 9 total) == Jul 31 01:31:55 submit26-clnb9 setroubleshoot[1565392]: 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 Jul 31 01:31:55 submit26-clnb9 setroubleshoot[1565392]: 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 Jul 31 01:31:55 submit26-clnb9 setroubleshoot[1565392]: 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 31 01:31:55 submit26-clnb9 setroubleshoot[1565392]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.6RIuyx/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Jul 31 01:31:55 submit26-clnb9 setroubleshoot[1565392]: 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 31 01:31:55 submit26-clnb9 setroubleshoot[1565392]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.6RIuyx. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 31 01:31:55 submit26-clnb9 setroubleshoot[1565392]: 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 Jul 31 01:31:55 submit26-clnb9 setroubleshoot[1565392]: 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 31 01:31:55 submit26-clnb9 setroubleshoot[1565392]: 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 == teaching-awards (2 distinct, 2 total) == Jul 31 01:07:31 teaching-awards krb5_child[1629573]: Client 'admin@UMD.EDU' not found in Kerberos database Jul 31 01:07:43 teaching-awards sshd-session[1629582]: error: Protocol major versions differ: 2 vs. 1
participants (1)
-
cron/zfs00.cs.umd.edu