Summary:	ASTERISK-11453: Asterisk Frequent Crash
Reporter:	destiny6628 (destiny6628)	Labels:
Date Opened:	2008-02-16 05:04:05.000-0600	Date Closed:	2008-04-01 17:25:27
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_zap
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) asterisk.txt ( 1) asteriskbtbtfull.txt ( 2) asteriskcrash.txt ( 3) btbtfull.txt ( 4) coredump.txt ( 5) coredumpppp.txt ( 6) valgrind.JPG
Description:	Hello , we have been facing asterisk frequent crashes on CENTOS 5.0 , Asterisk-1.4.18 , Zaptel-1.4.8 and Libpri-1.4.3 . Over a period of time when zap channels goes above 85 to 90 then asterisk starts getting crash frequently and starts giving core dump . This is happening on Zap dialing and happening very frequently . Is there any solution to same . Everytime when asterisk has got crashed the status seems to be NO ANSWER and wait for answer .
Comments:	By: Tilghman Lesher (tilghman) 2008-02-16 11:40:00.000-0600 Please follow the instructions in doc/valgrind.txt By: destiny6628 (destiny6628) 2008-02-17 22:38:56.000-0600 Hi its a production server and i cant do valgrind test on that because it takes away huge load on the server and causes the whole application to be stopped . Any other step plz guide will try ?? By: Tilghman Lesher (tilghman) 2008-02-17 22:52:04.000-0600 Sorry, I don't know of another way to debug what appears to be memory corruption.  If you know of a better tool, I'd love to hear about it. By: Abhay Gupta (agupta) 2008-02-18 08:47:41.000-0600 opt_args = {0x0, 0x0, 0x0, 0x0, 0x0, 0x28 <Address 0x28 out of bounds>, 0x0, 0xb6396b00 "", 0x0} This seems to be some issue with dial_exec_full .  We are also facing slightly different issue but there also the same pointer and same function dial_exec_full is creating a problem . By: Tilghman Lesher (tilghman) 2008-02-18 15:52:22.000-0600 There's no other way I can say this.  I need valgrind output. By: destiny6628 (destiny6628) 2008-02-19 02:24:34.000-0600 hi i tried valgrind on the production server and as expected server load goes high on that as 35 agents were logged in on the server and making and receiving calls . So with no other option i had to stopped valgrind test as it was causing servere voice breakage problem . I am attaching a print screen for the same as well . We surely need to find another way as i am sure other's as well will face same issue running valgrind on the production server . By: Digium Subversion (svnbot) 2008-02-29 17:30:56.000-0600 Repository: asterisk Revision: 105409 U   branches/1.4/main/autoservice.c ------------------------------------------------------------------------ r105409 | russell | 2008-02-29 17:30:48 -0600 (Fri, 29 Feb 2008) | 23 lines Fix a major bug in autoservice.  There was a race condition in the handling of the list of channels in autoservice.  The problem was that it was possible for a channel to get removed from autoservice and destroyed, while the autoservice was still messing with the channel.  This led to memory corruption, and caused crashes.  This explains multiple backtraces I have seen that have references to autoservice, but do to the nature of the issue (memory corruption), could cause crashes in a number of areas. (fixes the crash in BE-386) (closes issue ASTERISK-11165) (closes issue ASTERISK-11391) The following issues could be related.  If you are the reporter of one of these, please update to include this fix and try again. (potentially fixes issue ASTERISK-10713) (potentially fixes issue ASTERISK-11545) (potentially fixes issue ASTERISK-11058) (potentially fixes issue ASTERISK-11453) (potentially fixes issue ASTERISK-10713) (potentially fixes issue ASTERISK-11437) (potentially fixes issue ASTERISK-11259) ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=105409 By: Digium Subversion (svnbot) 2008-02-29 17:33:02.000-0600 Repository: asterisk Revision: 105410 _U  trunk/ U   trunk/main/autoservice.c ------------------------------------------------------------------------ r105410 | russell | 2008-02-29 17:33:00 -0600 (Fri, 29 Feb 2008) | 31 lines Merged revisions 105409 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r105409 | russell | 2008-02-29 17:34:32 -0600 (Fri, 29 Feb 2008) | 23 lines Fix a major bug in autoservice.  There was a race condition in the handling of the list of channels in autoservice.  The problem was that it was possible for a channel to get removed from autoservice and destroyed, while the autoservice was still messing with the channel.  This led to memory corruption, and caused crashes.  This explains multiple backtraces I have seen that have references to autoservice, but do to the nature of the issue (memory corruption), could cause crashes in a number of areas. (fixes the crash in BE-386) (closes issue ASTERISK-11165) (closes issue ASTERISK-11391) The following issues could be related.  If you are the reporter of one of these, please update to include this fix and try again. (potentially fixes issue ASTERISK-10713) (potentially fixes issue ASTERISK-11545) (potentially fixes issue ASTERISK-11058) (potentially fixes issue ASTERISK-11453) (potentially fixes issue ASTERISK-10713) (potentially fixes issue ASTERISK-11437) (potentially fixes issue ASTERISK-11259) ........ ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=105410 By: Digium Subversion (svnbot) 2008-02-29 17:57:03.000-0600 Repository: asterisk Revision: 105409 U   branches/1.4/main/autoservice.c ------------------------------------------------------------------------ r105409 | russell | 2008-02-29 17:34:32 -0600 (Fri, 29 Feb 2008) | 23 lines Fix a major bug in autoservice.  There was a race condition in the handling of the list of channels in autoservice.  The problem was that it was possible for a channel to get removed from autoservice and destroyed, while the autoservice thread was still messing with the channel.  This led to memory corruption, and caused crashes.  This explains multiple backtraces I have seen that have references to autoservice, but do to the nature of the issue (memory corruption), could cause crashes in a number of areas. (fixes the crash in BE-386) (closes issue ASTERISK-11165) (closes issue ASTERISK-11391) The following issues could be related.  If you are the reporter of one of these, please update to include this fix and try again. (potentially fixes issue ASTERISK-10713) (potentially fixes issue ASTERISK-11545) (potentially fixes issue ASTERISK-11058) (potentially fixes issue ASTERISK-11453) (potentially fixes issue ASTERISK-10713) (potentially fixes issue ASTERISK-11437) (potentially fixes issue ASTERISK-11259) ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=105409 By: Digium Subversion (svnbot) 2008-02-29 17:57:35.000-0600 Repository: asterisk Revision: 105410 _U  trunk/ U   trunk/main/autoservice.c ------------------------------------------------------------------------ r105410 | russell | 2008-02-29 17:36:46 -0600 (Fri, 29 Feb 2008) | 31 lines Merged revisions 105409 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r105409 | russell | 2008-02-29 17:34:32 -0600 (Fri, 29 Feb 2008) | 23 lines Fix a major bug in autoservice.  There was a race condition in the handling of the list of channels in autoservice.  The problem was that it was possible for a channel to get removed from autoservice and destroyed, while the autoservice thread was still messing with the channel.  This led to memory corruption, and caused crashes.  This explains multiple backtraces I have seen that have references to autoservice, but do to the nature of the issue (memory corruption), could cause crashes in a number of areas. (fixes the crash in BE-386) (closes issue ASTERISK-11165) (closes issue ASTERISK-11391) The following issues could be related.  If you are the reporter of one of these, please update to include this fix and try again. (potentially fixes issue ASTERISK-10713) (potentially fixes issue ASTERISK-11545) (potentially fixes issue ASTERISK-11058) (potentially fixes issue ASTERISK-11453) (potentially fixes issue ASTERISK-10713) (potentially fixes issue ASTERISK-11437) (potentially fixes issue ASTERISK-11259) ........ ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=105410 By: destiny6628 (destiny6628) 2008-03-01 04:56:19.000-0600 Have updated the server with the latest patches for autoservice.c . Hope that resolve the issues and will keep you all updated . By: destiny6628 (destiny6628) 2008-03-01 04:56:29.000-0600 Have updated the server with the latest patches for autoservice.c . Hope that resolve the issues and will keep you all updated . By: destiny6628 (destiny6628) 2008-03-03 00:58:11.000-0600 After upgrading the patch as well still asterisk gave core dump . Attaching the core dump as well by the name of coredump.txt. Waiting for reply on same . By: destiny6628 (destiny6628) 2008-03-03 06:26:35.000-0600 I have got another core dump , after upgrading the patch second time today . Its related to ast_channel_free . Attached is the core dump by the name of coredumppppp.txt By: Jason Parker (jparker) 2008-04-01 17:25:26 This is the same as issue ASTERISK-11443.