[asterisk-users] Fwd: Re: Asterisk CLI unresponsive

[Jonas Kellens]

On 02/06/2012 12:14 PM, Steve Davies wrote:
>
> On 6 February 2012 10:45, Jonas Kellens <jonas.kellens at telenet.be 
> <mailto:jonas.kellens at telenet.be>> wrote:
>
>     Hello,
>
>     is there anyone that can give me some more information on these
>     "deadlocks" ?!
>
>     How can these deadlocks occur and what is "good practise" to avoid
>     these problems ??
>
>
>     Jonas.
>
>
> The only way to avoid deadlocks is to report them when they happen, 
> provide the requested debug, and hope for a fix.
>
> Deadlocks are just a type of bug. Nothing you can do to avoid it 
> unless you can work out the events that lead up to it, and avoid doing 
> that.
>
> I am still using 1.6.2.22 in many places, and if I see a deadlock 
> "show locks" trace on the mailing list - I will certainly be looking 
> into it.
>

I am not sure if "show locks" will give me any output, because the 
Asterisk CLI is unresponsive... Haven't tried it thought.

Can I then act upon the information that "show locks" gives me ? Is 
there some other command to "unlock" the Channels that produce the lock ??


Kind regards,
Jonas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20120206/39d4e3ac/attachment.htm>