6 Jun
2015
6 Jun
'15
11:53 p.m.
Earlier today, we saw a lockup of Kamailio
4.2:61d84c020e35d529ba6782628a66af7c4a8df4a2 in a single-CPU VMware
host. The last message was:
Jun 6 14:42:10 localhost /usr/local/sbin/kamailio[1802]: NOTICE: dialog
[dlg_hash.c:255]: dlg_clean_run(): dialog in early state is too old
(0x7f6cc9c4e578 ref 1)
After that, nothing occurred until Kamailio was restarted. No SIP
messages were processed.
Any insight would be appreciated.
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
9 Jun
9 Jun
1:08 p.m.
Hello,
what there a high CPU usage? If not, the it was not a lock on mutex,
could have been a block on an I/O operation.
Before restarting in such case, grab the backtrace -- with recent
versions, it can be quickly done with:
kamctl trap
Cheers,
Daniel
On 06/06/15 22:53, Alex Balashov wrote:
Earlier today, we saw a lockup of Kamailio
4.2:61d84c020e35d529ba6782628a66af7c4a8df4a2 in a single-CPU VMware
host. The last message was:
Jun 6 14:42:10 localhost /usr/local/sbin/kamailio[1802]: NOTICE:
dialog [dlg_hash.c:255]: dlg_clean_run(): dialog in early state is too
old (0x7f6cc9c4e578 ref 1)
After that, nothing occurred until Kamailio was restarted. No SIP
messages were processed.
Any insight would be appreciated.
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
3454
days inactive
3457
days old
1 comments
2 participants
participants (2)
-
Alex Balashov -
Daniel-Constantin Mierla