[SR-Users] Random Proxy Crash, Restarted OK Anything Here For Concern?

[Daniel-Constantin Mierla]

Hello,

I would suggest to update to latest 4.1.x version, the 4.1.0 is the
first in the 4.1 series and many issues have been fixed in later 4.1.x
version. There should be no database structure update or config changes,
just deploy a newer 4.1.x version and restart.

The double free crashes can be avoided with config parameter
mem_safety=1, but it can be side effect of another bug that may hit
anyhow at some point, however, you may also get around it in a nicer way.

Cheers,
Daniel

On 07.07.17 18:34, JR Richardson wrote:
> Hi All,
>
> I have a basic proxy up and running for over 6 months without issue,
> had a random crash, not sure why. Restarted kamailio process and it's
> working as expected. Any clue is the log to indicate what might have
> happened?
>
> ----snip----
> Jul  5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13416]: :
> <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already
> freed pointer (0x7fa1e1ebd658), called from <core>: mem/shm_mem.c:
> sh_realloc(88), first free <core>: mem/shm_mem.c: sh_realloc(88) -
> aborting
> Jul  5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]:
> ALERT: <core> [main.c:775]: handle_sigs(): child process 13416 exited
> by a signal 6
> Jul  5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]:
> ALERT: <core> [main.c:778]: handle_sigs(): core was not generated
> Jul  5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]:
> INFO: <core> [main.c:790]: handle_sigs(): INFO: terminating due to
> SIGCHLD
> Jul  5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13423]:
> INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
> Jul  5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13420]:
> INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
> Jul  5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13424]:
> INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
> Jul  5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13419]:
> INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
> Jul  5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13421]:
> INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
> Jul  5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13422]:
> INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
> Jul  5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13418]:
> INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
> Jul  5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13417]:
> INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
> Jul  5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]:
> ERROR: ctl [ctl.c:379]: mod_destroy(): ERROR: ctl: could not delete
> unix socket /tmp/kamailio_ctl: Operation not permitted (1)
> ----snip----
>
> RTPProxy also running on the server was not affected.
>
> root at sip-router3-ve206:/var/log# kamailio -V
> version: kamailio 4.1.0 (x86_64/linux) 350d2e
> flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
> DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
> DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
> USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
> MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
> id: 350d2e
> compiled on 16:41:38 Dec 17 2013 with gcc 4.4.5
>
> Yes, I know it's an older version but I prefer not to upgrade unless
> absolutely necessary. I'm sure this was a random event, not too
> concerned but since it is a production server, I'm obligated to
> investigate.
>
> Thanks.
>
> JR

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com