Hi Rik,
The attached BT is irrelevant as it is from the attendant process which
tried to do the cleanup and it failed. Probably one of the processed
crashed (generated a core file) and triggered the whole OpenSIPS
shutdown. When doing the cleanup, a second crash of the attendant
process (probabaly because the memory was corrupted after the first
crash) overwritten the core :(.
Check the chapter "How to make sure OpenSIPS dumps a proper core file"
to be sure you avoid the core file to be overwritten:
http://www.opensips.org/Documentation/TroubleShooting-Crash
And let's see if the crash happens again.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 25.02.2015 11:40, Rik Broers wrote:
No idea what triggered this crash, otherwise a very stable machine.
Memory was not full and logs before the crash indicated no problems or
other strange things.
I have monitoring on opensips memory usage which triggers on 65%
usage. (which did not trigger)
Backtrace is attached. If you need more info please ask J
Regards,
Vriendelijke groet,
*Rik Broers*
Voice Engineer
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
