Guest

Preview Tool

Cisco Bug: CSCun66866 - CTIManager coredump when configuring CallPark via BAT

Last Modified

Jan 23, 2019

Products (8)

  • Cisco Unified Communications Manager (CallManager)
  • Cisco Intercompany Media Engine
  • Cisco Business Edition 5000 Version 8.6
  • Cisco Business Edition 3000 Version 8.6
  • Cisco Business Edition 6000 Version 8.6
  • Cisco Unified Communications Manager Version 8.6
  • Cisco Unity Connection Version 8.6
  • Cisco Unified Communications Manager Session Management Edition

Known Affected Releases

8.6(2)

Description (partial)

Symptom:
Multiple CTIManager coredump files when configuring Call Park via BAT caused due to memory crash.

Conditions:
When configuring Call Park via BAT.

output of 'utils core analyze':

====================================
backtrace
===================================
#0 0x05fdfcf3 in _int_malloc () from /lib/libc.so.6
#1 0x05fe1dfe in malloc () from /lib/libc.so.6
#2 0x0075a577 in operator new(unsigned int) () from /usr/local/cm/lib/libstlport.so.5.1
#3 0x08428929 in __stl_new (this=0xb15f9b04, __n=4701, __obj=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_new.h:147
#4 allocate (this=0xb15f9b04, __n=4701, __obj=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_alloc.h:130
#5 allocate (this=0xb15f9b04, __n=4701, __obj=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_alloc.h:381
#6 allocate (this=0xb15f9b04, __n=4701, __obj=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_alloc.h:616
#7 _M_create_node (this=0xb15f9b04, __n=4701, __obj=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_slist.h:252
#8 _M_insert_after (this=0xb15f9b04, __n=4701, __obj=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_slist.h:467
#9 insert_after (this=0xb15f9b04, __n=4701, __obj=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_slist.h:599
#10 stlp_std::hashtable, CCtiApiLineHandle, CCtiApiLineHandleHash, stlp_priv::_HashMapTraitsT >, stlp_priv::_Select1st >, CCtiApiLineHandleEq, stlp_std::allocator > >::_M_insert_noresize (this=0xb15f9b04, __n=4701, __obj=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_hashtable.c:167
#11 0x08428aab in stlp_std::hashtable, CCtiApiLineHandle, CCtiApiLineHandleHash, stlp_priv::_HashMapTraitsT >, stlp_priv::_Select1st >, CCtiApiLineHandleEq, stlp_std::allocator > >::insert_unique_noresize (this=0xb15f9b04, __obj=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_hashtable.c:201
#12 0x0844242c in stlp_std::hashtable, CCtiApiLineHandle, CCtiApiLineHandleHash, stlp_priv::_HashMapTraitsT >, stlp_priv::_Select1st >, CCtiApiLineHandleEq, stlp_std::allocator > >::_M_insert (this=0xb15f9b04, __obj=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_hashtable.c:234
#13 0x083eb3c2 in CTIHandler::ready_CtiLineOpenLineReq (this=0xb15eefc0, s=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_hash_map.h:207
#14 0x084162f6 in CTIHandler::fireSignal (this=0xb15eefc0, sdlSignal=...) at ../Include/ProcessCTIHandler.hpp:983
#15 0x086003e0 in SdlProcessBase::inputSignal (this=0xb15eefc0, rSignal=0xabfbee0, traceType=SignalRouterThread, highPriority=0, normalPriority=0, lowPriority=0, veryLowPriority=0, lazyPriority=0, dbUpdatePriority=0) at SdlProcessBase.cpp:363
#16 0x086069a4 in SdlRouter::callProcess (this=0x9245a10, _sdlSignal=0xabfbee0, _deleteSignal=@0x5e293a7, _traceType=SignalRouterThread, _hp=0, _np=0, _lp=0, _vlp=0, _lzp=0, _dbp=0) at SdlRouter.cpp:258
#17 0x086070d8 in SdlRouter::scheduler (this=0x9245a10) at SdlRouter.cpp:164
#18 0x004fb6e1 in start_thread () from /lib/libpthread.so.0
#19 0x0604ad3e in clone () from /lib/libc.so.6


