Checking the code, the line corresponds to a SIGTERM or SIGINT handling, which is normal termination of the application. So it seems that the application was stopped.
Cheers, Daniel On 30/03/15 23:22, Alex Balashov wrote: > In the absence of any other information, I am going to chalk this up > to the fact that our SIP stack responsiveness check, which was added > to the monitoring script to monitor for the deadlock I reported > earlier, is too sensitive. It probably restarted Kamailio on a hair > trigger, and the memory error in PID 6979 is just a side effect. > > I'm going to disable the SIP check, and hope your patch fixes any > possible deadlock. > -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com _______________________________________________ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
