Command: /usr/local/sbin/syslog-digest.py Time : 0.0516s Status : exited 0 Output : Syslog digest — 2026-09-23 19:05 EDT Processed 2,431 lines, filtered 2,028 (83%). 403 unknown (197 distinct) from 19 host(s). == b0b02.cs.umd.edu (4 distinct, 4 total) == Sep 23 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-23T22:10:59.429910465Z" level=info msg="PurgeUploads starting: olderThan=2026-09-16 22:10:59.429792684 +0000 UTC m=+4408620.189721006, actuallyDelete=true" Sep 23 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-23T22:10:59.430667062Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Sep 23 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-23T22:10:59.430697183Z" 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 Sep 23 18:57:23 b0b02.cs.umd.edu rustdesk[326951]: cannot open display: == bale (5 distinct, 87 total) == Sep 23 18:06:06 bale setroubleshoot[2194807]: failed to retrieve rpm info for /dev/nvme0 [x37] Sep 23 18:06:07 bale setroubleshoot[2194807]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x13] Sep 23 18:06:09 bale setroubleshoot[2194807]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13] Sep 23 18:06:12 bale setroubleshoot[2194807]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x11] Sep 23 18:06:24 bale setroubleshoot[2195422]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x13] == biggulp.cs.umd.edu (2 distinct, 2 total) == Sep 23 18:53:16 biggulp.cs.umd.edu krb5_child[3721286]: Preauthentication failed Sep 23 18:53:16 biggulp.cs.umd.edu sshd-session[3721282]: error: PAM: Authentication failure for leoliu from 128.8.126.63 == galax (1 distinct, 6 total) == Sep 23 18:10:03 galax systemd[1]: sysstat-collect.service: Condition check process exited, code=dumped, status=11/SEGV [x6] == idm00 (1 distinct, 1 total) == Sep 23 18:54:05 idm00 named[4166701]: client @0x7f11a0057bb8 10.73.240.42#59031: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 23 18:39:31 idmp0 named[1598691]: client @0x7f2d3802f8f8 10.73.240.43#49360: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Sep 23 18:43:00 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 4 total) == Sep 23 18:17:59 munin sudo[2489400]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 23 18:17:59 munin sudo[2489400]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == newhonors2 (1 distinct, 24 total) == Sep 23 18:13:02 newhonors2 dhcpcd[3052514]: dhcpcd is not running [x24] == ntop00 (101 distinct, 141 total) == Sep 23 18:05:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 134) *** Sep 23 18:05:19 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 134, QN: 11461/11461, ET: 18) *** Sep 23 18:05:19 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 134, QN: 70/70, ET: 18) *** Sep 23 18:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 135) *** Sep 23 18:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 135, QN: 12238/12238, ET: 0) *** Sep 23 18:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 135) *** Sep 23 18:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 135, QN: 58/58, ET: 0) *** Sep 23 18:08:02 ntop00 setroubleshoot[58647]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 5b65c96c-a9fa-4175-8126-0641b1ec385c [x11] Sep 23 18:08:02 ntop00 setroubleshoot[58647]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 0d1f7214-3aae-48d5-8fed-48565bd90d17 [x11] Sep 23 18:08:02 ntop00 setroubleshoot[58647]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11] Sep 23 18:08:02 ntop00 setroubleshoot[58647]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 4a9c8c49-4f0d-4ad5-b926-84fe3642d3ee [x11] Sep 23 18:10:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 136) *** Sep 23 18:10:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 136) *** Sep 23 18:10:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 136, QN: 51/51, ET: 0) *** Sep 23 18:10:18 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 136, QN: 13065/13065, ET: 17) *** Sep 23 18:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 137) *** Sep 23 18:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 137, QN: 11483/11483, ET: 0) *** Sep 23 18:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 137) *** Sep 23 18:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 137, QN: 63/63, ET: 0) *** Sep 23 18:15:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 138) *** Sep 23 18:15:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 138) *** Sep 23 18:15:13 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 138, QN: 9249/9249, ET: 12) *** Sep 23 18:15:13 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 138, QN: 65/65, ET: 12) *** Sep 23 18:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 139) *** Sep 23 18:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 139, QN: 9966/9966, ET: 0) *** Sep 23 18:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 139) *** Sep 23 18:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 139, QN: 47/47, ET: 0) *** Sep 23 18:20:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 140) *** Sep 23 18:20:02 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 140) *** Sep 23 18:20:17 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 140, QN: 11997/11997, ET: 16) *** ... 71 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 23 18:09:09 outbound00.cs.umd.edu python3[3166031]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 23 18:13:06 outbound01.cs.umd.edu python3[1232150]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 23 18:09:27 sentry-docker00.cs.umd.edu systemd-udevd[2336058]: link_config: could not get ethtool features for vethb0f5704 Sep 23 18:09:27 sentry-docker00.cs.umd.edu systemd-udevd[2336058]: Could not set offload features of vethb0f5704: No such device Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336074]: Could not generate persistent MAC address for veth65c37d4: No such file or directory Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336075]: Could not generate persistent MAC address for vethd2d7db4: No such file or directory Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336093]: Could not generate persistent MAC address for veth205b1db: No such file or directory Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336075]: Could not generate persistent MAC address for vethba5979f: No such file or directory Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336102]: Could not generate persistent MAC address for veth4244178: No such file or directory Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336103]: Could not generate persistent MAC address for veth3b71b75: No such file or directory Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336112]: Could not generate persistent MAC address for veth6def173: No such file or directory Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336121]: Could not generate persistent MAC address for vethf0bdeb6: No such file or directory Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336137]: Could not generate persistent MAC address for veth98d9e41: No such file or directory Sep 23 18:09:28 sentry-docker00.cs.umd.edu systemd-udevd[2336139]: Could not generate persistent MAC address for veth77f5f3a: No such file or directory Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345575]: link_config: could not get ethtool features for veth98d9e41 Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345575]: Could not set offload features of veth98d9e41: No such device Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345612]: Could not generate persistent MAC address for veth78a9c85: No such file or directory Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345613]: Could not generate persistent MAC address for veth241aad2: No such file or directory Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345616]: Could not generate persistent MAC address for veth04096d6: No such file or directory Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345617]: Could not generate persistent MAC address for veth83a81bb: No such file or directory Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345630]: Could not generate persistent MAC address for veth4b5ca59: No such file or directory Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345613]: Could not generate persistent MAC address for veth30efd7d: No such file or directory Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345625]: Could not generate persistent MAC address for vetha150ae3: No such file or directory Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345628]: Could not generate persistent MAC address for veth66f0e76: No such file or directory Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345671]: Could not generate persistent MAC address for vethfc7b455: No such file or directory Sep 23 18:29:36 sentry-docker00.cs.umd.edu systemd-udevd[2345675]: Could not generate persistent MAC address for veth734ebe2: No such file or directory Sep 23 18:49:44 sentry-docker00.cs.umd.edu systemd-udevd[2354934]: link_config: could not get ethtool features for veth78a9c85 Sep 23 18:49:44 sentry-docker00.cs.umd.edu systemd-udevd[2354934]: Could not set offload features of veth78a9c85: No such device Sep 23 18:49:44 sentry-docker00.cs.umd.edu systemd-udevd[2354963]: Could not generate persistent MAC address for veth329cc0c: No such file or directory Sep 23 18:49:44 sentry-docker00.cs.umd.edu systemd-udevd[2354964]: Could not generate persistent MAC address for veth109f718: No such file or directory Sep 23 18:49:44 sentry-docker00.cs.umd.edu systemd-udevd[2354971]: Could not generate persistent MAC address for vethe95fb56: No such file or directory Sep 23 18:49:44 sentry-docker00.cs.umd.edu systemd-udevd[2354968]: Could not generate persistent MAC address for vethc43a0e6: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 23 18:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 23 18:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 23 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 23 18:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 23 18:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 23 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 23 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (12 distinct, 14 total) == Sep 23 18:20:36 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Sep 23 18:25:27 submit26-b9-f1 systemd-coredump[3196000]: Process 3195997 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3195997:#012#0 0x00007f6c9e28d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f6c9e23fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f6c9e229873 abort (libc.so.6 + 0x29873)#012#3 0x00007f6c9e22a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f6c9e31d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f6c9e31e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040176d main (grades + 0x176d)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Sep 23 18:25:27 submit26-b9-f1 systemd-coredump[3196011]: Process 3196008 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3196008:#012#0 0x00007eff8228d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007eff8223fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007eff82229873 abort (libc.so.6 + 0x29873)#012#3 0x00007eff8222a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007eff8231d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007eff8231e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040176d main (grades + 0x176d)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Sep 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 Sep 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 Sep 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 Sep 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.9rOHc7/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 Sep 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.9rOHc7. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 Sep 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 Sep 23 18:25:55 submit26-b9-f1 setroubleshoot[3196191]: 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 (11 distinct, 16 total) == Sep 23 18:06:37 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: 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 [x2] Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: 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 [x2] Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: 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 Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.0wf1m9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: 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 Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.0wf1m9. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: 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 [x2] Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: 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 Sep 23 18:06:50 submit26-b9-f2 setroubleshoot[2285035]: 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 [x2] Sep 23 18:06:51 submit26-b9-f2 setroubleshoot[2285035]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xY1dgk. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 == submit26-b9-f3 (3 distinct, 5 total) == Sep 23 18:22:24 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Sep 23 18:45:30 submit26-b9-f3 systemd-coredump[2837975]: Process 2837972 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2837972:#012#0 0x00007f46f128d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f46f123fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f46f1229873 abort (libc.so.6 + 0x29873)#012#3 0x00007f46f122a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f46f131d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f46f131e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040176d main (grades + 0x176d)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Sep 23 18:45:30 submit26-b9-f3 systemd-coredump[2837985]: Process 2837982 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2837982:#012#0 0x00007fcdbe28d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fcdbe23fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fcdbe229873 abort (libc.so.6 + 0x29873)#012#3 0x00007fcdbe22a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fcdbe31d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fcdbe31e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x000000000040176d main (grades + 0x176d)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f4 (1 distinct, 4 total) == Sep 23 18:15:04 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == vpn00a.cs.umd.edu (6 distinct, 6 total) == Sep 23 18:14:03 vpn00a.cs.umd.edu setroubleshoot[1294846]: failed to retrieve rpm info for path '/var/lib/ipa-client/sysrestore/sysrestore.index': Sep 23 18:14:04 vpn00a.cs.umd.edu setroubleshoot[1294846]: SELinux is preventing /usr/bin/python3.9 from search access on the directory /var/lib/ipa-client/sysrestore/sysrestore.index. For complete SELinux messages run: sealert -l aaf84404-597f-4dfb-ac0f-2e8cbbdc14b4 Sep 23 18:14:04 vpn00a.cs.umd.edu setroubleshoot[1294846]: SELinux is preventing /usr/bin/python3.9 from read access on the file /var/lib/ipa-client/sysrestore/sysrestore.index. For complete SELinux messages run: sealert -l 666e06a7-327b-48d7-bb9f-4475f9036316 Sep 23 18:14:04 vpn00a.cs.umd.edu setroubleshoot[1294846]: SELinux is preventing /usr/bin/python3.9 from open access on the file /var/lib/ipa-client/sysrestore/sysrestore.index. For complete SELinux messages run: sealert -l 91b1a9db-b8c3-4017-8d03-a86ace59bbe4 Sep 23 18:14:04 vpn00a.cs.umd.edu setroubleshoot[1294846]: SELinux is preventing /usr/bin/python3.9 from getattr access on the file /var/lib/ipa-client/sysrestore/sysrestore.index. For complete SELinux messages run: sealert -l c81675b5-39be-478f-842c-9d78125f7f88 Sep 23 18:14:04 vpn00a.cs.umd.edu setroubleshoot[1294846]: SELinux is preventing /usr/bin/python3.9 from ioctl access on the file /var/lib/ipa-client/sysrestore/sysrestore.index. For complete SELinux messages run: sealert -l 8e209ef6-d276-493a-bbe4-409df332225e