[asterisk-bugs] [Asterisk 0012508]: handle_response_peerpoke floods asterisk cli with notices, cli crashes

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12508 
====================================================================== 
Reported By:                kactus
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12508
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!): 114601 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-23-2008 22:35 CDT
Last Modified:              07-01-2008 21:51 CDT
====================================================================== 
Summary:                    handle_response_peerpoke floods asterisk cli with
notices, cli crashes
Description: 
Since upgrading asterisk to svn later than 1.6 beta 8 cli is flooded with 

NOTICE[7435]: chan_sip.c:16045 handle_response_peerpoke: Peer 'PEERNAME'
is now Reachable. (71ms / 2000ms)

several times a second. Did not happen with svn releases around the time
of beta 6 and 7 aprox around april 17 (sorry didn't keep the old revision
numbers) or earlier revisions. 

disconnecting phone or rebooting causes:
[Apr 24 11:22:31] NOTICE[7435]: chan_sip.c:19841 sip_poke_noanswer: Peer
'DRA-997896-0043' is now UNREACHABLE!

being spammed in the same fashion.

after running it for a while we end up seeing

[root at voip02 asterisk]# /usr/sbin/safe_asterisk: line 117:  7427
Segmentation fault      (core dumped) nice -n $PRIORITY
${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} >&/dev/${TTY} </dev/${TTY}
Asterisk ended with exit status 139
Asterisk exited on signal 11.
Automatically restarting Asterisk.
mpg123: no process killed

I'll need to recompile for "don't optimise" so I haven't attached a core
debug, let me know if you need it. I will attached the sip info with sip
debug as well.
====================================================================== 

---------------------------------------------------------------------- 
 kactus - 07-01-08 21:51  
---------------------------------------------------------------------- 
Hi Corydon I've just put 1.4.21.1 on one of the xen virtuals and still get
the chan_sip.c:12669 handle_response_peerpoke: Peer 'DRA-997896-0041' is
now Reachable. (49ms / 2000ms) spamming the screen

of interest even after it runs out of physical mem, and I disconnect from
the ssh session it hammering the network at 500kbs. The snom 190 displays a
low mem message and then reboots and is unable to register after it comes
back up (same as with the previous version).

I also have an asterisk SVN-trunk-r126681 running through valgrind server
that has a spa962 trying to connect to it that I left over night, it no
longer takes sip registrations, CPU usage has dropped off but asterisk
(well memcheck) is using 780MB of mem.

Let me know if you want me to kill this to try and generate a core dump. I
double checked menuselect and realised I hadn't specified debug malloc on
this virtual (the svn one) :( so more than likely I'll need to re run it
over night again if you still think that it is a memory issue.

In any case let me know what you want me to do next, if you want me to run
different versions etc or if you need specific compiler flags such as debug
threads etc. The new xen server is beefy enough so, for all intents and
purposes, I'm not limited by the number of boxes I can clone and
configure.

Please let me know if it is worthwile running valgrind as without it I can
get the boxes to a point of no longer accepting connections much faster.

Thanks - Kamil 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-01-08 21:51  kactus         Note Added: 0089568                          
======================================================================