Summary:ASTERISK-15165: Asterisk Asterisk crashes intermittently cause unknown.
Reporter:rootforce (rootforce)Labels:
Date Opened:2009-11-18 10:59:10.000-0600Date Closed:2010-05-13 09:17:15
Versions:Frequency of
Environment:Attachments:( 0) backtrace2009-11-10.txt
( 1) backtrace2009-11-15.txt
( 2) backtrace2009-11-16.txt
( 3) backtrace2009-11-8.txt
Description:Asterisk crashes intermittently for an unknown reason. This server has over 700 sip peers registered at any given point in time. I have backtraces from the most recent crashes, but I need to make sure they are not world readable. Does setting the ticket to private accomplish this? Below is the console output from the crash on the 8th.


-- Executing [111@sip-subscriber:1] VoiceMailMain("SIP/<did1 removed>-b765a4a8", "<did1 removed>") in new stack
   -- <SIP/<did1 removed>-b765a4a8> Playing 'vm-password.ulaw' (language 'en')
   -- <SIP/<did1 removed>-b767c6a0> Playing 'vm-toforward.ulaw' (language 'en')
   -- Incorrect password '21817' for user '<did1 removed>' (context = default)
   -- <SIP/<did1 removed>-b765a4a8> Playing 'vm-incorrect.ulaw' (language 'en')
   -- <SIP/<did1 removed>-b765a4a8> Playing 'vm-password.ulaw' (language 'en')
   -- <SIP/<did1 removed>-b767c6a0> Playing 'vm-savemessage.ulaw' (language 'en')
[Nov  8 12:40:41] NOTICE[25976]: chan_sip.c:16301 attempt_transfer: SIP Transfer attempted with no appropriate bridged calls to transfer
[Nov  8 12:40:41] WARNING[25976]: channel.c:1647 ast_hangup: Hard hangup called by thread -1211352160 on SIP/<did1 removed>-b767c6a0, while fd is blocked by thread -1237615712 in procedure ast_waitfor_nandfds!  Expect a failure
[Nov  8 12:40:41] WARNING[6525]: app_voicemail.c:7637 vm_authenticate: Unable to read password
[Nov  8 12:40:41] WARNING[25976]: channel.c:1336 ast_channel_free: PBX may not have been terminated properly on 'SIP/<did1 removed>-b767c6a0'
Disconnected from Asterisk server
Comments:By: Leif Madsen (lmadsen) 2009-11-18 12:21:10.000-0600

Yes, setting to private causes this issue to not be seen except by a select few people.

By: Leif Madsen (lmadsen) 2009-11-18 12:21:50.000-0600

Please provide a proper backtrace of the crash per the doc/backtrace.txt file in your asterisk source. Additionally, if you can test a newer version that would be ideal.

By: rootforce (rootforce) 2009-11-18 14:05:26.000-0600

I am not able to try a more recent version unless the issue is verified as fixed as this is a production system. I can try more a more recent version on a test box, but the issue may only occur on loaded servers.

By: rootforce (rootforce) 2009-11-23 09:46:31.000-0600

Is there more feedback needed?

By: Leif Madsen (lmadsen) 2009-11-23 20:15:22.000-0600

There is no more information requested. It would be ideal if you could reproduce the issue on a test system and attempt a newer version though.

By: Leif Madsen (lmadsen) 2010-04-30 11:59:55

Is this still an issue on the latest 1.6.0.x?

By: Leif Madsen (lmadsen) 2010-04-30 12:00:10

Current release candidate is

By: Paul Belanger (pabelanger) 2010-05-13 09:17:14

Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.6.0 and 1.6.1 branches has ended. For continued maintenance support please move to the 1.6.2 branch.

More information on this change can be found in the release announcement: http://www.asterisk.org/node/49924