8 Sep
2015
8 Sep
'15
11:44 p.m.
Thanks Daniel for pointing out, so if I upgrade my Kamailio it should all
go away , right. Will do a version upgrade and check similar calls.
I've seen very similar crashes EOF on 11, EOF of 16 etc etc in few other
situations as well, while at once such occasion it was an invalid kamctl
command and it crashed kamailio(Another thread maybe)
If Kamailio crashing before it can even get some route started then we
can't perform sanity checks and hence even if I've DNS SRV, LinuxHA, or
anything the caller might keep trying call over and again and keep crashing
the whole layer :)
On Tue, Sep 8, 2015 at 3:46 PM, Daniel-Constantin Mierla <miconda(a)gmail.com>
wrote:
Hello,
looks like there were updates to dialog modules in 4.1 after 4.1.4. The
code lines do not match the back trace.
You should upgrade to latest version in 4.1 branch -- there is no change
that you have to do in kamailio.cfg or database.
Meanwhile, we can see the relevant pieces of code from your specific
version with following commands in gdb:
frame 0
list
frame 4
list
Cheers,
Daniel
On 08/09/15 21:12, SamyGo wrote:
Hi Daniel,
Thanks a ton for replying, please see the attached full trace.
Please note the Public IPs have been masked.
Best Regards,
Sammy
On Tue, Sep 8, 2015 at 3:01 PM, Daniel-Constantin Mierla <
<miconda@gmail.com>miconda@gmail.com> wrote:
Hello,
can you give the output of 'bt full' in gdb to see where it actually
crashed?
Cheers,
Daniel
On 08/09/15 20:20, SamyGo wrote:
Hi,
I'm randomly getting crash in my Kamailio with an error in log files like
this:
<core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 19
ALERT: <core> [main.c:775]: handle_sigs(): child process 6853 exited by a
signal 11
ALERT: <core> [main.c:778]: handle_sigs(): core was generated
INFO: <core> [main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD
*Version of Kamailio is: *
[root@kamailio /]#kamailio -V
version: kamailio 4.1.4 (x86_64/linux) 39adca
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: 39adca
compiled on 03:48:50 Aug 1 2014 with gcc 4.4.7
And gdb bt output is attached in text file.
One thing out that is common in all the previous core files is this:
#12 0x00000000004a54ab in receive_msg (
buf=0x924600 "INVITE <http://sip:+17036833500@14.131.165.9:5073>
sip:+17036833500@14.131.165.9:5073 SIP/2.0\r\nVia: SIP/2.0/UDP
14.55.2.43:5060;branch=z9hG4bK0eB8f68591a19b9b8f0\r\nFrom: \"Anonymous\"
<sip:Anonymous@Anonymous.invalid>;tag=gK0e13e132\r\nTo: <sip:+170"...,
len=1018, rcv_info=0x7fff3dbee970) at receive.c:212
#13 0x000000000053c9a8 in udp_rcv_loop () at udp_server.c:536
Does this mean that Kamailio can't understand the From Domain:
Anonymous.invalid and hence crashes ?
Thanks,
Sammy
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat