I build kamailio from latest 4.4 git source and got crash at start:
(gdb) where #0 0x0000000000449af8 in add_interfaces ( if_name=0x7f0e770106e8 "192.98.102.10", family=0, port=13880, proto=1978, ai_l=0x1277600) at socket_info.c:1210 #1 0x000000000044ad77 in fix_socket_list (list=0x5, type_flags=0xffffffff) at socket_info.c:1406 #2 0x000000000044de70 in fix_all_socket_lists () at socket_info.c:1807 #3 0x000000000041b535 in main (argc=0, argv=0x7fff8cfaf1e8) at main.c:2390
-- Juha
Juha Heinanen writes:
I build kamailio from latest 4.4 git source and got crash at start:
(gdb) where #0 0x0000000000449af8 in add_interfaces ( if_name=0x7f0e770106e8 "192.98.102.10", family=0, port=13880, proto=1978, ai_l=0x1277600) at socket_info.c:1210 #1 0x000000000044ad77 in fix_socket_list (list=0x5, type_flags=0xffffffff) at socket_info.c:1406 #2 0x000000000044de70 in fix_all_socket_lists () at socket_info.c:1807 #3 0x000000000041b535 in main (argc=0, argv=0x7fff8cfaf1e8) at main.c:2390
Perhaps recent commit e6dd2c172be3712e8c468cbe7e55ba94d81a7b62 is to blame of the crash.
I built 4.4 on Debian Jessie.
-- Juha
Have you reverted only e6dd2c172be3712e8c468cbe7e55ba94d81a7b62, or also d7fca53e8c5409849ec044098a143e7254129c00.
From the core file, can you give the output with gdb for:
p ifa p *ifa p *ifa->ifa_addr
Also, are you using listen with interface id (e.g., eth0)? Or is with ip only, or no listen parameter?
Cheers, Daniel
On 06/04/16 18:14, Juha Heinanen wrote:
Juha Heinanen writes:
Perhaps recent commit e6dd2c172be3712e8c468cbe7e55ba94d81a7b62 is to blame of the crash.
Yes, I reverted the commit in my local source and the crash is gone.
-- Juha
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Daniel-Constantin Mierla writes:
Have you reverted only e6dd2c172be3712e8c468cbe7e55ba94d81a7b62, or also d7fca53e8c5409849ec044098a143e7254129c00.
I'm not quite sure. I just replaced socket_info.c with the one that is enclosed.
From the core file, can you give the output with gdb for:
p ifa p *ifa p *ifa->ifa_addr
(gdb) p ifa $1 = (struct ifaddrs *) 0x12778d8 (gdb) p *ifa $2 = {ifa_next = 0x1277990, ifa_name = 0x127797c "ppp0", ifa_flags = 69841, ifa_addr = 0x0, ifa_netmask = 0x0, ifa_ifu = {ifu_broadaddr = 0x0, ifu_dstaddr = 0x0}, ifa_data = 0x1278064} (gdb) p *ifa->ifa_addr Cannot access memory at address 0x0
Also, are you using listen with interface id (e.g., eth0)? Or is with ip only, or no listen parameter?
listen=192.98.102.10:5060 listen=tcp:192.98.102.10:8000 listen=udp:127.0.0.1:5070 listen=tcp:127.0.0.1:5070 listen=udp:127.0.0.1:5070 listen=tcp:127.0.0.1:5070 listen=tcp:127.0.0.1:6060
-- Juha
Thanks! Can you try with the patch 1545b8de396e8e5d0ef24c9102beff18b3cf36e5?
Also, check that all listen ip addresses are actually used by kamailio (they should be printed at startup).
Cheers, Daniel
On 06/04/16 18:49, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Have you reverted only e6dd2c172be3712e8c468cbe7e55ba94d81a7b62, or also d7fca53e8c5409849ec044098a143e7254129c00.
I'm not quite sure. I just replaced socket_info.c with the one that is enclosed.
From the core file, can you give the output with gdb for:
p ifa p *ifa p *ifa->ifa_addr
(gdb) p ifa $1 = (struct ifaddrs *) 0x12778d8 (gdb) p *ifa $2 = {ifa_next = 0x1277990, ifa_name = 0x127797c "ppp0", ifa_flags = 69841, ifa_addr = 0x0, ifa_netmask = 0x0, ifa_ifu = {ifu_broadaddr = 0x0, ifu_dstaddr = 0x0}, ifa_data = 0x1278064} (gdb) p *ifa->ifa_addr Cannot access memory at address 0x0
Also, are you using listen with interface id (e.g., eth0)? Or is with ip only, or no listen parameter?
listen=192.98.102.10:5060 listen=tcp:192.98.102.10:8000 listen=udp:127.0.0.1:5070 listen=tcp:127.0.0.1:5070 listen=udp:127.0.0.1:5070 listen=tcp:127.0.0.1:5070 listen=tcp:127.0.0.1:6060
-- Juha
Daniel-Constantin Mierla writes:
Thanks! Can you try with the patch 1545b8de396e8e5d0ef24c9102beff18b3cf36e5?
I tried and there was no crash.
Also, check that all listen ip addresses are actually used by kamailio (they should be printed at startup).
They were all listed.
-- Juha
On Wednesday, April 06, 2016 09:22:21 PM Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Thanks! Can you try with the patch 1545b8de396e8e5d0ef24c9102beff18b3cf36e5?
I tried and there was no crash.
Also, check that all listen ip addresses are actually used by kamailio (they should be printed at startup).
They were all listed.
-- Juha
I haven't had time to test yet, but I believe this is https://github.com/kamailio/kamailio/issues/560
On 07/04/16 02:08, Anthony Messina wrote:
On Wednesday, April 06, 2016 09:22:21 PM Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Thanks! Can you try with the patch 1545b8de396e8e5d0ef24c9102beff18b3cf36e5?
I tried and there was no crash.
Also, check that all listen ip addresses are actually used by kamailio (they should be printed at startup).
They were all listed.
-- Juha
I haven't had time to test yet, but I believe this is https://github.com/kamailio/kamailio/issues/560
To close the thread on this mailing list - the issue 560 is fixed as well by those patches.
Cheers, Daniel
-
Anthony Messina -
Daniel-Constantin Mierla -
Juha Heinanen