Command: /usr/local/sbin/syslog-digest.py Time : 0.0478s Status : exited 0 Output : Syslog digest — 2026-10-02 23:05 EDT Processed 1,848 lines, filtered 1,491 (80%). 357 unknown (192 distinct) from 22 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 2 22:10:49 b0b02.cs.umd.edu rustdesk[3748727]: cannot open display: == idm00 (1 distinct, 1 total) == Oct 2 22:54:36 idm00 named[4166701]: client @0x7f119806c0a8 10.73.240.42#63334: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 2 22:39:24 idmp0 named[1598691]: client @0x7f2d50022b88 10.73.240.43#52499: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 1 total) == Oct 2 22:39:35 inbound00.cs.umd.edu sshd-session[2291990]: fatal: userauth_pubkey: parse publickey packet: incomplete message [preauth] == inbound01.cs.umd.edu (1 distinct, 1 total) == Oct 2 22:39:33 inbound01.cs.umd.edu krb5_child[308214]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 3 total) == Oct 2 22:43:05 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x3] == matrix (3 distinct, 4 total) == Oct 2 22:25:10 matrix krb5_child[924291]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Oct 2 22:25:12 matrix sshd[924157]: error: PAM: Authentication failure for admin from 130.211.80.141 Oct 2 22:26:26 matrix sshd[925466]: error: Protocol major versions differ: 2 vs. 1 == mcstic (2 distinct, 5 total) == Oct 2 22:35:13 mcstic krb5_child[1452017]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Oct 2 22:35:17 mcstic sshd[1452012]: error: PAM: Authentication failure for admin from 34.14.6.137 == munin (2 distinct, 10 total) == Oct 2 22:08:37 munin sudo[3084221]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x5] Oct 2 22:08:37 munin sudo[3084221]: 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 2 22:13:45 netman.cs.umd.edu krb5_child[3717388]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] == newhonors2 (1 distinct, 24 total) == Oct 2 22:13:03 newhonors2 dhcpcd[3476850]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Oct 2 22:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2074) *** Oct 2 22:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2074) *** Oct 2 22:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2074, QN: 68/68, ET: 0) *** Oct 2 22:05:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2074, QN: 4968/4968, ET: 7) *** Oct 2 22:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2075) *** Oct 2 22:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2075, QN: 53/53, ET: 0) *** Oct 2 22:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2075) *** Oct 2 22:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2075, QN: 4725/4725, ET: 0) *** Oct 2 22:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2076) *** Oct 2 22:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2076) *** Oct 2 22:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2076, QN: 52/52, ET: 0) *** Oct 2 22:10:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2076, QN: 4381/4381, ET: 7) *** Oct 2 22:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2077) *** Oct 2 22:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2077, QN: 51/51, ET: 0) *** Oct 2 22:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2077) *** Oct 2 22:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2077, QN: 4419/4419, ET: 0) *** Oct 2 22:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2078) *** Oct 2 22:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2078) *** Oct 2 22:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2078, QN: 56/56, ET: 0) *** Oct 2 22:15:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2078, QN: 4598/4598, ET: 7) *** Oct 2 22:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2079) *** Oct 2 22:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2079, QN: 4553/4553, ET: 0) *** Oct 2 22:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2079) *** Oct 2 22:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2079, QN: 61/61, ET: 0) *** Oct 2 22:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2080) *** Oct 2 22:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2080) *** Oct 2 22:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2080, QN: 53/53, ET: 0) *** Oct 2 22:20:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2080, QN: 4494/4494, ET: 7) *** Oct 2 22:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2081) *** Oct 2 22:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2081, QN: 4834/4834, ET: 0) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (3 distinct, 8 total) == Oct 2 22:09:09 outbound00.cs.umd.edu python3[2114480]: ldapdb [x6] Oct 2 22:34:41 outbound00.cs.umd.edu krb5_child[2120594]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 2 22:35:10 outbound00.cs.umd.edu sshd-session[2120647]: error: Protocol major versions differ: 2 vs. 1 == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 2 22:13:06 outbound01.cs.umd.edu python3[186436]: ldapdb [x6] == portal (1 distinct, 72 total) == Oct 2 22:05:06 portal setroubleshoot[326544]: 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 [x72] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Oct 2 22:20:46 sentry-docker00.cs.umd.edu systemd-udevd[175180]: link_config: could not get ethtool features for veth92990b6 Oct 2 22:20:46 sentry-docker00.cs.umd.edu systemd-udevd[175180]: Could not set offload features of veth92990b6: No such device Oct 2 22:20:46 sentry-docker00.cs.umd.edu systemd-udevd[175214]: Could not generate persistent MAC address for veth82d884a: No such file or directory Oct 2 22:20:46 sentry-docker00.cs.umd.edu systemd-udevd[175215]: Could not generate persistent MAC address for veth34a40d4: No such file or directory Oct 2 22:20:46 sentry-docker00.cs.umd.edu systemd-udevd[175218]: Could not generate persistent MAC address for vethbbfc339: No such file or directory Oct 2 22:20:46 sentry-docker00.cs.umd.edu systemd-udevd[175219]: Could not generate persistent MAC address for veth8c7d49f: No such file or directory Oct 2 22:20:46 sentry-docker00.cs.umd.edu systemd-udevd[175219]: Could not generate persistent MAC address for vethd0a2edd: No such file or directory Oct 2 22:20:46 sentry-docker00.cs.umd.edu systemd-udevd[175241]: Could not generate persistent MAC address for veth8adbc0a: No such file or directory Oct 2 22:20:46 sentry-docker00.cs.umd.edu systemd-udevd[175232]: Could not generate persistent MAC address for veth1d8b88c: No such file or directory Oct 2 22:20:46 sentry-docker00.cs.umd.edu systemd-udevd[175235]: Could not generate persistent MAC address for veth5bd8ef3: No such file or directory Oct 2 22:20:46 sentry-docker00.cs.umd.edu systemd-udevd[175288]: Could not generate persistent MAC address for veth896d53c: No such file or directory Oct 2 22:20:46 sentry-docker00.cs.umd.edu systemd-udevd[175282]: Could not generate persistent MAC address for veth574bbcc: No such file or directory Oct 2 22:40:54 sentry-docker00.cs.umd.edu systemd-udevd[184548]: link_config: could not set ethtool features for vethbbfc339 Oct 2 22:40:54 sentry-docker00.cs.umd.edu systemd-udevd[184548]: Could not set offload features of vethbbfc339: Operation not permitted Oct 2 22:40:54 sentry-docker00.cs.umd.edu systemd-udevd[184585]: Could not generate persistent MAC address for vethc848d7b: No such file or directory Oct 2 22:40:54 sentry-docker00.cs.umd.edu systemd-udevd[184586]: Could not generate persistent MAC address for veth9a0a032: No such file or directory Oct 2 22:40:54 sentry-docker00.cs.umd.edu systemd-udevd[184589]: Could not generate persistent MAC address for veth83857a0: No such file or directory Oct 2 22:40:54 sentry-docker00.cs.umd.edu systemd-udevd[184593]: Could not generate persistent MAC address for vethce8db62: No such file or directory Oct 2 22:40:54 sentry-docker00.cs.umd.edu systemd-udevd[184586]: Could not generate persistent MAC address for veth206b15e: No such file or directory Oct 2 22:40:54 sentry-docker00.cs.umd.edu systemd-udevd[184597]: Could not generate persistent MAC address for veth0ab2057: No such file or directory Oct 2 22:40:54 sentry-docker00.cs.umd.edu systemd-udevd[184617]: Could not generate persistent MAC address for veth7b6e341: No such file or directory Oct 2 22:40:54 sentry-docker00.cs.umd.edu systemd-udevd[184618]: Could not generate persistent MAC address for veth847b1d0: No such file or directory Oct 2 22:40:54 sentry-docker00.cs.umd.edu systemd-udevd[184639]: Could not generate persistent MAC address for veth3184be8: No such file or directory Oct 2 22:40:54 sentry-docker00.cs.umd.edu systemd-udevd[184633]: Could not generate persistent MAC address for vethff3f6e8: No such file or directory Oct 2 23:01:03 sentry-docker00.cs.umd.edu systemd-udevd[193942]: Could not generate persistent MAC address for veth5233ac1: No such file or directory Oct 2 23:01:03 sentry-docker00.cs.umd.edu systemd-udevd[193943]: Could not generate persistent MAC address for vethe1fcec9: No such file or directory Oct 2 23:01:03 sentry-docker00.cs.umd.edu systemd-udevd[193946]: Could not generate persistent MAC address for veth61c1449: No such file or directory Oct 2 23:01:03 sentry-docker00.cs.umd.edu systemd-udevd[193947]: Could not generate persistent MAC address for veth6a1dd84: No such file or directory Oct 2 23:01:03 sentry-docker00.cs.umd.edu systemd-udevd[193970]: Could not generate persistent MAC address for veth9d08852: No such file or directory Oct 2 23:01:03 sentry-docker00.cs.umd.edu systemd-udevd[193971]: Could not generate persistent MAC address for vethf4809cb: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 2 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 2 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 2 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 2 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 2 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 2 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 2 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 14 total) == Oct 2 22:20:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] Oct 2 22:25:59 submit26-b9-f1 setroubleshoot[572707]: 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 2 22:25:59 submit26-b9-f1 setroubleshoot[572707]: 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 2 22:25:59 submit26-b9-f1 setroubleshoot[572707]: 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 2 22:26:00 submit26-b9-f1 setroubleshoot[572707]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.AEZ0S4/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Oct 2 22:26:00 submit26-b9-f1 setroubleshoot[572707]: 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 2 22:26:00 submit26-b9-f1 setroubleshoot[572707]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.AEZ0S4. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 2 22:26:00 submit26-b9-f1 setroubleshoot[572707]: 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 2 22:26:00 submit26-b9-f1 setroubleshoot[572707]: 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 2 22:26:00 submit26-b9-f1 setroubleshoot[572707]: 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 (16 distinct, 21 total) == Oct 2 22:06:54 submit26-b9-f2 setroubleshoot[3888961]: 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 2 22:06:54 submit26-b9-f2 setroubleshoot[3888961]: 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 2 22:06:54 submit26-b9-f2 setroubleshoot[3888961]: 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 2 22:06:54 submit26-b9-f2 setroubleshoot[3888961]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.eiQwdl/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Oct 2 22:06:54 submit26-b9-f2 setroubleshoot[3888961]: 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 2 22:06:54 submit26-b9-f2 setroubleshoot[3888961]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.eiQwdl. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 2 22:06:54 submit26-b9-f2 setroubleshoot[3888961]: 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 2 22:06:54 submit26-b9-f2 setroubleshoot[3888961]: 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 2 22:06:54 submit26-b9-f2 setroubleshoot[3888961]: 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 2 22:17:33 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Oct 2 22:32:43 submit26-b9-f2 systemd-coredump[3894383]: Process 3894380 (release13) of user 1001 dumped core.#012#012Stack trace of thread 3894380:#012#0 0x00007f2dc236f37c __strlen_evex (libc.so.6 + 0x16f37c)#012#1 0x00000000004013d8 compact (release13 + 0x13d8)#012#2 0x00000000004011f1 main (release13 + 0x11f1)#012#3 0x00007f2dc222a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f2dc222a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release13 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 2 22:32:43 submit26-b9-f2 systemd-coredump[3894393]: Process 3894390 (release15) of user 1001 dumped core.#012#012Stack trace of thread 3894390:#012#0 0x00007f2ab776f37c __strlen_evex (libc.so.6 + 0x16f37c)#012#1 0x00000000004013e5 compact (release15 + 0x13e5)#012#2 0x00000000004011f1 main (release15 + 0x11f1)#012#3 0x00007f2ab762a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f2ab762a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release15 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 2 22:44:51 submit26-b9-f2 systemd-coredump[3899445]: Process 3899442 (release13) of user 1001 dumped core.#012#012Stack trace of thread 3899442:#012#0 0x00007fb5f056f37c __strlen_evex (libc.so.6 + 0x16f37c)#012#1 0x00000000004013b0 compact (release13 + 0x13b0)#012#2 0x00000000004011f1 main (release13 + 0x11f1)#012#3 0x00007fb5f042a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fb5f042a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release13 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 2 22:44:51 submit26-b9-f2 systemd-coredump[3899455]: Process 3899452 (release15) of user 1001 dumped core.#012#012Stack trace of thread 3899452:#012#0 0x00007fb68976f37c __strlen_evex (libc.so.6 + 0x16f37c)#012#1 0x00000000004013bd compact (release15 + 0x13bd)#012#2 0x00000000004011f1 main (release15 + 0x11f1)#012#3 0x00007fb68962a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fb68962a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release15 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 2 22:53:15 submit26-b9-f2 systemd-coredump[3899991]: Process 3899988 (release13) of user 1001 dumped core.#012#012Stack trace of thread 3899988:#012#0 0x00007fd40176f37c __strlen_evex (libc.so.6 + 0x16f37c)#012#1 0x00000000004013d8 compact (release13 + 0x13d8)#012#2 0x00000000004011f1 main (release13 + 0x11f1)#012#3 0x00007fd40162a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fd40162a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release13 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 2 22:53:15 submit26-b9-f2 systemd-coredump[3900003]: Process 3900000 (release15) of user 1001 dumped core.#012#012Stack trace of thread 3900000:#012#0 0x00007f438f16f37c __strlen_evex (libc.so.6 + 0x16f37c)#012#1 0x00000000004013e5 compact (release15 + 0x13e5)#012#2 0x00000000004011f1 main (release15 + 0x11f1)#012#3 0x00007f438f02a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f438f02a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release15 + 0x1085)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f3 (1 distinct, 3 total) == Oct 2 22:14:26 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f4 (3 distinct, 5 total) == Oct 2 22:20:09 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Oct 2 22:24:38 submit26-b9-f4 systemd-coredump[3491414]: Process 3491411 (release13) of user 1001 dumped core.#012#012Stack trace of thread 3491411:#012#0 0x00007f963a4ae0ea __strlen_sse2 (libc.so.6 + 0xae0ea)#012#1 0x00000000004013b0 compact (release13 + 0x13b0)#012#2 0x00000000004011f1 main (release13 + 0x11f1)#012#3 0x00007f963a42a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f963a42a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release13 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 2 22:24:38 submit26-b9-f4 systemd-coredump[3491423]: Process 3491421 (release15) of user 1001 dumped core.#012#012Stack trace of thread 3491421:#012#0 0x00007f95740ae0ea __strlen_sse2 (libc.so.6 + 0xae0ea)#012#1 0x00000000004013bd compact (release15 + 0x13bd)#012#2 0x00000000004011f1 main (release15 + 0x11f1)#012#3 0x00007f957402a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f957402a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release15 + 0x1085)#012ELF object binary architecture: AMD x86-64 == vacuum.cs.umd.edu (4 distinct, 4 total) == Oct 2 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[14881]: Process 10496 (driver) of user 33 killed by SIGSEGV - dumping core Oct 2 22:11:59 vacuum.cs.umd.edu abrt-server[14883]: Package 'amanda-backup_server' isn't signed with proper key Oct 2 22:11:59 vacuum.cs.umd.edu abrt-server[14883]: 'post-create' on '/var/spool/abrt/ccpp-2026-10-02-22:11:58-10496' exited with 1 Oct 2 22:11:59 vacuum.cs.umd.edu abrt-server[14883]: Deleting problem directory '/var/spool/abrt/ccpp-2026-10-02-22:11:58-10496'
participants (1)
-
cron/syslog01.cs.umd.edu