Command: /usr/local/sbin/syslog-digest.py Time : 0.1720s Status : exited 0 Output : Syslog digest — 2026-10-07 19:05 EDT Processed 6,286 lines, filtered 3,150 (50%). 3,136 unknown (458 distinct) from 27 host(s). == abuse (1 distinct, 346 total) == Oct 7 18:05:25 abuse rsyslogd[1033]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x346] == amoeba (5 distinct, 5 total) == Oct 7 18:07:11 amoeba gsd-subman[2241527]: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Oct 7 18:07:14 amoeba org.gnome.Shell.desktop[2660299] The XKEYBOARD keymap compiler (xkbcomp) reports: Oct 7 18:07:14 amoeba org.gnome.Shell.desktop[2660299] > Warning: Unsupported maximum keycode 708, clipping. Oct 7 18:07:14 amoeba org.gnome.Shell.desktop[2660299] > X11 cannot support keycodes above 255. Oct 7 18:07:14 amoeba org.gnome.Shell.desktop[2660299] Errors from xkbcomp are not fatal to the X server == b0b02.cs.umd.edu (4 distinct, 4 total) == Oct 7 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-10-07T22:10:59.441651129Z" level=info msg="PurgeUploads starting: olderThan=2026-09-30 22:10:59.441554347 +0000 UTC m=+5618220.201482662, actuallyDelete=true" Oct 7 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-10-07T22:10:59.44213489Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Oct 7 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-10-07T22:10:59.442155203Z" 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 7 18:17:51 b0b02.cs.umd.edu rustdesk[1321272]: cannot open display: == galax (1 distinct, 1 total) == Oct 7 18:09:22 galax kernel: rtw89_8922ae 0000:06:00.0: failed to wait RF DACK == gle-dind00.cs.umd.edu (88 distinct, 88 total) == Oct 7 18:16:13 gle-dind00.cs.umd.edu systemd-udevd[2945702]: Could not generate persistent MAC address for veth149cbc5: No such file or directory Oct 7 18:16:13 gle-dind00.cs.umd.edu systemd-udevd[2945701]: Could not generate persistent MAC address for veth748a6e6: No such file or directory Oct 7 18:16:32 gle-dind00.cs.umd.edu systemd-udevd[2945966]: Could not generate persistent MAC address for veth68653f5: No such file or directory Oct 7 18:16:32 gle-dind00.cs.umd.edu systemd-udevd[2945967]: Could not generate persistent MAC address for veth0f71765: No such file or directory Oct 7 18:16:35 gle-dind00.cs.umd.edu systemd-udevd[2946133]: Could not generate persistent MAC address for vethd87b84b: No such file or directory Oct 7 18:16:35 gle-dind00.cs.umd.edu systemd-udevd[2946134]: Could not generate persistent MAC address for vethb58ee65: No such file or directory Oct 7 18:16:36 gle-dind00.cs.umd.edu systemd-udevd[2946234]: Could not generate persistent MAC address for veth5aae25c: No such file or directory Oct 7 18:16:36 gle-dind00.cs.umd.edu systemd-udevd[2946235]: Could not generate persistent MAC address for veth6862994: No such file or directory Oct 7 18:16:36 gle-dind00.cs.umd.edu systemd-udevd[2946329]: Could not generate persistent MAC address for vethdbbc304: No such file or directory Oct 7 18:16:36 gle-dind00.cs.umd.edu systemd-udevd[2946330]: Could not generate persistent MAC address for vetha130b3f: No such file or directory Oct 7 18:16:38 gle-dind00.cs.umd.edu systemd-udevd[2946428]: Could not generate persistent MAC address for vethd351285: No such file or directory Oct 7 18:16:38 gle-dind00.cs.umd.edu systemd-udevd[2946429]: Could not generate persistent MAC address for veth6a61769: No such file or directory Oct 7 18:16:38 gle-dind00.cs.umd.edu systemd-udevd[2946517]: Could not generate persistent MAC address for veth0605990: No such file or directory Oct 7 18:16:38 gle-dind00.cs.umd.edu systemd-udevd[2946518]: Could not generate persistent MAC address for vethd8c3572: No such file or directory Oct 7 18:16:56 gle-dind00.cs.umd.edu systemd-udevd[2946830]: Could not generate persistent MAC address for veth66f4ba1: No such file or directory Oct 7 18:16:56 gle-dind00.cs.umd.edu systemd-udevd[2946831]: Could not generate persistent MAC address for veth02be8c8: No such file or directory Oct 7 18:16:57 gle-dind00.cs.umd.edu systemd-udevd[2946925]: Could not generate persistent MAC address for vethc149b07: No such file or directory Oct 7 18:16:57 gle-dind00.cs.umd.edu systemd-udevd[2946926]: Could not generate persistent MAC address for veth467bdaf: No such file or directory Oct 7 18:16:59 gle-dind00.cs.umd.edu systemd-udevd[2947098]: Could not generate persistent MAC address for vethc603e1a: No such file or directory Oct 7 18:16:59 gle-dind00.cs.umd.edu systemd-udevd[2947099]: Could not generate persistent MAC address for veth7c9c268: No such file or directory Oct 7 18:17:00 gle-dind00.cs.umd.edu systemd-udevd[2947213]: Could not generate persistent MAC address for veth037da23: No such file or directory Oct 7 18:17:00 gle-dind00.cs.umd.edu systemd-udevd[2947214]: Could not generate persistent MAC address for vethcddabe5: No such file or directory Oct 7 18:30:54 gle-dind00.cs.umd.edu systemd-udevd[2951428]: Could not generate persistent MAC address for vethd49cc3b: No such file or directory Oct 7 18:30:54 gle-dind00.cs.umd.edu systemd-udevd[2951429]: Could not generate persistent MAC address for veth5247d8d: No such file or directory Oct 7 18:31:14 gle-dind00.cs.umd.edu systemd-udevd[2951550]: Could not generate persistent MAC address for veth2ea8dac: No such file or directory Oct 7 18:31:14 gle-dind00.cs.umd.edu systemd-udevd[2951551]: Could not generate persistent MAC address for veth612141e: No such file or directory Oct 7 18:31:16 gle-dind00.cs.umd.edu systemd-udevd[2951710]: Could not generate persistent MAC address for vetha00c45c: No such file or directory Oct 7 18:31:16 gle-dind00.cs.umd.edu systemd-udevd[2951711]: Could not generate persistent MAC address for vethfd9adad: No such file or directory Oct 7 18:31:17 gle-dind00.cs.umd.edu systemd-udevd[2951810]: Could not generate persistent MAC address for vethf80ccd0: No such file or directory Oct 7 18:31:17 gle-dind00.cs.umd.edu systemd-udevd[2951809]: Could not generate persistent MAC address for vetha66a0ef: No such file or directory ... 58 more distinct messages not shown == gle-dind02.cs.umd.edu (111 distinct, 111 total) == Oct 7 18:12:19 gle-dind02.cs.umd.edu systemd-udevd[1783598]: Could not generate persistent MAC address for veth933a43d: No such file or directory Oct 7 18:12:19 gle-dind02.cs.umd.edu systemd-udevd[1783599]: Could not generate persistent MAC address for veth4ff4e88: No such file or directory Oct 7 18:12:36 gle-dind02.cs.umd.edu systemd-udevd[1783714]: Could not generate persistent MAC address for vethe025001: No such file or directory Oct 7 18:12:36 gle-dind02.cs.umd.edu systemd-udevd[1783713]: Could not generate persistent MAC address for vethd88c4a8: No such file or directory Oct 7 18:12:38 gle-dind02.cs.umd.edu systemd-udevd[1783889]: Could not generate persistent MAC address for vethf2336cf: No such file or directory Oct 7 18:12:38 gle-dind02.cs.umd.edu systemd-udevd[1783890]: Could not generate persistent MAC address for veth527e9e7: No such file or directory Oct 7 18:12:39 gle-dind02.cs.umd.edu systemd-udevd[1783989]: Could not generate persistent MAC address for veth344877b: No such file or directory Oct 7 18:12:39 gle-dind02.cs.umd.edu systemd-udevd[1783990]: Could not generate persistent MAC address for veth2fe245a: No such file or directory Oct 7 18:12:40 gle-dind02.cs.umd.edu systemd-udevd[1784088]: Could not generate persistent MAC address for veth2fd460b: No such file or directory Oct 7 18:12:40 gle-dind02.cs.umd.edu systemd-udevd[1784089]: Could not generate persistent MAC address for veth50a7b78: No such file or directory Oct 7 18:12:41 gle-dind02.cs.umd.edu systemd-udevd[1784185]: Could not generate persistent MAC address for veth0277313: No such file or directory Oct 7 18:12:41 gle-dind02.cs.umd.edu systemd-udevd[1784186]: Could not generate persistent MAC address for veth702f34c: No such file or directory Oct 7 18:12:42 gle-dind02.cs.umd.edu systemd-udevd[1784275]: Could not generate persistent MAC address for veth7db80fd: No such file or directory Oct 7 18:12:42 gle-dind02.cs.umd.edu systemd-udevd[1784276]: Could not generate persistent MAC address for vethaaec3e8: No such file or directory Oct 7 18:13:00 gle-dind02.cs.umd.edu systemd-udevd[1784593]: Could not generate persistent MAC address for vethf7f7262: No such file or directory Oct 7 18:13:00 gle-dind02.cs.umd.edu systemd-udevd[1784594]: Could not generate persistent MAC address for vethf10806a: No such file or directory Oct 7 18:13:00 gle-dind02.cs.umd.edu systemd-udevd[1784692]: Could not generate persistent MAC address for veth94c20b6: No such file or directory Oct 7 18:13:00 gle-dind02.cs.umd.edu systemd-udevd[1784693]: Could not generate persistent MAC address for veth1078a94: No such file or directory Oct 7 18:13:02 gle-dind02.cs.umd.edu systemd-udevd[1784872]: Could not generate persistent MAC address for veth41d9fc9: No such file or directory Oct 7 18:13:02 gle-dind02.cs.umd.edu systemd-udevd[1784873]: Could not generate persistent MAC address for vethf759f7e: No such file or directory Oct 7 18:13:03 gle-dind02.cs.umd.edu systemd-udevd[1784986]: Could not generate persistent MAC address for vethbecd918: No such file or directory Oct 7 18:13:03 gle-dind02.cs.umd.edu systemd-udevd[1784987]: Could not generate persistent MAC address for veth8f60ddd: No such file or directory Oct 7 18:22:59 gle-dind02.cs.umd.edu systemd-udevd[1787301]: Could not generate persistent MAC address for veth5e75650: No such file or directory Oct 7 18:22:59 gle-dind02.cs.umd.edu systemd-udevd[1787300]: Could not generate persistent MAC address for vetha368ecb: No such file or directory Oct 7 18:23:18 gle-dind02.cs.umd.edu systemd-udevd[1787454]: Could not generate persistent MAC address for veth685144d: No such file or directory Oct 7 18:23:18 gle-dind02.cs.umd.edu systemd-udevd[1787453]: Could not generate persistent MAC address for veth09b317c: No such file or directory Oct 7 18:23:20 gle-dind02.cs.umd.edu systemd-udevd[1787611]: Could not generate persistent MAC address for veth091ab9f: No such file or directory Oct 7 18:23:20 gle-dind02.cs.umd.edu systemd-udevd[1787613]: Could not generate persistent MAC address for veth4cdd35c: No such file or directory Oct 7 18:23:21 gle-dind02.cs.umd.edu systemd-udevd[1787709]: Could not generate persistent MAC address for veth0c21f17: No such file or directory Oct 7 18:23:21 gle-dind02.cs.umd.edu systemd-udevd[1787710]: Could not generate persistent MAC address for vethd681b74: No such file or directory ... 81 more distinct messages not shown == gle-dind04 (36 distinct, 48 total) == Oct 7 18:05:49 gle-dind04 lldpd[1171]: unable to send packet on real device for veth6f71739: No such device or address Oct 7 18:05:57 gle-dind04 lldpd[1171]: unable to send packet on real device for veth9e77bc5: No such device or address Oct 7 18:08:23 gle-dind04 kernel: overlayfs: upperdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. [x7] Oct 7 18:08:23 gle-dind04 kernel: overlayfs: workdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. [x7] Oct 7 18:12:55 gle-dind04 lldpd[1171]: unable to send packet on real device for veth45214f8: No such device or address Oct 7 18:15:40 gle-dind04 lldpd[1171]: unable to send packet on real device for veth3054894: No such device or address Oct 7 18:17:03 gle-dind04 lldpd[1171]: unable to send packet on real device for vethd0939f7: No such device or address Oct 7 18:17:04 gle-dind04 lldpd[1171]: unable to send packet on real device for vethda79e20: No such device or address Oct 7 18:19:39 gle-dind04 lldpd[1171]: unable to send packet on real device for veth4277706: No such device or address Oct 7 18:20:16 gle-dind04 lldpd[1171]: unable to send packet on real device for veth80dfe81: No such device or address Oct 7 18:20:50 gle-dind04 lldpd[1171]: unable to send packet on real device for vethd4692c0: No such device or address Oct 7 18:20:59 gle-dind04 lldpd[1171]: unable to send packet on real device for veth4563b7d: No such device or address Oct 7 18:21:00 gle-dind04 lldpd[1171]: unable to send packet on real device for veth17c36da: No such device or address Oct 7 18:21:55 gle-dind04 lldpd[1171]: unable to send packet on real device for veth66488db: No such device or address Oct 7 18:22:33 gle-dind04 lldpd[1171]: unable to send packet on real device for vethb42ae02: No such device or address Oct 7 18:24:06 gle-dind04 lldpd[1171]: unable to send packet on real device for vethbade778: No such device or address Oct 7 18:39:42 gle-dind04 lldpd[1171]: unable to send packet on real device for vetha4e5dc6: No such device or address Oct 7 18:41:09 gle-dind04 lldpd[1171]: unable to send packet on real device for veth17538e2: No such device or address Oct 7 18:48:49 gle-dind04 lldpd[1171]: unable to send packet on real device for veth23f6b61: No such device or address Oct 7 18:49:39 gle-dind04 lldpd[1171]: unable to send packet on real device for vethc939f86: No such device or address Oct 7 18:49:58 gle-dind04 lldpd[1171]: unable to send packet on real device for veth1a02757: No such device or address Oct 7 18:50:11 gle-dind04 lldpd[1171]: unable to send packet on real device for veth715ae5d: No such device or address Oct 7 18:53:00 gle-dind04 lldpd[1171]: unable to send packet on real device for veth03ddc0c: No such device or address Oct 7 18:53:53 gle-dind04 lldpd[1171]: unable to send packet on real device for vethed8f3d2: No such device or address Oct 7 18:54:30 gle-dind04 lldpd[1171]: unable to send packet on real device for veth57e04c6: No such device or address Oct 7 18:54:40 gle-dind04 lldpd[1171]: unable to send packet on real device for vethd39d37f: No such device or address Oct 7 18:57:01 gle-dind04 lldpd[1171]: unable to send packet on real device for vethcf169ab: No such device or address Oct 7 18:58:48 gle-dind04 lldpd[1171]: unable to send packet on real device for veth65507ed: No such device or address Oct 7 18:59:20 gle-dind04 lldpd[1171]: unable to send packet on real device for vethadc9729: No such device or address Oct 7 18:59:51 gle-dind04 lldpd[1171]: unable to send packet on real device for veth73e4192: No such device or address ... 6 more distinct messages not shown == idm00 (1 distinct, 1 total) == Oct 7 18:54:40 idm00 named[4166701]: client @0x7f11a93d3738 10.73.240.42#59024: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 7 18:39:22 idmp0 named[1598691]: client @0x7f2d3002f808 10.73.240.43#62778: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Oct 7 18:18:07 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x2] == mashie (66 distinct, 704 total) == Oct 7 18:40:44 mashie kernel: EXT4-fs error: 62 callbacks suppressed Oct 7 18:40:44 mashie kernel: EXT4-fs error (device vda1): ext4_journal_check_start:83: comm find: Detected aborted journal [x320] Oct 7 18:40:44 mashie kernel: EXT4-fs: 62 callbacks suppressed Oct 7 18:40:44 mashie kernel: EXT4-fs (vda1): Remounting filesystem read-only [x320] Oct 7 18:40:49 mashie kernel: EXT4-fs error: 1097 callbacks suppressed Oct 7 18:40:49 mashie kernel: EXT4-fs: 1097 callbacks suppressed Oct 7 18:40:54 mashie kernel: EXT4-fs error: 2233 callbacks suppressed Oct 7 18:40:54 mashie kernel: EXT4-fs: 2233 callbacks suppressed Oct 7 18:40:59 mashie kernel: EXT4-fs error: 1561 callbacks suppressed Oct 7 18:40:59 mashie kernel: EXT4-fs: 1561 callbacks suppressed Oct 7 18:41:04 mashie kernel: EXT4-fs error: 2531 callbacks suppressed Oct 7 18:41:04 mashie kernel: EXT4-fs: 2531 callbacks suppressed Oct 7 18:41:09 mashie kernel: EXT4-fs error: 1330 callbacks suppressed Oct 7 18:41:09 mashie kernel: EXT4-fs: 1330 callbacks suppressed Oct 7 18:41:14 mashie kernel: EXT4-fs error: 2542 callbacks suppressed Oct 7 18:41:14 mashie kernel: EXT4-fs: 2542 callbacks suppressed Oct 7 18:41:19 mashie kernel: EXT4-fs error: 2551 callbacks suppressed Oct 7 18:41:19 mashie kernel: EXT4-fs: 2551 callbacks suppressed Oct 7 18:41:24 mashie kernel: EXT4-fs error: 2301 callbacks suppressed Oct 7 18:41:24 mashie kernel: EXT4-fs: 2301 callbacks suppressed Oct 7 18:41:29 mashie kernel: EXT4-fs error: 1360 callbacks suppressed Oct 7 18:41:29 mashie kernel: EXT4-fs: 1360 callbacks suppressed Oct 7 18:41:34 mashie kernel: EXT4-fs error: 973 callbacks suppressed Oct 7 18:41:34 mashie kernel: EXT4-fs: 973 callbacks suppressed Oct 7 18:41:39 mashie kernel: EXT4-fs error: 916 callbacks suppressed Oct 7 18:41:39 mashie kernel: EXT4-fs: 916 callbacks suppressed Oct 7 18:41:44 mashie kernel: EXT4-fs error: 786 callbacks suppressed Oct 7 18:41:44 mashie kernel: EXT4-fs: 786 callbacks suppressed Oct 7 18:41:49 mashie kernel: EXT4-fs error: 968 callbacks suppressed Oct 7 18:41:49 mashie kernel: EXT4-fs: 968 callbacks suppressed ... 36 more distinct messages not shown == munin (2 distinct, 8 total) == Oct 7 18:29:04 munin sudo[1413792]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Oct 7 18:29:04 munin sudo[1413792]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Oct 7 18:13:03 newhonors2 dhcpcd[3701075]: dhcpcd is not running [x24] == ntop00 (94 distinct, 94 total) == Oct 7 18:05:27 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 4858, QN: 12806/12806, ET: 26) *** Oct 7 18:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 4859) *** Oct 7 18:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 4859, QN: 58/58, ET: 0) *** Oct 7 18:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 4859) *** Oct 7 18:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 4859, QN: 14478/14478, ET: 0) *** Oct 7 18:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 4860) *** Oct 7 18:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 4860) *** Oct 7 18:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 4860, QN: 55/55, ET: 0) *** Oct 7 18:10:30 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 4860, QN: 16246/16246, ET: 29) *** Oct 7 18:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 4861) *** Oct 7 18:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 4861, QN: 15307/15307, ET: 0) *** Oct 7 18:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 4861) *** Oct 7 18:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 4861, QN: 56/56, ET: 0) *** Oct 7 18:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 4862) *** Oct 7 18:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 4862) *** Oct 7 18:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 4862, QN: 61/61, ET: 0) *** Oct 7 18:15:26 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 4862, QN: 16033/16033, ET: 25) *** Oct 7 18:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 4863) *** Oct 7 18:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 4863, QN: 16723/16723, ET: 0) *** Oct 7 18:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 4863) *** Oct 7 18:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 4863, QN: 79/79, ET: 0) *** Oct 7 18:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 4864) *** Oct 7 18:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 4864) *** Oct 7 18:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 4864, QN: 76/76, ET: 0) *** Oct 7 18:20:30 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 4864, QN: 15912/15912, ET: 29) *** Oct 7 18:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 4865) *** Oct 7 18:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 4865, QN: 16100/16100, ET: 0) *** Oct 7 18:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 4865) *** Oct 7 18:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 4865, QN: 66/66, ET: 0) *** Oct 7 18:25:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 4866) *** ... 64 more distinct messages not shown == orchids (2 distinct, 2 total) == Oct 7 18:27:27 orchids systemd[1]: tailscaled.service: Got notification message from PID 265316, but reception only permitted for main PID 265269 Oct 7 18:27:27 orchids systemd[1]: tailscaled.service: Got notification message from PID 265317, but reception only permitted for main PID 265269 == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 7 18:09:09 outbound00.cs.umd.edu python3[360325]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 7 18:13:07 outbound01.cs.umd.edu python3[1821969]: ldapdb [x6] == portal (1 distinct, 74 total) == Oct 7 18:05:14 portal setroubleshoot[1867210]: SELinux is preventing /usr/local/bin/traefik from connectto access on the unix_stream_socket /run/podman/podman.sock. For complete SELinux messages run: sealert -l e0a307a3-2c22-4320-8f9d-6a166c45222d [x74] == strawberry (7 distinct, 38 total) == Oct 7 18:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 7 18:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 7 18:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 7 18:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 7 18:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 7 18:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 7 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit10-cln25 (5 distinct, 1539 total) == Oct 7 18:05:22 submit10-cln25 rsyslogd: file '/var/log/messages': open error: Input/output error [v8.24.0-57.el7_9.3 try http://www.rsyslog.com/e/2433 ] [x1200] Oct 7 18:05:22 submit10-cln25 rsyslogd: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.24.0-57.el7_9.3 try http://www.rsyslog.com/e/2013 ] [x334] Oct 7 18:25:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_check: Input/output error [x2] Oct 7 18:28:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmie_check: Input/output error [x2] Oct 7 18:30:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_daily: Input/output error == submit26-b9-3 (2 distinct, 4 total) == Sep 9 17:25:05 submit26-b9-3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Sep 9 17:30:08 submit26-b9-3 systemd-coredump[2470428]: Process 2470425 (secret02) of user 1001 dumped core.#012#012Stack trace of thread 2470425:#012#0 0x00007f1b5428d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f1b5423fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f1b54229873 abort (libc.so.6 + 0x29873)#012#3 0x00007f1b5422a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f1b5431d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f1b5431e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401231 main (secret02 + 0x1231)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f1 (10 distinct, 10 total) == Oct 7 18:26:02 submit26-b9-f1 setroubleshoot[1852975]: 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 7 18:26:02 submit26-b9-f1 setroubleshoot[1852975]: 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 7 18:26:02 submit26-b9-f1 setroubleshoot[1852975]: 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 7 18:26:02 submit26-b9-f1 setroubleshoot[1852975]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.x61cjw/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Oct 7 18:26:02 submit26-b9-f1 setroubleshoot[1852975]: 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 7 18:26:02 submit26-b9-f1 setroubleshoot[1852975]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.x61cjw. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 7 18:26:02 submit26-b9-f1 setroubleshoot[1852975]: 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 7 18:26:02 submit26-b9-f1 setroubleshoot[1852975]: 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 7 18:26:02 submit26-b9-f1 setroubleshoot[1852975]: 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 7 18:33:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (12 distinct, 14 total) == Oct 7 18:06:55 submit26-b9-f2 setroubleshoot[943044]: 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 7 18:06:55 submit26-b9-f2 setroubleshoot[943044]: 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 7 18:06:55 submit26-b9-f2 setroubleshoot[943044]: 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 7 18:06:55 submit26-b9-f2 setroubleshoot[943044]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.F6v6JZ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Oct 7 18:06:55 submit26-b9-f2 setroubleshoot[943044]: 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 7 18:06:55 submit26-b9-f2 setroubleshoot[943044]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.F6v6JZ. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 7 18:06:55 submit26-b9-f2 setroubleshoot[943044]: 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 7 18:06:55 submit26-b9-f2 setroubleshoot[943044]: 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 7 18:06:56 submit26-b9-f2 setroubleshoot[943044]: 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 7 18:15:37 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Oct 7 18:38:10 submit26-b9-f2 systemd-coredump[945157]: Process 945154 (secret02) of user 1001 dumped core.#012#012Stack trace of thread 945154:#012#0 0x00007fc35708d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fc35703fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fc357029873 abort (libc.so.6 + 0x29873)#012#3 0x00007fc35702a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fc35711d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fc35711e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401231 main (secret02 + 0x1231)#012ELF object binary architecture: AMD x86-64 Oct 7 18:38:13 submit26-b9-f2 systemd-coredump[945329]: Process 945326 (secret02) of user 1001 dumped core.#012#012Stack trace of thread 945326:#012#0 0x00007f657ec8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f657ec3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f657ec29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f657ec2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f657ed1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f657ed1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401231 main (secret02 + 0x1231)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f3 (1 distinct, 2 total) == Oct 7 18:15:05 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f4 (2 distinct, 2 total) == Oct 7 18:18:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL Oct 7 18:18:12 submit26-b9-f4 systemd-coredump[374680]: Process 374677 (secret02) of user 1001 dumped core.#012#012Stack trace of thread 374677:#012#0 0x00007fc8a648d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fc8a643fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fc8a6429873 abort (libc.so.6 + 0x29873)#012#3 0x00007fc8a642a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fc8a651d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fc8a651e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401231 main (secret02 + 0x1231)#012ELF object binary architecture: AMD x86-64 == teaching-awards (1 distinct, 1 total) == Oct 7 18:56:33 teaching-awards krb5_child[77361]: Preauthentication failed == yogurt (1 distinct, 1 total) == Oct 7 19:03:09 yogurt xdg-desktop-por[1084445]: Backend call failed: Cannot invoke method; proxy is for the well-known name org.freedesktop.ScreenSaver without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag