Re: [SR-Users] Core Dump during shutdown on SPARC64
Hi Daniel, I was able to prevent the bus error by reverting part of commit 1b366aa1c6c37e2320da10fb68f0370199333f5d as below: diff --git a/cfg/cfg_struct.c b/cfg/cfg_struct.c index 8bfe429..519c6a9 100644 --- a/cfg/cfg_struct.c +++ b/cfg/cfg_struct.c @@ -295,8 +295,7 @@ static void cfg_destory_groups(unsigned char *block) if (((CFG_VAR_TYPE([i]) == CFG_VAR_STRING) || (CFG_VAR_TYPE([i]) == CFG_VAR_STR)) && mapping[i].flag & cfg_var_shmized) { - - old_string = *(char **)(block + group->var_offset + mapping[i].offset); + memcpy(_string, block + group->var_offset + mapping[i].offset, sizeof(char *)); if (old_string) shm_free(old_string); } I can’t really see why there would be a bus error… thoughts? Thanks, Spencer On Jan 14, 2016, at 6:52 PM, Spencer Thomason> wrote: Hi Daniel, I haven’t yet but I will try to test shortly. Here is the value of the block variable: (gdb) p /s block $1 = (unsigned char *) 0x76e5ded4 “" Thanks, Spencer On Jan 13, 2016, at 11:07 PM, Daniel-Constantin Mierla > wrote: Hello, hmm, they are multiple of 8, so they should be aligned to 64bits. Or maybe the 'block' variable value is not aligned to 8bytes ... Have you done any sip traffic via this kamailio instance. Is all ok at runtime? Cheers, Daniel On 14/01/16 08:01, Spencer Thomason wrote: Hi Daniel, See below: (gdb) p group->var_offset $1 = 64 (gdb) p mapping[i].offset $2 = 56 Thanks! Spencer On Jan 13, 2016, at 10:18 PM, Daniel-Constantin Mierla > wrote: Hello, can you get the values for group->var_offset and mapping[i].offset in frame 0? Cheers, Daniel On 14/01/16 05:41, Spencer Thomason wrote: Hello, I’m trying to get Kamailio running on Solaris 11 SPARC64 and I’m receiving a bus error on shutdown. If needed, we can make SPARC hardware available for testing. Thanks, Spencer Core was generated by `/opt/kamailio/sbin/kamailio -f /opt/kamailio/etc/kamailio/kamailio.cfg -P /syst'. Program terminated with signal 10, Bus error. #0 0x0001003e73f0 in cfg_destory_groups (block=0x76e5ded4 "") at cfg/cfg_struct.c:299 299 old_string = *(char **)(block + group->var_offset + mapping[i].offset); (gdb) bt full #0 0x0001003e73f0 in cfg_destory_groups (block=0x76e5ded4 "") at cfg/cfg_struct.c:299 group = 0x100745e20 def = i = 14 group2 = mapping = 0x100745a78 old_string = #1 cfg_destroy () at cfg/cfg_struct.c:391 __FUNCTION__ = "cfg_destroy" #2 0x000100163fc4 in cleanup (show_status=show_status@entry=1) at main.c:540 memlog = __FUNCTION__ = "cleanup" #3 0x0001001650d4 in shutdown_children (show_status=show_status@entry=1, sig=15) at main.c:665 No locals. #4 0x000100165c0c in handle_sigs () at main.c:695 chld = chld_status = 0 memlog = __FUNCTION__ = "handle_sigs" #5 0x00010016e678 in main_loop () at main.c:1722 i = pid = si = si_desc = "udp receiver child=15 sock=104.222.31.55:9000\000\005\066\377\377\377\377v\345\322\370\000\000\000\000\000\020\000\063\377\377\377\377\177\377\360q\000\000\000\001\000B\277 \000\000\000\001\000^:P\000\000\000\001\000\002\356(\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375" nrprocs = woneinit = __FUNCTION__ = "main_loop" #6 0x00010042cafc in main (argc=, argv=) at main.c:2597 cfg_stream = c = r = tmp = 0x7d57 "" tmp_len = 0 port = 0 proto = 0 options = 0x100036918 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:" ret = -1 seed = 4139658536 rfd = debug_save = debug_flag = dont_fork_cnt = p = st = {st_dev = 2478196129807, st_ino = 405001306, st_mode = 16832, st_nlink = 2, st_uid = 0, st_gid = 0, st_rdev = 18446744073709551615, st_size = 117, st_atim = {tv_sec = 1452739293, tv_nsec = 444332080}, st_mtim = { tv_sec = 1452739411, tv_nsec = 727071262}, st_ctim = {tv_sec = 1452739411, tv_nsec = 727071262}, st_blksize = 8192, st_blocks = 16, st_fstype = "tmpfs\000\000\000\000\000\000\000\000\000\000"} __FUNCTION__ = “main" # this file is autogenerated by make cfg MAIN_NAME= kamailio CFG_NAME= kamailio SCR_NAME= sip-router FLAVOUR= kamailio INSTALL_FLAVOUR= kamailio SRC_NAME= sip-router RELEASE= 4.4.0-dev8 OS= solaris ARCH= sparc64 C_DEFS= -DNAME='"kamailio"' -DVERSION='"4.4.0-dev8"' -DARCH='"sparc64"'
Re: [SR-Users] Core Dump during shutdown on SPARC64
Hi Daniel, I haven’t yet but I will try to test shortly. Here is the value of the block variable: (gdb) p /s block $1 = (unsigned char *) 0x76e5ded4 “" Thanks, Spencer On Jan 13, 2016, at 11:07 PM, Daniel-Constantin Mierla> wrote: Hello, hmm, they are multiple of 8, so they should be aligned to 64bits. Or maybe the 'block' variable value is not aligned to 8bytes ... Have you done any sip traffic via this kamailio instance. Is all ok at runtime? Cheers, Daniel On 14/01/16 08:01, Spencer Thomason wrote: Hi Daniel, See below: (gdb) p group->var_offset $1 = 64 (gdb) p mapping[i].offset $2 = 56 Thanks! Spencer On Jan 13, 2016, at 10:18 PM, Daniel-Constantin Mierla > wrote: Hello, can you get the values for group->var_offset and mapping[i].offset in frame 0? Cheers, Daniel On 14/01/16 05:41, Spencer Thomason wrote: Hello, I’m trying to get Kamailio running on Solaris 11 SPARC64 and I’m receiving a bus error on shutdown. If needed, we can make SPARC hardware available for testing. Thanks, Spencer Core was generated by `/opt/kamailio/sbin/kamailio -f /opt/kamailio/etc/kamailio/kamailio.cfg -P /syst'. Program terminated with signal 10, Bus error. #0 0x0001003e73f0 in cfg_destory_groups (block=0x76e5ded4 "") at cfg/cfg_struct.c:299 299 old_string = *(char **)(block + group->var_offset + mapping[i].offset); (gdb) bt full #0 0x0001003e73f0 in cfg_destory_groups (block=0x76e5ded4 "") at cfg/cfg_struct.c:299 group = 0x100745e20 def = i = 14 group2 = mapping = 0x100745a78 old_string = #1 cfg_destroy () at cfg/cfg_struct.c:391 __FUNCTION__ = "cfg_destroy" #2 0x000100163fc4 in cleanup (show_status=show_status@entry=1) at main.c:540 memlog = __FUNCTION__ = "cleanup" #3 0x0001001650d4 in shutdown_children (show_status=show_status@entry=1, sig=15) at main.c:665 No locals. #4 0x000100165c0c in handle_sigs () at main.c:695 chld = chld_status = 0 memlog = __FUNCTION__ = "handle_sigs" #5 0x00010016e678 in main_loop () at main.c:1722 i = pid = si = si_desc = "udp receiver child=15 sock=104.222.31.55:9000\000\005\066\377\377\377\377v\345\322\370\000\000\000\000\000\020\000\063\377\377\377\377\177\377\360q\000\000\000\001\000B\277 \000\000\000\001\000^:P\000\000\000\001\000\002\356(\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375" nrprocs = woneinit = __FUNCTION__ = "main_loop" #6 0x00010042cafc in main (argc=, argv=) at main.c:2597 cfg_stream = c = r = tmp = 0x7d57 "" tmp_len = 0 port = 0 proto = 0 options = 0x100036918 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:" ret = -1 seed = 4139658536 rfd = debug_save = debug_flag = dont_fork_cnt = p = st = {st_dev = 2478196129807, st_ino = 405001306, st_mode = 16832, st_nlink = 2, st_uid = 0, st_gid = 0, st_rdev = 18446744073709551615, st_size = 117, st_atim = {tv_sec = 1452739293, tv_nsec = 444332080}, st_mtim = { tv_sec = 1452739411, tv_nsec = 727071262}, st_ctim = {tv_sec = 1452739411, tv_nsec = 727071262}, st_blksize = 8192, st_blocks = 16, st_fstype = "tmpfs\000\000\000\000\000\000\000\000\000\000"} __FUNCTION__ = “main" # this file is autogenerated by make cfg MAIN_NAME= kamailio CFG_NAME= kamailio SCR_NAME= sip-router FLAVOUR= kamailio INSTALL_FLAVOUR= kamailio SRC_NAME= sip-router RELEASE= 4.4.0-dev8 OS= solaris ARCH= sparc64 C_DEFS= -DNAME='"kamailio"' -DVERSION='"4.4.0-dev8"' -DARCH='"sparc64"' -DOS='solaris_' -DOS_QUOTED='"solaris"' -DCOMPILER='"gcc 4.8.2"' -D__CPU_sparc64 -D__OS_solaris -DSER_VER=4004000 -DCFG_DIR='"/opt/kamailio/etc/kamailio/"' -DRUN_DIR='"/var/run/kamailio/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DWITH_XAVP -DF_MALLOC -DQ_MALLOC -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS -DSTATISTICS -DMALLOC_STATS -DWITH_AS_SUPPORT -DUSE_SCTP -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DSPARC64_MODE -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALLOCA_H -DUSE_SIGACTION -DHAVE_DEVPOLL -DHAVE_SELECT -DHAVE_FILIO_H DEFS_RM= PROFILE= CC= gcc LD= gcc MKDEP= gcc -MM -MG MKTAGS= ctags LDFLAGS= -m64 -O2 C_INCLUDES= CC_MKDEP_OPTS= -MMD -MP MOD_LDFLAGS= -G -m64 -O2 LIB_LDFLAGS= -G -m64 -O2 UTILS_LDFLAGS= -m64 -O2 LIB_SONAME= -Wl,-h, LD_RPATH= -Wl,-R, LIB_SUFFIX= .so LIB_PREFIX= lib LIBS= -ldl -lresolv -L/usr/local/lib -lxnet -lsocket -lnsl -lrt LEX= flex YACC= bison YACC_FLAGS= -d -b cfg PREFIX=
Re: [SR-Users] Core Dump during shutdown on SPARC64
Hi Daniel, See below: (gdb) p group->var_offset $1 = 64 (gdb) p mapping[i].offset $2 = 56 Thanks! Spencer > On Jan 13, 2016, at 10:18 PM, Daniel-Constantin Mierla> wrote: > > Hello, > > can you get the values for group->var_offset and mapping[i].offset in > frame 0? > > Cheers, > Daniel > > On 14/01/16 05:41, Spencer Thomason wrote: >> Hello, >> I’m trying to get Kamailio running on Solaris 11 SPARC64 and I’m receiving a >> bus error on shutdown. If needed, we can make SPARC hardware available for >> testing. >> >> Thanks, >> Spencer >> >> >> Core was generated by `/opt/kamailio/sbin/kamailio -f >> /opt/kamailio/etc/kamailio/kamailio.cfg -P /syst'. >> Program terminated with signal 10, Bus error. >> #0 0x0001003e73f0 in cfg_destory_groups (block=0x76e5ded4 "") >> at cfg/cfg_struct.c:299 >> 299 old_string = *(char >> **)(block + group->var_offset + mapping[i].offset); >> (gdb) bt full >> #0 0x0001003e73f0 in cfg_destory_groups (block=0x76e5ded4 "") >> at cfg/cfg_struct.c:299 >>group = 0x100745e20 >>def = >>i = 14 >>group2 = >>mapping = 0x100745a78 >>old_string = >> #1 cfg_destroy () at cfg/cfg_struct.c:391 >>__FUNCTION__ = "cfg_destroy" >> #2 0x000100163fc4 in cleanup (show_status=show_status@entry=1) at >> main.c:540 >>memlog = >>__FUNCTION__ = "cleanup" >> #3 0x0001001650d4 in shutdown_children >> (show_status=show_status@entry=1, sig=15) at main.c:665 >> No locals. >> #4 0x000100165c0c in handle_sigs () at main.c:695 >>chld = >>chld_status = 0 >>memlog = >>__FUNCTION__ = "handle_sigs" >> #5 0x00010016e678 in main_loop () at main.c:1722 >>i = >>pid = >>si = >>si_desc = "udp receiver child=15 >> sock=104.222.31.55:9000\000\005\066\377\377\377\377v\345\322\370\000\000\000\000\000\020\000\063\377\377\377\377\177\377\360q\000\000\000\001\000B\277 >> >> \000\000\000\001\000^:P\000\000\000\001\000\002\356(\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375" >>nrprocs = >>woneinit = >>__FUNCTION__ = "main_loop" >> #6 0x00010042cafc in main (argc=, argv=) >> at main.c:2597 >>cfg_stream = >>c = >>r = >>tmp = 0x7d57 "" >>tmp_len = 0 >>port = 0 >>proto = 0 >>options = 0x100036918 >> ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:" >>ret = -1 >>seed = 4139658536 >>rfd = >>debug_save = >>debug_flag = >>dont_fork_cnt = >>p = >>st = {st_dev = 2478196129807, st_ino = 405001306, st_mode = 16832, >> st_nlink = 2, st_uid = 0, st_gid = 0, >> st_rdev = 18446744073709551615, st_size = 117, st_atim = {tv_sec = >> 1452739293, tv_nsec = 444332080}, st_mtim = { >>tv_sec = 1452739411, tv_nsec = 727071262}, st_ctim = {tv_sec = >> 1452739411, tv_nsec = 727071262}, st_blksize = 8192, >> st_blocks = 16, st_fstype = >> "tmpfs\000\000\000\000\000\000\000\000\000\000"} >>__FUNCTION__ = “main" >> >> # this file is autogenerated by make cfg >> MAIN_NAME= kamailio >> CFG_NAME= kamailio >> SCR_NAME= sip-router >> FLAVOUR= kamailio >> INSTALL_FLAVOUR= kamailio >> SRC_NAME= sip-router >> RELEASE= 4.4.0-dev8 >> OS= solaris >> ARCH= sparc64 >> C_DEFS= -DNAME='"kamailio"' -DVERSION='"4.4.0-dev8"' -DARCH='"sparc64"' >> -DOS='solaris_' -DOS_QUOTED='"solaris"' -DCOMPILER='"gcc 4.8.2"' >> -D__CPU_sparc64 -D__OS_solaris -DSER_VER=4004000 >> -DCFG_DIR='"/opt/kamailio/etc/kamailio/"' -DRUN_DIR='"/var/run/kamailio/"' >> -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DUSE_TCP >> -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER >> -DUSE_DST_BLACKLIST -DUSE_NAPTR -DWITH_XAVP -DF_MALLOC -DQ_MALLOC >> -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS >> -DSTATISTICS -DMALLOC_STATS -DWITH_AS_SUPPORT -DUSE_SCTP -DFAST_LOCK >> -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DSPARC64_MODE >> -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD >> -DHAVE_ALLOCA_H -DUSE_SIGACTION -DHAVE_DEVPOLL -DHAVE_SELECT -DHAVE_FILIO_H >> DEFS_RM= >> PROFILE= >> CC= gcc >> LD= gcc >> MKDEP= gcc -MM -MG >> MKTAGS= ctags >> LDFLAGS= -m64 -O2 >> C_INCLUDES= >> CC_MKDEP_OPTS= -MMD -MP >> MOD_LDFLAGS= -G -m64 -O2 >> LIB_LDFLAGS= -G -m64 -O2 >> UTILS_LDFLAGS= -m64 -O2 >> LIB_SONAME= -Wl,-h, >> LD_RPATH= -Wl,-R, >> LIB_SUFFIX= .so >> LIB_PREFIX= lib >> LIBS= -ldl -lresolv -L/usr/local/lib -lxnet -lsocket -lnsl -lrt >> LEX= flex >> YACC= bison >> YACC_FLAGS= -d -b cfg >> PREFIX= /opt/kamailio >> LOCALBASE= /usr/local >> TAR= gtar >> INSTALL= ginstall >> INSTALL_CFG= ginstall -m 644 >>
Re: [SR-Users] Core Dump during shutdown on SPARC64
Hello, can you get the values for group->var_offset and mapping[i].offset in frame 0? Cheers, Daniel On 14/01/16 05:41, Spencer Thomason wrote: > Hello, > I’m trying to get Kamailio running on Solaris 11 SPARC64 and I’m receiving a > bus error on shutdown. If needed, we can make SPARC hardware available for > testing. > > Thanks, > Spencer > > > Core was generated by `/opt/kamailio/sbin/kamailio -f > /opt/kamailio/etc/kamailio/kamailio.cfg -P /syst'. > Program terminated with signal 10, Bus error. > #0 0x0001003e73f0 in cfg_destory_groups (block=0x76e5ded4 "") at > cfg/cfg_struct.c:299 > 299 old_string = *(char > **)(block + group->var_offset + mapping[i].offset); > (gdb) bt full > #0 0x0001003e73f0 in cfg_destory_groups (block=0x76e5ded4 "") at > cfg/cfg_struct.c:299 > group = 0x100745e20 > def = > i = 14 > group2 = > mapping = 0x100745a78 > old_string = > #1 cfg_destroy () at cfg/cfg_struct.c:391 > __FUNCTION__ = "cfg_destroy" > #2 0x000100163fc4 in cleanup (show_status=show_status@entry=1) at > main.c:540 > memlog = > __FUNCTION__ = "cleanup" > #3 0x0001001650d4 in shutdown_children (show_status=show_status@entry=1, > sig=15) at main.c:665 > No locals. > #4 0x000100165c0c in handle_sigs () at main.c:695 > chld = > chld_status = 0 > memlog = > __FUNCTION__ = "handle_sigs" > #5 0x00010016e678 in main_loop () at main.c:1722 > i = > pid = > si = > si_desc = "udp receiver child=15 > sock=104.222.31.55:9000\000\005\066\377\377\377\377v\345\322\370\000\000\000\000\000\020\000\063\377\377\377\377\177\377\360q\000\000\000\001\000B\277 > > \000\000\000\001\000^:P\000\000\000\001\000\002\356(\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375" > nrprocs = > woneinit = > __FUNCTION__ = "main_loop" > #6 0x00010042cafc in main (argc=, argv=) > at main.c:2597 > cfg_stream = > c = > r = > tmp = 0x7d57 "" > tmp_len = 0 > port = 0 > proto = 0 > options = 0x100036918 > ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:" > ret = -1 > seed = 4139658536 > rfd = > debug_save = > debug_flag = > dont_fork_cnt = > p = > st = {st_dev = 2478196129807, st_ino = 405001306, st_mode = 16832, > st_nlink = 2, st_uid = 0, st_gid = 0, > st_rdev = 18446744073709551615, st_size = 117, st_atim = {tv_sec = > 1452739293, tv_nsec = 444332080}, st_mtim = { > tv_sec = 1452739411, tv_nsec = 727071262}, st_ctim = {tv_sec = > 1452739411, tv_nsec = 727071262}, st_blksize = 8192, > st_blocks = 16, st_fstype = > "tmpfs\000\000\000\000\000\000\000\000\000\000"} > __FUNCTION__ = “main" > > # this file is autogenerated by make cfg > MAIN_NAME= kamailio > CFG_NAME= kamailio > SCR_NAME= sip-router > FLAVOUR= kamailio > INSTALL_FLAVOUR= kamailio > SRC_NAME= sip-router > RELEASE= 4.4.0-dev8 > OS= solaris > ARCH= sparc64 > C_DEFS= -DNAME='"kamailio"' -DVERSION='"4.4.0-dev8"' -DARCH='"sparc64"' > -DOS='solaris_' -DOS_QUOTED='"solaris"' -DCOMPILER='"gcc 4.8.2"' > -D__CPU_sparc64 -D__OS_solaris -DSER_VER=4004000 > -DCFG_DIR='"/opt/kamailio/etc/kamailio/"' -DRUN_DIR='"/var/run/kamailio/"' > -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DUSE_TCP > -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER > -DUSE_DST_BLACKLIST -DUSE_NAPTR -DWITH_XAVP -DF_MALLOC -DQ_MALLOC > -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS > -DSTATISTICS -DMALLOC_STATS -DWITH_AS_SUPPORT -DUSE_SCTP -DFAST_LOCK > -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DSPARC64_MODE > -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALLOCA_H > -DUSE_SIGACTION -DHAVE_DEVPOLL -DHAVE_SELECT -DHAVE_FILIO_H > DEFS_RM= > PROFILE= > CC= gcc > LD= gcc > MKDEP= gcc -MM -MG > MKTAGS= ctags > LDFLAGS= -m64 -O2 > C_INCLUDES= > CC_MKDEP_OPTS= -MMD -MP > MOD_LDFLAGS= -G -m64 -O2 > LIB_LDFLAGS= -G -m64 -O2 > UTILS_LDFLAGS= -m64 -O2 > LIB_SONAME= -Wl,-h, > LD_RPATH= -Wl,-R, > LIB_SUFFIX= .so > LIB_PREFIX= lib > LIBS= -ldl -lresolv -L/usr/local/lib -lxnet -lsocket -lnsl -lrt > LEX= flex > YACC= bison > YACC_FLAGS= -d -b cfg > PREFIX= /opt/kamailio > LOCALBASE= /usr/local > TAR= gtar > INSTALL= ginstall > INSTALL_CFG= ginstall -m 644 > INSTALL_BIN= ginstall -m 755 > INSTALL_MODULES= ginstall -m 755 > INSTALL_DOC= ginstall -m 644 > INSTALL_MAN= ginstall -m 644 > INSTALL_LIB= ginstall -m 755 > INSTALL_TOUCH= touch > INSTALL_SHARE= ginstall -m 644 > Q= 1 > CC_EXTRA_OPTS= -O2 -m64 > CPU= ultrasparc > CFLAGS_RM= > CFLAGS= -g
Re: [SR-Users] Core Dump during shutdown on SPARC64
Hello, hmm, they are multiple of 8, so they should be aligned to 64bits. Or maybe the 'block' variable value is not aligned to 8bytes ... Have you done any sip traffic via this kamailio instance. Is all ok at runtime? Cheers, Daniel On 14/01/16 08:01, Spencer Thomason wrote: > Hi Daniel, > See below: > (gdb) p group->var_offset > $1 = 64 > (gdb) p mapping[i].offset > $2 = 56 > > Thanks! > Spencer > > >> On Jan 13, 2016, at 10:18 PM, Daniel-Constantin Mierla>> wrote: >> >> Hello, >> >> can you get the values for group->var_offset and mapping[i].offset in >> frame 0? >> >> Cheers, >> Daniel >> >> On 14/01/16 05:41, Spencer Thomason wrote: >>> Hello, >>> I’m trying to get Kamailio running on Solaris 11 SPARC64 and I’m receiving >>> a bus error on shutdown. If needed, we can make SPARC hardware available >>> for testing. >>> >>> Thanks, >>> Spencer >>> >>> >>> Core was generated by `/opt/kamailio/sbin/kamailio -f >>> /opt/kamailio/etc/kamailio/kamailio.cfg -P /syst'. >>> Program terminated with signal 10, Bus error. >>> #0 0x0001003e73f0 in cfg_destory_groups (block=0x76e5ded4 "") >>> at cfg/cfg_struct.c:299 >>> 299 old_string = *(char >>> **)(block + group->var_offset + mapping[i].offset); >>> (gdb) bt full >>> #0 0x0001003e73f0 in cfg_destory_groups (block=0x76e5ded4 "") >>> at cfg/cfg_struct.c:299 >>>group = 0x100745e20 >>>def = >>>i = 14 >>>group2 = >>>mapping = 0x100745a78 >>>old_string = >>> #1 cfg_destroy () at cfg/cfg_struct.c:391 >>>__FUNCTION__ = "cfg_destroy" >>> #2 0x000100163fc4 in cleanup (show_status=show_status@entry=1) at >>> main.c:540 >>>memlog = >>>__FUNCTION__ = "cleanup" >>> #3 0x0001001650d4 in shutdown_children >>> (show_status=show_status@entry=1, sig=15) at main.c:665 >>> No locals. >>> #4 0x000100165c0c in handle_sigs () at main.c:695 >>>chld = >>>chld_status = 0 >>>memlog = >>>__FUNCTION__ = "handle_sigs" >>> #5 0x00010016e678 in main_loop () at main.c:1722 >>>i = >>>pid = >>>si = >>>si_desc = "udp receiver child=15 >>> sock=104.222.31.55:9000\000\005\066\377\377\377\377v\345\322\370\000\000\000\000\000\020\000\063\377\377\377\377\177\377\360q\000\000\000\001\000B\277 >>> >>> \000\000\000\001\000^:P\000\000\000\001\000\002\356(\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375" >>>nrprocs = >>>woneinit = >>>__FUNCTION__ = "main_loop" >>> #6 0x00010042cafc in main (argc=, argv=) >>> at main.c:2597 >>>cfg_stream = >>>c = >>>r = >>>tmp = 0x7d57 "" >>>tmp_len = 0 >>>port = 0 >>>proto = 0 >>>options = 0x100036918 >>> ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:" >>>ret = -1 >>>seed = 4139658536 >>>rfd = >>>debug_save = >>>debug_flag = >>>dont_fork_cnt = >>>p = >>>st = {st_dev = 2478196129807, st_ino = 405001306, st_mode = 16832, >>> st_nlink = 2, st_uid = 0, st_gid = 0, >>> st_rdev = 18446744073709551615, st_size = 117, st_atim = {tv_sec = >>> 1452739293, tv_nsec = 444332080}, st_mtim = { >>>tv_sec = 1452739411, tv_nsec = 727071262}, st_ctim = {tv_sec = >>> 1452739411, tv_nsec = 727071262}, st_blksize = 8192, >>> st_blocks = 16, st_fstype = >>> "tmpfs\000\000\000\000\000\000\000\000\000\000"} >>>__FUNCTION__ = “main" >>> >>> # this file is autogenerated by make cfg >>> MAIN_NAME= kamailio >>> CFG_NAME= kamailio >>> SCR_NAME= sip-router >>> FLAVOUR= kamailio >>> INSTALL_FLAVOUR= kamailio >>> SRC_NAME= sip-router >>> RELEASE= 4.4.0-dev8 >>> OS= solaris >>> ARCH= sparc64 >>> C_DEFS= -DNAME='"kamailio"' -DVERSION='"4.4.0-dev8"' -DARCH='"sparc64"' >>> -DOS='solaris_' -DOS_QUOTED='"solaris"' -DCOMPILER='"gcc 4.8.2"' >>> -D__CPU_sparc64 -D__OS_solaris -DSER_VER=4004000 >>> -DCFG_DIR='"/opt/kamailio/etc/kamailio/"' -DRUN_DIR='"/var/run/kamailio/"' >>> -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DUSE_TCP >>> -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER >>> -DUSE_DST_BLACKLIST -DUSE_NAPTR -DWITH_XAVP -DF_MALLOC -DQ_MALLOC >>> -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS >>> -DSTATISTICS -DMALLOC_STATS -DWITH_AS_SUPPORT -DUSE_SCTP -DFAST_LOCK >>> -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM >>> -DSPARC64_MODE -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H >>> -DHAVE_SCHED_YIELD -DHAVE_ALLOCA_H -DUSE_SIGACTION -DHAVE_DEVPOLL >>> -DHAVE_SELECT -DHAVE_FILIO_H >>> DEFS_RM= >>> PROFILE= >>> CC= gcc >>> LD= gcc >>> MKDEP= gcc -MM -MG >>> MKTAGS= ctags >>> LDFLAGS= -m64 -O2 >>> C_INCLUDES= >>> CC_MKDEP_OPTS= -MMD -MP >>>
Re: [SR-Users] Core dump while saving user location in mongo
Hi, Thanks for the patch, Kamailio doesn't crash anymore. However, I'm encountering another issue with usrloc + Mongo, I will write a new post. Thanks, Mickael From: Daniel-Constantin Mierla [mailto:mico...@gmail.com] Sent: Friday, January 30, 2015 7:22 AM To: Mickael Marrache Cc: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Core dump while saving user location in mongo Hello, I pushed a patch that takes care of initializing the columns array of the result - it is in the master branch for now. However, the log messages don't seem to be complete, were you sending all. The backtrace shows a line which is executed only if an error message is printed, it is not in the logs you sent. One thing that I remembered was that usrloc requires parameter db_insert_null to be set in order to work with mongodb: - http://kamailio.org/docs/modules/stable/modules/usrloc.html#usrloc.p.db_insert_null The crash shouldn't happen and hopefully the patch I pushed catches it. Try the patch without db_insert_null just to see if there is still a crash or not. Cheers, Daniel On Thu, Jan 29, 2015 at 11:51 AM, Mickael Marrache mickaelmarra...@gmail.com wrote: Now, it didn't crash during the REGISTER but during the INVITE: kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:705]: db_mongodb_query(): query to collection [location] kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:726]: db_mongodb_query(): query filter: { username : m1 } kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:745]: db_mongodb_query(): columns filter: { contact : 1, expires : 1, q : 1, callid : 1, cseq : 1, flags : 1, cflags : 1, user_agent : 1, received : 1, path : 1, socket : 1, methods : 1, last_modified : 1, ruid : 1, instance : 1, reg_id : 1 } kamailio[32599]: DEBUG: core [db_res.c:118]: db_new_result(): allocate 56 bytes for result set at 0x7f83a32daa48 kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:203]: db_mongodb_get_columns(): 16 columns returned from the query kamailio[32599]: DEBUG: core [db_res.c:155]: db_allocate_columns(): allocate 128 bytes for result names at 0x7f83a32daf98 kamailio[32599]: DEBUG: core [db_res.c:165]: db_allocate_columns(): allocate 64 bytes for result types at 0x7f83a32daed8 kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:231]: db_mongodb_get_columns(): Found a field[0] named: contact kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:250]: db_mongodb_get_columns(): allocate 16 bytes for RES_NAMES[0] at 0x7f83a32daab8 kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:285]: db_mongodb_get_columns(): use DB1_STRING result type kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:314]: db_mongodb_get_columns(): RES_NAMES(0x7f83a32daab8)[0]=[contact] (2) kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:231]: db_mongodb_get_columns(): Found a field[1] named: expires kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:250]: db_mongodb_get_columns(): allocate 16 bytes for RES_NAMES[1] at 0x7f83a32dab98 kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:275]: db_mongodb_get_columns(): use DB1_DATETIME result type kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:314]: db_mongodb_get_columns(): RES_NAMES(0x7f83a32dab98)[1]=[expires] (9) kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:231]: db_mongodb_get_columns(): Found a field[2] named: q kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:250]: db_mongodb_get_columns(): allocate 16 bytes for RES_NAMES[2] at 0x7f83a32dabe0 kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:270]: db_mongodb_get_columns(): use DB1_DOUBLE result type kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:314]: db_mongodb_get_columns(): RES_NAMES(0x7f83a32dabe0)[2]=[q] (1) kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:231]: db_mongodb_get_columns(): Found a field[3] named: callid kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:250]: db_mongodb_get_columns(): allocate 16 bytes for RES_NAMES[3] at 0x7f83a32dac70 kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:285]: db_mongodb_get_columns(): use DB1_STRING result type kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:314]: db_mongodb_get_columns(): RES_NAMES(0x7f83a32dac70)[3]=[callid] (2) kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:231]: db_mongodb_get_columns(): Found a field[4] named: cseq kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:250]: db_mongodb_get_columns(): allocate 16 bytes for RES_NAMES[4] at 0x7f83a32dac28 kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:260]: db_mongodb_get_columns(): use DB1_INT result type kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:314]: db_mongodb_get_columns(): RES_NAMES(0x7f83a32dac28)[4]=[cseq] (16) kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:231]: db_mongodb_get_columns(): Found a field[5] named: flags kamailio[32599]: DEBUG: db_mongodb [mongodb_dbase.c:250]: db_mongodb_get_columns(): allocate 16 bytes
Re: [SR-Users] Core dump while saving user location in mongo
Hello, can you give the parameters for usrloc module? Are you using DB_ONLY mode? Cheers, Daniel On 29/01/15 08:55, Mickael Marrache wrote: Hi, When my proxy receives a REGISTER request, it crashes while saving the user location in MongoDB. This is the backtrace from the core dump: #0 0x003f08e32625 in raise () from /lib64/libc.so.6 #1 0x003f08e33e05 in abort () from /lib64/libc.so.6 #2 0x006196f9 in fm_free (qm=0x7f4368bf7010, p=0x210add0, file=0x7f4367fd7608 core: db_res.c, func=0x7f4367fd8100 db_free_columns, line=86) at mem/f_malloc.c:588 #3 0x7f4367fc37ab in db_free_columns (_r=0x7f4368ca0430) at db_res.c:86 #4 0x7f4367fc479e in db_free_result (_r=0x7f4368ca0430) at db_res.c:134 #5 0x7f4367da37cb in db_mongodb_free_result (_h=0x7f4368c94718, _r=0x7f4368ca0430) at mongodb_dbase.c:646 #6 0x7f4367da5d65 in db_mongodb_query (_h=0x7f4368c94718, _k=0x7fffa03d5550, _op=0x0, _v=0x7fffa03d5510, _c=0x7fffa03d5560, _n=1, _nc=16, _o=0x7f4365ed2c80, _r=0x7fffa03d5508) at mongodb_dbase.c:783 #7 0x7f4365cac7d2 in db_load_urecord (_c=0x7f4368c94718, _d=0x7f436154a0e8, _aor=0x7fffa03d59d0) at udomain.c:601 #8 0x7f4365cb1e8e in get_urecord (_d=0x7f436154a0e8, _aor=0x7fffa03d59d0, _r=0x7fffa03d5760) at udomain.c:1106 #9 0x7f4365a75dea in add_contacts (_m=0x7f4368cbdc40, _d=0x7f436154a0e8, _a=0x7fffa03d59d0, _mode=1, _use_regid=1) at save.c:832 #10 0x7f4365a77d32 in save (_m=0x7f4368cbdc40, _d=0x7f436154a0e8, _cflags=4, _uri=0x0) at save.c:986 #11 0x7f4365a606db in w_save2 (_m=0x7f4368cbdc40, _d=0x7f436154a0e8 H\240TaC\177, _cflags=0x4 Address 0x4 out of bounds) at reg_mod.c:447 #12 0x0041d489 in do_action (h=0x7fffa03d6180, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1100 #13 0x00429a7a in run_actions (h=0x7fffa03d6180, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1583 #14 0x0042a0df in run_actions_safe (h=0x7fffa03d7470, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1648 #15 0x00540b7c in rval_get_int (h=0x7fffa03d7470, msg=0x7f4368cbdc40, i=0x7fffa03d6658, rv=0x7f4368c72830, cache=0x0) at rvalue.c:924 #16 0x00544db4 in rval_expr_eval_int (h=0x7fffa03d7470, msg=0x7f4368cbdc40, res=0x7fffa03d6658, rve=0x7f4368c72828) at rvalue.c:1918 #17 0x005451aa in rval_expr_eval_int (h=0x7fffa03d7470, msg=0x7f4368cbdc40, res=0x7fffa03d6ae0, rve=0x7f4368c72070) at rvalue.c:1926 #18 0x0041ce4e in do_action (h=0x7fffa03d7470, a=0x7f4368c73148, msg=0x7f4368cbdc40) at action.c:1064 #19 0x00429a7a in run_actions (h=0x7fffa03d7470, a=0x7f4368c71cc0, msg=0x7f4368cbdc40) at action.c:1583 #20 0x00419dea in do_action (h=0x7fffa03d7470, a=0x7f4368c3bdb8, msg=0x7f4368cbdc40) at action.c:712 #21 0x00429a7a in run_actions (h=0x7fffa03d7470, a=0x7f4368c33898, msg=0x7f4368cbdc40) at action.c:1583 #22 0x0042a1a7 in run_top_route (a=0x7f4368c33898, msg=0x7f4368cbdc40, c=0x0) at action.c:1669 #23 0x0050747e in receive_msg ( buf=0xa6f780 REGISTER sip::5060;transport=tcp SIP/2.0\r\nVia: SIP/2.0/UDP X;branch=z9hG4bK242c.26de52a75c8675f6757e0958454a0ad5.0;i=1\r\nv: SIP/2.0/TCP XX:62051;received=..., len=1004, rcv_info=0x7fffa03d7760) at receive.c:216 #24 0x00606e76 in udp_rcv_loop () at udp_server.c:521 #25 0x004a5c97 in main_loop () at main.c:1629 #26 0x004aaf2a in main (argc=13, argv=0x7fffa03d7b78) at main.c:2561 I tested multiple times, it occurs everytime. Let me know if you need more information. Thanks, Mickael ___ 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 http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda ___ 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
Re: [SR-Users] Core dump while saving user location in mongo
The parameters: modparam(usrloc, db_url, mongodb://DB_MONGO_HOST:DB_MONGO_PORT/DB_MONGO_DBNAME) modparam(usrloc, db_mode, 3) modparam(usrloc, use_domain, 0) modparam(usrloc, timer_interval, 60) Yes, I use DB_ONLY (3) mode. Mickael From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Thursday, January 29, 2015 12:23 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Core dump while saving user location in mongo Hello, can you give the parameters for usrloc module? Are you using DB_ONLY mode? Cheers, Daniel On 29/01/15 08:55, Mickael Marrache wrote: Hi, When my proxy receives a REGISTER request, it crashes while saving the user location in MongoDB. This is the backtrace from the core dump: #0 0x003f08e32625 in raise () from /lib64/libc.so.6 #1 0x003f08e33e05 in abort () from /lib64/libc.so.6 #2 0x006196f9 in fm_free (qm=0x7f4368bf7010, p=0x210add0, file=0x7f4367fd7608 core: db_res.c, func=0x7f4367fd8100 db_free_columns, line=86) at mem/f_malloc.c:588 #3 0x7f4367fc37ab in db_free_columns (_r=0x7f4368ca0430) at db_res.c:86 #4 0x7f4367fc479e in db_free_result (_r=0x7f4368ca0430) at db_res.c:134 #5 0x7f4367da37cb in db_mongodb_free_result (_h=0x7f4368c94718, _r=0x7f4368ca0430) at mongodb_dbase.c:646 #6 0x7f4367da5d65 in db_mongodb_query (_h=0x7f4368c94718, _k=0x7fffa03d5550, _op=0x0, _v=0x7fffa03d5510, _c=0x7fffa03d5560, _n=1, _nc=16, _o=0x7f4365ed2c80, _r=0x7fffa03d5508) at mongodb_dbase.c:783 #7 0x7f4365cac7d2 in db_load_urecord (_c=0x7f4368c94718, _d=0x7f436154a0e8, _aor=0x7fffa03d59d0) at udomain.c:601 #8 0x7f4365cb1e8e in get_urecord (_d=0x7f436154a0e8, _aor=0x7fffa03d59d0, _r=0x7fffa03d5760) at udomain.c:1106 #9 0x7f4365a75dea in add_contacts (_m=0x7f4368cbdc40, _d=0x7f436154a0e8, _a=0x7fffa03d59d0, _mode=1, _use_regid=1) at save.c:832 #10 0x7f4365a77d32 in save (_m=0x7f4368cbdc40, _d=0x7f436154a0e8, _cflags=4, _uri=0x0) at save.c:986 #11 0x7f4365a606db in w_save2 (_m=0x7f4368cbdc40, _d=0x7f436154a0e8 H\240TaC\177, _cflags=0x4 Address 0x4 out of bounds) at reg_mod.c:447 #12 0x0041d489 in do_action (h=0x7fffa03d6180, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1100 #13 0x00429a7a in run_actions (h=0x7fffa03d6180, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1583 #14 0x0042a0df in run_actions_safe (h=0x7fffa03d7470, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1648 #15 0x00540b7c in rval_get_int (h=0x7fffa03d7470, msg=0x7f4368cbdc40, i=0x7fffa03d6658, rv=0x7f4368c72830, cache=0x0) at rvalue.c:924 #16 0x00544db4 in rval_expr_eval_int (h=0x7fffa03d7470, msg=0x7f4368cbdc40, res=0x7fffa03d6658, rve=0x7f4368c72828) at rvalue.c:1918 #17 0x005451aa in rval_expr_eval_int (h=0x7fffa03d7470, msg=0x7f4368cbdc40, res=0x7fffa03d6ae0, rve=0x7f4368c72070) at rvalue.c:1926 #18 0x0041ce4e in do_action (h=0x7fffa03d7470, a=0x7f4368c73148, msg=0x7f4368cbdc40) at action.c:1064 #19 0x00429a7a in run_actions (h=0x7fffa03d7470, a=0x7f4368c71cc0, msg=0x7f4368cbdc40) at action.c:1583 #20 0x00419dea in do_action (h=0x7fffa03d7470, a=0x7f4368c3bdb8, msg=0x7f4368cbdc40) at action.c:712 #21 0x00429a7a in run_actions (h=0x7fffa03d7470, a=0x7f4368c33898, msg=0x7f4368cbdc40) at action.c:1583 #22 0x0042a1a7 in run_top_route (a=0x7f4368c33898, msg=0x7f4368cbdc40, c=0x0) at action.c:1669 #23 0x0050747e in receive_msg ( buf=0xa6f780 REGISTER sip::5060;transport=tcp SIP/2.0\r\nVia: SIP/2.0/UDP X;branch=z9hG4bK242c.26de52a75c8675f6757e0958454a0ad5.0;i=1\r\nv: SIP/2.0/TCP XX:62051;received=..., len=1004, rcv_info=0x7fffa03d7760) at receive.c:216 #24 0x00606e76 in udp_rcv_loop () at udp_server.c:521 #25 0x004a5c97 in main_loop () at main.c:1629 #26 0x004aaf2a in main (argc=13, argv=0x7fffa03d7b78) at main.c:2561 I tested multiple times, it occurs everytime. Let me know if you need more information. Thanks, Mickael ___ 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 http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda ___ 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
Re: [SR-Users] Core dump while saving user location in mongo
Also, give the error messages from syslog file. Cheers, Daniel On 29/01/15 11:23, Daniel-Constantin Mierla wrote: Hello, can you give the parameters for usrloc module? Are you using DB_ONLY mode? Cheers, Daniel On 29/01/15 08:55, Mickael Marrache wrote: Hi, When my proxy receives a REGISTER request, it crashes while saving the user location in MongoDB. This is the backtrace from the core dump: #0 0x003f08e32625 in raise () from /lib64/libc.so.6 #1 0x003f08e33e05 in abort () from /lib64/libc.so.6 #2 0x006196f9 in fm_free (qm=0x7f4368bf7010, p=0x210add0, file=0x7f4367fd7608 core: db_res.c, func=0x7f4367fd8100 db_free_columns, line=86) at mem/f_malloc.c:588 #3 0x7f4367fc37ab in db_free_columns (_r=0x7f4368ca0430) at db_res.c:86 #4 0x7f4367fc479e in db_free_result (_r=0x7f4368ca0430) at db_res.c:134 #5 0x7f4367da37cb in db_mongodb_free_result (_h=0x7f4368c94718, _r=0x7f4368ca0430) at mongodb_dbase.c:646 #6 0x7f4367da5d65 in db_mongodb_query (_h=0x7f4368c94718, _k=0x7fffa03d5550, _op=0x0, _v=0x7fffa03d5510, _c=0x7fffa03d5560, _n=1, _nc=16, _o=0x7f4365ed2c80, _r=0x7fffa03d5508) at mongodb_dbase.c:783 #7 0x7f4365cac7d2 in db_load_urecord (_c=0x7f4368c94718, _d=0x7f436154a0e8, _aor=0x7fffa03d59d0) at udomain.c:601 #8 0x7f4365cb1e8e in get_urecord (_d=0x7f436154a0e8, _aor=0x7fffa03d59d0, _r=0x7fffa03d5760) at udomain.c:1106 #9 0x7f4365a75dea in add_contacts (_m=0x7f4368cbdc40, _d=0x7f436154a0e8, _a=0x7fffa03d59d0, _mode=1, _use_regid=1) at save.c:832 #10 0x7f4365a77d32 in save (_m=0x7f4368cbdc40, _d=0x7f436154a0e8, _cflags=4, _uri=0x0) at save.c:986 #11 0x7f4365a606db in w_save2 (_m=0x7f4368cbdc40, _d=0x7f436154a0e8 H\240TaC\177, _cflags=0x4 Address 0x4 out of bounds) at reg_mod.c:447 #12 0x0041d489 in do_action (h=0x7fffa03d6180, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1100 #13 0x00429a7a in run_actions (h=0x7fffa03d6180, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1583 #14 0x0042a0df in run_actions_safe (h=0x7fffa03d7470, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1648 #15 0x00540b7c in rval_get_int (h=0x7fffa03d7470, msg=0x7f4368cbdc40, i=0x7fffa03d6658, rv=0x7f4368c72830, cache=0x0) at rvalue.c:924 #16 0x00544db4 in rval_expr_eval_int (h=0x7fffa03d7470, msg=0x7f4368cbdc40, res=0x7fffa03d6658, rve=0x7f4368c72828) at rvalue.c:1918 #17 0x005451aa in rval_expr_eval_int (h=0x7fffa03d7470, msg=0x7f4368cbdc40, res=0x7fffa03d6ae0, rve=0x7f4368c72070) at rvalue.c:1926 #18 0x0041ce4e in do_action (h=0x7fffa03d7470, a=0x7f4368c73148, msg=0x7f4368cbdc40) at action.c:1064 #19 0x00429a7a in run_actions (h=0x7fffa03d7470, a=0x7f4368c71cc0, msg=0x7f4368cbdc40) at action.c:1583 #20 0x00419dea in do_action (h=0x7fffa03d7470, a=0x7f4368c3bdb8, msg=0x7f4368cbdc40) at action.c:712 #21 0x00429a7a in run_actions (h=0x7fffa03d7470, a=0x7f4368c33898, msg=0x7f4368cbdc40) at action.c:1583 #22 0x0042a1a7 in run_top_route (a=0x7f4368c33898, msg=0x7f4368cbdc40, c=0x0) at action.c:1669 #23 0x0050747e in receive_msg ( buf=0xa6f780 REGISTER sip::5060;transport=tcp SIP/2.0\r\nVia: SIP/2.0/UDP X;branch=z9hG4bK242c.26de52a75c8675f6757e0958454a0ad5.0;i=1\r\nv: SIP/2.0/TCP XX:62051;received=..., len=1004, rcv_info=0x7fffa03d7760) at receive.c:216 #24 0x00606e76 in udp_rcv_loop () at udp_server.c:521 #25 0x004a5c97 in main_loop () at main.c:1629 #26 0x004aaf2a in main (argc=13, argv=0x7fffa03d7b78) at main.c:2561 I tested multiple times, it occurs everytime. Let me know if you need more information. Thanks, Mickael ___ 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 http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda ___ 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
Re: [SR-Users] Core dump while saving user location in mongo
=0x7f83a32d91f0) at rvalue.c:1918 #18 0x0041ce4e in do_action (h=0x7fff25b774c0, a=0x7f83a32d9d58, msg=0x7f83a33083e0) at action.c:1064 #19 0x00429a7a in run_actions (h=0x7fff25b774c0, a=0x7f83a32d9d58, msg=0x7f83a33083e0) at action.c:1583 #20 0x00419dea in do_action (h=0x7fff25b774c0, a=0x7f83a32c9048, msg=0x7f83a33083e0) at action.c:712 #21 0x00429a7a in run_actions (h=0x7fff25b774c0, a=0x7f83a32c3cd8, msg=0x7f83a33083e0) at action.c:1583 #22 0x00419dea in do_action (h=0x7fff25b774c0, a=0x7f83a328d418, msg=0x7f83a33083e0) at action.c:712 #23 0x00429a7a in run_actions (h=0x7fff25b774c0, a=0x7f83a328d418, msg=0x7f83a33083e0) at action.c:1583 #24 0x0041d2cd in do_action (h=0x7fff25b774c0, a=0x7f83a328d658, msg=0x7f83a33083e0) at action.c:1079 #25 0x00429a7a in run_actions (h=0x7fff25b774c0, a=0x7f83a327d898, msg=0x7f83a33083e0) at action.c:1583 #26 0x0042a1a7 in run_top_route (a=0x7f83a327d898, msg=0x7f83a33083e0, c=0x0) at action.c:1669 #27 0x0050747e in receive_msg ( buf=0xa6f780 INVITE sip:XX@XXX SIP/2.0\r\nRecord-Route: sip:X;lr\r\nVia: SIP/2.0/UDP XXX;branch=z9hG4bK2be.f31409f558981039fd70ad46afc97176.0\r\nVia: SIP/2.0/UDP ..., len=1151, rcv_info=0x7fff25b777b0) at receive.c:216 #28 0x00606e76 in udp_rcv_loop () at udp_server.c:521 #29 0x004a5c97 in main_loop () at main.c:1629 #30 0x004aaf2a in main (argc=13, argv=0x7fff25b77bc8) at main.c:2561 I can try to reproduce the issue with the REGISTER if you need. Mickael From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Thursday, January 29, 2015 12:26 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Core dump while saving user location in mongo Also, give the error messages from syslog file. Cheers, Daniel On 29/01/15 11:23, Daniel-Constantin Mierla wrote: Hello, can you give the parameters for usrloc module? Are you using DB_ONLY mode? Cheers, Daniel On 29/01/15 08:55, Mickael Marrache wrote: Hi, When my proxy receives a REGISTER request, it crashes while saving the user location in MongoDB. This is the backtrace from the core dump: #0 0x003f08e32625 in raise () from /lib64/libc.so.6 #1 0x003f08e33e05 in abort () from /lib64/libc.so.6 #2 0x006196f9 in fm_free (qm=0x7f4368bf7010, p=0x210add0, file=0x7f4367fd7608 core: db_res.c, func=0x7f4367fd8100 db_free_columns, line=86) at mem/f_malloc.c:588 #3 0x7f4367fc37ab in db_free_columns (_r=0x7f4368ca0430) at db_res.c:86 #4 0x7f4367fc479e in db_free_result (_r=0x7f4368ca0430) at db_res.c:134 #5 0x7f4367da37cb in db_mongodb_free_result (_h=0x7f4368c94718, _r=0x7f4368ca0430) at mongodb_dbase.c:646 #6 0x7f4367da5d65 in db_mongodb_query (_h=0x7f4368c94718, _k=0x7fffa03d5550, _op=0x0, _v=0x7fffa03d5510, _c=0x7fffa03d5560, _n=1, _nc=16, _o=0x7f4365ed2c80, _r=0x7fffa03d5508) at mongodb_dbase.c:783 #7 0x7f4365cac7d2 in db_load_urecord (_c=0x7f4368c94718, _d=0x7f436154a0e8, _aor=0x7fffa03d59d0) at udomain.c:601 #8 0x7f4365cb1e8e in get_urecord (_d=0x7f436154a0e8, _aor=0x7fffa03d59d0, _r=0x7fffa03d5760) at udomain.c:1106 #9 0x7f4365a75dea in add_contacts (_m=0x7f4368cbdc40, _d=0x7f436154a0e8, _a=0x7fffa03d59d0, _mode=1, _use_regid=1) at save.c:832 #10 0x7f4365a77d32 in save (_m=0x7f4368cbdc40, _d=0x7f436154a0e8, _cflags=4, _uri=0x0) at save.c:986 #11 0x7f4365a606db in w_save2 (_m=0x7f4368cbdc40, _d=0x7f436154a0e8 H\240TaC\177, _cflags=0x4 Address 0x4 out of bounds) at reg_mod.c:447 #12 0x0041d489 in do_action (h=0x7fffa03d6180, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1100 #13 0x00429a7a in run_actions (h=0x7fffa03d6180, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1583 #14 0x0042a0df in run_actions_safe (h=0x7fffa03d7470, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1648 #15 0x00540b7c in rval_get_int (h=0x7fffa03d7470, msg=0x7f4368cbdc40, i=0x7fffa03d6658, rv=0x7f4368c72830, cache=0x0) at rvalue.c:924 #16 0x00544db4 in rval_expr_eval_int (h=0x7fffa03d7470, msg=0x7f4368cbdc40, res=0x7fffa03d6658, rve=0x7f4368c72828) at rvalue.c:1918 #17 0x005451aa in rval_expr_eval_int (h=0x7fffa03d7470, msg=0x7f4368cbdc40, res=0x7fffa03d6ae0, rve=0x7f4368c72070) at rvalue.c:1926 #18 0x0041ce4e in do_action (h=0x7fffa03d7470, a=0x7f4368c73148, msg=0x7f4368cbdc40) at action.c:1064 #19 0x00429a7a in run_actions (h=0x7fffa03d7470, a=0x7f4368c71cc0, msg=0x7f4368cbdc40) at action.c:1583 #20 0x00419dea in do_action (h=0x7fffa03d7470, a=0x7f4368c3bdb8, msg=0x7f4368cbdc40) at action.c:712 #21 0x00429a7a in run_actions (h=0x7fffa03d7470, a=0x7f4368c33898, msg=0x7f4368cbdc40) at action.c:1583 #22 0x0042a1a7 in run_top_route (a=0x7f4368c33898, msg=0x7f4368cbdc40, c=0x0) at action.c:1669 #23 0x0050747e
Re: [SR-Users] Core dump while saving user location in mongo
=0x7f839b9700e8, _uri=0x0, _mode=0) at lookup.c:173 #10 0x7f839fe79ffd in lookup (_m=0x7f83a33083e0, _d=0x7f839b9700e8, _uri=0x0) at lookup.c:88 #11 0x7f839fe7eb35 in lookup_branches (msg=0x7f83a33083e0, d=0x7f839b9700e8) at lookup.c:448 #12 0x7f839fe870dd in w_lookup_branches (_m=0x7f83a33083e0, _d=0x7f839b9700e8 H, _p2=0x0) at reg_mod.c:499 #13 0x0041d3f2 in do_action (h=0x7fff25b755d0, a=0x7f83a32d8cc8, msg=0x7f83a33083e0) at action.c:1094 #14 0x00429a7a in run_actions (h=0x7fff25b755d0, a=0x7f83a32d8cc8, msg=0x7f83a33083e0) at action.c:1583 #15 0x0042a0df in run_actions_safe (h=0x7fff25b774c0, a=0x7f83a32d8cc8, msg=0x7f83a33083e0) at action.c:1648 #16 0x00540b7c in rval_get_int (h=0x7fff25b774c0, msg=0x7f83a33083e0, i=0x7fff25b75d90, rv=0x7f83a32d91f8, cache=0x0) at rvalue.c:924 #17 0x00544db4 in rval_expr_eval_int (h=0x7fff25b774c0, msg=0x7f83a33083e0, res=0x7fff25b75d90, rve=0x7f83a32d91f0) at rvalue.c:1918 #18 0x0041ce4e in do_action (h=0x7fff25b774c0, a=0x7f83a32d9d58, msg=0x7f83a33083e0) at action.c:1064 #19 0x00429a7a in run_actions (h=0x7fff25b774c0, a=0x7f83a32d9d58, msg=0x7f83a33083e0) at action.c:1583 #20 0x00419dea in do_action (h=0x7fff25b774c0, a=0x7f83a32c9048, msg=0x7f83a33083e0) at action.c:712 #21 0x00429a7a in run_actions (h=0x7fff25b774c0, a=0x7f83a32c3cd8, msg=0x7f83a33083e0) at action.c:1583 #22 0x00419dea in do_action (h=0x7fff25b774c0, a=0x7f83a328d418, msg=0x7f83a33083e0) at action.c:712 #23 0x00429a7a in run_actions (h=0x7fff25b774c0, a=0x7f83a328d418, msg=0x7f83a33083e0) at action.c:1583 #24 0x0041d2cd in do_action (h=0x7fff25b774c0, a=0x7f83a328d658, msg=0x7f83a33083e0) at action.c:1079 #25 0x00429a7a in run_actions (h=0x7fff25b774c0, a=0x7f83a327d898, msg=0x7f83a33083e0) at action.c:1583 #26 0x0042a1a7 in run_top_route (a=0x7f83a327d898, msg=0x7f83a33083e0, c=0x0) at action.c:1669 #27 0x0050747e in receive_msg ( buf=0xa6f780 INVITE sip:XX@XXX SIP/2.0\r\nRecord-Route: sip:X;lr\r\nVia: SIP/2.0/UDP XXX;branch=z9hG4bK2be.f31409f558981039fd70ad46afc97176.0\r\nVia: SIP/2.0/UDP ..., len=1151, rcv_info=0x7fff25b777b0) at receive.c:216 #28 0x00606e76 in udp_rcv_loop () at udp_server.c:521 #29 0x004a5c97 in main_loop () at main.c:1629 #30 0x004aaf2a in main (argc=13, argv=0x7fff25b77bc8) at main.c:2561 I can try to reproduce the issue with the REGISTER if you need. Mickael *From:* sr-users [mailto:sr-users-boun...@lists.sip-router.org] *On Behalf Of *Daniel-Constantin Mierla *Sent:* Thursday, January 29, 2015 12:26 PM *To:* Kamailio (SER) - Users Mailing List *Subject:* Re: [SR-Users] Core dump while saving user location in mongo Also, give the error messages from syslog file. Cheers, Daniel On 29/01/15 11:23, Daniel-Constantin Mierla wrote: Hello, can you give the parameters for usrloc module? Are you using DB_ONLY mode? Cheers, Daniel On 29/01/15 08:55, Mickael Marrache wrote: Hi, When my proxy receives a REGISTER request, it crashes while saving the user location in MongoDB. This is the backtrace from the core dump: #0 0x003f08e32625 in raise () from /lib64/libc.so.6 #1 0x003f08e33e05 in abort () from /lib64/libc.so.6 #2 0x006196f9 in fm_free (qm=0x7f4368bf7010, p=0x210add0, file=0x7f4367fd7608 core: db_res.c, func=0x7f4367fd8100 db_free_columns, line=86) at mem/f_malloc.c:588 #3 0x7f4367fc37ab in db_free_columns (_r=0x7f4368ca0430) at db_res.c:86 #4 0x7f4367fc479e in db_free_result (_r=0x7f4368ca0430) at db_res.c:134 #5 0x7f4367da37cb in db_mongodb_free_result (_h=0x7f4368c94718, _r=0x7f4368ca0430) at mongodb_dbase.c:646 #6 0x7f4367da5d65 in db_mongodb_query (_h=0x7f4368c94718, _k=0x7fffa03d5550, _op=0x0, _v=0x7fffa03d5510, _c=0x7fffa03d5560, _n=1, _nc=16, _o=0x7f4365ed2c80, _r=0x7fffa03d5508) at mongodb_dbase.c:783 #7 0x7f4365cac7d2 in db_load_urecord (_c=0x7f4368c94718, _d=0x7f436154a0e8, _aor=0x7fffa03d59d0) at udomain.c:601 #8 0x7f4365cb1e8e in get_urecord (_d=0x7f436154a0e8, _aor=0x7fffa03d59d0, _r=0x7fffa03d5760) at udomain.c:1106 #9 0x7f4365a75dea in add_contacts (_m=0x7f4368cbdc40, _d=0x7f436154a0e8, _a=0x7fffa03d59d0, _mode=1, _use_regid=1) at save.c:832 #10 0x7f4365a77d32 in save (_m=0x7f4368cbdc40, _d=0x7f436154a0e8, _cflags=4, _uri=0x0) at save.c:986 #11 0x7f4365a606db in w_save2 (_m=0x7f4368cbdc40, _d=0x7f436154a0e8 H\240TaC\177, _cflags=0x4 Address 0x4 out of bounds) at reg_mod.c:447 #12 0x0041d489 in do_action (h=0x7fffa03d6180, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1100 #13 0x00429a7a in run_actions (h=0x7fffa03d6180, a=0x7f4368c71e98, msg=0x7f4368cbdc40) at action.c:1583 #14 0x0042a0df in run_actions_safe (h=0x7fffa03d7470
Re: [SR-Users] Core Dump from select stmt
The fix fixed the problem with the select but I am still getting core dumps. This looks like when an Option request comes in. I have included the back trace from the core files. Thanks Nathaniel On 4/19/2012 10:16 AM, Akan wrote: The fix resolved the problem. Thanks Nathaniel On 4/18/2012 3:03 AM, Daniel-Constantin Mierla wrote: Hello, On 4/17/12 4:52 AM, Akan wrote: Sorry, I am new to git. What is the git command to add the patch or can I just download all of the updates? you can download now all updates if you install latest git branch 3.2: * http://www.kamailio.org/wiki/install/3.2.x/git For backporting patches, here are some guidelines: * http://www.kamailio.org/wiki/devel/backporting-to-3.2.x Cheers, Daniel Thanks Nathaniel On 4/16/2012 8:31 AM, Daniel-Constantin Mierla wrote: Hello, the issue was produced inside the debugger module, while printing config trace, according to the worker process back trace. Can you try with the patch from following commit: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=40ddcf88df9ef71bba7c182b7a1d76b559645628 If all goes fine with it, I will backport to stable branch. Cheers, Daniel On 4/16/12 2:58 AM, Akan wrote: On Solaris they seem to manage core dumps a little differently. Only 3 processes produced core dumps. I have included the text files of the back trace. Thanks Nathaniel On 4/15/2012 5:34 AM, Daniel-Constantin Mierla wrote: Hello, this one seems from the main process during the shut down cleanup. Perhaps the core from main process overwritten the one from worker process. Can you enable one core file per process in Solaris? In linux is possible via: echo 1 /proc/sys/kernel/core_uses_pid Then you have to reproduce the case and get the backtraces from each corefile. Cheers, Daniel On 4/14/12 6:58 PM, Akan wrote: Here is the output from gdb that you requested: Core was generated by `./kamailio'. Program terminated with signal 10, Bus error. #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 306 old_string = *(char **)(block + group-var_offset + mapping[i].offset); (gdb) bt full #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 group = 0x1004e2528 def = value optimized out i = value optimized out group2 = value optimized out mapping = 0x1004e23d8 old_string = value optimized out #1 cfg_destroy () at cfg/cfg_struct.c:398 __FUNCTION__ = cfg_destroy #2 0x000100060d44 in cleanup (show_status=1) at main.c:553 memlog = value optimized out __FUNCTION__ = cleanup #3 0x000100061ae0 in shutdown_children (show_status=value optimized out, sig=15) at main.c:678 No locals. #4 0x000100063470 in handle_sigs () at main.c:769 chld = 0 chld_status = 0 memlog = value optimized out #5 0x000100066310 in main_loop () at main.c:1713 i = value optimized out pid = value optimized out si = value optimized out si_desc = udp receiver child=3 sock=209.252.110.38:5060\000óÐ\000\000\000\001\000BE\000\000\000\000\000\000\000\000\002\177ÿóÁ\000\000\000\001\000\037z\200, '\000' repeats 14 times, gÐÿÿÿýÿÿÿýÿÿÿýÿÿÿý #6 0x0001001f7e94 in main (argc=value optimized out, argv=value optimized out) at main.c:2475 cfg_stream = value optimized out c = value optimized out r = -1 tmp = 0x0 tmp_len = 0 options = 0x100222858 :f:cm:M:dVhEb:l:L:n:vrRDTN:W:w:t:u:g:P:G:SQ:O:a:A: seed = 660384647 rfd = value optimized out debug_save = value optimized out debug_flag = value optimized out dont_fork_cnt = value optimized out n_lst = 0x10 p = value optimized out (gdb) Thanks Nathaniel On 4/14/2012 3:10 AM, Daniel-Constantin Mierla wrote: Hello, from the log messages, you got a core dump file. Locate it (should be in / if you haven't specified -w 'path' or solaris does not have a special directory for corefiles) and get the back trace: gdb /path/to/kamailio /path/to/corefile Then inside gdb execute 'bt full' and send the output here. Cheers, Daniel On 4/14/12 2:56 AM, Akan Technology wrote: hello, I am running kamailio 3.2.2 on Solaris 10 64 bit and I am getting a core dump on this statement: $ru = sip: + $rU + @ + $sel(cfg_get.registrar1.server_ip) + $sel(cfg_get.registrar1.server_port); Here is how the variable is defined: registrar1.server_ip = xxx.xxx.xxx.xxx desc Registrar server IP address registrar1.server_port = 5080 desc Registrar server Port Here is the output from the logs with debug: 10(25373) ERROR: *** cfgtrace: c=[/opt/kamailio-3.2/etc/kamailio/kamailio.cfg] l=1072 a=65 n=assign 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b2bc0 10(25373) DEBUG: core [select.c:424]:
Re: [SR-Users] Core Dump from select stmt
The fix resolved the problem. Thanks Nathaniel On 4/18/2012 3:03 AM, Daniel-Constantin Mierla wrote: Hello, On 4/17/12 4:52 AM, Akan wrote: Sorry, I am new to git. What is the git command to add the patch or can I just download all of the updates? you can download now all updates if you install latest git branch 3.2: * http://www.kamailio.org/wiki/install/3.2.x/git For backporting patches, here are some guidelines: * http://www.kamailio.org/wiki/devel/backporting-to-3.2.x Cheers, Daniel Thanks Nathaniel On 4/16/2012 8:31 AM, Daniel-Constantin Mierla wrote: Hello, the issue was produced inside the debugger module, while printing config trace, according to the worker process back trace. Can you try with the patch from following commit: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=40ddcf88df9ef71bba7c182b7a1d76b559645628 If all goes fine with it, I will backport to stable branch. Cheers, Daniel On 4/16/12 2:58 AM, Akan wrote: On Solaris they seem to manage core dumps a little differently. Only 3 processes produced core dumps. I have included the text files of the back trace. Thanks Nathaniel On 4/15/2012 5:34 AM, Daniel-Constantin Mierla wrote: Hello, this one seems from the main process during the shut down cleanup. Perhaps the core from main process overwritten the one from worker process. Can you enable one core file per process in Solaris? In linux is possible via: echo 1 /proc/sys/kernel/core_uses_pid Then you have to reproduce the case and get the backtraces from each corefile. Cheers, Daniel On 4/14/12 6:58 PM, Akan wrote: Here is the output from gdb that you requested: Core was generated by `./kamailio'. Program terminated with signal 10, Bus error. #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 306 old_string = *(char **)(block + group-var_offset + mapping[i].offset); (gdb) bt full #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 group = 0x1004e2528 def = value optimized out i = value optimized out group2 = value optimized out mapping = 0x1004e23d8 old_string = value optimized out #1 cfg_destroy () at cfg/cfg_struct.c:398 __FUNCTION__ = cfg_destroy #2 0x000100060d44 in cleanup (show_status=1) at main.c:553 memlog = value optimized out __FUNCTION__ = cleanup #3 0x000100061ae0 in shutdown_children (show_status=value optimized out, sig=15) at main.c:678 No locals. #4 0x000100063470 in handle_sigs () at main.c:769 chld = 0 chld_status = 0 memlog = value optimized out #5 0x000100066310 in main_loop () at main.c:1713 i = value optimized out pid = value optimized out si = value optimized out si_desc = udp receiver child=3 sock=209.252.110.38:5060\000óÐ\000\000\000\001\000BE\000\000\000\000\000\000\000\000\002\177ÿóÁ\000\000\000\001\000\037z\200, '\000' repeats 14 times, gÐÿÿÿýÿÿÿýÿÿÿýÿÿÿý #6 0x0001001f7e94 in main (argc=value optimized out, argv=value optimized out) at main.c:2475 cfg_stream = value optimized out c = value optimized out r = -1 tmp = 0x0 tmp_len = 0 options = 0x100222858 :f:cm:M:dVhEb:l:L:n:vrRDTN:W:w:t:u:g:P:G:SQ:O:a:A: seed = 660384647 rfd = value optimized out debug_save = value optimized out debug_flag = value optimized out dont_fork_cnt = value optimized out n_lst = 0x10 p = value optimized out (gdb) Thanks Nathaniel On 4/14/2012 3:10 AM, Daniel-Constantin Mierla wrote: Hello, from the log messages, you got a core dump file. Locate it (should be in / if you haven't specified -w 'path' or solaris does not have a special directory for corefiles) and get the back trace: gdb /path/to/kamailio /path/to/corefile Then inside gdb execute 'bt full' and send the output here. Cheers, Daniel On 4/14/12 2:56 AM, Akan Technology wrote: hello, I am running kamailio 3.2.2 on Solaris 10 64 bit and I am getting a core dump on this statement: $ru = sip: + $rU + @ + $sel(cfg_get.registrar1.server_ip) + $sel(cfg_get.registrar1.server_port); Here is how the variable is defined: registrar1.server_ip = xxx.xxx.xxx.xxx desc Registrar server IP address registrar1.server_port = 5080 desc Registrar server Port Here is the output from the logs with debug: 10(25373) ERROR: *** cfgtrace: c=[/opt/kamailio-3.2/etc/kamailio/kamailio.cfg] l=1072 a=65 n=assign 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b2bc0 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b4da0 10(25373) ERROR: *** cfgtrace:14(25377) : core [pass_fd.c:293]: ERROR: receive_fd: EOF on 22 14(25377) DEBUG: core [tcp_main.c:3555]: DBG: handle_ser_child: dead child 10, pid 25373 (shutting down?) 14(25377)
Re: [SR-Users] Core Dump from select stmt
Hello, the issue was produced inside the debugger module, while printing config trace, according to the worker process back trace. Can you try with the patch from following commit: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=40ddcf88df9ef71bba7c182b7a1d76b559645628 If all goes fine with it, I will backport to stable branch. Cheers, Daniel On 4/16/12 2:58 AM, Akan wrote: On Solaris they seem to manage core dumps a little differently. Only 3 processes produced core dumps. I have included the text files of the back trace. Thanks Nathaniel On 4/15/2012 5:34 AM, Daniel-Constantin Mierla wrote: Hello, this one seems from the main process during the shut down cleanup. Perhaps the core from main process overwritten the one from worker process. Can you enable one core file per process in Solaris? In linux is possible via: echo 1 /proc/sys/kernel/core_uses_pid Then you have to reproduce the case and get the backtraces from each corefile. Cheers, Daniel On 4/14/12 6:58 PM, Akan wrote: Here is the output from gdb that you requested: Core was generated by `./kamailio'. Program terminated with signal 10, Bus error. #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 306 old_string = *(char **)(block + group-var_offset + mapping[i].offset); (gdb) bt full #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 group = 0x1004e2528 def = value optimized out i = value optimized out group2 = value optimized out mapping = 0x1004e23d8 old_string = value optimized out #1 cfg_destroy () at cfg/cfg_struct.c:398 __FUNCTION__ = cfg_destroy #2 0x000100060d44 in cleanup (show_status=1) at main.c:553 memlog = value optimized out __FUNCTION__ = cleanup #3 0x000100061ae0 in shutdown_children (show_status=value optimized out, sig=15) at main.c:678 No locals. #4 0x000100063470 in handle_sigs () at main.c:769 chld = 0 chld_status = 0 memlog = value optimized out #5 0x000100066310 in main_loop () at main.c:1713 i = value optimized out pid = value optimized out si = value optimized out si_desc = udp receiver child=3 sock=209.252.110.38:5060\000óÐ\000\000\000\001\000BE\000\000\000\000\000\000\000\000\002\177ÿóÁ\000\000\000\001\000\037z\200, '\000' repeats 14 times, gÐÿÿÿýÿÿÿýÿÿÿýÿÿÿý #6 0x0001001f7e94 in main (argc=value optimized out, argv=value optimized out) at main.c:2475 cfg_stream = value optimized out c = value optimized out r = -1 tmp = 0x0 tmp_len = 0 options = 0x100222858 :f:cm:M:dVhEb:l:L:n:vrRDTN:W:w:t:u:g:P:G:SQ:O:a:A: seed = 660384647 rfd = value optimized out debug_save = value optimized out debug_flag = value optimized out dont_fork_cnt = value optimized out n_lst = 0x10 p = value optimized out (gdb) Thanks Nathaniel On 4/14/2012 3:10 AM, Daniel-Constantin Mierla wrote: Hello, from the log messages, you got a core dump file. Locate it (should be in / if you haven't specified -w 'path' or solaris does not have a special directory for corefiles) and get the back trace: gdb /path/to/kamailio /path/to/corefile Then inside gdb execute 'bt full' and send the output here. Cheers, Daniel On 4/14/12 2:56 AM, Akan Technology wrote: hello, I am running kamailio 3.2.2 on Solaris 10 64 bit and I am getting a core dump on this statement: $ru = sip: + $rU + @ + $sel(cfg_get.registrar1.server_ip) + $sel(cfg_get.registrar1.server_port); Here is how the variable is defined: registrar1.server_ip = xxx.xxx.xxx.xxx desc Registrar server IP address registrar1.server_port = 5080 desc Registrar server Port Here is the output from the logs with debug: 10(25373) ERROR: *** cfgtrace: c=[/opt/kamailio-3.2/etc/kamailio/kamailio.cfg] l=1072 a=65 n=assign 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b2bc0 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b4da0 10(25373) ERROR: *** cfgtrace:14(25377) : core [pass_fd.c:293]: ERROR: receive_fd: EOF on 22 14(25377) DEBUG: core [tcp_main.c:3555]: DBG: handle_ser_child: dead child 10, pid 25373 (shutting down?) 14(25377) DEBUG: core [io_wait.h:617]: DBG: io_watch_del (1003738b8, 22, 0, 0x0) fd_no=18 called 14(25377) DEBUG: core [tcp_main.c:3316]: DBG: handle_tcp_child: dead tcp child 0 (pid 25373, no 10) (shutting down?) 14(25377) DEBUG: core [io_wait.h:617]: DBG: io_watch_del (1003738b8, 24, 1, 0x0) fd_no=17 called 0(25363) ALERT: core [main.c:751]: child process 25373 exited by a signal 11 0(25363) ALERT: core [main.c:754]: core was generated 0(25363) INFO: core [main.c:766]: INFO: terminating due to SIGCHLD 14(25377) INFO: core [main.c:817]: INFO: signal 15 received Here is the full route
Re: [SR-Users] Core Dump from select stmt
Sorry, I am new to git. What is the git command to add the patch or can I just download all of the updates? Thanks Nathaniel On 4/16/2012 8:31 AM, Daniel-Constantin Mierla wrote: Hello, the issue was produced inside the debugger module, while printing config trace, according to the worker process back trace. Can you try with the patch from following commit: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=40ddcf88df9ef71bba7c182b7a1d76b559645628 If all goes fine with it, I will backport to stable branch. Cheers, Daniel On 4/16/12 2:58 AM, Akan wrote: On Solaris they seem to manage core dumps a little differently. Only 3 processes produced core dumps. I have included the text files of the back trace. Thanks Nathaniel On 4/15/2012 5:34 AM, Daniel-Constantin Mierla wrote: Hello, this one seems from the main process during the shut down cleanup. Perhaps the core from main process overwritten the one from worker process. Can you enable one core file per process in Solaris? In linux is possible via: echo 1 /proc/sys/kernel/core_uses_pid Then you have to reproduce the case and get the backtraces from each corefile. Cheers, Daniel On 4/14/12 6:58 PM, Akan wrote: Here is the output from gdb that you requested: Core was generated by `./kamailio'. Program terminated with signal 10, Bus error. #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 306 old_string = *(char **)(block + group-var_offset + mapping[i].offset); (gdb) bt full #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 group = 0x1004e2528 def = value optimized out i = value optimized out group2 = value optimized out mapping = 0x1004e23d8 old_string = value optimized out #1 cfg_destroy () at cfg/cfg_struct.c:398 __FUNCTION__ = cfg_destroy #2 0x000100060d44 in cleanup (show_status=1) at main.c:553 memlog = value optimized out __FUNCTION__ = cleanup #3 0x000100061ae0 in shutdown_children (show_status=value optimized out, sig=15) at main.c:678 No locals. #4 0x000100063470 in handle_sigs () at main.c:769 chld = 0 chld_status = 0 memlog = value optimized out #5 0x000100066310 in main_loop () at main.c:1713 i = value optimized out pid = value optimized out si = value optimized out si_desc = udp receiver child=3 sock=209.252.110.38:5060\000óÐ\000\000\000\001\000BE\000\000\000\000\000\000\000\000\002\177ÿóÁ\000\000\000\001\000\037z\200, '\000' repeats 14 times, gÐÿÿÿýÿÿÿýÿÿÿýÿÿÿý #6 0x0001001f7e94 in main (argc=value optimized out, argv=value optimized out) at main.c:2475 cfg_stream = value optimized out c = value optimized out r = -1 tmp = 0x0 tmp_len = 0 options = 0x100222858 :f:cm:M:dVhEb:l:L:n:vrRDTN:W:w:t:u:g:P:G:SQ:O:a:A: seed = 660384647 rfd = value optimized out debug_save = value optimized out debug_flag = value optimized out dont_fork_cnt = value optimized out n_lst = 0x10 p = value optimized out (gdb) Thanks Nathaniel On 4/14/2012 3:10 AM, Daniel-Constantin Mierla wrote: Hello, from the log messages, you got a core dump file. Locate it (should be in / if you haven't specified -w 'path' or solaris does not have a special directory for corefiles) and get the back trace: gdb /path/to/kamailio /path/to/corefile Then inside gdb execute 'bt full' and send the output here. Cheers, Daniel On 4/14/12 2:56 AM, Akan Technology wrote: hello, I am running kamailio 3.2.2 on Solaris 10 64 bit and I am getting a core dump on this statement: $ru = sip: + $rU + @ + $sel(cfg_get.registrar1.server_ip) + $sel(cfg_get.registrar1.server_port); Here is how the variable is defined: registrar1.server_ip = xxx.xxx.xxx.xxx desc Registrar server IP address registrar1.server_port = 5080 desc Registrar server Port Here is the output from the logs with debug: 10(25373) ERROR: *** cfgtrace: c=[/opt/kamailio-3.2/etc/kamailio/kamailio.cfg] l=1072 a=65 n=assign 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b2bc0 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b4da0 10(25373) ERROR: *** cfgtrace:14(25377) : core [pass_fd.c:293]: ERROR: receive_fd: EOF on 22 14(25377) DEBUG: core [tcp_main.c:3555]: DBG: handle_ser_child: dead child 10, pid 25373 (shutting down?) 14(25377) DEBUG: core [io_wait.h:617]: DBG: io_watch_del (1003738b8, 22, 0, 0x0) fd_no=18 called 14(25377) DEBUG: core [tcp_main.c:3316]: DBG: handle_tcp_child: dead tcp child 0 (pid 25373, no 10) (shutting down?) 14(25377) DEBUG: core [io_wait.h:617]: DBG: io_watch_del (1003738b8, 24, 1, 0x0) fd_no=17 called 0(25363) ALERT: core [main.c:751]: child process 25373 exited by a signal 11 0(25363) ALERT: core
Re: [SR-Users] Core Dump from select stmt
Hello, this one seems from the main process during the shut down cleanup. Perhaps the core from main process overwritten the one from worker process. Can you enable one core file per process in Solaris? In linux is possible via: echo 1 /proc/sys/kernel/core_uses_pid Then you have to reproduce the case and get the backtraces from each corefile. Cheers, Daniel On 4/14/12 6:58 PM, Akan wrote: Here is the output from gdb that you requested: Core was generated by `./kamailio'. Program terminated with signal 10, Bus error. #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 306 old_string = *(char **)(block + group-var_offset + mapping[i].offset); (gdb) bt full #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 group = 0x1004e2528 def = value optimized out i = value optimized out group2 = value optimized out mapping = 0x1004e23d8 old_string = value optimized out #1 cfg_destroy () at cfg/cfg_struct.c:398 __FUNCTION__ = cfg_destroy #2 0x000100060d44 in cleanup (show_status=1) at main.c:553 memlog = value optimized out __FUNCTION__ = cleanup #3 0x000100061ae0 in shutdown_children (show_status=value optimized out, sig=15) at main.c:678 No locals. #4 0x000100063470 in handle_sigs () at main.c:769 chld = 0 chld_status = 0 memlog = value optimized out #5 0x000100066310 in main_loop () at main.c:1713 i = value optimized out pid = value optimized out si = value optimized out si_desc = udp receiver child=3 sock=209.252.110.38:5060\000óÐ\000\000\000\001\000BE\000\000\000\000\000\000\000\000\002\177ÿóÁ\000\000\000\001\000\037z\200, '\000' repeats 14 times, gÐÿÿÿýÿÿÿýÿÿÿýÿÿÿý #6 0x0001001f7e94 in main (argc=value optimized out, argv=value optimized out) at main.c:2475 cfg_stream = value optimized out c = value optimized out r = -1 tmp = 0x0 tmp_len = 0 options = 0x100222858 :f:cm:M:dVhEb:l:L:n:vrRDTN:W:w:t:u:g:P:G:SQ:O:a:A: seed = 660384647 rfd = value optimized out debug_save = value optimized out debug_flag = value optimized out dont_fork_cnt = value optimized out n_lst = 0x10 p = value optimized out (gdb) Thanks Nathaniel On 4/14/2012 3:10 AM, Daniel-Constantin Mierla wrote: Hello, from the log messages, you got a core dump file. Locate it (should be in / if you haven't specified -w 'path' or solaris does not have a special directory for corefiles) and get the back trace: gdb /path/to/kamailio /path/to/corefile Then inside gdb execute 'bt full' and send the output here. Cheers, Daniel On 4/14/12 2:56 AM, Akan Technology wrote: hello, I am running kamailio 3.2.2 on Solaris 10 64 bit and I am getting a core dump on this statement: $ru = sip: + $rU + @ + $sel(cfg_get.registrar1.server_ip) + $sel(cfg_get.registrar1.server_port); Here is how the variable is defined: registrar1.server_ip = xxx.xxx.xxx.xxx desc Registrar server IP address registrar1.server_port = 5080 desc Registrar server Port Here is the output from the logs with debug: 10(25373) ERROR: *** cfgtrace: c=[/opt/kamailio-3.2/etc/kamailio/kamailio.cfg] l=1072 a=65 n=assign 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b2bc0 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b4da0 10(25373) ERROR: *** cfgtrace:14(25377) : core [pass_fd.c:293]: ERROR: receive_fd: EOF on 22 14(25377) DEBUG: core [tcp_main.c:3555]: DBG: handle_ser_child: dead child 10, pid 25373 (shutting down?) 14(25377) DEBUG: core [io_wait.h:617]: DBG: io_watch_del (1003738b8, 22, 0, 0x0) fd_no=18 called 14(25377) DEBUG: core [tcp_main.c:3316]: DBG: handle_tcp_child: dead tcp child 0 (pid 25373, no 10) (shutting down?) 14(25377) DEBUG: core [io_wait.h:617]: DBG: io_watch_del (1003738b8, 24, 1, 0x0) fd_no=17 called 0(25363) ALERT: core [main.c:751]: child process 25373 exited by a signal 11 0(25363) ALERT: core [main.c:754]: core was generated 0(25363) INFO: core [main.c:766]: INFO: terminating due to SIGCHLD 14(25377) INFO: core [main.c:817]: INFO: signal 15 received Here is the full route code: route[TO_REGISTRAR] { # check if Registrar server's IP is defined if (strempty($sel(cfg_get.registrar1.server_ip))) { xlog(SCRIPT: REGISTRAR - registrar1.server_ip not defined\n); return; } $ru = sip: + $rU + @ + $sel(cfg_get.registrar1.server_ip) + : + $sel(cfg_get.registrar1.server_port); route(RELAY); exit; } # End of TO_Registrar Route I am trying to setup the proxy server to route all registers requests to another kamailio server Thanks Nathaniel
Re: [SR-Users] Core Dump from select stmt
On Solaris they seem to manage core dumps a little differently. Only 3 processes produced core dumps. I have included the text files of the back trace. Thanks Nathaniel On 4/15/2012 5:34 AM, Daniel-Constantin Mierla wrote: Hello, this one seems from the main process during the shut down cleanup. Perhaps the core from main process overwritten the one from worker process. Can you enable one core file per process in Solaris? In linux is possible via: echo 1 /proc/sys/kernel/core_uses_pid Then you have to reproduce the case and get the backtraces from each corefile. Cheers, Daniel On 4/14/12 6:58 PM, Akan wrote: Here is the output from gdb that you requested: Core was generated by `./kamailio'. Program terminated with signal 10, Bus error. #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 306 old_string = *(char **)(block + group-var_offset + mapping[i].offset); (gdb) bt full #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 group = 0x1004e2528 def = value optimized out i = value optimized out group2 = value optimized out mapping = 0x1004e23d8 old_string = value optimized out #1 cfg_destroy () at cfg/cfg_struct.c:398 __FUNCTION__ = cfg_destroy #2 0x000100060d44 in cleanup (show_status=1) at main.c:553 memlog = value optimized out __FUNCTION__ = cleanup #3 0x000100061ae0 in shutdown_children (show_status=value optimized out, sig=15) at main.c:678 No locals. #4 0x000100063470 in handle_sigs () at main.c:769 chld = 0 chld_status = 0 memlog = value optimized out #5 0x000100066310 in main_loop () at main.c:1713 i = value optimized out pid = value optimized out si = value optimized out si_desc = udp receiver child=3 sock=209.252.110.38:5060\000óÐ\000\000\000\001\000BE\000\000\000\000\000\000\000\000\002\177ÿóÁ\000\000\000\001\000\037z\200, '\000' repeats 14 times, gÐÿÿÿýÿÿÿýÿÿÿýÿÿÿý #6 0x0001001f7e94 in main (argc=value optimized out, argv=value optimized out) at main.c:2475 cfg_stream = value optimized out c = value optimized out r = -1 tmp = 0x0 tmp_len = 0 options = 0x100222858 :f:cm:M:dVhEb:l:L:n:vrRDTN:W:w:t:u:g:P:G:SQ:O:a:A: seed = 660384647 rfd = value optimized out debug_save = value optimized out debug_flag = value optimized out dont_fork_cnt = value optimized out n_lst = 0x10 p = value optimized out (gdb) Thanks Nathaniel On 4/14/2012 3:10 AM, Daniel-Constantin Mierla wrote: Hello, from the log messages, you got a core dump file. Locate it (should be in / if you haven't specified -w 'path' or solaris does not have a special directory for corefiles) and get the back trace: gdb /path/to/kamailio /path/to/corefile Then inside gdb execute 'bt full' and send the output here. Cheers, Daniel On 4/14/12 2:56 AM, Akan Technology wrote: hello, I am running kamailio 3.2.2 on Solaris 10 64 bit and I am getting a core dump on this statement: $ru = sip: + $rU + @ + $sel(cfg_get.registrar1.server_ip) + $sel(cfg_get.registrar1.server_port); Here is how the variable is defined: registrar1.server_ip = xxx.xxx.xxx.xxx desc Registrar server IP address registrar1.server_port = 5080 desc Registrar server Port Here is the output from the logs with debug: 10(25373) ERROR: *** cfgtrace: c=[/opt/kamailio-3.2/etc/kamailio/kamailio.cfg] l=1072 a=65 n=assign 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b2bc0 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b4da0 10(25373) ERROR: *** cfgtrace:14(25377) : core [pass_fd.c:293]: ERROR: receive_fd: EOF on 22 14(25377) DEBUG: core [tcp_main.c:3555]: DBG: handle_ser_child: dead child 10, pid 25373 (shutting down?) 14(25377) DEBUG: core [io_wait.h:617]: DBG: io_watch_del (1003738b8, 22, 0, 0x0) fd_no=18 called 14(25377) DEBUG: core [tcp_main.c:3316]: DBG: handle_tcp_child: dead tcp child 0 (pid 25373, no 10) (shutting down?) 14(25377) DEBUG: core [io_wait.h:617]: DBG: io_watch_del (1003738b8, 24, 1, 0x0) fd_no=17 called 0(25363) ALERT: core [main.c:751]: child process 25373 exited by a signal 11 0(25363) ALERT: core [main.c:754]: core was generated 0(25363) INFO: core [main.c:766]: INFO: terminating due to SIGCHLD 14(25377) INFO: core [main.c:817]: INFO: signal 15 received Here is the full route code: route[TO_REGISTRAR] { # check if Registrar server's IP is defined if (strempty($sel(cfg_get.registrar1.server_ip))) { xlog(SCRIPT: REGISTRAR - registrar1.server_ip not defined\n); return; } $ru = sip: + $rU + @ + $sel(cfg_get.registrar1.server_ip) + : + $sel(cfg_get.registrar1.server_port);
Re: [SR-Users] Core Dump from select stmt
Hello, from the log messages, you got a core dump file. Locate it (should be in / if you haven't specified -w 'path' or solaris does not have a special directory for corefiles) and get the back trace: gdb /path/to/kamailio /path/to/corefile Then inside gdb execute 'bt full' and send the output here. Cheers, Daniel On 4/14/12 2:56 AM, Akan Technology wrote: hello, I am running kamailio 3.2.2 on Solaris 10 64 bit and I am getting a core dump on this statement: $ru = sip: + $rU + @ + $sel(cfg_get.registrar1.server_ip) + $sel(cfg_get.registrar1.server_port); Here is how the variable is defined: registrar1.server_ip = xxx.xxx.xxx.xxx desc Registrar server IP address registrar1.server_port = 5080 desc Registrar server Port Here is the output from the logs with debug: 10(25373) ERROR: *** cfgtrace: c=[/opt/kamailio-3.2/etc/kamailio/kamailio.cfg] l=1072 a=65 n=assign 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b2bc0 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b4da0 10(25373) ERROR: *** cfgtrace:14(25377) : core [pass_fd.c:293]: ERROR: receive_fd: EOF on 22 14(25377) DEBUG: core [tcp_main.c:3555]: DBG: handle_ser_child: dead child 10, pid 25373 (shutting down?) 14(25377) DEBUG: core [io_wait.h:617]: DBG: io_watch_del (1003738b8, 22, 0, 0x0) fd_no=18 called 14(25377) DEBUG: core [tcp_main.c:3316]: DBG: handle_tcp_child: dead tcp child 0 (pid 25373, no 10) (shutting down?) 14(25377) DEBUG: core [io_wait.h:617]: DBG: io_watch_del (1003738b8, 24, 1, 0x0) fd_no=17 called 0(25363) ALERT: core [main.c:751]: child process 25373 exited by a signal 11 0(25363) ALERT: core [main.c:754]: core was generated 0(25363) INFO: core [main.c:766]: INFO: terminating due to SIGCHLD 14(25377) INFO: core [main.c:817]: INFO: signal 15 received Here is the full route code: route[TO_REGISTRAR] { # check if Registrar server's IP is defined if (strempty($sel(cfg_get.registrar1.server_ip))) { xlog(SCRIPT: REGISTRAR - registrar1.server_ip not defined\n); return; } $ru = sip: + $rU + @ + $sel(cfg_get.registrar1.server_ip) + : + $sel(cfg_get.registrar1.server_port); route(RELAY); exit; } # End of TO_Registrar Route I am trying to setup the proxy server to route all registers requests to another kamailio server Thanks Nathaniel ___ 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 Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany http://www.asipto.com/index.php/kamailio-advanced-training/ ___ 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
Re: [SR-Users] Core Dump from select stmt
Here is the output from gdb that you requested: Core was generated by `./kamailio'. Program terminated with signal 10, Bus error. #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 306 old_string = *(char **)(block + group-var_offset + mapping[i].offset); (gdb) bt full #0 0x0001001c9ff0 in cfg_destory_groups () at cfg/cfg_struct.c:306 group = 0x1004e2528 def = value optimized out i = value optimized out group2 = value optimized out mapping = 0x1004e23d8 old_string = value optimized out #1 cfg_destroy () at cfg/cfg_struct.c:398 __FUNCTION__ = cfg_destroy #2 0x000100060d44 in cleanup (show_status=1) at main.c:553 memlog = value optimized out __FUNCTION__ = cleanup #3 0x000100061ae0 in shutdown_children (show_status=value optimized out, sig=15) at main.c:678 No locals. #4 0x000100063470 in handle_sigs () at main.c:769 chld = 0 chld_status = 0 memlog = value optimized out #5 0x000100066310 in main_loop () at main.c:1713 i = value optimized out pid = value optimized out si = value optimized out si_desc = udp receiver child=3 sock=209.252.110.38:5060\000óÐ\000\000\000\001\000BE\000\000\000\000\000\000\000\000\002\177ÿóÁ\000\000\000\001\000\037z\200, '\000' repeats 14 times, gÐÿÿÿýÿÿÿýÿÿÿýÿÿÿý #6 0x0001001f7e94 in main (argc=value optimized out, argv=value optimized out) at main.c:2475 cfg_stream = value optimized out c = value optimized out r = -1 tmp = 0x0 tmp_len = 0 options = 0x100222858 :f:cm:M:dVhEb:l:L:n:vrRDTN:W:w:t:u:g:P:G:SQ:O:a:A: seed = 660384647 rfd = value optimized out debug_save = value optimized out debug_flag = value optimized out dont_fork_cnt = value optimized out n_lst = 0x10 p = value optimized out (gdb) Thanks Nathaniel On 4/14/2012 3:10 AM, Daniel-Constantin Mierla wrote: Hello, from the log messages, you got a core dump file. Locate it (should be in / if you haven't specified -w 'path' or solaris does not have a special directory for corefiles) and get the back trace: gdb /path/to/kamailio /path/to/corefile Then inside gdb execute 'bt full' and send the output here. Cheers, Daniel On 4/14/12 2:56 AM, Akan Technology wrote: hello, I am running kamailio 3.2.2 on Solaris 10 64 bit and I am getting a core dump on this statement: $ru = sip: + $rU + @ + $sel(cfg_get.registrar1.server_ip) + $sel(cfg_get.registrar1.server_port); Here is how the variable is defined: registrar1.server_ip = xxx.xxx.xxx.xxx desc Registrar server IP address registrar1.server_port = 5080 desc Registrar server Port Here is the output from the logs with debug: 10(25373) ERROR: *** cfgtrace: c=[/opt/kamailio-3.2/etc/kamailio/kamailio.cfg] l=1072 a=65 n=assign 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b2bc0 10(25373) DEBUG: core [select.c:424]: Calling SELECT 1004b4da0 10(25373) ERROR: *** cfgtrace:14(25377) : core [pass_fd.c:293]: ERROR: receive_fd: EOF on 22 14(25377) DEBUG: core [tcp_main.c:3555]: DBG: handle_ser_child: dead child 10, pid 25373 (shutting down?) 14(25377) DEBUG: core [io_wait.h:617]: DBG: io_watch_del (1003738b8, 22, 0, 0x0) fd_no=18 called 14(25377) DEBUG: core [tcp_main.c:3316]: DBG: handle_tcp_child: dead tcp child 0 (pid 25373, no 10) (shutting down?) 14(25377) DEBUG: core [io_wait.h:617]: DBG: io_watch_del (1003738b8, 24, 1, 0x0) fd_no=17 called 0(25363) ALERT: core [main.c:751]: child process 25373 exited by a signal 11 0(25363) ALERT: core [main.c:754]: core was generated 0(25363) INFO: core [main.c:766]: INFO: terminating due to SIGCHLD 14(25377) INFO: core [main.c:817]: INFO: signal 15 received Here is the full route code: route[TO_REGISTRAR] { # check if Registrar server's IP is defined if (strempty($sel(cfg_get.registrar1.server_ip))) { xlog(SCRIPT: REGISTRAR - registrar1.server_ip not defined\n); return; } $ru = sip: + $rU + @ + $sel(cfg_get.registrar1.server_ip) + : + $sel(cfg_get.registrar1.server_port); route(RELAY); exit; } # End of TO_Registrar Route I am trying to setup the proxy server to route all registers requests to another kamailio server Thanks Nathaniel ___ 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 ___ 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
Re: [SR-Users] core dump
Thanks Klaus, I found the commit which is included in release 3.1.3. We've upgraded some hours ago and no crash at the moment (so no core dump is neither generated). I'll let you know about this issue. Regards, Ricardo -Mensaje original- De: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] En nombre de Klaus Darilion Enviado el: miércoles, 11 de mayo de 2011 11:40 Para: sr-users@lists.sip-router.org Asunto: Re: [SR-Users] core dump IIRC there were some changes in recent kernels which needs some more tweaking (there was a commit from Daniel, but I can't remember the details) regards Klaus Am 11.05.2011 10:28, schrieb Dominguez Jover, Ricardo: Hi everybody, We are having an uncontrolled crash in Kamailio 3.1: May 10 20:34:51 tip1 /usr/local/kamailio-3.1/sbin/kamailio[23366]: : core [pass_fd.c:293]: ERROR: receive_fd: EOF on 39 May 10 20:34:51 tip1 /usr/local/kamailio-3.1/sbin/kamailio[23327]: ALERT: core [main.c:741]: child process 23364 exited by a signal 11 May 10 20:34:51 tip1 /usr/local/kamailio-3.1/sbin/kamailio[23327]: ALERT: core [main.c:744]: core was not generated I've read in several posts I must generate the Core Dump to know what is happening. I'm trying to generate it in this way. /etc/init.d/Kamailio file: if test $DUMP_CORE = yes ; then 1. set proper ulimit ulimit -c unlimited directory for the core dump files COREDIR=/dumps/ [ -d $COREDIR ] || mkdir $COREDIR chmod 777 $COREDIR echo $COREDIR/core.%e.sig%s.%p /proc/sys/kernel/core_pattern fi /etc/default/Kamailio file: DUMP_CORE=yes But the core is not yet generated. Then I've added -w option: OPTIONS=-P $PID_FILE -m $MEMORY -u $USER -g $GROUP -w /dumps/ But core still not generated In kamailio.cfg I´ve also added: disable_core_dump=no User running Kamailio is kamailio who has 777 permissions in /dumps/ directory. No way. Anyhelp would be appreciated. Cheers, Ricardo Domínguez ___ 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 ___ 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 ___ 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
Re: [SR-Users] core dump
Hi, I also have the same problem with kamailio 3.1 I made a modification to the file daemonize.c because if lim.rlim_cur is set to -1 the test with size parameter at line 491 do not work because rlimit parameters are unsigned int. --- kamailio-3.1.0/daemonize.c.ori 2011-04-12 12:24:14.0 +0200 +++ kamailio-3.1.0/daemonize.c 2011-04-12 12:24:57.0 +0200 @@ -488,7 +488,7 @@ strerror(errno)); goto error; } - if (lim.rlim_cursize){ + if ((int)lim.rlim_cursize){ /* first try max limits */ newlim.rlim_max=RLIM_INFINITY; newlim.rlim_cur=newlim.rlim_max; Thanks to this patch the core dump should be generated. This work for me on my testing servers, BUT with my production servers (debian 5.0.1) where the core is not generated and I cannot understand why... Herv On 11/05/2011 10:28, Dominguez Jover, Ricardo wrote: Hi everybody, We are having an uncontrolled crash in Kamailio 3.1: May 10 20:34:51 tip1 /usr/local/kamailio-3.1/sbin/kamailio[23366]: : core [pass_fd.c:293]: ERROR: receive_fd: EOF on 39 May 10 20:34:51 tip1 /usr/local/kamailio-3.1/sbin/kamailio[23327]: ALERT: core [main.c:741]: child process 23364 exited by a signal 11 May 10 20:34:51 tip1 /usr/local/kamailio-3.1/sbin/kamailio[23327]: ALERT: core [main.c:744]: core was not generated I've read in several posts I must generate the "Core Dump" to know what is happening. I'm trying to generate it in this way. "/etc/init.d/Kamailio" file: if test "$DUMP_CORE" = "yes" ; then 1. set proper ulimit ulimit -c unlimited directory for the core dump files COREDIR=/dumps/ [ -d $COREDIR ] || mkdir $COREDIR chmod 777 $COREDIR echo "$COREDIR/core.%e.sig%s.%p" /proc/sys/kernel/core_pattern fi "/etc/default/Kamailio" file: DUMP_CORE=yes But the core is not yet generated. Then I've added -w option: OPTIONS="-P $PID_FILE -m $MEMORY -u $USER -g $GROUP -w /dumps/" But core still not generated In "kamailio.cfg" Ive also added: disable_core_dump=no User running Kamailio is "kamailio" who has 777 permissions in /dumps/ directory. No way. Anyhelp would be appreciated. Cheers, Ricardo Domnguez ___ 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 -- Herv COCHET. Ingnieur en dveloppement logiciel. Tel Direct: +33(0)482 531 303 TECHNOSENS SAS Donnons du sens la Technologie 31, rue Gustave Eiffel F-38000 Grenoble +33(0)476 230 240 www.technosens.fr Ce message et les documents l'accompagnant sont confidentiels. Ils contiennent des informations qui sont destines uniquement la personne ou l'entit dont le nom est indiqu ci-dessus. Toute reproduction, divulgation ou autre utilisation de ces informations, mme partiellement, par un autre destinataire est strictement interdite. Si ce message vous est parvenu par erreur, veuillez le dtruire immdiatement et nous le faire savoir par tlphone, Fax ou e-mail. ___ 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
Re: [SR-Users] core dump
Thanks Hervé. I'm using Kamailio 3.1.0 in a RHEL 5. Do you know if this issue is solved in Kamailio release 3.1.3? Cheers, Ricardo Domínguez De: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] En nombre de Hervé Cochet Enviado el: miércoles, 11 de mayo de 2011 11:20 Para: sr-users@lists.sip-router.org Asunto: Re: [SR-Users] core dump Hi, I also have the same problem with kamailio 3.1 I made a modification to the file daemonize.c because if lim.rlim_cur is set to -1 the test with size parameter at line 491 do not work because rlimit parameters are unsigned int. --- kamailio-3.1.0/daemonize.c.ori 2011-04-12 12:24:14.0 +0200 +++ kamailio-3.1.0/daemonize.c 2011-04-12 12:24:57.0 +0200 @@ -488,7 +488,7 @@ strerror(errno)); goto error; } - if (lim.rlim_cursize){ + if ((int)lim.rlim_cursize){ /* first try max limits */ newlim.rlim_max=RLIM_INFINITY; newlim.rlim_cur=newlim.rlim_max; Thanks to this patch the core dump should be generated. This work for me on my testing servers, BUT with my production servers (debian 5.0.1) where the core is not generated and I cannot understand why... Hervé On 11/05/2011 10:28, Dominguez Jover, Ricardo wrote: Hi everybody, We are having an uncontrolled crash in Kamailio 3.1: May 10 20:34:51 tip1 /usr/local/kamailio-3.1/sbin/kamailio[23366]: : core [pass_fd.c:293]: ERROR: receive_fd: EOF on 39 May 10 20:34:51 tip1 /usr/local/kamailio-3.1/sbin/kamailio[23327]: ALERT: core [main.c:741]: child process 23364 exited by a signal 11 May 10 20:34:51 tip1 /usr/local/kamailio-3.1/sbin/kamailio[23327]: ALERT: core [main.c:744]: core was not generated I've read in several posts I must generate the Core Dump to know what is happening. I'm trying to generate it in this way. /etc/init.d/Kamailio file: if test $DUMP_CORE = yes ; then 1. set proper ulimit ulimit -c unlimited directory for the core dump files COREDIR=/dumps/ [ -d $COREDIR ] || mkdir $COREDIR chmod 777 $COREDIR echo $COREDIR/core.%e.sig%s.%p /proc/sys/kernel/core_pattern fi /etc/default/Kamailio file: DUMP_CORE=yes But the core is not yet generated. Then I've added -w option: OPTIONS=-P $PID_FILE -m $MEMORY -u $USER -g $GROUP -w /dumps/ But core still not generated In kamailio.cfg I´ve also added: disable_core_dump=no User running Kamailio is kamailio who has 777 permissions in /dumps/ directory. No way. Anyhelp would be appreciated. Cheers, Ricardo Domínguez ___ 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 -- Hervé COCHET. Ingénieur en développement logiciel. Tel Direct: +33(0)482 531 303 TECHNOSENS SAS Donnons du sens à la Technologie 31, rue Gustave Eiffel F-38000 Grenoble +33(0)476 230 240 www.technosens.fr Ce message et les documents l'accompagnant sont confidentiels. Ils contiennent des informations qui sont destinées uniquement à la personne ou l'entité dont le nom est indiqué ci-dessus. Toute reproduction, divulgation ou autre utilisation de ces informations, même partiellement, par un autre destinataire est strictement interdite. Si ce message vous est parvenu par erreur, veuillez le détruire immédiatement et nous le faire savoir par téléphone, Fax ou e-mail. ___ 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