[Home]

Summary:ASTERISK-09186: Asterisk 1.2.17 crashes with SIP message could not be handled error
Reporter:gbodemantv (gbodemantv)Labels:
Date Opened:2007-04-04 12:49:04Date Closed:2011-06-07 14:00:27
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:At time of crash fill log output had many of these

Apr  3 13:03:27 DEBUG[19222] chan_sip.c: Stopping retransmission on '000dbdb7-aef7026d-24d97ada-79e0aedc@10.210.20.64' of Response 102: Match Found
Apr  3 13:03:28 DEBUG[19222] chan_sip.c: SIP message could not be handled, bad request: 039D2FFE-1DD2-11B2-AA45-B770E8CB4C84@10.210.20.36                    
Apr  3 13:03:29 DEBUG[19222] chan_sip.c: SIP message could not be handled, bad request: 1FC8195A-1DD2-11B2-BDE7-EA540EFEEC92@10.210.20.106                    
Apr  3 13:03:29 DEBUG[19222] chan_sip.c: SIP message could not be handled, bad request: 12DBA230-1DD2-11B2-AEC9-954C67011F31@10.210.20.93                    
Apr  3 13:03:29 DEBUG[19222] chan_sip.c: SIP message could not be handled, bad request: BFE044F2-1DD1-11B2-98E3-AF0C414A955B@10.210.20.177                    
Apr  3 13:03:29 DEBUG[19222] chan_sip.c: SIP message could not be handled, bad request: E41E77B8-1DD1-11B2-B767-BFAD4425EACD@10.210.20.92                    
Apr  3 13:03:30 DEBUG[19222] chan_sip.c: SIP message could not be handled, bad request: 74F461EA-1DD2-11B2-9EC1-B6BC846A5BE3@10.210.20.83                    
Apr  3 13:03:31 DEBUG[19222] chan_sip.c: SIP message could not be handled, bad request: 3C31C01C-1DD2-11B2-8CF0-E64B7955E21A@10.210.20.105                    
Apr  3 13:03:31 DEBUG[19222] chan_sip.c: SIP message could not be handled, bad request: C51D3D22-1DD1-11B2-A23D-97C3224F129F@10.210.20.102                    
Apr  3 13:03:31 DEBUG[19222] chan_sip.c: SIP message could not be handled, bad request: 4514BBC4-1DD2-11B2-9F2F-FAFD8E12B3F6@10.210.20.95

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

this also occured in 1.2.13 on same server. It happens about every 1 1/2 days.
Comments:By: Serge Vecher (serge-v) 2007-04-05 08:23:19

you need to provide a backtrace of core file dumped after a crash:
1. compile asterisk 1.2.17 with make dont-optimize
3. Start Asterisk with '-g' option
4. When crash occurs, perform 'bt' on the core file. Then 'thread apply all bt full'


also, if possible, please include a sip debug as per following:
1) Prepare test environment (reduce the amount of unrelated traffic on the server);
2) Make sure your logger.conf has the following line:
  console => notice,warning,error,debug
3) restart Asterisk with the following command:
  'asterisk -Tvvvvvdddddngc | tee /tmp/verbosedebug.txt'
4) Enable SIP transaction logging with the following CLI commands (1.4/trunk commands in parenthesis):
set debug 4 (core set debug 4)
set verbose 4 (core set verbose 4)
sip debug (sip set debug)
5) Reproduce the problem
6) Trim startup information and attach verbosedebug.txt to the issue.
By: gbodemantv (gbodemantv) 2007-04-10 13:31:23

1. Compiled with 1.2.17 make -dont-optimize
2. No crashes since

I have core dumps from before the make dont-optimize. can those be helpful at all?
By: Serge Vecher (serge-v) 2007-04-10 13:42:25

well, usually they are not, but let's have a look.

perform bt / bt full on the core files and attach output to this note. Also, it would be useful to see that sip debug if you are able to go back to optimized builds just to get us the debugging output.
By: gbodemantv (gbodemantv) 2007-04-10 15:00:38

Unable to run gbd. Can I upload core file?
By: Joshua C. Colp (jcolp) 2007-04-26 15:31:15

A core dump is usually only useable on the machine it was created on.
By: Olle Johansson (oej) 2007-04-27 03:13:47

Any updates?
By: Olle Johansson (oej) 2007-04-27 09:13:07

We do need a SIP debug for those messages.
By: gbodemantv (gbodemantv) 2007-05-01 16:31:21

It finally crashed in Dont optimize. I have core file but cannot seeme to run backtrace. Can you point me in the direction to do this.
By: Olle Johansson (oej) 2007-05-16 06:07:08

There is documention in the /doc directory

http://svn.digium.com/view/asterisk/branches/1.4/doc/backtrace.txt?rev=46298

Looking forward to more information.
By: Olle Johansson (oej) 2007-05-29 03:12:15

I really need feedback from you on this bug report.
By: Joshua C. Colp (jcolp) 2007-06-19 10:00:53

I'm suspending this bug since it's been over a month and a half without a backtrace. If you have it please reopen this and attach it. Thanks.