On 02/03/2012 03:48 PM, Paul Belanger wrote:
On 12-02-03 09:05 AM, Jonas Kellens wrote:
On 02/03/2012 02:52 PM, Paul Belanger wrote:
On 12-02-03 07:55 AM, Jonas Kellens wrote:
This is a production server. Will it affect theserver ?I already have
"dont_optimize" checked in the debug options.
Yes, reproduce the issue on your test infrastructure. then generate a
backtrace [1].
[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
How can I reproduce when I don't know what causes the "deadlock" ??
That is part of my question : what can have caused this "deadlock" ?
I can go on for weeks without any problem, and then suddenly there's
what appears to be a "deadlock".
That's what the backtrace will tell us. If you already have
DONT_OPTIMIZED compiled on your production server, then attach gdb to
the process and generate the backtrace.
I can not reproduce a problem which I don't know what causes it.
These seems like the chicken and the egg.
There is no core-file generated. It's just the CLI that freezes, not a
restart of Asterisk.
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
