Command: /usr/local/sbin/syslog-digest.py Time : 0.0489s Status : exited 0 Output : Syslog digest — 2026-10-13 15:05 EDT Processed 1,429 lines, filtered 882 (61%). 547 unknown (170 distinct) from 21 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 13 14:26:17 b0b02.cs.umd.edu rustdesk[3456299]: cannot open display: == biggulp.cs.umd.edu (1 distinct, 1 total) == Oct 13 14:25:40 biggulp.cs.umd.edu sshd-session[1810322]: error: send_error: write: Connection reset by peer == cheezit.cs.umd.edu (1 distinct, 1 total) == Oct 13 15:00:28 cheezit.cs.umd.edu sshd-session[2358387]: error: Protocol major versions differ: 2 vs. 1 == idm00 (1 distinct, 1 total) == Oct 13 14:54:47 idm00 named[1014]: client @0x7fcbc93b0a78 10.73.240.42#61483: update '73.10.in-addr.arpa/IN' denied == idmh1 (13 distinct, 156 total) == Oct 13 14:06:05 idmh1 check-named-alive[392082]: zone cs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 14:06:06 idmh1 check-named-alive[392143]: zone csdlabs.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 14:06:06 idmh1 check-named-alive[392204]: zone csic.umd.edu: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 14:06:06 idmh1 check-named-alive[392265]: zone 72.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 14:06:06 idmh1 check-named-alive[392326]: zone 73.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 14:06:06 idmh1 check-named-alive[392387]: zone 88.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 14:06:07 idmh1 check-named-alive[392448]: zone 125.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 14:06:07 idmh1 check-named-alive[392509]: zone 126.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 14:06:07 idmh1 check-named-alive[392570]: zone 127.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 14:06:07 idmh1 check-named-alive[392631]: zone 128.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 14:06:07 idmh1 check-named-alive[392693]: zone 129.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837289 by 26071 (threshold 3600); not acting [x12] Oct 13 14:06:08 idmh1 check-named-alive[392754]: zone 130.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791837290 by 26072 (threshold 3600); not acting [x12] Oct 13 14:06:08 idmh1 check-named-alive[392815]: 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 14:39:44 idmp0 named[1180]: client @0x7fe054023c68 10.73.240.43#62213: update '73.10.in-addr.arpa/IN' denied == idmv0 (13 distinct, 156 total) == Oct 13 14:06:29 idmv0 check-named-alive[423325]: zone cs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 14:06:29 idmv0 check-named-alive[423386]: zone csdlabs.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 14:06:29 idmv0 check-named-alive[423447]: zone csic.umd.edu: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 14:06:29 idmv0 check-named-alive[423508]: zone 72.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 14:06:29 idmv0 check-named-alive[423569]: zone 73.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 14:06:30 idmv0 check-named-alive[423630]: zone 88.10.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 14:06:30 idmv0 check-named-alive[423691]: zone 125.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 14:06:30 idmv0 check-named-alive[423756]: zone 126.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 14:06:30 idmv0 check-named-alive[423817]: zone 127.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 14:06:30 idmv0 check-named-alive[423878]: zone 128.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 14:06:30 idmv0 check-named-alive[423939]: zone 129.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837289 by 22368 (threshold 3600); not acting [x12] Oct 13 14:06:31 idmv0 check-named-alive[424000]: zone 130.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] Oct 13 14:06:31 idmv0 check-named-alive[424061]: zone 131.8.128.in-addr.arpa: local SOA serial 1791814921 lags newest peer 1791837290 by 22369 (threshold 3600); not acting [x12] == itmon02 (1 distinct, 5 total) == Oct 13 14:28:02 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x5] == krispykreme.cs.umd.edu (2 distinct, 6 total) == Oct 13 15:01:27 krispykreme.cs.umd.edu sshd-session[1305619]: error: send_error: write: Connection reset by peer [x5] Oct 13 15:01:36 krispykreme.cs.umd.edu sshd-session[1305639]: error: Protocol major versions differ: 2 vs. 1 == lifepix (1 distinct, 2 total) == Oct 13 14:38:03 lifepix setroubleshoot[2818130]: SELinux is preventing /usr/bin/podman from using the nnp_transition access on a process. For complete SELinux messages run: sealert -l db6b3d2c-fa5b-4b9b-8ef7-675cd3f54e86 [x2] == munin (2 distinct, 16 total) == Oct 13 14:14:05 munin sudo[251592]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x8] Oct 13 14:14:05 munin sudo[251592]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x8] == neoavion (1 distinct, 1 total) == Oct 13 14:45:15 neoavion pipewire[1280736]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files == newhonors2 (1 distinct, 24 total) == Oct 13 14:13:03 newhonors2 dhcpcd[3973062]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Oct 13 14:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8218) *** Oct 13 14:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8218, QN: 76/76, ET: 0) *** Oct 13 14:05:18 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8218, QN: 7786/7786, ET: 17) *** Oct 13 14:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8219) *** Oct 13 14:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8219, QN: 7613/7613, ET: 0) *** Oct 13 14:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8219) *** Oct 13 14:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8219, QN: 55/55, ET: 0) *** Oct 13 14:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8220) *** Oct 13 14:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8220) *** Oct 13 14:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8220, QN: 47/47, ET: 0) *** Oct 13 14:10:16 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8220, QN: 7300/7300, ET: 15) *** Oct 13 14:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8221) *** Oct 13 14:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8221, QN: 7235/7235, ET: 0) *** Oct 13 14:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8221) *** Oct 13 14:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8221, QN: 50/50, ET: 0) *** Oct 13 14:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8222) *** Oct 13 14:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8222) *** Oct 13 14:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8222, QN: 54/54, ET: 0) *** Oct 13 14:15:19 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8222, QN: 7686/7686, ET: 18) *** Oct 13 14:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8223) *** Oct 13 14:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8223, QN: 8365/8365, ET: 0) *** Oct 13 14:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8223) *** Oct 13 14:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 8223, QN: 64/64, ET: 0) *** Oct 13 14:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8224) *** Oct 13 14:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 8224) *** Oct 13 14:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8224, QN: 67/67, ET: 0) *** Oct 13 14:20:19 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 8224, QN: 8391/8391, ET: 18) *** Oct 13 14:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 8225) *** Oct 13 14:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 8225, QN: 8657/8657, ET: 0) *** Oct 13 14:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 8225) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 7 total) == Oct 13 14:09:09 outbound00.cs.umd.edu python3[2308809]: ldapdb [x6] Oct 13 14:48:35 outbound00.cs.umd.edu krb5_child[2317691]: Client 'admin@UMD.EDU' not found in Kerberos database == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 13 14:13:06 outbound01.cs.umd.edu python3[3796035]: ldapdb [x6] == strawberry (7 distinct, 38 total) == Oct 13 14: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 14: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 14:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 13 14: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 14: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 14:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 13 14:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-3 (1 distinct, 4 total) == Sep 16 01:07:56 submit26-b9-3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f1 (12 distinct, 13 total) == Oct 13 14:26:05 submit26-b9-f1 setroubleshoot[2649704]: 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 13 14:26:05 submit26-b9-f1 setroubleshoot[2649704]: 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 13 14:26:05 submit26-b9-f1 setroubleshoot[2649704]: 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 14:26:05 submit26-b9-f1 setroubleshoot[2649704]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.mVdcbo/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Oct 13 14:26:05 submit26-b9-f1 setroubleshoot[2649704]: 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 14:26:05 submit26-b9-f1 setroubleshoot[2649704]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.mVdcbo. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 13 14:26:05 submit26-b9-f1 setroubleshoot[2649704]: 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 14:26:05 submit26-b9-f1 setroubleshoot[2649704]: 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 14:26:05 submit26-b9-f1 setroubleshoot[2649704]: 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 Oct 13 14:50:49 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Oct 13 14:50:52 submit26-b9-f1 systemd-coredump[2650747]: Process 2650744 (release02) of user 1001 dumped core.#012#012Stack trace of thread 2650744:#012#0 0x000000000040252c highlight_text (release02 + 0x252c)#012#1 0x0000000000401583 main (release02 + 0x1583)#012#2 0x5d5b5d5b5d5b5d5b n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Oct 13 14:53:12 submit26-b9-f1 systemd-coredump[2650954]: Process 2650951 (release02) of user 1001 dumped core.#012#012Stack trace of thread 2650951:#012#0 0x00000000004024fa highlight_text (release02 + 0x24fa)#012#1 0x0000000000401593 main (release02 + 0x1593)#012#2 0x5d5b5d5b5d5b5d5b n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f2 (9 distinct, 9 total) == Oct 13 14:06:58 submit26-b9-f2 setroubleshoot[1760448]: 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 Oct 13 14:06:58 submit26-b9-f2 setroubleshoot[1760448]: 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 Oct 13 14:06:58 submit26-b9-f2 setroubleshoot[1760448]: 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 14:06:58 submit26-b9-f2 setroubleshoot[1760448]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.uMS260/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Oct 13 14:06:58 submit26-b9-f2 setroubleshoot[1760448]: 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 14:06:58 submit26-b9-f2 setroubleshoot[1760448]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.uMS260. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 13 14:06:58 submit26-b9-f2 setroubleshoot[1760448]: 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 14:06:58 submit26-b9-f2 setroubleshoot[1760448]: 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 14:06:58 submit26-b9-f2 setroubleshoot[1760448]: 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 == submit26-b9-f3 (3 distinct, 3 total) == Oct 13 14:12:12 submit26-b9-f3 systemd-coredump[3241147]: Process 3241144 (release02) of user 1001 dumped core. Oct 13 14:33:09 submit26-b9-f3 systemd-coredump[3242138]: Process 3242135 (release02) of user 1001 dumped core. Oct 13 14:58:00 submit26-b9-f3 systemd-coredump[3243828]: Process 3243825 (release02) of user 1001 dumped core.