Just updated RL 9.5 tonight and, on a VM I have running ansible playbooks on, I have had 4 Segmentation Violations leading to coredumps in the first hour. These are origiating in libpython3.9 . I have also had one happen in ssh, which may be related.
[root@table coredump]# cat /etc/redhat-release
Rocky Linux release 9.5 (Blue Onyx)
[root@table coredump]# coredumpctl list
TIME PID UID GID SIG COREFILE EXE SIZE
Sun 2025-03-23 23:05:48 CDT 8010 1000 1000 SIGSEGV present /usr/bin/ssh 117.6K
Sun 2025-03-23 23:05:50 CDT 7858 1000 1000 SIGSEGV present /usr/bin/python3.9 6.7M
Sun 2025-03-23 23:05:57 CDT 8074 1000 1000 SIGSEGV present /usr/bin/python3.9 7.0M
Sun 2025-03-23 23:11:49 CDT 8529 1000 1000 SIGSEGV present /usr/bin/python3.9 6.7M
Sun 2025-03-23 23:11:50 CDT 8438 1000 1000 SIGSEGV present /usr/bin/python3.9 6.7M
[root@table coredump]#
[root@table coredump]# dmesg|grep -i segfault
[ 5768.845009] ssh[8010]: segfault at 7f20a79cb360 ip 00007f20b79f6904 sp 00007ffcd507a7b0 error 4 in ld-linux-x86-64.so.2[7f20b79ef000+27000] likely on CPU 0 (core 0, socket 0)
[ 5770.368967] ansible-playboo[7858]: segfault at 7ff7ec7535e8 ip 00007ff7fff25380 sp 00007ffdf184c860 error 4 in libpython3.9.so.1.0[7ff7ffe5a000+20a000] likely on CPU 0 (core 0, socket 0)
[ 5777.547772] ansible-playboo[8074]: segfault at 7ff7ec7535e8 ip 00007ff7fff25380 sp 00007ffdf18494a0 error 4 in libpython3.9.so.1.0[7ff7ffe5a000+20a000] likely on CPU 0 (core 0, socket 0)
[ 6129.551501] ansible-playboo[8529]: segfault at 55e51823ab00 ip 00007f1940953773 sp 00007fffe9ee5450 error 4 in libpython3.9.so.1.0[7f194085a000+20a000] likely on CPU 0 (core 0, socket 0)
[ 6130.011111] ansible-playboo[8438]: segfault at 7f1900b91dc9 ip 00007f1940943824 sp 00007fffe9ee9450 error 4 in libpython3.9.so.1.0[7f194085a000+20a000] likely on CPU 0 (core 0, socket 0)
[root@table coredump]# ls -al
total 28060
drwxr-xr-x. 2 root root 4096 Mar 23 23:11 .
drwxr-xr-x. 7 root root 98 Mar 18 07:30 ..
-rw-r-----+ 1 root root 7113911 Mar 23 23:05 core.ansible-playboo.1000.e421fe782b56464fb646db384422ffc9.7858.1742789150000000.zst
-rw-r-----+ 1 root root 7378301 Mar 23 23:05 core.ansible-playboo.1000.e421fe782b56464fb646db384422ffc9.8074.1742789157000000.zst
-rw-r-----+ 1 root root 7030032 Mar 23 23:11 core.ansible-playboo.1000.e421fe782b56464fb646db384422ffc9.8438.1742789509000000.zst
-rw-r-----+ 1 root root 7057326 Mar 23 23:11 core.ansible-playboo.1000.e421fe782b56464fb646db384422ffc9.8529.1742789509000000.zst
-rw-r-----+ 1 root root 120516 Mar 23 23:05 core.ssh.1000.e421fe782b56464fb646db384422ffc9.8010.1742789148000000.zst
This system is heavily depended on for my network security (homebrew distributed IDS/IPS).
I am relying on the stock python install, here.
[root@table coredump]# ls -al /usr/bin/python3*
lrwxrwxrwx. 1 root root 9 Dec 12 11:18 /usr/bin/python3 -> python3.9
-rwxr-xr-x. 1 root root 15632 Dec 12 11:18 /usr/bin/python3.9
[root@table coredump]#
[root@table coredump]# rpm -qa|grep -i python3-libs-
python3-libs-3.9.21-1.el9_5.x86_64
[root@table coredump]# rpm -qa|grep -i ansible
ansible-core-2.14.17-1.el9.x86_64
ansible-7.7.0-1.el9.noarch
[root@table coredump]#
This issue appears to have settled down in the last 30 minutes (even with continuous usage).
Anyone else having any related issues? I am nowhere near setup for debugging these coredumps, here.