Command: /usr/local/sbin/syslog-digest.py Time : 0.0467s Status : exited 0 Output : Syslog digest — 2026-10-15 03:05 EDT Processed 1,262 lines, filtered 701 (55%). 561 unknown (170 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 15 02:28:33 b0b02.cs.umd.edu rustdesk[4004793]: cannot open display: == emaar (1 distinct, 1 total) == Oct 15 02:16:11 emaar systemd[1]: cgroup compatibility translation between legacy and unified hierarchy settings activated. See cgroup-compat debug messages for details. == florence-ruohan (9 distinct, 15 total) == Oct 15 03:04:07 florence-ruohan nologin[598553]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN Oct 15 03:04:07 florence-ruohan pipewire[598549]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied [x2] Oct 15 03:04:07 florence-ruohan pipewire[598549]: mod.rt: could not set nice-level to -11: Permission denied Oct 15 03:04:07 florence-ruohan systemd-udevd[83597]: /etc/udev/rules.d/99-virtualgl-dri.rules:1 Unknown group 'vglusers', ignoring Oct 15 03:04:07 florence-ruohan pipewire-media-session[598550]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied Oct 15 03:04:07 florence-ruohan pipewire-media-session[598550]: mod.rt: could not make thread 598569 realtime using RTKit: Permission denied Oct 15 03:04:07 florence-ruohan pipewire[598549]: mod.rt: could not make thread 598586 realtime using RTKit: Permission denied Oct 15 03:04:07 florence-ruohan pulseaudio[598551]: Failed to create secure directory (/nonexistent/.config/pulse): No such file or directory [x5] Oct 15 03:04:08 florence-ruohan puppet-agent[598559]: Certificate 'CN=florence-ruohan.cs.umd.edu' is revoked [x2] == idm00 (1 distinct, 1 total) == Oct 15 02:54:49 idm00 named[1014]: client @0x7fcbc938f7c8 10.73.240.42#56821: update '73.10.in-addr.arpa/IN' denied == idmh1 (12 distinct, 144 total) == Oct 15 02:08:26 idmh1 check-named-alive[881038]: zone cs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 15 02:08:26 idmh1 check-named-alive[881099]: zone csdlabs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 02:08:27 idmh1 check-named-alive[881160]: zone csic.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 02:08:27 idmh1 check-named-alive[881221]: zone 72.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 02:08:27 idmh1 check-named-alive[881342]: zone 88.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 02:08:27 idmh1 check-named-alive[881403]: zone 125.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 02:08:28 idmh1 check-named-alive[881464]: zone 126.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 02:08:28 idmh1 check-named-alive[881525]: zone 127.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 15 02:08:28 idmh1 check-named-alive[881586]: zone 128.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 15 02:08:28 idmh1 check-named-alive[881647]: zone 129.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 15 02:08:28 idmh1 check-named-alive[881708]: zone 130.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 15 02:08:29 idmh1 check-named-alive[881769]: zone 131.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] == idmp0 (1 distinct, 1 total) == Oct 15 02:40:03 idmp0 named[1180]: client @0x7fe038007d58 10.73.240.43#61379: update '73.10.in-addr.arpa/IN' denied == idmv0 (12 distinct, 144 total) == Oct 15 02:09:03 idmv0 check-named-alive[983661]: zone cs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 15 02:09:03 idmv0 check-named-alive[983722]: zone csdlabs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 02:09:03 idmv0 check-named-alive[983783]: zone csic.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 02:09:03 idmv0 check-named-alive[983844]: zone 72.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 02:09:04 idmv0 check-named-alive[983965]: zone 88.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 02:09:04 idmv0 check-named-alive[984026]: zone 125.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 02:09:04 idmv0 check-named-alive[984087]: zone 126.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 02:09:04 idmv0 check-named-alive[984148]: zone 127.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 15 02:09:04 idmv0 check-named-alive[984209]: zone 128.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 15 02:09:04 idmv0 check-named-alive[984270]: zone 129.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 15 02:09:05 idmv0 check-named-alive[984331]: zone 130.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 15 02:09:05 idmv0 check-named-alive[984392]: zone 131.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] == inbound00.cs.umd.edu (1 distinct, 1 total) == Oct 15 02:49:25 inbound00.cs.umd.edu krb5_child[2245138]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 5 total) == Oct 15 02:08:21 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x5] == krispykreme.cs.umd.edu (1 distinct, 1 total) == Oct 15 02:13:16 krispykreme.cs.umd.edu sshd-session[1899005]: pam_access(sshd:auth): access denied for user `lin' from `74.96.151.253' == munin (2 distinct, 44 total) == Oct 15 02:13:58 munin sudo[1031311]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x22] Oct 15 02:13:58 munin sudo[1031311]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x22] == newhonors2 (1 distinct, 24 total) == Oct 15 02:13:03 newhonors2 dhcpcd[4040993]: dhcpcd is not running [x24] == ntop00 (98 distinct, 98 total) == Oct 15 02:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9082) *** Oct 15 02:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9082, QN: 69/69, ET: 0) *** Oct 15 02:05:19 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9082, QN: 7937/7937, ET: 18) *** Oct 15 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 9083) *** Oct 15 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 9083, QN: 5196/5196, ET: 0) *** Oct 15 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 9083) *** Oct 15 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 9083, QN: 53/53, ET: 0) *** Oct 15 02:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9084) *** Oct 15 02:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9084) *** Oct 15 02:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9084, QN: 64/64, ET: 0) *** Oct 15 02:10:12 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9084, QN: 4937/4937, ET: 11) *** Oct 15 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 9085) *** Oct 15 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 9085, QN: 5121/5121, ET: 0) *** Oct 15 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 9085) *** Oct 15 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 9085, QN: 63/63, ET: 0) *** Oct 15 02:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9086) *** Oct 15 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9086) *** Oct 15 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9086, QN: 54/54, ET: 0) *** Oct 15 02:15:12 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9086, QN: 4983/4983, ET: 11) *** Oct 15 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 9087) *** Oct 15 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 9087, QN: 5016/5016, ET: 0) *** Oct 15 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 9087) *** Oct 15 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 9087, QN: 54/54, ET: 0) *** Oct 15 02:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9088) *** Oct 15 02:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 9088) *** Oct 15 02:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9088, QN: 52/52, ET: 0) *** Oct 15 02:20:13 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 9088, QN: 5288/5288, ET: 12) *** Oct 15 02:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 9089) *** Oct 15 02:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 9089, QN: 5276/5276, ET: 0) *** Oct 15 02:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 9089) *** ... 68 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 15 02:09:08 outbound00.cs.umd.edu python3[2808071]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 15 02:13:07 outbound01.cs.umd.edu python3[107818]: ldapdb [x6] == strawberry (7 distinct, 38 total) == Oct 15 02:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 15 02:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 15 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 15 02:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 15 02:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 15 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 15 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-3 (1 distinct, 4 total) == Sep 17 16:00:27 submit26-b9-3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f1 (10 distinct, 16 total) == Oct 15 02:15:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] Oct 15 02:26:05 submit26-b9-f1 setroubleshoot[2834424]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c Oct 15 02:26:05 submit26-b9-f1 setroubleshoot[2834424]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36 Oct 15 02:26:05 submit26-b9-f1 setroubleshoot[2834424]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6 [x2] Oct 15 02:26:05 submit26-b9-f1 setroubleshoot[2834424]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.PV3Muz/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d [x2] Oct 15 02:26:05 submit26-b9-f1 setroubleshoot[2834424]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee [x2] Oct 15 02:26:06 submit26-b9-f1 setroubleshoot[2834424]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.PV3Muz. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 15 02:26:06 submit26-b9-f1 setroubleshoot[2834424]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d Oct 15 02:26:06 submit26-b9-f1 setroubleshoot[2834424]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9 Oct 15 02:26:06 submit26-b9-f1 setroubleshoot[2834424]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848 == submit26-b9-f2 (9 distinct, 11 total) == Oct 15 02:06:58 submit26-b9-f2 setroubleshoot[1971839]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 [x2] Oct 15 02:06:58 submit26-b9-f2 setroubleshoot[1971839]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a [x2] Oct 15 02:06:58 submit26-b9-f2 setroubleshoot[1971839]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 Oct 15 02:06:58 submit26-b9-f2 setroubleshoot[1971839]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.GYG0Pw/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Oct 15 02:06:58 submit26-b9-f2 setroubleshoot[1971839]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 Oct 15 02:06:58 submit26-b9-f2 setroubleshoot[1971839]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GYG0Pw. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 15 02:06:58 submit26-b9-f2 setroubleshoot[1971839]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885 Oct 15 02:06:58 submit26-b9-f2 setroubleshoot[1971839]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af Oct 15 02:06:58 submit26-b9-f2 setroubleshoot[1971839]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7
participants (1)
-
cron/syslog01.cs.umd.edu