====================================
backtrace
===================================
#0 operator= (this=0x8b643b8, pAllParkDNInfoList=0x968cce0, parkDNCount=0x968cce4) at /view/BLD-cm_8_6_2_new-cct-ccm-d/vob/ccm/Common/Include/CtiInterface/CtiInterface_Types.hpp:560
#1 dBProcs::ReadCallParkRec (this=0x8b643b8, pAllParkDNInfoList=0x968cce0, parkDNCount=0x968cce4) at CTIDatabase.cpp:1695
#2 0x082c5d9f in Db::initializing_CtiCallParkRetrieveParkDNReq (this=0x968cb38, s=...) at ProcessCTIDatabase.cpp:451
#3 0x082c9776 in Db::fireSignal (this=0x968cb38, sdlSignal=...) at ../Include/ProcessCTIDatabase.hpp:55
#4 0x086003e0 in SdlProcessBase::inputSignal (this=0x968cb38, rSignal=0xb3f8d270, traceType=SignalThreadedNoPriorities, highPriority=0, normalPriority=0, lowPriority=0, veryLowPriority=0, lazyPriority=0, dbUpdatePriority=0) at SdlProcessBase.cpp:363
#5 0x08633039 in SdlThreadedProcess::threadQueueReader (this=0x968cb38) at SdlThreadedProcess.cpp:112
#6 0x009a46e1 in start_thread () from /lib/libpthread.so.0
#7 0x006f4d3e in clone () from /lib/libc.so.6


====================================
backtrace
===================================
#0 0x0292125a in _int_malloc () from /lib/libc.so.6
#1 0x02922dfe in malloc () from /lib/libc.so.6
#2 0x00327577 in operator new(unsigned int) () from /usr/local/cm/lib/libstlport.so.5.1
#3 0x084294b9 in __stl_new (this=0xa7278108, __x=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_new.h:147
#4 allocate (this=0xa7278108, __x=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_alloc.h:130
#5 allocate (this=0xa7278108, __x=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_alloc.h:381
#6 allocate (this=0xa7278108, __x=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_alloc.h:616
#7 _M_create_node (this=0xa7278108, __x=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_list.h:282
#8 insert (this=0xa7278108, __x=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_list.h:416
#9 _M_insert_dispatch > > (this=0xa7278108, __x=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_list.h:453
#10 _M_insert > > (this=0xa7278108, __x=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_list.h:431
#11 list > > (this=0xa7278108, __x=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_list.h:324
#12 _M_splice_insert_dispatch > > (this=0xa7278108, __x=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_list.h:483
#13 insert > > (this=0xa7278108, __x=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_list.h:461
#14 stlp_std::list >::operator= (this=0xa7278108, __x=...) at /view/BLD-cm_8_6_2_new-raw-d/vob/ccm_tpl/release/include/stlport/stl/_list.c:114
#15 0x083dc12f in CTIHandler::ready_CtiCallParkRetrieveParkDNRes (this=0xaabaa498, s=...) at ProcessCTIHandler.cpp:6268
#16 0x084162f6 in CTIHandler::fireSignal (this=0xaabaa498, sdlSignal=...) at ../Include/ProcessCTIHandler.hpp:983
#17 0x086003e0 in SdlProcessBase::inputSignal (this=0xaabaa498, rSignal=0xa0fcc3e0, traceType=SignalRouterThread, highPriority=0, normalPriority=52, lowPriority=0, veryLowPriority=0, lazyPriority=0, dbUpdatePriority=0) at SdlProcessBase.cpp:363
#18 0x086069a4 in SdlRouter::callProcess (this=0x9a9ba60, _sdlSignal=0xa0fcc3e0, _deleteSignal=@0x2c083a7, _traceType=SignalRouterThread, _hp=0, _np=52, _lp=0, _vlp=0, _lzp=0, _dbp=0) at SdlRouter.cpp:258
#19 0x086070d8 in SdlRouter::scheduler (this=0x9a9ba60) at SdlRouter.cpp:164
#20 0x0023a6e1 in start_thread () from /lib/libpthread.so.0
#21 0x0298bd3e in clone () from /lib/libc.so.6

Related Community Discussions

Call Park を BAT でインポートすると Core File が出力される
2015年10月14日(初版) 2015年10月14日(アップデート) TAC SR Collection 主な問題 | Cisco Unified Communications Manager (CUCM) で、Call Park の設定を Bulk Administration Tool (以下BAT) | を使ってインポートすると、インポート自体は成功しますが、CTIManager Service が Core File を出力し、再起動されることがあります。   原因 不具合 <key>CSCun66866</key> が原因です。 BAT を用いてのCall Park 投入で Directory Number (以下DN) の総数を計算するためのメモリの使用方法に問題があり、メモリリークを起こすことがあります。特に大量の Call Park の DN が含まれている場合、それに伴い処理負荷も増加するので本事象の発生確率が高くなります。   解決策 不具合が修正されているバージョンにアップグレードしてください。
Latest activity: Oct 14, 2015
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.