[sr-dev] Kamailio lockup

Daniel-Constantin Mierla miconda at gmail.com
Tue Jun 9 12:08:48 CEST 2015


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




More information about the sr-dev mailing list