Command: /usr/local/sbin/syslog-digest.py Time : 0.0571s Status : exited 0 Output : Syslog digest — 2026-10-04 22:05 EDT Processed 2,395 lines, filtered 1,798 (75%). 597 unknown (358 distinct) from 25 host(s). == atif01.cs.umd.edu (1 distinct, 1 total) == Oct 4 21:24:03 atif01.cs.umd.edu kernel: net_ratelimit: 1 callbacks suppressed == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 4 21:13:46 b0b02.cs.umd.edu rustdesk[270285]: cannot open display: == biggulp.cs.umd.edu (7 distinct, 8 total) == Oct 4 21:36:45 biggulp.cs.umd.edu sshd-session[2493347]: error: kex_protocol_error: type 20 seq 2 [preauth] Oct 4 21:36:45 biggulp.cs.umd.edu sshd-session[2493347]: error: kex_protocol_error: type 30 seq 3 [preauth] Oct 4 21:36:45 biggulp.cs.umd.edu sshd-session[2493347]: error: kex_protocol_error: type 20 seq 4 [preauth] Oct 4 21:36:45 biggulp.cs.umd.edu sshd-session[2493347]: error: kex_protocol_error: type 30 seq 5 [preauth] Oct 4 21:42:08 biggulp.cs.umd.edu sshd-session[2494245]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2] Oct 4 21:42:14 biggulp.cs.umd.edu krb5_child[2494250]: Preauthentication failed Oct 4 21:42:14 biggulp.cs.umd.edu sshd-session[2494243]: error: PAM: Authentication failure for larry from 71.191.93.172 == gle-dind00.cs.umd.edu (80 distinct, 80 total) == Oct 4 21:07:59 gle-dind00.cs.umd.edu systemd-udevd[1926051]: Could not generate persistent MAC address for veth5e49990: No such file or directory Oct 4 21:07:59 gle-dind00.cs.umd.edu systemd-udevd[1926052]: Could not generate persistent MAC address for vethcf5a3bb: No such file or directory Oct 4 21:08:00 gle-dind00.cs.umd.edu systemd-udevd[1926153]: Could not generate persistent MAC address for veth4021457: No such file or directory Oct 4 21:08:00 gle-dind00.cs.umd.edu systemd-udevd[1926154]: Could not generate persistent MAC address for veth8a71942: No such file or directory Oct 4 21:08:01 gle-dind00.cs.umd.edu systemd-udevd[1926251]: Could not generate persistent MAC address for veth26ed0b9: No such file or directory Oct 4 21:08:01 gle-dind00.cs.umd.edu systemd-udevd[1926252]: Could not generate persistent MAC address for veth68b5041: No such file or directory Oct 4 21:08:02 gle-dind00.cs.umd.edu systemd-udevd[1926367]: Could not generate persistent MAC address for veth418d7e3: No such file or directory Oct 4 21:08:02 gle-dind00.cs.umd.edu systemd-udevd[1926368]: Could not generate persistent MAC address for veth91ba88b: No such file or directory Oct 4 21:08:02 gle-dind00.cs.umd.edu systemd-udevd[1926456]: Could not generate persistent MAC address for veth79b71a2: No such file or directory Oct 4 21:08:02 gle-dind00.cs.umd.edu systemd-udevd[1926457]: Could not generate persistent MAC address for veth5ad165a: No such file or directory Oct 4 21:08:20 gle-dind00.cs.umd.edu systemd-udevd[1926796]: Could not generate persistent MAC address for veth88b7e00: No such file or directory Oct 4 21:08:20 gle-dind00.cs.umd.edu systemd-udevd[1926797]: Could not generate persistent MAC address for veth0830587: No such file or directory Oct 4 21:08:21 gle-dind00.cs.umd.edu systemd-udevd[1926893]: Could not generate persistent MAC address for veth659a4dc: No such file or directory Oct 4 21:08:21 gle-dind00.cs.umd.edu systemd-udevd[1926894]: Could not generate persistent MAC address for veth8d419a3: No such file or directory Oct 4 21:08:23 gle-dind00.cs.umd.edu systemd-udevd[1927073]: Could not generate persistent MAC address for veth3149a97: No such file or directory Oct 4 21:08:23 gle-dind00.cs.umd.edu systemd-udevd[1927074]: Could not generate persistent MAC address for veth06432a0: No such file or directory Oct 4 21:08:24 gle-dind00.cs.umd.edu systemd-udevd[1927187]: Could not generate persistent MAC address for veth64a1147: No such file or directory Oct 4 21:08:24 gle-dind00.cs.umd.edu systemd-udevd[1927188]: Could not generate persistent MAC address for vethc630455: No such file or directory Oct 4 21:16:39 gle-dind00.cs.umd.edu systemd-udevd[1929061]: Could not generate persistent MAC address for vethc6ed22b: No such file or directory Oct 4 21:16:39 gle-dind00.cs.umd.edu systemd-udevd[1929062]: Could not generate persistent MAC address for veth4803929: No such file or directory Oct 4 21:16:58 gle-dind00.cs.umd.edu systemd-udevd[1929201]: Could not generate persistent MAC address for vethdbe2f13: No such file or directory Oct 4 21:16:58 gle-dind00.cs.umd.edu systemd-udevd[1929202]: Could not generate persistent MAC address for veth08fdd64: No such file or directory Oct 4 21:20:57 gle-dind00.cs.umd.edu systemd-udevd[1930105]: Could not generate persistent MAC address for veth92fae10: No such file or directory Oct 4 21:20:57 gle-dind00.cs.umd.edu systemd-udevd[1930106]: Could not generate persistent MAC address for vethb8c5334: No such file or directory Oct 4 21:20:58 gle-dind00.cs.umd.edu systemd-udevd[1930296]: Could not generate persistent MAC address for veth23c4ef0: No such file or directory Oct 4 21:20:58 gle-dind00.cs.umd.edu systemd-udevd[1930297]: Could not generate persistent MAC address for veth8c2c0bd: No such file or directory Oct 4 21:20:58 gle-dind00.cs.umd.edu systemd-udevd[1930424]: Could not generate persistent MAC address for veth3e4b2ea: No such file or directory Oct 4 21:20:58 gle-dind00.cs.umd.edu systemd-udevd[1930425]: Could not generate persistent MAC address for veth9bba428: No such file or directory Oct 4 21:21:00 gle-dind00.cs.umd.edu systemd-udevd[1930573]: Could not generate persistent MAC address for vethdcf00f3: No such file or directory Oct 4 21:21:00 gle-dind00.cs.umd.edu systemd-udevd[1930574]: Could not generate persistent MAC address for veth5c44801: No such file or directory ... 50 more distinct messages not shown == gle-dind02.cs.umd.edu (80 distinct, 80 total) == Oct 4 21:17:03 gle-dind02.cs.umd.edu systemd-udevd[899966]: Could not generate persistent MAC address for veth3cb4ccd: No such file or directory Oct 4 21:17:03 gle-dind02.cs.umd.edu systemd-udevd[899964]: Could not generate persistent MAC address for veth64c464f: No such file or directory Oct 4 21:17:03 gle-dind02.cs.umd.edu systemd-udevd[900098]: Could not generate persistent MAC address for veth8f1663a: No such file or directory Oct 4 21:17:03 gle-dind02.cs.umd.edu systemd-udevd[900099]: Could not generate persistent MAC address for veth56d53cb: No such file or directory Oct 4 21:17:04 gle-dind02.cs.umd.edu systemd-udevd[900198]: Could not generate persistent MAC address for veth7c9e252: No such file or directory Oct 4 21:17:04 gle-dind02.cs.umd.edu systemd-udevd[900199]: Could not generate persistent MAC address for vethbdac71b: No such file or directory Oct 4 21:17:05 gle-dind02.cs.umd.edu systemd-udevd[900379]: Could not generate persistent MAC address for veth552b583: No such file or directory Oct 4 21:17:05 gle-dind02.cs.umd.edu systemd-udevd[900380]: Could not generate persistent MAC address for veth881e9a0: No such file or directory Oct 4 21:17:06 gle-dind02.cs.umd.edu systemd-udevd[900560]: Could not generate persistent MAC address for vethc7250c3: No such file or directory Oct 4 21:17:06 gle-dind02.cs.umd.edu systemd-udevd[900561]: Could not generate persistent MAC address for vethce9a5ba: No such file or directory Oct 4 21:17:24 gle-dind02.cs.umd.edu systemd-udevd[900949]: Could not generate persistent MAC address for vethc8f3909: No such file or directory Oct 4 21:17:24 gle-dind02.cs.umd.edu systemd-udevd[900950]: Could not generate persistent MAC address for veth036cf97: No such file or directory Oct 4 21:17:24 gle-dind02.cs.umd.edu systemd-udevd[901049]: Could not generate persistent MAC address for vetha177054: No such file or directory Oct 4 21:17:24 gle-dind02.cs.umd.edu systemd-udevd[901050]: Could not generate persistent MAC address for vetheec6b0d: No such file or directory Oct 4 21:17:26 gle-dind02.cs.umd.edu systemd-udevd[901232]: Could not generate persistent MAC address for veth9b3fe83: No such file or directory Oct 4 21:17:26 gle-dind02.cs.umd.edu systemd-udevd[901233]: Could not generate persistent MAC address for veth3fd412c: No such file or directory Oct 4 21:17:27 gle-dind02.cs.umd.edu systemd-udevd[901343]: Could not generate persistent MAC address for vethd985701: No such file or directory Oct 4 21:17:27 gle-dind02.cs.umd.edu systemd-udevd[901344]: Could not generate persistent MAC address for vethee952c1: No such file or directory Oct 4 21:26:23 gle-dind02.cs.umd.edu systemd-udevd[903272]: Could not generate persistent MAC address for vethe511aff: No such file or directory Oct 4 21:26:23 gle-dind02.cs.umd.edu systemd-udevd[903271]: Could not generate persistent MAC address for vethdeeab4a: No such file or directory Oct 4 21:26:40 gle-dind02.cs.umd.edu systemd-udevd[903390]: Could not generate persistent MAC address for veth887682a: No such file or directory Oct 4 21:26:40 gle-dind02.cs.umd.edu systemd-udevd[903392]: Could not generate persistent MAC address for veth5ed395d: No such file or directory Oct 4 21:27:33 gle-dind02.cs.umd.edu systemd-udevd[904004]: Could not generate persistent MAC address for veth0e80ee5: No such file or directory Oct 4 21:27:33 gle-dind02.cs.umd.edu systemd-udevd[904003]: Could not generate persistent MAC address for veth4140914: No such file or directory Oct 4 21:27:34 gle-dind02.cs.umd.edu systemd-udevd[904122]: Could not generate persistent MAC address for veth861b8da: No such file or directory Oct 4 21:27:34 gle-dind02.cs.umd.edu systemd-udevd[904123]: Could not generate persistent MAC address for veth630c68d: No such file or directory Oct 4 21:27:35 gle-dind02.cs.umd.edu systemd-udevd[904223]: Could not generate persistent MAC address for veth145ed0c: No such file or directory Oct 4 21:27:35 gle-dind02.cs.umd.edu systemd-udevd[904224]: Could not generate persistent MAC address for veth5d3c27d: No such file or directory Oct 4 21:27:36 gle-dind02.cs.umd.edu systemd-udevd[904322]: Could not generate persistent MAC address for veth17ac4bf: No such file or directory Oct 4 21:27:36 gle-dind02.cs.umd.edu systemd-udevd[904323]: Could not generate persistent MAC address for vethbc5b429: No such file or directory ... 50 more distinct messages not shown == gle-dind04 (12 distinct, 22 total) == Oct 4 21:10:56 gle-dind04 lldpd[1171]: unable to send packet on real device for veth7270e43: No such device or address Oct 4 21:12:28 gle-dind04 kernel: overlayfs: upperdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. [x6] Oct 4 21:12:28 gle-dind04 kernel: overlayfs: workdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. [x6] Oct 4 21:13:11 gle-dind04 lldpd[1171]: unable to send packet on real device for veth982b592: No such device or address Oct 4 21:13:15 gle-dind04 lldpd[1171]: unable to send packet on real device for vethd17c12d: No such device or address Oct 4 21:25:16 gle-dind04 lldpd[1171]: unable to send packet on real device for vethbcbe910: No such device or address Oct 4 21:26:02 gle-dind04 lldpd[1171]: unable to send packet on real device for vethdb808d3: No such device or address Oct 4 21:32:16 gle-dind04 lldpd[1171]: unable to send packet on real device for veth639c982: No such device or address Oct 4 21:32:19 gle-dind04 lldpd[1171]: unable to send packet on real device for veth8700541: No such device or address Oct 4 21:46:05 gle-dind04 lldpd[1171]: unable to send packet on real device for vethea41c67: No such device or address Oct 4 21:46:05 gle-dind04 lldpd[1171]: unable to send packet on real device for veth9046fc5: No such device or address Oct 4 22:00:57 gle-dind04 lldpd[1171]: unable to send packet on real device for veth4bd300b: No such device or address == hazfs.cs.umd.edu (1 distinct, 1 total) == Oct 4 22:04:31 hazfs.cs.umd.edu rpc.mountd[1586325]: refused mount request from 10.227.96.19 for /raid/webdev (/): not exported == idm00 (1 distinct, 1 total) == Oct 4 21:54:38 idm00 named[4166701]: client @0x7f11a4042778 10.73.240.42#63267: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 4 21:39:24 idmp0 named[1598691]: client @0x7f2d28029f68 10.73.240.43#52333: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Oct 4 21:08:03 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 82 total) == Oct 4 21:08:05 munin sudo[4103554]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x41] Oct 4 21:08:05 munin sudo[4103554]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x41] == newhonors2 (1 distinct, 24 total) == Oct 4 21:13:03 newhonors2 dhcpcd[3565816]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Oct 4 21:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3202) *** Oct 4 21:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3202, QN: 62/62, ET: 0) *** Oct 4 21:05:10 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3202, QN: 6698/6698, ET: 9) *** Oct 4 21:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3203) *** Oct 4 21:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3203, QN: 6444/6444, ET: 0) *** Oct 4 21:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3203) *** Oct 4 21:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3203, QN: 69/69, ET: 0) *** Oct 4 21:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3204) *** Oct 4 21:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3204) *** Oct 4 21:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3204, QN: 55/55, ET: 0) *** Oct 4 21:10:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3204, QN: 6209/6209, ET: 10) *** Oct 4 21:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3205) *** Oct 4 21:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3205, QN: 5894/5894, ET: 0) *** Oct 4 21:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3205) *** Oct 4 21:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3205, QN: 64/64, ET: 0) *** Oct 4 21:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3206) *** Oct 4 21:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3206) *** Oct 4 21:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3206, QN: 64/64, ET: 0) *** Oct 4 21:15:10 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3206, QN: 5686/5686, ET: 9) *** Oct 4 21:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3207) *** Oct 4 21:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3207, QN: 6024/6024, ET: 0) *** Oct 4 21:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3207) *** Oct 4 21:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3207, QN: 50/50, ET: 0) *** Oct 4 21:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3208) *** Oct 4 21:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3208) *** Oct 4 21:20:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3208, QN: 49/49, ET: 1) *** Oct 4 21:20:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3208, QN: 6044/6044, ET: 10) *** Oct 4 21:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3209) *** Oct 4 21:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3209, QN: 4895/4895, ET: 0) *** Oct 4 21:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3209) *** ... 67 more distinct messages not shown == openrepo (1 distinct, 1 total) == Oct 4 21:21:21 openrepo systemd[1]: resmon.service: Supervising process 841438 which is not our child. We'll most likely not notice when it exits. == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 4 21:09:09 outbound00.cs.umd.edu python3[2775433]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 7 total) == Oct 4 21:08:28 outbound01.cs.umd.edu krb5_child[847677]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 4 21:13:07 outbound01.cs.umd.edu python3[848709]: ldapdb [x6] == portal (1 distinct, 75 total) == Oct 4 21:05:18 portal setroubleshoot[952859]: 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 [x75] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Oct 4 21:20:11 sentry-docker00.cs.umd.edu systemd-udevd[1497843]: link_config: could not get ethtool features for vethb5e059f Oct 4 21:20:11 sentry-docker00.cs.umd.edu systemd-udevd[1497843]: Could not set offload features of vethb5e059f: No such device Oct 4 21:20:11 sentry-docker00.cs.umd.edu systemd-udevd[1497908]: Could not generate persistent MAC address for veth686aef7: No such file or directory Oct 4 21:20:11 sentry-docker00.cs.umd.edu systemd-udevd[1497907]: Could not generate persistent MAC address for veth666bb37: No such file or directory Oct 4 21:20:11 sentry-docker00.cs.umd.edu systemd-udevd[1497911]: Could not generate persistent MAC address for vethd0c9a97: No such file or directory Oct 4 21:20:11 sentry-docker00.cs.umd.edu systemd-udevd[1497913]: Could not generate persistent MAC address for veth5f1a8e2: No such file or directory Oct 4 21:20:11 sentry-docker00.cs.umd.edu systemd-udevd[1497936]: Could not generate persistent MAC address for vethb255c78: No such file or directory Oct 4 21:20:11 sentry-docker00.cs.umd.edu systemd-udevd[1497937]: Could not generate persistent MAC address for veth60296d1: No such file or directory Oct 4 21:20:11 sentry-docker00.cs.umd.edu systemd-udevd[1497947]: Could not generate persistent MAC address for veth767622d: No such file or directory Oct 4 21:20:11 sentry-docker00.cs.umd.edu systemd-udevd[1497959]: Could not generate persistent MAC address for veth48186bd: No such file or directory Oct 4 21:20:11 sentry-docker00.cs.umd.edu systemd-udevd[1497995]: Could not generate persistent MAC address for veth867f40d: No such file or directory Oct 4 21:20:11 sentry-docker00.cs.umd.edu systemd-udevd[1497993]: Could not generate persistent MAC address for vethe06ee0d: No such file or directory Oct 4 21:40:19 sentry-docker00.cs.umd.edu systemd-udevd[1507286]: link_config: could not get ethtool features for vethb255c78 Oct 4 21:40:19 sentry-docker00.cs.umd.edu systemd-udevd[1507286]: Could not set offload features of vethb255c78: No such device Oct 4 21:40:19 sentry-docker00.cs.umd.edu systemd-udevd[1507376]: Could not generate persistent MAC address for vethb6bcbbf: No such file or directory Oct 4 21:40:19 sentry-docker00.cs.umd.edu systemd-udevd[1507377]: Could not generate persistent MAC address for veth9c2478c: No such file or directory Oct 4 21:40:19 sentry-docker00.cs.umd.edu systemd-udevd[1507380]: Could not generate persistent MAC address for vethc5bf52f: No such file or directory Oct 4 21:40:19 sentry-docker00.cs.umd.edu systemd-udevd[1507386]: Could not generate persistent MAC address for vethb3a550e: No such file or directory Oct 4 21:40:19 sentry-docker00.cs.umd.edu systemd-udevd[1507388]: Could not generate persistent MAC address for vethc0336d2: No such file or directory Oct 4 21:40:19 sentry-docker00.cs.umd.edu systemd-udevd[1507380]: Could not generate persistent MAC address for vethe98b8ae: No such file or directory Oct 4 21:40:19 sentry-docker00.cs.umd.edu systemd-udevd[1507406]: Could not generate persistent MAC address for vethc095349: No such file or directory Oct 4 21:40:19 sentry-docker00.cs.umd.edu systemd-udevd[1507407]: Could not generate persistent MAC address for veth1d15483: No such file or directory Oct 4 21:40:19 sentry-docker00.cs.umd.edu systemd-udevd[1507455]: Could not generate persistent MAC address for veth4d749b5: No such file or directory Oct 4 21:40:19 sentry-docker00.cs.umd.edu systemd-udevd[1507463]: Could not generate persistent MAC address for veth0b34856: No such file or directory Oct 4 22:00:27 sentry-docker00.cs.umd.edu systemd-udevd[1516954]: link_config: could not get ethtool features for vethc5bf52f Oct 4 22:00:27 sentry-docker00.cs.umd.edu systemd-udevd[1516954]: Could not set offload features of vethc5bf52f: No such device Oct 4 22:00:27 sentry-docker00.cs.umd.edu systemd-udevd[1516990]: Could not generate persistent MAC address for veth12edc89: No such file or directory Oct 4 22:00:27 sentry-docker00.cs.umd.edu systemd-udevd[1516991]: Could not generate persistent MAC address for vethd3bf08c: No such file or directory Oct 4 22:00:27 sentry-docker00.cs.umd.edu systemd-udevd[1516994]: Could not generate persistent MAC address for vethae30a81: No such file or directory Oct 4 22:00:27 sentry-docker00.cs.umd.edu systemd-udevd[1516995]: Could not generate persistent MAC address for veth468e6e9: No such file or directory ... 6 more distinct messages not shown == smokeping (1 distinct, 1 total) == Oct 4 21:21:12 smokeping systemd[1]: resmon.service: Supervising process 4044795 which is not our child. We'll most likely not notice when it exits. == smokeping-slave (1 distinct, 1 total) == Oct 4 21:21:40 smokeping-slave systemd[1]: resmon.service: Supervising process 3637959 which is not our child. We'll most likely not notice when it exits. == strawberry (7 distinct, 38 total) == Oct 4 21:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 4 21:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 4 21:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 4 21:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 4 21:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 4 21:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 4 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (10 distinct, 14 total) == Oct 4 21:06:48 submit26-b9-f3 setroubleshoot[983808]: 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 [x2] Oct 4 21:06:48 submit26-b9-f3 setroubleshoot[983808]: 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 [x2] Oct 4 21:06:48 submit26-b9-f3 setroubleshoot[983808]: 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 21:06:48 submit26-b9-f3 setroubleshoot[983808]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ao4bcH/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 4 21:06:48 submit26-b9-f3 setroubleshoot[983808]: 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 21:06:48 submit26-b9-f3 setroubleshoot[983808]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ao4bcH. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 4 21:06:48 submit26-b9-f3 setroubleshoot[983808]: 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 [x2] Oct 4 21:06:48 submit26-b9-f3 setroubleshoot[983808]: 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 21:06:48 submit26-b9-f3 setroubleshoot[983808]: 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 [x2] Oct 4 21:06:48 submit26-b9-f3 setroubleshoot[983808]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.MJ3b5b. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd == submit26-b9-f4 (11 distinct, 14 total) == Oct 4 21:24:52 submit26-b9-f4 setroubleshoot[3769879]: 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 21:24:52 submit26-b9-f4 setroubleshoot[3769879]: 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 21:24:52 submit26-b9-f4 setroubleshoot[3769879]: 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 [x2] Oct 4 21:24:52 submit26-b9-f4 setroubleshoot[3769879]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3aY37P/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 4 21:24:52 submit26-b9-f4 setroubleshoot[3769879]: 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 [x2] Oct 4 21:24:52 submit26-b9-f4 setroubleshoot[3769879]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3aY37P. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 4 21:24:52 submit26-b9-f4 setroubleshoot[3769879]: 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 21:24:52 submit26-b9-f4 setroubleshoot[3769879]: 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 [x2] Oct 4 21:24:52 submit26-b9-f4 setroubleshoot[3769879]: 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 Oct 4 21:24:52 submit26-b9-f4 setroubleshoot[3769879]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.nbhZ0J/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 4 21:48:08 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == unknown (1 distinct, 1 total) == using-explainable-ai == zfs04 (1 distinct, 1 total) == Oct 4 21:21:58 zfs04 systemd[1]: resmon.service: Supervising process 2388767 which is not our child. We'll most likely not notice when it exits.