Guest

Preview Tool

Cisco Bug: CSCuj45391 - Routing loop causes leak resulting in core

Last Modified

Sep 24, 2019

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

8.6(2.22900.9) 9.1(1.20000.5)

Description (partial)

Symptom:
The CUCM cluster that originates the MWI message may experience a core and the receiving node may have trouble processing phone keepalives and experience an unregistration event.

SDL traces may show:
004326664 |2013/09/11 05:28:37.850 |100 |SdlSig    |SIPTimer                               |wait                           |SIPHandler(2,100,71,1)           |SdlTimerService(2,100,3,1)       |2,100,63,1.46780^10.65.114.76^*          |[T:H-H:44,N:65368,L:0,V:0,Z:0,D:0]  TimerType=SIP_TIMER_CLIENT_TCB value=32000 numRetries=0

Note that there are over 65,000 messages in the normal priority queue. 

utils core analyze from CLI may show backtrace:

 ====================================
 backtrace
 ===================================
 #0  0x031fd206 in raise () from /lib/libc.so.6
#1  0x031febd1 in abort () from /lib/libc.so.6
#2  0x0a3cee2a in SdlMsgQueueCirc::enqueueSignal (this=0xdeb9850, msg=0x27063d80, priority=2) at SdlMsgQueueCirc.cpp:140
#3  0x0a3aeafc in enqueueSignal (this=0xdeb9068, rSignal=0x27063d80) at /view/BLD-cm_su3_8_6_2-cct-ccm-d/vob/ccm/Common/Include/Sdl/SdlMsgQueue.hpp:66
#4  SdlThreadedProcess::inputSignal (this=0xdeb9068, rSignal=0x27063d80) at SdlThreadedProcess.cpp:171
#5  0x0a382b84 in SdlRouter::callProcess (this=0xb7ef82c8, _sdlSignal=0x27063d80, _deleteSignal=@0xcb563a7, _traceType=SignalRouterThread, _hp=0, _np=4, _lp=0, _vlp=0, _lzp=0, _dbp=0) at SdlRouter.cpp:258
#6  0x0a3832b8 in SdlRouter::scheduler (this=0xb7ef82c8) at SdlRouter.cpp:164
#7  0x008b86e1 in start_thread () from /lib/libpthread.so.0
#8  0x032a9d3e in clone () from /lib/libc.so.6

Conditions:
Message flow for MWI in which MWI messages are passed between two UCM clusters and there is a routing loop configured between the two clusters
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.