Hey guys,
Our monitoring system caught kamailio coring. I did a dmesg and gave me this:
[Tue Sep 1 09:12:34 2020] kamailio[1375]: segfault at 1 ip 0000000000000001 sp 00007fff4203f098 error 14 in kamailio[563969b5a000+4a4000]
[Tue Sep 1 09:12:34 2020] Code: Bad RIP value.
[Tue Sep 1 09:12:34 2020] kamailio[1363]: segfault at 0 ip 0000000000000000 sp 00007fff4203f368 error 14 in kamailio[563969b5a000+4a4000]
[Tue Sep 1 09:12:34 2020] Code: Bad RIP value.
[Tue Sep 1 09:12:34 2020] kamailio[1377]: segfault at 1 ip 0000000000000001 sp 00007fff4203e308 error 14 in kamailio[563969b5a000+4a4000]
[Tue Sep 1 09:12:34 2020] Code: Bad RIP value.
After doing gdb bt, didn't tell me much except it can't access some parts of the memory:
warning: Unexpected size of section `.reg-xstate/1624' in core file.
Cannot access memory at address 0x7fb23433e148
Cannot access memory at address 0x7fb23433e140
Failed to read a valid object file image from memory.
Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'.
Program terminated with signal SIGSEGV, Segmentation fault.
warning: Unexpected size of section `.reg-xstate/1624' in core file.
#0 0x0000000000000001 in ?? ()
(gdb) bt full
#0 0x0000000000000001 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7fff4203e1f8
(gdb) quit
Any idea on how to troubleshoot this further?
Thanks.
--
Andy Chen
Sr. Telephony Lead Engineer