Command: /usr/local/sbin/syslog-digest.py Time : 0.0457s Status : exited 0 Output : Syslog digest — 2026-09-09 02:05 EDT Processed 2,142 lines, filtered 1,760 (82%). 382 unknown (88 distinct) from 16 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 9 01:35:27 b0b02.cs.umd.edu rustdesk[3243950]: cannot open display: == csfw00a (1 distinct, 136 total) == Sep 9 01:03:53 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x136] == hazfs.cs.umd.edu (12 distinct, 68 total) == Sep 9 01:19:02 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Sep 9 01:19:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Sep 9 01:19:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Sep 9 01:19:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Sep 9 01:19:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Sep 9 01:19:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Sep 9 01:19:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Sep 9 01:19:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Sep 9 01:19:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Sep 9 01:19:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Sep 9 01:19:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] Sep 9 01:25:02 hazfs.cs.umd.edu pcp[2364326]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2] == idm00 (1 distinct, 1 total) == Sep 9 01:53:47 idm00 named[3831946]: client @0x7f1e693cc818 10.73.240.42#54347: update '73.10.in-addr.arpa/IN' denied == idmp0 (2 distinct, 2 total) == Sep 9 01:24:51 idmp0 named[1239047]: client @0x7fd514000cc8 10.73.245.12#49692: update '73.10.in-addr.arpa/IN' denied Sep 9 01:37:42 idmp0 named[1239047]: client @0x7fd50c061a08 10.73.240.43#58601: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 37 total) == Sep 9 01:07:53 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x37] == newhonors2 (1 distinct, 24 total) == Sep 9 01:13:03 newhonors2 dhcpcd[2381793]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 9 01:09:09 outbound00.cs.umd.edu python3[2324776]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 9 01:13:06 outbound01.cs.umd.edu python3[385647]: ldapdb [x6] == portal (1 distinct, 2 total) == Sep 9 01:37:49 portal (httpd)[15777]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS [x2] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 9 01:23:31 sentry-docker00.cs.umd.edu systemd-udevd[723774]: link_config: could not get ethtool features for vethfae380e Sep 9 01:23:31 sentry-docker00.cs.umd.edu systemd-udevd[723774]: Could not set offload features of vethfae380e: No such device Sep 9 01:23:31 sentry-docker00.cs.umd.edu systemd-udevd[723810]: Could not generate persistent MAC address for veth9c66c6a: No such file or directory Sep 9 01:23:31 sentry-docker00.cs.umd.edu systemd-udevd[723811]: Could not generate persistent MAC address for vethf289b9c: No such file or directory Sep 9 01:23:31 sentry-docker00.cs.umd.edu systemd-udevd[723814]: Could not generate persistent MAC address for veth18490cd: No such file or directory Sep 9 01:23:31 sentry-docker00.cs.umd.edu systemd-udevd[723815]: Could not generate persistent MAC address for vethdb67bdc: No such file or directory Sep 9 01:23:31 sentry-docker00.cs.umd.edu systemd-udevd[723817]: Could not generate persistent MAC address for vethea21366: No such file or directory Sep 9 01:23:31 sentry-docker00.cs.umd.edu systemd-udevd[723829]: Could not generate persistent MAC address for veth71bd121: No such file or directory Sep 9 01:23:31 sentry-docker00.cs.umd.edu systemd-udevd[723817]: Could not generate persistent MAC address for veth37e997e: No such file or directory Sep 9 01:23:31 sentry-docker00.cs.umd.edu systemd-udevd[723829]: Could not generate persistent MAC address for veth01b299a: No such file or directory Sep 9 01:23:31 sentry-docker00.cs.umd.edu systemd-udevd[723821]: Could not generate persistent MAC address for veth97138bf: No such file or directory Sep 9 01:23:31 sentry-docker00.cs.umd.edu systemd-udevd[723829]: Could not generate persistent MAC address for veth156bfac: No such file or directory Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733065]: link_config: could not get ethtool features for veth18490cd Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733065]: Could not set offload features of veth18490cd: No such device Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733163]: link_config: could not get ethtool features for veth71bd121 Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733163]: Could not set offload features of veth71bd121: No such device Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733187]: Could not generate persistent MAC address for veth15de9b9: No such file or directory Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733188]: Could not generate persistent MAC address for vethebf9a50: No such file or directory Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733191]: Could not generate persistent MAC address for veth899f13f: No such file or directory Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733192]: Could not generate persistent MAC address for vetha029ffd: No such file or directory Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733215]: Could not generate persistent MAC address for vethe64e43c: No such file or directory Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733216]: Could not generate persistent MAC address for vethd219b10: No such file or directory Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733234]: Could not generate persistent MAC address for veth3f36ec4: No such file or directory Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733221]: Could not generate persistent MAC address for veth31e13ac: No such file or directory Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733221]: Could not generate persistent MAC address for vethea900ab: No such file or directory Sep 9 01:43:39 sentry-docker00.cs.umd.edu systemd-udevd[733233]: Could not generate persistent MAC address for veth7155f89: No such file or directory Sep 9 02:03:47 sentry-docker00.cs.umd.edu systemd-udevd[742627]: link_config: could not get ethtool features for veth899f13f Sep 9 02:03:47 sentry-docker00.cs.umd.edu systemd-udevd[742627]: Could not set offload features of veth899f13f: No such device Sep 9 02:03:48 sentry-docker00.cs.umd.edu systemd-udevd[742665]: Could not generate persistent MAC address for veth9fa75a3: No such file or directory Sep 9 02:03:48 sentry-docker00.cs.umd.edu systemd-udevd[742666]: Could not generate persistent MAC address for veth2952995: No such file or directory ... 8 more distinct messages not shown == soul (1 distinct, 1 total) == Sep 9 01:57:01 soul krb5_child[1591802]: Client 'admin@UMD.EDU' not found in Kerberos database == strawberry (7 distinct, 38 total) == Sep 9 01:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 9 01:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 9 01:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 9 01:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 9 01:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 9 01:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 9 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 9 total) == Sep 9 01:06:34 submit26-b9-f3 setroubleshoot[13134]: 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 9 01:06:34 submit26-b9-f3 setroubleshoot[13134]: 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 9 01:06:34 submit26-b9-f3 setroubleshoot[13134]: 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 9 01:06:34 submit26-b9-f3 setroubleshoot[13134]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.YElkv7/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 9 01:06:34 submit26-b9-f3 setroubleshoot[13134]: 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 9 01:06:34 submit26-b9-f3 setroubleshoot[13134]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.YElkv7. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 9 01:06:34 submit26-b9-f3 setroubleshoot[13134]: 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 9 01:06:34 submit26-b9-f3 setroubleshoot[13134]: 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 9 01:06:34 submit26-b9-f3 setroubleshoot[13134]: 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 == submit26-b9-f4 (10 distinct, 12 total) == Sep 9 01:24:36 submit26-b9-f4 setroubleshoot[12167]: 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 [x2] Sep 9 01:24:36 submit26-b9-f4 setroubleshoot[12167]: 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 [x2] Sep 9 01:24:36 submit26-b9-f4 setroubleshoot[12167]: 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 9 01:24:36 submit26-b9-f4 setroubleshoot[12167]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.HzJ8b3/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 9 01:24:36 submit26-b9-f4 setroubleshoot[12167]: 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 9 01:24:36 submit26-b9-f4 setroubleshoot[12167]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.HzJ8b3. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 9 01:24:36 submit26-b9-f4 setroubleshoot[12167]: SELinux is preventing /usr/bin/python3.9 from read access on the directory /tmp/libdnf.HzJ8b3. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 9 01:24:36 submit26-b9-f4 setroubleshoot[12167]: 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 9 01:24:36 submit26-b9-f4 setroubleshoot[12167]: 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 9 01:24:36 submit26-b9-f4 setroubleshoot[12167]: 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 == tma-0 (1 distinct, 1 total) == Sep 9 01:58:05 tma-0 sshd[14997]: error: PAM: Authentication failure for admin from 12.87.175.207.bc.googleusercontent.com
participants (1)
-
cron/syslog01.cs.umd.edu