[Home]

Summary:ASTERISK-16048: Asterisk segfault xml_translate manager api
Reporter:Ove Aursand (aurs)Labels:
Date Opened:2010-05-04 07:33:52Date Closed:2010-05-10 11:20:43
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Core/ManagerInterface
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) bt_full.txt
( 1) bt.txt
Description:Not sure what is causing this.. I'm using the manager api to fetch statistics (number of calls, number of sip clients online etc). Have 3 coredumps with the same info.
Approx 800 sip peers on the server.
It's running on optimized code, so I'm not sure how useful the backtrace is..
Tried to discuss this on #asterisk-bugs, but I think I'm in the wrong timezone :D

****** ADDITIONAL INFORMATION ******

Removed inline optimized backtrace - pabelanger
Comments:By: Ove Aursand (aurs) 2010-05-04 08:06:34

update: have now compiled asterisk with dont_optimize flag. Will post new bt if it crashes again.
By: Paul Belanger (pabelanger) 2010-05-04 08:57:22

Correct.  When you get a new backtrace upload the file to this issue.
By: Ove Aursand (aurs) 2010-05-05 03:21:23

I have a "HTTP Content" sensor in PRTG that runs SIPPeers command every 5 minutes. I can request the web page directly from my network, and yesterday I tried to "spam" the URL that PRTG is using to try to reproduce a crash. That didn't happen. But it crashed now at 10:00:34 (GMT+2). This is usually the time with most calls, so this could be related to the volume of calls on the server.
By: Leif Madsen (lmadsen) 2010-05-07 11:16:27

I've related this to ASTERISK-15359 -- is that a similar (or duplicate) issue?
By: Evandro César Arruda (ecarruda) 2010-05-07 11:20:09

lmadsen is the same, just on different callback part, we are working with rawman, and this people are working with xml response.

i read the backtraces, is duplicated.

People, try to apply my patch on the another issue related by lmadsen and give me feedback.

Thanks
By: Leif Madsen (lmadsen) 2010-05-10 11:20:42

I am closing this issue as a duplicate of ASTERISK-15359 -- there is a patch which you should test if you are having this issue (unless of course that issue is now closed as fixed, in which case you should just update Asterisk :))