[asterisk-bugs] [Asterisk 0014309]: SIP/realtime problems => 100 % CPU
Asterisk Bug Tracker
noreply at bugs.digium.com
Sat Feb 14 08:40:37 CST 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14309
======================================================================
Reported By: pkempgen
Assigned To: Corydon76
======================================================================
Project: Asterisk
Issue ID: 14309
Category: Channels/chan_sip/General
Reproducibility: always
Severity: major
Priority: normal
Status: ready for testing
Asterisk Version: 1.4.22
Regression: Yes
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-01-22 07:50 CST
Last Modified: 2009-02-14 08:40 CST
======================================================================
Summary: SIP/realtime problems => 100 % CPU
Description:
As reported on
http://lists.digium.com/pipermail/asterisk-users/2009-January/225274.html
:
> Carlos Chavez schrieb:
>> Since 1.4.22 realtime status for sip peers seems to be broken. If I
do
>> a "sip show peers" from the CLI I get this:
>>
>> 2001/2001 192.168.2.234 D 5060
UNKNOWN
>> Cached RT
>>
>> It is arbitrary which peers will say OK and which will say UNKNOWN
and
>> it changes over time.
>
>> This used to work fine until 1.4.21
>> so why did it break and why wasn't it fixed on 1.4.23? This only
>> happens when using realtime peers, static peers will always show the
>> proper status.
>
> It might be related to this issue (thread in German)
>
http://www.mail-archive.com/gemeinschaft-users@lists.amooma.de/msg00083.html
>
http://www.mail-archive.com/gemeinschaft-users@lists.amooma.de/msg00152.html
>
http://www.mail-archive.com/gemeinschaft-users@lists.amooma.de/msg00153.html
> etc.
>
> Several people, including me, have confirmed that since Asterisk
> 1.4.22 you get hundreds (probably depends on the number of SIP
> peers/users) of SQL queries per second and the CLI is being flooded
> with
> ---cut---
> [Oct 8 12:22:56] NOTICE[2487]: chan_sip.c:16223 sip_poke_noanswer:
Peer
> '8280' is now UNREACHABLE! Last qualify: 0
> ---cut---
> leading to 100 % CPU usage.
>
> 1.4.21.2 didn't have the problem.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0004362 [patch] new config option 'rtautoreg'
======================================================================
----------------------------------------------------------------------
(0100159) pkempgen (reporter) - 2009-02-14 08:40
http://bugs.digium.com/view.php?id=14309#c100159
----------------------------------------------------------------------
"suspicious" commits between 1.4.21.2 (2008 Jul 23) and
1.4.22 (2008 Oct 02) include:
r133488
http://svn.digium.com/view/asterisk/branches/1.4/channels/chan_sip.c?r1=132790&r2=133488
"Fix rtautoclear and rtcachefriends (Closes issue
http://bugs.digium.com/view.php?id=12707)"
r138258
http://svn.digium.com/view/asterisk/branches/1.4/channels/chan_sip.c?r1=133572&r2=138258
"More fixes for realtime peers. (closes issue
http://bugs.digium.com/view.php?id=12921)"
Issue History
Date Modified Username Field Change
======================================================================
2009-02-14 08:40 pkempgen Note Added: 0100159
======================================================================
More information about the asterisk-bugs
mailing list