Command: /usr/local/sbin/syslog-digest.py Time : 0.0518s Status : exited 0 Output : Syslog digest — 2026-10-04 18:05 EDT Processed 2,019 lines, filtered 1,587 (78%). 432 unknown (273 distinct) from 21 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 4 17:13:33 b0b02.cs.umd.edu rustdesk[209715]: cannot open display: == cheezit.cs.umd.edu (1 distinct, 1 total) == Oct 4 17:57:53 cheezit.cs.umd.edu sshd-session[2045581]: pam_access(sshd:auth): access denied for user `alanfluo' from `71.126.169.100' == frozone (1 distinct, 1 total) == Oct 4 17:35:54 frozone systemd-tmpfiles[3487479]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted == gle-dind00.cs.umd.edu (40 distinct, 40 total) == Oct 4 17:27:52 gle-dind00.cs.umd.edu systemd-udevd[1865658]: Could not generate persistent MAC address for vethdc6138c: No such file or directory Oct 4 17:27:52 gle-dind00.cs.umd.edu systemd-udevd[1865657]: Could not generate persistent MAC address for vethcc1a80f: No such file or directory Oct 4 17:27:53 gle-dind00.cs.umd.edu systemd-udevd[1865759]: Could not generate persistent MAC address for vetha8452e6: No such file or directory Oct 4 17:27:53 gle-dind00.cs.umd.edu systemd-udevd[1865760]: Could not generate persistent MAC address for vethf5279a6: No such file or directory Oct 4 17:27:54 gle-dind00.cs.umd.edu systemd-udevd[1865860]: Could not generate persistent MAC address for vethf8089b7: No such file or directory Oct 4 17:27:54 gle-dind00.cs.umd.edu systemd-udevd[1865861]: Could not generate persistent MAC address for veth0ae18f3: No such file or directory Oct 4 17:27:55 gle-dind00.cs.umd.edu systemd-udevd[1865954]: Could not generate persistent MAC address for veth6e70a9d: No such file or directory Oct 4 17:27:55 gle-dind00.cs.umd.edu systemd-udevd[1865955]: Could not generate persistent MAC address for vethf5e7d4b: No such file or directory Oct 4 17:27:55 gle-dind00.cs.umd.edu systemd-udevd[1866044]: Could not generate persistent MAC address for veth8fafb34: No such file or directory Oct 4 17:27:55 gle-dind00.cs.umd.edu systemd-udevd[1866043]: Could not generate persistent MAC address for veth3660868: No such file or directory Oct 4 17:28:13 gle-dind00.cs.umd.edu systemd-udevd[1866544]: Could not generate persistent MAC address for vetha2483ca: No such file or directory Oct 4 17:28:13 gle-dind00.cs.umd.edu systemd-udevd[1866545]: Could not generate persistent MAC address for veth4a81914: No such file or directory Oct 4 17:28:14 gle-dind00.cs.umd.edu systemd-udevd[1866643]: Could not generate persistent MAC address for vethafacddb: No such file or directory Oct 4 17:28:14 gle-dind00.cs.umd.edu systemd-udevd[1866644]: Could not generate persistent MAC address for vethbec5016: No such file or directory Oct 4 17:28:15 gle-dind00.cs.umd.edu systemd-udevd[1866833]: Could not generate persistent MAC address for veth4788134: No such file or directory Oct 4 17:28:15 gle-dind00.cs.umd.edu systemd-udevd[1866832]: Could not generate persistent MAC address for veth0c5a622: No such file or directory Oct 4 17:28:17 gle-dind00.cs.umd.edu systemd-udevd[1866981]: Could not generate persistent MAC address for veth1be1389: No such file or directory Oct 4 17:28:17 gle-dind00.cs.umd.edu systemd-udevd[1866980]: Could not generate persistent MAC address for veth1e38272: No such file or directory Oct 4 17:35:20 gle-dind00.cs.umd.edu systemd-udevd[1868443]: Could not generate persistent MAC address for veth3082d9e: No such file or directory Oct 4 17:35:20 gle-dind00.cs.umd.edu systemd-udevd[1868444]: Could not generate persistent MAC address for veth1d884b0: No such file or directory Oct 4 17:35:38 gle-dind00.cs.umd.edu systemd-udevd[1868563]: Could not generate persistent MAC address for veth83101a6: No such file or directory Oct 4 17:35:38 gle-dind00.cs.umd.edu systemd-udevd[1868564]: Could not generate persistent MAC address for veth8091057: No such file or directory Oct 4 17:59:58 gle-dind00.cs.umd.edu systemd-udevd[1873995]: Could not generate persistent MAC address for vethee97922: No such file or directory Oct 4 17:59:58 gle-dind00.cs.umd.edu systemd-udevd[1873996]: Could not generate persistent MAC address for veth61473ce: No such file or directory Oct 4 17:59:59 gle-dind00.cs.umd.edu systemd-udevd[1874095]: Could not generate persistent MAC address for veth9ed93c3: No such file or directory Oct 4 17:59:59 gle-dind00.cs.umd.edu systemd-udevd[1874096]: Could not generate persistent MAC address for veth4b132dc: No such file or directory Oct 4 18:00:00 gle-dind00.cs.umd.edu systemd-udevd[1874198]: Could not generate persistent MAC address for veth6878708: No such file or directory Oct 4 18:00:00 gle-dind00.cs.umd.edu systemd-udevd[1874199]: Could not generate persistent MAC address for veth96621b9: No such file or directory Oct 4 18:00:01 gle-dind00.cs.umd.edu systemd-udevd[1874299]: Could not generate persistent MAC address for veth5fee3ee: No such file or directory Oct 4 18:00:01 gle-dind00.cs.umd.edu systemd-udevd[1874300]: Could not generate persistent MAC address for veth5d3f4e9: No such file or directory ... 10 more distinct messages not shown == gle-dind02.cs.umd.edu (45 distinct, 45 total) == Oct 4 17:17:52 gle-dind02.cs.umd.edu systemd-udevd[838653]: Could not generate persistent MAC address for veth136db17: No such file or directory Oct 4 17:17:52 gle-dind02.cs.umd.edu systemd-udevd[838654]: Could not generate persistent MAC address for veth00c6ab4: No such file or directory Oct 4 17:17:53 gle-dind02.cs.umd.edu systemd-udevd[838752]: Could not generate persistent MAC address for veth4504a5d: No such file or directory Oct 4 17:17:53 gle-dind02.cs.umd.edu systemd-udevd[838753]: Could not generate persistent MAC address for vethbbefec1: No such file or directory Oct 4 17:17:54 gle-dind02.cs.umd.edu systemd-udevd[838851]: Could not generate persistent MAC address for veth5468e14: No such file or directory Oct 4 17:17:54 gle-dind02.cs.umd.edu systemd-udevd[838852]: Could not generate persistent MAC address for vethaefd0d4: No such file or directory Oct 4 17:17:55 gle-dind02.cs.umd.edu systemd-udevd[838950]: Could not generate persistent MAC address for vethdeac98d: No such file or directory Oct 4 17:17:55 gle-dind02.cs.umd.edu systemd-udevd[838951]: Could not generate persistent MAC address for veth4e26ec4: No such file or directory Oct 4 17:17:55 gle-dind02.cs.umd.edu systemd-udevd[839040]: Could not generate persistent MAC address for veth1a0feb2: No such file or directory Oct 4 17:17:55 gle-dind02.cs.umd.edu systemd-udevd[839041]: Could not generate persistent MAC address for vethb85fab4: No such file or directory Oct 4 17:18:13 gle-dind02.cs.umd.edu systemd-udevd[839360]: Could not generate persistent MAC address for vethd67aa63: No such file or directory Oct 4 17:18:13 gle-dind02.cs.umd.edu systemd-udevd[839361]: Could not generate persistent MAC address for veth97cead7: No such file or directory Oct 4 17:18:14 gle-dind02.cs.umd.edu systemd-udevd[839458]: Could not generate persistent MAC address for vethbaa1076: No such file or directory Oct 4 17:18:14 gle-dind02.cs.umd.edu systemd-udevd[839459]: Could not generate persistent MAC address for veth8f4d651: No such file or directory Oct 4 17:18:16 gle-dind02.cs.umd.edu systemd-udevd[839638]: Could not generate persistent MAC address for veth0e2a578: No such file or directory Oct 4 17:18:16 gle-dind02.cs.umd.edu systemd-udevd[839639]: Could not generate persistent MAC address for veth85eb9fe: No such file or directory Oct 4 17:18:17 gle-dind02.cs.umd.edu systemd-udevd[839745]: Could not generate persistent MAC address for veth9315904: No such file or directory Oct 4 17:18:17 gle-dind02.cs.umd.edu systemd-udevd[839746]: Could not generate persistent MAC address for vethf7eacbb: No such file or directory Oct 4 17:28:52 gle-dind02.cs.umd.edu systemd-udevd[842050]: Could not generate persistent MAC address for veth75579b8: No such file or directory Oct 4 17:28:52 gle-dind02.cs.umd.edu systemd-udevd[842051]: Could not generate persistent MAC address for veth0dc0421: No such file or directory Oct 4 17:29:10 gle-dind02.cs.umd.edu systemd-udevd[842201]: Could not generate persistent MAC address for veth6295aba: No such file or directory Oct 4 17:29:10 gle-dind02.cs.umd.edu systemd-udevd[842202]: Could not generate persistent MAC address for vethe313e39: No such file or directory Oct 4 17:57:00 gle-dind02.cs.umd.edu systemd-udevd[846753]: Could not generate persistent MAC address for veth98a2903: No such file or directory Oct 4 17:57:00 gle-dind02.cs.umd.edu systemd-udevd[846752]: Could not generate persistent MAC address for vetha3322f7: No such file or directory Oct 4 17:57:01 gle-dind02.cs.umd.edu systemd-udevd[846865]: Could not generate persistent MAC address for vethffc86eb: No such file or directory Oct 4 17:57:01 gle-dind02.cs.umd.edu systemd-udevd[846864]: Could not generate persistent MAC address for veth32649e8: No such file or directory Oct 4 17:57:01 gle-dind02.cs.umd.edu systemd-udevd[846970]: Could not generate persistent MAC address for vethe9ce1d8: No such file or directory Oct 4 17:57:01 gle-dind02.cs.umd.edu systemd-udevd[846971]: Could not generate persistent MAC address for vethc7c36b4: No such file or directory Oct 4 17:57:03 gle-dind02.cs.umd.edu systemd-udevd[847085]: Could not generate persistent MAC address for veth283118a: No such file or directory Oct 4 17:57:03 gle-dind02.cs.umd.edu systemd-udevd[847086]: Could not generate persistent MAC address for vethbc73e66: No such file or directory ... 15 more distinct messages not shown == gle-dind04 (13 distinct, 13 total) == Oct 4 17:23:20 gle-dind04 kernel: overlayfs: upperdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. Oct 4 17:23:20 gle-dind04 kernel: overlayfs: workdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. Oct 4 17:24:34 gle-dind04 lldpd[1171]: unable to send packet on real device for veth2904cef: No such device or address Oct 4 17:37:11 gle-dind04 systemd-coredump[2209725]: Process 2209722 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2209722:#012#0 0x00005651f86802ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x00005651f869f2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x00005651f869efc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x00005651f869a1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x00005651f869a0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x00005651f869a065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x00005651f86beada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x00005651f86b8651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x00005651f86b47a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x00005651f8697edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x00005651f86c8b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x00005651f8702a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Oct 4 17:37:11 gle-dind04 systemd-coredump[2209732]: Process 2209730 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2209730:#012#0 0x000055e4840432ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055e4840622c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055e484061fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055e48405d1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055e48405d0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055e48405d065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055e484081ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055e48407b651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055e4840777a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055e48405aedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055e48408bb52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055e4840c5a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Oct 4 17:37:11 gle-dind04 systemd-coredump[2209739]: Process 2209737 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2209737:#012#0 0x000055ee06d592ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055ee06d782c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055ee06d77fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055ee06d731d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055ee06d730a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055ee06d73065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055ee06d97ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055ee06d91651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055ee06d8d7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055ee06d70edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055ee06da1b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055ee06ddba47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Oct 4 17:37:11 gle-dind04 systemd-coredump[2209746]: Process 2209744 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2209744:#012#0 0x00005578984482ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x00005578984672c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000557898466fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x00005578984621d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x00005578984620a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000557898462065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000557898486ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000557898480651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055789847c7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055789845fedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000557898490b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x00005578984caa47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Oct 4 17:37:11 gle-dind04 systemd-coredump[2209753]: Process 2209751 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2209751:#012#0 0x0000564fbb8212ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000564fbb8402c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000564fbb83ffc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000564fbb83b1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000564fbb83b0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000564fbb83b065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000564fbb85fada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000564fbb859651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000564fbb8557a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000564fbb838edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000564fbb869b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000564fbb8a3a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Oct 4 17:37:12 gle-dind04 systemd-coredump[2209761]: Process 2209759 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2209759:#012#0 0x00005643fef852ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x00005643fefa42c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x00005643fefa3fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x00005643fef9f1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x00005643fef9f0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x00005643fef9f065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x00005643fefc3ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x00005643fefbd651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x00005643fefb97a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x00005643fef9cedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x00005643fefcdb52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x00005643ff007a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Oct 4 17:37:12 gle-dind04 systemd-coredump[2209768]: Process 2209766 (ctr) of user 0 dumped core.#012#012Stack trace of thread 2209766:#012#0 0x000055b3e5eb42ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055b3e5ed32c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055b3e5ed2fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055b3e5ece1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055b3e5ece0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055b3e5ece065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055b3e5ef2ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055b3e5eec651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055b3e5ee87a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055b3e5ecbedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055b3e5efcb52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055b3e5f36a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Oct 4 17:55:21 gle-dind04 lldpd[1171]: unable to send packet on real device for veth36191f9: No such device or address Oct 4 17:55:21 gle-dind04 lldpd[1171]: unable to send packet on real device for veth0a91838: No such device or address Oct 4 18:01:40 gle-dind04 lldpd[1171]: unable to send packet on real device for veth16eaad0: No such device or address == idm00 (1 distinct, 1 total) == Oct 4 17:54:37 idm00 named[4166701]: client @0x7f11a400ab58 10.73.240.42#62050: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 4 17:39:24 idmp0 named[1598691]: client @0x7f2d280332b8 10.73.240.43#60045: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 2 total) == Oct 4 17:10:24 inbound00.cs.umd.edu krb5_child[2896213]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == itmon02 (1 distinct, 6 total) == Oct 4 17:08:02 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x6] == munin (2 distinct, 10 total) == Oct 4 17:23:23 munin sudo[4022426]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x5] Oct 4 17:23:23 munin sudo[4022426]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x5] == netman.cs.umd.edu (1 distinct, 4 total) == Oct 4 17:09:21 netman.cs.umd.edu krb5_child[292922]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] == newhonors2 (1 distinct, 24 total) == Oct 4 17:13:03 newhonors2 dhcpcd[3558429]: dhcpcd is not running [x24] == ntop00 (95 distinct, 95 total) == Oct 4 17:05:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3106, QN: 6526/6526, ET: 10) *** Oct 4 17:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3107) *** Oct 4 17:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3107, QN: 7677/7677, ET: 0) *** Oct 4 17:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3107) *** Oct 4 17:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3107, QN: 72/72, ET: 0) *** Oct 4 17:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3108) *** Oct 4 17:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3108) *** Oct 4 17:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3108, QN: 66/66, ET: 0) *** Oct 4 17:10:12 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3108, QN: 8365/8365, ET: 11) *** Oct 4 17:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3109) *** Oct 4 17:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3109, QN: 7447/7447, ET: 0) *** Oct 4 17:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3109) *** Oct 4 17:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3109, QN: 58/58, ET: 0) *** Oct 4 17:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3110) *** Oct 4 17:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3110) *** Oct 4 17:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3110, QN: 50/50, ET: 0) *** Oct 4 17:15:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3110, QN: 7360/7360, ET: 10) *** Oct 4 17:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3111) *** Oct 4 17:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3111, QN: 6643/6643, ET: 0) *** Oct 4 17:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3111) *** Oct 4 17:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3111, QN: 60/60, ET: 0) *** Oct 4 17:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3112) *** Oct 4 17:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3112) *** Oct 4 17:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3112, QN: 65/65, ET: 0) *** Oct 4 17:20:13 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3112, QN: 7770/7770, ET: 12) *** Oct 4 17:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3113) *** Oct 4 17:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3113, QN: 8854/8854, ET: 0) *** Oct 4 17:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3113) *** Oct 4 17:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3113, QN: 64/64, ET: 0) *** Oct 4 17:25:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3114) *** ... 65 more distinct messages not shown == outbound00.cs.umd.edu (4 distinct, 9 total) == Oct 4 17:09:08 outbound00.cs.umd.edu python3[2719639]: ldapdb [x6] Oct 4 17:16:25 outbound00.cs.umd.edu krb5_child[2721232]: Client 'test1@UMD.EDU' not found in Kerberos database Oct 4 17:34:11 outbound00.cs.umd.edu krb5_child[2725566]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 4 17:35:59 outbound00.cs.umd.edu krb5_child[2726095]: Preauthentication failed == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 4 17:13:06 outbound01.cs.umd.edu python3[792740]: ldapdb [x6] == portal (1 distinct, 79 total) == Oct 4 17:06:08 portal setroubleshoot[901008]: 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 [x79] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1384958]: link_config: could not get ethtool features for veth5095afb Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1384958]: Could not set offload features of veth5095afb: No such device Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1384959]: link_config: could not get ethtool features for veth04e3d73 Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1384959]: Could not set offload features of veth04e3d73: No such device Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1384993]: Could not generate persistent MAC address for vethe659305: No such file or directory Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1384994]: Could not generate persistent MAC address for veth5bde5b4: No such file or directory Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1384997]: Could not generate persistent MAC address for veth7a9b8cc: No such file or directory Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1384998]: Could not generate persistent MAC address for veth0258f58: No such file or directory Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1385021]: Could not generate persistent MAC address for vethcc779f4: No such file or directory Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1385022]: Could not generate persistent MAC address for vethe54fc19: No such file or directory Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1385040]: Could not generate persistent MAC address for vethd2e803d: No such file or directory Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1385047]: Could not generate persistent MAC address for vethd90d9fd: No such file or directory Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1385056]: Could not generate persistent MAC address for veth654d58c: No such file or directory Oct 4 17:18:31 sentry-docker00.cs.umd.edu systemd-udevd[1385058]: Could not generate persistent MAC address for veth529167c: No such file or directory Oct 4 17:38:39 sentry-docker00.cs.umd.edu systemd-udevd[1394546]: link_config: could not get ethtool features for vethd2e803d Oct 4 17:38:39 sentry-docker00.cs.umd.edu systemd-udevd[1394546]: Could not set offload features of vethd2e803d: No such device Oct 4 17:38:39 sentry-docker00.cs.umd.edu systemd-udevd[1394578]: Could not generate persistent MAC address for veth1d3327d: No such file or directory Oct 4 17:38:39 sentry-docker00.cs.umd.edu systemd-udevd[1394579]: Could not generate persistent MAC address for veth852e79b: No such file or directory Oct 4 17:38:39 sentry-docker00.cs.umd.edu systemd-udevd[1394582]: Could not generate persistent MAC address for vethe44b82a: No such file or directory Oct 4 17:38:39 sentry-docker00.cs.umd.edu systemd-udevd[1394583]: Could not generate persistent MAC address for vethc5bed9b: No such file or directory Oct 4 17:38:39 sentry-docker00.cs.umd.edu systemd-udevd[1394604]: Could not generate persistent MAC address for veth8b2c532: No such file or directory Oct 4 17:38:39 sentry-docker00.cs.umd.edu systemd-udevd[1394597]: Could not generate persistent MAC address for veth9d95430: No such file or directory Oct 4 17:38:39 sentry-docker00.cs.umd.edu systemd-udevd[1394608]: Could not generate persistent MAC address for veth1ad62ab: No such file or directory Oct 4 17:38:39 sentry-docker00.cs.umd.edu systemd-udevd[1394609]: Could not generate persistent MAC address for veth8cf9a3b: No such file or directory Oct 4 17:38:39 sentry-docker00.cs.umd.edu systemd-udevd[1394618]: Could not generate persistent MAC address for veth7c174f7: No such file or directory Oct 4 17:38:39 sentry-docker00.cs.umd.edu systemd-udevd[1394615]: Could not generate persistent MAC address for veth0b3aab6: No such file or directory Oct 4 17:58:47 sentry-docker00.cs.umd.edu systemd-udevd[1403920]: link_config: could not get ethtool features for vethe44b82a Oct 4 17:58:47 sentry-docker00.cs.umd.edu systemd-udevd[1403920]: Could not set offload features of vethe44b82a: No such device Oct 4 17:58:48 sentry-docker00.cs.umd.edu systemd-udevd[1403952]: Could not generate persistent MAC address for veth28ee7b6: No such file or directory Oct 4 17:58:48 sentry-docker00.cs.umd.edu systemd-udevd[1403953]: Could not generate persistent MAC address for veth55d2f2c: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 4 17:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 4 17:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 4 17:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 4 17:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 4 17:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 4 17:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 4 17:34:43 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 9 total) == Oct 4 17:06:48 submit26-b9-f3 setroubleshoot[943709]: 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 Oct 4 17:06:48 submit26-b9-f3 setroubleshoot[943709]: 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 Oct 4 17:06:48 submit26-b9-f3 setroubleshoot[943709]: 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 4 17:06:48 submit26-b9-f3 setroubleshoot[943709]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.yZkULf/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 4 17:06:48 submit26-b9-f3 setroubleshoot[943709]: 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 4 17:06:48 submit26-b9-f3 setroubleshoot[943709]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.yZkULf. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 4 17:06:48 submit26-b9-f3 setroubleshoot[943709]: 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 4 17:06:48 submit26-b9-f3 setroubleshoot[943709]: 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 4 17:06:48 submit26-b9-f3 setroubleshoot[943709]: 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 4 17:24:51 submit26-b9-f4 setroubleshoot[3740940]: 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 4 17:24:51 submit26-b9-f4 setroubleshoot[3740940]: 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 4 17:24:51 submit26-b9-f4 setroubleshoot[3740940]: 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 4 17:24:51 submit26-b9-f4 setroubleshoot[3740940]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.J5NHWf/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 4 17:24:51 submit26-b9-f4 setroubleshoot[3740940]: 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 4 17:24:51 submit26-b9-f4 setroubleshoot[3740940]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.J5NHWf. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 4 17:24:51 submit26-b9-f4 setroubleshoot[3740940]: 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 4 17:24:52 submit26-b9-f4 setroubleshoot[3740940]: 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 4 17:24:52 submit26-b9-f4 setroubleshoot[3740940]: 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