On 12-02-06 09:23 AM, Jonas Kellens wrote:
On 02/06/2012 03:19 PM, Paul Belanger wrote:
On 12-02-06 09:15 AM, Jonas Kellens wrote:
On 02/06/2012 12:25 PM, isr...@gmail.com wrote:
Your running into a bug and the only way to solve it is to report it
and debug it and hope for a fix
There is no way someone can help without it being debugged and knowing
what's causing it to lockup
The only key to unlcock it when it gets locked is by restarting
asterisk
I am now using 1.6.2.22. Would I then be better upgrading to 1.8 ? Does
1.8 has fewer bugs ?!
Showing us the deadlock is the best thing you can do right now.
Paul,
if the CLI is unresponsive, how can I show you the output of "show locks" ?
Everything you need to do is described in the wiki page[1] we previous
linked.
[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
--
Paul Belanger
Digium, Inc. | Software Developer
twitter: pabelanger | IRC: pabelanger (Freenode)
Check us out at: http://digium.com & http://asterisk.org
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
