|Summary:||ASTERISK-16896: Crash when loading xml documentation|
|Reporter:||Atis Lezdins (atis)||Labels:|
|Date Opened:||2010-11-01 06:59:27||Date Closed:||2011-01-19 14:50:42.000-0600|
|Environment:||Attachments:||( 0) addons-en_US.xml|
( 1) asterisk.conf
( 2) bt.2010-11-01T04:21:49-0700-A1.28313.txt
|Description:||I did an upgrade of |
Asterisk 18.104.22.168 + addons 22.214.171.124
Asterisk 126.96.36.199-rc1 + addons 188.8.131.52
Upon restart I got crash within ast_xmldoc_load_documentation / ast_xml_open ( "/var/lib/asterisk/documentation/addons-en_US.xml" )
Apparently addons install put a file
-rw-r--r-- 1 root root 793 Nov 1 04:20 /var/lib/asterisk/documentation/addons-en_US.xml
which contains documentation for app SayCountPL (which was disabled in menuselect by the way).
Removing xml file solved crash.
Attached backtrace and XML file.
|Comments:||By: Paul Belanger (pabelanger) 2010-11-01 14:11:41|
Do you mind attaching your asterisk.conf file?
By: Atis Lezdins (atis) 2010-11-01 14:19:56
First exec line would return:
systemname = A1
second exec line would return nothing
Btw, it's weird that I have the same addons-en_US.xml on two other machines one of which was upgraded the same time, but that didn't cause crash. Crashing machine is the only one located on Amazon EC2
By: Leif Madsen (lmadsen) 2010-11-04 13:19:42
Assigned to Paul to run the XML documentation through the xmllint application to verify if we have an XML error in the documentation that may be causing libxml to crash.
By: Brett Bryant (bbryant) 2011-01-14 10:10:33.000-0600
Thank you for the bug report. However I am unable to reproduce this issue. We are now going to close this report - please feel free to reopen when you have more information at hand.
By: Atis Lezdins (atis) 2011-01-14 10:22:46.000-0600
I have experienced this couple of more times on Amazon EC2 with FC8 image.
Of course I have a way to fix it by deleting addons XML, but I could help tracing it. Anything else I can do?
By: Brett Bryant (bbryant) 2011-01-18 10:14:07.000-0600
atis, FC8 is a pretty old version of Fedora. The current version of Fedora is Fedora 14, and you'll likely have more luck with that as this seems like an issue with libxml that could possibly be related to how old the libxml version on FC8 probably is.