Command: /usr/local/sbin/syslog-digest.py Time : 0.0446s Status : exited 0 Output : Syslog digest — 2026-10-12 15:05 EDT Processed 1,480 lines, filtered 1,091 (73%). 389 unknown (160 distinct) from 20 host(s). == abuse (4 distinct, 5 total) == Oct 12 14:28:14 abuse kernel: conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module. Oct 12 14:30:12 abuse systemd[1]: New main PID 15708 does not belong to service, and PID file is not owned by root. Refusing. [x2] Oct 12 14:30:29 abuse systemd[1]: Daemon never wrote its PID file. Failing. Oct 12 14:30:40 abuse systemd[1]: pmlogger.service: Supervising process 22743 which is not our child. We'll most likely not notice when it exits. == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 12 14:24:44 b0b02.cs.umd.edu rustdesk[3089776]: cannot open display: == idm00 (1 distinct, 1 total) == Oct 12 14:54:47 idm00 named[1029]: client @0x7fc470034bd8 10.73.240.42#49877: update '73.10.in-addr.arpa/IN' denied == idmh1 (13 distinct, 156 total) == Oct 12 14:09:32 idmh1 check-named-alive[65644]: zone cs.umd.edu: local SOA serial 1791811218 lags newest peer 1791817249 by 6031 (threshold 3600); not acting [x12] Oct 12 14:09:32 idmh1 check-named-alive[65705]: zone csdlabs.umd.edu: local SOA serial 1791811218 lags newest peer 1791817250 by 6032 (threshold 3600); not acting [x12] Oct 12 14:09:33 idmh1 check-named-alive[65766]: zone csic.umd.edu: local SOA serial 1791811218 lags newest peer 1791817250 by 6032 (threshold 3600); not acting [x12] Oct 12 14:09:33 idmh1 check-named-alive[65827]: zone 72.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791817250 by 6032 (threshold 3600); not acting [x12] Oct 12 14:09:33 idmh1 check-named-alive[65888]: zone 73.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791817250 by 6032 (threshold 3600); not acting [x12] Oct 12 14:09:33 idmh1 check-named-alive[65949]: zone 88.10.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791817249 by 6031 (threshold 3600); not acting [x12] Oct 12 14:09:33 idmh1 check-named-alive[66010]: zone 125.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791817249 by 6031 (threshold 3600); not acting [x12] Oct 12 14:09:33 idmh1 check-named-alive[66071]: zone 126.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791817249 by 6031 (threshold 3600); not acting [x12] Oct 12 14:09:34 idmh1 check-named-alive[66132]: zone 127.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791817249 by 6031 (threshold 3600); not acting [x12] Oct 12 14:09:34 idmh1 check-named-alive[66193]: zone 128.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791817249 by 6031 (threshold 3600); not acting [x12] Oct 12 14:09:34 idmh1 check-named-alive[66254]: zone 129.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791817249 by 6031 (threshold 3600); not acting [x12] Oct 12 14:09:34 idmh1 check-named-alive[66315]: zone 130.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791817249 by 6031 (threshold 3600); not acting [x12] Oct 12 14:09:34 idmh1 check-named-alive[66376]: zone 131.8.128.in-addr.arpa: local SOA serial 1791811218 lags newest peer 1791817249 by 6031 (threshold 3600); not acting [x12] == idmp0 (1 distinct, 1 total) == Oct 12 14:39:21 idmp0 named[19286]: client @0x7faae0012c38 10.73.240.43#49905: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 5 total) == Oct 12 14:12:59 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x5] == lifepix (1 distinct, 2 total) == Oct 12 14:38:03 lifepix setroubleshoot[2680306]: 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] == matrix (2 distinct, 3 total) == Oct 12 14:17:44 matrix krb5_child[609065]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Oct 12 14:17:46 matrix sshd[609059]: error: PAM: Authentication failure for admin from 193.24.211.219 == munin (2 distinct, 8 total) == Oct 12 14:43:00 munin sudo[3934628]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Oct 12 14:43:00 munin sudo[3934628]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Oct 12 14:13:03 newhonors2 dhcpcd[3927661]: dhcpcd is not running [x24] == ntop00 (93 distinct, 93 total) == Oct 12 14:05:21 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 7642, QN: 7768/7768, ET: 20) *** Oct 12 14:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 7643) *** Oct 12 14:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 7643, QN: 7924/7924, ET: 0) *** Oct 12 14:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 7643) *** Oct 12 14:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 7643, QN: 57/57, ET: 0) *** Oct 12 14:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 7644) *** Oct 12 14:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 7644) *** Oct 12 14:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 7644, QN: 54/54, ET: 0) *** Oct 12 14:10:19 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 7644, QN: 7855/7855, ET: 18) *** Oct 12 14:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 7645) *** Oct 12 14:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 7645, QN: 8145/8145, ET: 0) *** Oct 12 14:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 7645) *** Oct 12 14:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 7645, QN: 55/55, ET: 0) *** Oct 12 14:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 7646) *** Oct 12 14:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 7646) *** Oct 12 14:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 7646, QN: 69/69, ET: 0) *** Oct 12 14:15:22 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 7646, QN: 8134/8134, ET: 21) *** Oct 12 14:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 7647) *** Oct 12 14:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 7647, QN: 8320/8320, ET: 0) *** Oct 12 14:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 7647) *** Oct 12 14:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 7647, QN: 60/60, ET: 0) *** Oct 12 14:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 7648) *** Oct 12 14:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 7648) *** Oct 12 14:20:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 7648, QN: 52/52, ET: 1) *** Oct 12 14:20:22 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 7648, QN: 8035/8035, ET: 21) *** Oct 12 14:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 7649) *** Oct 12 14:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 7649, QN: 8411/8411, ET: 0) *** Oct 12 14:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 7649) *** Oct 12 14:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 7649, QN: 78/78, ET: 0) *** Oct 12 14:25:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 7650) *** ... 63 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 12 14:09:08 outbound00.cs.umd.edu python3[1974545]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 7 total) == Oct 12 14:13:06 outbound01.cs.umd.edu python3[3457791]: ldapdb [x6] Oct 12 14:28:08 outbound01.cs.umd.edu krb5_child[3461606]: Client 'admin@UMD.EDU' not found in Kerberos database == quiss (7 distinct, 10 total) == Oct 12 14:08:37 quiss gnome-software[191719]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/josephao/.config/dconf/user.SJDRW3”: Permission denied Oct 12 14:08:40 quiss gnome-software[191719]: failed to get featured apps: no apps to show Oct 12 14:08:40 quiss gnome-software[191719]: Only 0 apps for curated list, hiding Oct 12 14:08:40 quiss gnome-software[191719]: Only 0 apps for recent list, hiding Oct 12 14:08:43 quiss packagekitd[3047938]: Failed to get cache filename for gnome-control-center-filesystem [x2] Oct 12 14:08:43 quiss packagekitd[3047938]: Failed to get cache filename for perl [x2] Oct 12 14:08:43 quiss packagekitd[3047938]: Failed to get cache filename for kernel [x2] == soul (1 distinct, 1 total) == Oct 12 14:12:01 soul krb5_child[461689]: Client 'admin@UMD.EDU' not found in Kerberos database == strawberry (7 distinct, 38 total) == Oct 12 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 12 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 12 14:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 12 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 12 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 12 14:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 12 14:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-3 (2 distinct, 5 total) == Sep 14 23:00:45 submit26-b9-3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] Sep 14 23:15:07 submit26-b9-3 systemd-coredump[3142096]: Process 3142093 (secret02) of user 1001 dumped core.#012#012Stack trace of thread 3142093:#012#0 0x00007f6c3c68d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f6c3c63fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f6c3c629873 abort (libc.so.6 + 0x29873)#012#3 0x00007f6c3c62a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f6c3c71d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f6c3c71e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401231 main (secret02 + 0x1231)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f1 (9 distinct, 9 total) == Oct 12 14:26:04 submit26-b9-f1 setroubleshoot[2462748]: 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 12 14:26:04 submit26-b9-f1 setroubleshoot[2462748]: 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 12 14:26:04 submit26-b9-f1 setroubleshoot[2462748]: 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 12 14:26:04 submit26-b9-f1 setroubleshoot[2462748]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.M7CBij/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Oct 12 14:26:04 submit26-b9-f1 setroubleshoot[2462748]: 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 12 14:26:04 submit26-b9-f1 setroubleshoot[2462748]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.M7CBij. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 12 14:26:04 submit26-b9-f1 setroubleshoot[2462748]: 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 12 14:26:04 submit26-b9-f1 setroubleshoot[2462748]: 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 12 14:26:04 submit26-b9-f1 setroubleshoot[2462748]: 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 (10 distinct, 13 total) == Oct 12 14:06:57 submit26-b9-f2 setroubleshoot[1556134]: 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 12 14:06:57 submit26-b9-f2 setroubleshoot[1556134]: 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 12 14:06:57 submit26-b9-f2 setroubleshoot[1556134]: 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 [x2] Oct 12 14:06:57 submit26-b9-f2 setroubleshoot[1556134]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.KJQGV4/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2] Oct 12 14:06:57 submit26-b9-f2 setroubleshoot[1556134]: 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 [x2] Oct 12 14:06:57 submit26-b9-f2 setroubleshoot[1556134]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.KJQGV4. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 12 14:06:57 submit26-b9-f2 setroubleshoot[1556134]: 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 12 14:06:57 submit26-b9-f2 setroubleshoot[1556134]: 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 12 14:06:57 submit26-b9-f2 setroubleshoot[1556134]: 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 Oct 12 14:15:23 submit26-b9-f2 systemd-coredump[1556998]: Process 1556996 (crashtest) of user 0 dumped core. == teaching-awards (1 distinct, 1 total) == Oct 12 14:40:01 teaching-awards krb5_child[454526]: Client 'admin@UMD.EDU' not found in Kerberos database