On 04/18/2011 06:36 PM, Paul Belanger wrote:
On 11-04-18 09:46 AM, Jonas Kellens wrote:
Asterisk freezed and only a reboot of the whole server fixed this. Any
command on the Asterisk CLI was not executed because Asterisk was too
busy processing all of these messages that you see in the debug log.
What is the origin of these messages ?
Sounds like a deadlock[1].
[1]
https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock
Hello,
the core dump file is saved in the /tmp directory. Of course this
morning the file was automatically deleted.
A "deadlock", what can be causing this ?
In the past I've posted another thread on this list about such a
"deadlock" and the advice then was to upgrade. I've upgraded from
1.6.2.10 to 1.6.2.16.1, but all of a sudden I have a "deadlock" again.
I've checked my verbose and debug log files, but I see nothing special.
There were some conversations going on... nothing abnormal.
Kind regards,
Jonas.
--
_____________________________________________________________________
-- 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
