Command: /usr/local/sbin/syslog-digest.py Time : 0.0459s Status : exited 0 Output : Syslog digest — 2026-10-13 10:05 EDT Processed 1,220 lines, filtered 684 (56%). 536 unknown (173 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 13 09:25:58 b0b02.cs.umd.edu rustdesk[3380266]: cannot open display: == cheezit.cs.umd.edu (1 distinct, 1 total) == Oct 13 09:51:17 cheezit.cs.umd.edu sshd-session[2283512]: error: send_error: write: Connection reset by peer == galax (3 distinct, 3 total) == Oct 13 09:07:56 galax kernel: kauditd_printk_skb: 5 callbacks suppressed Oct 13 09:32:12 galax update-notifier[790573]: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code. Oct 13 09:32:12 galax update-notifier[790573]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed == idm00 (1 distinct, 1 total) == Oct 13 09:54:47 idm00 named[1014]: client @0x7fcbc00216e8 10.73.240.42#62219: update '73.10.in-addr.arpa/IN' denied == idmh1 (15 distinct, 158 total) == Oct 13 09:05:46 idmh1 check-named-alive[324010]: zone cs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 09:05:46 idmh1 check-named-alive[324071]: zone csdlabs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 09:05:46 idmh1 check-named-alive[324132]: zone csic.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 09:05:47 idmh1 check-named-alive[324193]: zone 72.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 09:05:47 idmh1 check-named-alive[324254]: zone 73.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 09:05:47 idmh1 check-named-alive[324315]: zone 88.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 09:05:47 idmh1 check-named-alive[324376]: zone 125.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 09:05:47 idmh1 check-named-alive[324437]: zone 126.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 09:05:48 idmh1 check-named-alive[324498]: zone 127.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 09:05:48 idmh1 check-named-alive[324559]: zone 128.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 09:05:48 idmh1 check-named-alive[324620]: zone 129.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 09:05:48 idmh1 check-named-alive[324681]: zone 130.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 09:05:48 idmh1 check-named-alive[324742]: zone 131.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 10:00:14 idmh1 irqbalance[1021]: Cannot change IRQ 63 affinity: Operation not permitted Oct 13 10:00:14 idmh1 irqbalance[1021]: IRQ 63 affinity is now unmanaged == idmp0 (1 distinct, 1 total) == Oct 13 09:39:20 idmp0 named[1180]: client @0x7fe044029358 10.73.240.43#58114: update '73.10.in-addr.arpa/IN' denied == idmv0 (13 distinct, 156 total) == Oct 13 09:06:10 idmv0 check-named-alive[345541]: zone cs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 09:06:10 idmv0 check-named-alive[345602]: zone csdlabs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 09:06:10 idmv0 check-named-alive[345663]: zone csic.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 09:06:10 idmv0 check-named-alive[345724]: zone 72.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 09:06:11 idmv0 check-named-alive[345785]: zone 73.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 09:06:11 idmv0 check-named-alive[345846]: zone 88.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 09:06:11 idmv0 check-named-alive[345907]: zone 125.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 09:06:11 idmv0 check-named-alive[345968]: zone 126.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 09:06:11 idmv0 check-named-alive[346029]: zone 127.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 09:06:11 idmv0 check-named-alive[346090]: zone 128.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 09:06:12 idmv0 check-named-alive[346151]: zone 129.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 09:06:12 idmv0 check-named-alive[346212]: zone 130.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 09:06:12 idmv0 check-named-alive[346273]: 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 13 10:01:17 inbound00.cs.umd.edu sshd-session[1669365]: fatal: userauth_pubkey: parse publickey packet: incomplete message [preauth] == irb2156 (9 distinct, 13 total) == Oct 13 09:48:20 irb2156 systemd[1]: insights-client.service: Start request repeated too quickly. Oct 13 10:03:09 irb2156 packagekitd[1323448]: Failed to get cache filename for firefox Oct 13 10:03:09 irb2156 packagekitd[1323448]: Failed to get cache filename for firefox-nightly Oct 13 10:03:09 irb2156 packagekitd[1323448]: Failed to get cache filename for gnome-control-center-filesystem [x3] Oct 13 10:03:09 irb2156 packagekitd[1323448]: Failed to get cache filename for kernel-headers Oct 13 10:03:09 irb2156 packagekitd[1323448]: Failed to get cache filename for python3-perf Oct 13 10:03:09 irb2156 packagekitd[1323448]: Failed to get cache filename for gd Oct 13 10:03:09 irb2156 packagekitd[1323448]: Failed to get cache filename for kernel-devel Oct 13 10:03:09 irb2156 packagekitd[1323448]: Failed to get cache filename for kernel [x3] == itmon02 (1 distinct, 2 total) == Oct 13 09:42:59 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 8 total) == Oct 13 09:24:10 munin sudo[146958]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Oct 13 09:24:10 munin sudo[146958]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Oct 13 09:13:03 newhonors2 dhcpcd[3963816]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Oct 13 09:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8098) *** Oct 13 09:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8098, QN: 59/59, ET: 0) *** Oct 13 09:05:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8098, QN: 5080/5080, ET: 10) *** Oct 13 09:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8099) *** Oct 13 09:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8099, QN: 5360/5360, ET: 0) *** Oct 13 09:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8099) *** Oct 13 09:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8099, QN: 65/65, ET: 0) *** Oct 13 09:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8100) *** Oct 13 09:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8100) *** Oct 13 09:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8100, QN: 65/65, ET: 0) *** Oct 13 09:10:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8100, QN: 4943/4943, ET: 10) *** Oct 13 09:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8101) *** Oct 13 09:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8101, QN: 4567/4567, ET: 0) *** Oct 13 09:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8101) *** Oct 13 09:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8101, QN: 60/60, ET: 0) *** Oct 13 09:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8102) *** Oct 13 09:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8102) *** Oct 13 09:15:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8102, QN: 56/56, ET: 1) *** Oct 13 09:15:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8102, QN: 4715/4715, ET: 10) *** Oct 13 09:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8103) *** Oct 13 09:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8103, QN: 4814/4814, ET: 0) *** Oct 13 09:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8103) *** Oct 13 09:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8103, QN: 70/70, ET: 0) *** Oct 13 09:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8104) *** Oct 13 09:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8104) *** Oct 13 09:20:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8104, QN: 83/83, ET: 1) *** Oct 13 09:20:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8104, QN: 4772/4772, ET: 10) *** Oct 13 09:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8105) *** Oct 13 09:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8105, QN: 5320/5320, ET: 0) *** Oct 13 09:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8105) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 13 09:09:09 outbound00.cs.umd.edu python3[2239204]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 13 09:13:06 outbound01.cs.umd.edu python3[3726101]: ldapdb [x6] == strawberry (7 distinct, 38 total) == Oct 13 09:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 13 09:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 13 09:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 13 09:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 13 09:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 13 09:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 13 09:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Oct 13 09:05:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (9 distinct, 11 total) == Oct 13 09:06:51 submit26-b9-f3 setroubleshoot[3221829]: 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 [x2] Oct 13 09:06:51 submit26-b9-f3 setroubleshoot[3221829]: 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 [x2] Oct 13 09:06:51 submit26-b9-f3 setroubleshoot[3221829]: 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 Oct 13 09:06:51 submit26-b9-f3 setroubleshoot[3221829]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.o2p6gk/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 13 09:06:51 submit26-b9-f3 setroubleshoot[3221829]: 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 Oct 13 09:06:51 submit26-b9-f3 setroubleshoot[3221829]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.o2p6gk. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 13 09:06:51 submit26-b9-f3 setroubleshoot[3221829]: 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 Oct 13 09:06:51 submit26-b9-f3 setroubleshoot[3221829]: 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 Oct 13 09:06:51 submit26-b9-f3 setroubleshoot[3221829]: 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 (9 distinct, 9 total) == Oct 13 09:24:56 submit26-b9-f4 setroubleshoot[1082130]: 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 Oct 13 09:24:56 submit26-b9-f4 setroubleshoot[1082130]: 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 Oct 13 09:24:56 submit26-b9-f4 setroubleshoot[1082130]: 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 Oct 13 09:24:56 submit26-b9-f4 setroubleshoot[1082130]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.9NqLWb/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 13 09:24:56 submit26-b9-f4 setroubleshoot[1082130]: 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 Oct 13 09:24:56 submit26-b9-f4 setroubleshoot[1082130]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.9NqLWb. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 13 09:24:56 submit26-b9-f4 setroubleshoot[1082130]: 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 Oct 13 09:24:57 submit26-b9-f4 setroubleshoot[1082130]: 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 Oct 13 09:24:57 submit26-b9-f4 setroubleshoot[1082130]: 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
participants (1)
-
cron/syslog01.cs.umd.edu