[prev in list] [next in list] [prev in thread] [next in thread] 

List:       asterisk-dev
Subject:    Re: [asterisk-dev] $1000 reward for patch to cure call pickup
From:       Alistair Cunningham <acunningham () integrics ! com>
Date:       2011-07-28 23:43:59
Message-ID: 4E31F43F.2080508 () integrics ! com
[Download RAW message or body]

Thank you, those are all good ideas. I've just checked /var/log/kern.log 
around the time Asterisk locked up, and it shows nothing.

Unfortunately as soon as I told the customer that it was call pickup 
causing the problem they immediately disabled call pickup, so there 
won't be any more debugging from this customer. This seems to be the 
norm for this problem - no-one is willing to risk the stability of busy 
production systems. If anyone else is affected I'll try your other ideas.

Alistair Cunningham
+1 888 468 3111
+44 20 799 39 799
http://integrics.com/

On 29/07/11 09:34, James Cloos wrote:
>> Does anyone know any debugging that could be added to Asterisk for
>> the next time this happens?
>
> You might want to run top(1), hit H to show each thread on its own
> line, and check whether any asterisk thread are in D state.
>
> Also, attaching gdb might help (is the box fast enough to run an
> asterisk compiled with<-O0 -ggdb3>  given their load?), as might
> lsof(8) output for the box.
>
> Also, check dmesg(1) output and/or the kernel logs from syslog
> to see whether the kernel complained about anything.
>
> A thread stuck in kernel mode, or some sort of deadlock in either
> the kernel or asterisk seems most likely.
>
> (I didn't read the whole thread; hope I'm not repeating anything
> you've already tried.)
>
> -JimC

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev
[prev in list] [next in list] [prev in thread] [next in thread]