Command: /usr/local/sbin/syslog-digest.py Time : 0.1206s Status : exited 0 Output : Syslog digest — 2026-10-13 19:05 EDT Processed 4,246 lines, filtered 676 (15%). 3,570 unknown (441 distinct) from 19 host(s). == b0b02.cs.umd.edu (4 distinct, 4 total) == Oct 13 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-10-13T22:10:59.446127062Z" level=info msg="PurgeUploads starting: olderThan=2026-10-06 22:10:59.446046555 +0000 UTC m=+6136620.205974868, actuallyDelete=true" Oct 13 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-10-13T22:10:59.446617592Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Oct 13 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-10-13T22:10:59.44663817Z" level=info msg="Starting upload purge in 24h0m0s" go.version=go1.11.2 instance.id=68469aa4-7857-4a69-bf12-c2190b4f96d8 service=registry version=v2.7.1 Oct 13 18:26:32 b0b02.cs.umd.edu rustdesk[3516873]: cannot open display: == idm00 (1 distinct, 1 total) == Oct 13 18:54:47 idm00 named[1014]: client @0x7fcbc402f038 10.73.240.42#55544: update '73.10.in-addr.arpa/IN' denied == idmh1 (13 distinct, 156 total) == Oct 13 18:06:21 idmh1 check-named-alive[446318]: zone cs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 18:06:21 idmh1 check-named-alive[446379]: zone csdlabs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 18:06:21 idmh1 check-named-alive[446440]: zone csic.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 18:06:22 idmh1 check-named-alive[446501]: zone 72.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 18:06:22 idmh1 check-named-alive[446562]: zone 73.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 18:06:22 idmh1 check-named-alive[446623]: zone 88.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 18:06:22 idmh1 check-named-alive[446684]: zone 125.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 18:06:22 idmh1 check-named-alive[446745]: zone 126.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 18:06:23 idmh1 check-named-alive[446806]: zone 127.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 18:06:23 idmh1 check-named-alive[446867]: zone 128.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 18:06:23 idmh1 check-named-alive[446928]: zone 129.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 18:06:23 idmh1 check-named-alive[446989]: zone 130.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 18:06:23 idmh1 check-named-alive[447050]: 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 13 18:39:44 idmp0 named[1180]: client @0x7fe058014098 10.73.240.43#63959: update '73.10.in-addr.arpa/IN' denied == idmv0 (13 distinct, 156 total) == Oct 13 18:06:44 idmv0 check-named-alive[485704]: zone cs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 18:06:44 idmv0 check-named-alive[485765]: zone csdlabs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 18:06:44 idmv0 check-named-alive[485826]: zone csic.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 18:06:44 idmv0 check-named-alive[485887]: zone 72.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 18:06:45 idmv0 check-named-alive[485949]: zone 73.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 18:06:45 idmv0 check-named-alive[486010]: zone 88.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 18:06:45 idmv0 check-named-alive[486071]: zone 125.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 18:06:45 idmv0 check-named-alive[486132]: zone 126.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 18:06:45 idmv0 check-named-alive[486193]: zone 127.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 18:06:45 idmv0 check-named-alive[486254]: zone 128.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 18:06:46 idmv0 check-named-alive[486315]: zone 129.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 18:06:46 idmv0 check-named-alive[486376]: zone 130.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 18:06:46 idmv0 check-named-alive[486437]: zone 131.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] == irb2156 (2 distinct, 2 total) == Oct 13 19:02:32 irb2156 systemd-coredump[1665994]: Process 291911 (bbd) of user 0 dumped core.#012#012Stack trace of thread 291914:#012#0 0x00000000004113e6 bb_model_thread_cred_destroy (/opt/bitbison/sbin/bbd + 0x2113e6)#012#012Stack trace of thread 291913:#012#0 0x00000000003ee9f5 sccp (/opt/bitbison/sbin/bbd + 0x1ee9f5)#012#012Stack trace of thread 291911:#012#0 0x00000000003ee9f5 sccp (/opt/bitbison/sbin/bbd + 0x1ee9f5)#012#012Stack trace of thread 291917:#012#0 0x00000000003ee9f5 sccp (/opt/bitbison/sbin/bbd + 0x1ee9f5)#012#012Stack trace of thread 291916:#012#0 0x00000000003ee9f5 sccp (/opt/bitbison/sbin/bbd + 0x1ee9f5)#012ELF object binary architecture: AMD x86-64 Oct 13 19:02:42 irb2156 systemd[1]: bitbison-agent.service: Main process exited, code=dumped, status=11/SEGV == itmon02 (1 distinct, 1 total) == Oct 13 18:28:04 itmon02 sshd[805675]: error: beginning MaxStartups throttling == krispykreme.cs.umd.edu (1 distinct, 1 total) == Oct 13 18:26:12 krispykreme.cs.umd.edu sshd-session[1367566]: error: send_error: write: Connection reset by peer == mashie (276 distinct, 3046 total) == Oct 13 18:44:22 mashie kernel: EXT4-fs error: 3 callbacks suppressed Oct 13 18:44:22 mashie kernel: EXT4-fs error (device vda1): ext4_journal_check_start:83: comm find: Detected aborted journal [x1385] Oct 13 18:44:22 mashie kernel: EXT4-fs: 3 callbacks suppressed Oct 13 18:44:22 mashie kernel: EXT4-fs (vda1): Remounting filesystem read-only [x1385] Oct 13 18:44:27 mashie kernel: EXT4-fs error: 1335 callbacks suppressed Oct 13 18:44:27 mashie kernel: EXT4-fs: 1335 callbacks suppressed Oct 13 18:44:32 mashie kernel: EXT4-fs error: 2006 callbacks suppressed Oct 13 18:44:32 mashie kernel: EXT4-fs: 2006 callbacks suppressed Oct 13 18:44:37 mashie kernel: EXT4-fs error: 1853 callbacks suppressed Oct 13 18:44:37 mashie kernel: EXT4-fs: 1854 callbacks suppressed Oct 13 18:44:42 mashie kernel: EXT4-fs error: 2188 callbacks suppressed Oct 13 18:44:42 mashie kernel: EXT4-fs: 2187 callbacks suppressed Oct 13 18:44:47 mashie kernel: EXT4-fs error: 1429 callbacks suppressed Oct 13 18:44:47 mashie kernel: EXT4-fs: 1429 callbacks suppressed Oct 13 18:44:52 mashie kernel: EXT4-fs error: 2137 callbacks suppressed Oct 13 18:44:52 mashie kernel: EXT4-fs: 2137 callbacks suppressed Oct 13 18:44:57 mashie kernel: EXT4-fs error: 2605 callbacks suppressed Oct 13 18:44:57 mashie kernel: EXT4-fs: 2605 callbacks suppressed Oct 13 18:45:02 mashie kernel: EXT4-fs error: 2565 callbacks suppressed Oct 13 18:45:02 mashie kernel: EXT4-fs: 2565 callbacks suppressed Oct 13 18:45:07 mashie kernel: EXT4-fs error: 1263 callbacks suppressed Oct 13 18:45:07 mashie kernel: EXT4-fs: 1263 callbacks suppressed Oct 13 18:45:12 mashie kernel: EXT4-fs error: 736 callbacks suppressed Oct 13 18:45:12 mashie kernel: EXT4-fs: 736 callbacks suppressed Oct 13 18:45:17 mashie kernel: EXT4-fs error: 878 callbacks suppressed Oct 13 18:45:17 mashie kernel: EXT4-fs: 878 callbacks suppressed Oct 13 18:45:22 mashie kernel: EXT4-fs error: 837 callbacks suppressed Oct 13 18:45:22 mashie kernel: EXT4-fs: 837 callbacks suppressed Oct 13 18:45:27 mashie kernel: EXT4-fs error: 625 callbacks suppressed Oct 13 18:45:27 mashie kernel: EXT4-fs: 625 callbacks suppressed ... 246 more distinct messages not shown == munin (2 distinct, 2 total) == Oct 13 19:04:15 munin sudo[356117]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory Oct 13 19:04:15 munin sudo[356117]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. == newhonors2 (1 distinct, 24 total) == Oct 13 18:13:02 newhonors2 dhcpcd[3980553]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Oct 13 18:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8314) *** Oct 13 18:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8314) *** Oct 13 18:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8314, QN: 67/67, ET: 0) *** Oct 13 18:05:29 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8314, QN: 13170/13170, ET: 28) *** Oct 13 18:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8315) *** Oct 13 18:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8315, QN: 12195/12195, ET: 0) *** Oct 13 18:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8315) *** Oct 13 18:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8315, QN: 63/63, ET: 0) *** Oct 13 18:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8316) *** Oct 13 18:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8316) *** Oct 13 18:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8316, QN: 55/55, ET: 0) *** Oct 13 18:10:29 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8316, QN: 11318/11318, ET: 28) *** Oct 13 18:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8317) *** Oct 13 18:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8317, QN: 9017/9017, ET: 0) *** Oct 13 18:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8317) *** Oct 13 18:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8317, QN: 66/66, ET: 0) *** Oct 13 18:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8318) *** Oct 13 18:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8318) *** Oct 13 18:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8318, QN: 71/71, ET: 0) *** Oct 13 18:15:21 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8318, QN: 7376/7376, ET: 20) *** Oct 13 18:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8319) *** Oct 13 18:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8319, QN: 6602/6602, ET: 0) *** Oct 13 18:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8319) *** Oct 13 18:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8319, QN: 53/53, ET: 0) *** Oct 13 18:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8320) *** Oct 13 18:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8320) *** Oct 13 18:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8320, QN: 42/42, ET: 0) *** Oct 13 18:20:16 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8320, QN: 6638/6638, ET: 15) *** Oct 13 18:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8321) *** Oct 13 18:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8321, QN: 6325/6325, ET: 0) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 13 18:09:09 outbound00.cs.umd.edu python3[2363890]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 13 18:13:06 outbound01.cs.umd.edu python3[3851841]: ldapdb [x6] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Oct 13 19:03:43 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts == strawberry (7 distinct, 38 total) == Oct 13 18: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 18: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 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 13 18: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 18: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 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 13 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-3 (1 distinct, 5 total) == Sep 16 05:20:07 submit26-b9-3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f1 (10 distinct, 13 total) == Oct 13 18:20:08 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Oct 13 18:26:05 submit26-b9-f1 setroubleshoot[2661806]: 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 [x2] Oct 13 18:26:05 submit26-b9-f1 setroubleshoot[2661806]: 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 [x2] Oct 13 18:26:05 submit26-b9-f1 setroubleshoot[2661806]: 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 Oct 13 18:26:05 submit26-b9-f1 setroubleshoot[2661806]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.mkrC3H/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Oct 13 18:26:05 submit26-b9-f1 setroubleshoot[2661806]: 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 Oct 13 18:26:05 submit26-b9-f1 setroubleshoot[2661806]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.mkrC3H. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 13 18:26:05 submit26-b9-f1 setroubleshoot[2661806]: 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 13 18:26:05 submit26-b9-f1 setroubleshoot[2661806]: 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 13 18:26:05 submit26-b9-f1 setroubleshoot[2661806]: 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 13 18:06:57 submit26-b9-f2 setroubleshoot[1772753]: 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 13 18:06:58 submit26-b9-f2 setroubleshoot[1772753]: 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 13 18:06:58 submit26-b9-f2 setroubleshoot[1772753]: 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 13 18:06:58 submit26-b9-f2 setroubleshoot[1772753]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.CTXHVe/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Oct 13 18:06:58 submit26-b9-f2 setroubleshoot[1772753]: 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 13 18:06:58 submit26-b9-f2 setroubleshoot[1772753]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.CTXHVe. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 13 18:06:58 submit26-b9-f2 setroubleshoot[1772753]: 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 13 18:06:58 submit26-b9-f2 setroubleshoot[1772753]: 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 13 18:06:58 submit26-b9-f2 setroubleshoot[1772753]: 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