Am 14.01.2011 12:50, schrieb Jonas Kellens:
On 01/14/2011 12:44 PM, Thorsten Göllner wrote:
Am 14.01.2011 11:55, schrieb Jonas Kellens:
Hello list,
today I experienced the following for the first time :
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
<snip>
[Jan 14 11:26:19] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:19] DEBUG[27654] channel.c: Avoiding deadlock
for channel
'0x114af2c0'
[Jan 14 11:26:19] DEBUG[27654] channel.c: Failure, could not
lock
'0x114af2c0' after 199 retries!
Question 1 : What can be causing this ??
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 ?
Question 3 : How can I avoid this situation from happening
again ?
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"?
-Thorsten-
Hello,
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.
Asterisk was not responding as in "core show channels" had no
output,
"sip show peers" had no output, "core restart now" did nothing...
The Asterisk proces was still running though...
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.
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?
-Thorsten-
|
--
_____________________________________________________________________
-- 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
