Hello Dev,
I have recently moved some traffic to kamailio-4.2 (installed on a seperate
box) and it crashes quite often. Below is the backtrace of the core files -
<CORE#1>
(gdb) bt
#0 0x00000033d8c32635 in raise () from /lib64/libc.so.6
#1 0x00000033d8c33e15 in abort () from /lib64/libc.so.6
#2 0x000000000049add5 in sig_alarm_abort (signo=14) at main.c:689
#3 <signal handler called>
#4 0x00000033d8ce50c7 in syscall () from /lib64/libc.so.6
#5 0x00007f7ca2ea0a1e in futex_get (lock=0x7f7ca3334388) at
../../mem/../futexlock.h:110
#6 0x00007f7ca2ea1e99 in remove_dialog_timer (tl=0x7f7ca3384c98) at
dlg_timer.c:168
#7 0x00007f7ca2e83e9b in destroy_dlg (dlg=0x7f7ca3384c40) at dlg_hash.c:357
#8 0x00007f7ca2e84e19 in destroy_dlg_table () at dlg_hash.c:438
#9 0x00007f7ca2e50b89 in mod_destroy () at dialog.c:773
#10 0x000000000058dfd5 in destroy_modules () at sr_module.c:818
#11 0x0000000000499ad3 in cleanup (show_status=1) at main.c:564
#12 0x000000000049b096 in shutdown_children (sig=15, show_status=1) at
main.c:706
#13 0x000000000049d66c in handle_sigs () at main.c:797
#14 0x00000000004a4e57 in main_loop () at main.c:1757
#15 0x00000000004a8a43 in main (argc=2, argv=0x7fff58d21368) at main.c:2609
(gdb) quit
<CORE#2>
(gdb) bt
#0 0x00007f7ca2ea22d7 in update_dlg_timer (tl=0x58, timeout=10) at
dlg_timer.c:203
#1 0x00007f7ca2e824f3 in dlg_clean_run (ti=44865910) at dlg_hash.c:253
#2 0x00007f7ca2e566fc in dlg_clean_timer_exec (ticks=44865910, param=0x0)
at dialog.c:1250
#3 0x00000000005f93e8 in fork_sync_timer (child_id=-1, desc=0x7f7ca2eb3a71
"Dialog Clean Timer", make_sock=1, f=0x7f7ca2e566e3 <dlg_clean_timer_exec>,
param=0x0,
interval=90) at timer_proc.c:232
#4 0x00007f7ca2e50476 in child_init (rank=0) at dialog.c:730
#5 0x000000000058e385 in init_mod_child (m=0x7f7ca8c09eb8, rank=0) at
sr_module.c:930
#6 0x000000000058e0c0 in init_mod_child (m=0x7f7ca8c0b000, rank=0) at
sr_module.c:927
#7 0x000000000058e68f in init_child (rank=0) at sr_module.c:957
#8 0x00000000004a435c in main_loop () at main.c:1705
#9 0x00000000004a8a43 in main (argc=2, argv=0x7fff58d21368) at main.c:2609
(gdb) quit
kamailio -v
version: kamailio 4.2.0-pre0 (x86_64/linux) a78764-dirty
flags: STATS: Off, USE_TCP, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST,
DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC,
USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER,
USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: a78764 -dirty
Kindly let me know which version to move.
--
Warm Regds.
MathuRahul
Dear Kamailio Developers:
Hi.
I have some questions about kamailio, and want to gain some suggestions from you.
1、The 4 UDP child processes are using system resources(CPU、memory), but they are using only one CPU core(I use 8 core CPU). Why?
2、The ablity of handling the Concurrency is alike, no matter how many UDP child processes I use. Why? And what's the effection of the other UDP child processes?
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Seudin Kasumovic (seudin)
Attached to Project - sip-router
Summary - Dialog state changed after restart Kamailio for db_mode=REALTIME
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - Low
Priority - Normal
Reported Version - 4.2
Due in Version - Undecided
Due Date - Undecided
Details - Dialog state changed after restart Kamailio.
Kamailio dialog module parameter db_mode is set to REALTIME
modparam("dialog", "db_mode", 1)
Before restart:
dialog:: hash=3921:4512
state:: 5
ref_count:: 2
timestart:: 1417012586
timeout:: 0
callid:: 1435233227(a)10.1.130.137
from_uri:: sip:1002@orange.voip
from_tag:: 603880624
caller_contact:: sip:1002@198.51.100.137:50508
caller_cseq:: 2
caller_route_set:: <sip:172.16.23.130;r2=on;st=on;ftag=603880624;lr>,<sip:192.0.2.130;transport=udp;r2=on;st=on;ftag=603880624;lr>
caller_bind_addr:: udp:172.16.23.130:5070
callee_bind_addr:: udp:172.16.23.130:5070
to_uri:: sip:*368@orange.voip
to_tag:: S0520657r5Ktc
callee_contact:: sip:milliwatt@127.0.0.1:5090;transport=udp
callee_cseq:: 0
callee_route_set::
After restart:
dialog:: hash=3921:4512
state:: 4
ref_count:: 2
timestart:: 1417012586
timeout:: 89692990
callid:: 1435233227(a)10.1.130.137
from_uri:: sip:1002@orange.voip
from_tag:: 603880624
caller_contact:: sip:1002@198.51.100.137:50508
caller_cseq:: 2
caller_route_set:: <sip:172.16.23.130;r2=on;st=on;ftag=603880624;lr>,<sip:192.0.2.130;transport=udp;r2=on;st=on;ftag=603880624;lr>
caller_bind_addr:: udp:172.16.23.130:5070
callee_bind_addr:: udp:172.16.23.130:5070
to_uri:: sip:*368@orange.voip
to_tag:: S0520657r5Ktc
callee_contact:: sip:milliwatt@127.0.0.1:5090;transport=udp
callee_cseq:: 0
callee_route_set::
version: kamailio 4.2.1 (i386/linux)
flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id:
compiled on 13:45:56 Nov 21 2014 with gcc 4.5.4
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=496
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#495 - Kamailio Crash in WEBSOCKET module
User who did this - Varghese Paul (varghesepaul87)
----------
ok. Thanks for the update. Can you confirm is this the crash is a known issue and it is fixed in the latest release ?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=495#comment1708
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#495 - Kamailio Crash in WEBSOCKET module
User who did this - Daniel-Constantin Mierla (miconda)
----------
You have to upgrade to latest 4.1.x (no changes to config or database structure, this should be straightforward) or latest 4.2.x, there were fixes done to this module since release of 4.1.2.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=495#comment1707
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.