<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
<br>
Am 14.01.2011 12:50, schrieb Jonas Kellens:
<blockquote cite="mid:4D30387D.5010204@telenet.be" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 01/14/2011 12:44 PM, Thorsten Göllner wrote:
<blockquote cite="mid:4D303700.8010307@ovm-group.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Am 14.01.2011 11:55, schrieb Jonas Kellens:
<blockquote cite="mid:4D302BB8.1090307@telenet.be" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<font face="Helvetica, Arial, sans-serif">Hello list,<br>
<br>
today I experienced the following for the first time :<br>
<br>
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
<snip><br>
[Jan 14 11:26:19] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:19] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'<br>
[Jan 14 11:26:19] DEBUG[27654] channel.c: Failure, could not
lock
'0x114af2c0' after 199 retries!<br>
<br>
Question 1 : What can be causing this ??<br>
Question 2 : What can I do when this happens ? Because
Asterisk was no
longer responding untill I rebooted the server. What is the
right way
to handle this extreem situation ?<br>
Question 3 : How can I avoid this situation from happening
again ?</font></blockquote>
<font face="Helvetica, Arial, sans-serif"><br>
Sometimes I can see this messages too - but with no impact. It
is a
debug-message and should not indicate any problems. What does
it mean
when you say "Asterisk was no longer responding"?<br>
<br>
-Thorsten-<br>
</font> </blockquote>
<br>
Hello,<br>
<br>
the debug-file is flooded with this message during 2 à 3 seconds
and
counts about 300 à 400 lines... So I don't think it's just a
debug-message.<br>
<br>
Asterisk was not responding as in "core show channels" had no
output,
"sip show peers" had no output, "core restart now" did nothing...<br>
The Asterisk proces was still running though...<br>
<br>
Also: all registrations of SIP peers were lost. I could see that
the
IP-phones lost their registration to the Asterisk server. And they
did
not re-register untill the server was finally rebooted.</blockquote>
This message is repeated over 100 times. (You can take a look at the
source code.) Which Asterisk-Version do you use? Did it happen
before or again?<br>
-Thorsten-<br>
</body>
</html>