Preview Tool

Cisco Bug: CSCup13238 - TFTP service crashes on CUCM 8.6.2

Last Modified

Jul 31, 2016

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases


Description (partial)

++ TFTP process will Crash and recover on its own with the following trace back:
#0 0x00bbe206 in raise () from /lib/ 
#0 0x00bbe206 in raise () from /lib/ 
#1 0x00bbfbd1 in abort () from /lib/ 
#2 0x00bf5b6b in __libc_message () from /lib/ 
#3 0x00bfdf36 in _int_free () from /lib/ 
#4 0x00bfe369 in free () from /lib/ 
#5 0x00530041 in operator delete(void*) () from /usr/local/cm/lib/ 
#6 0x080dc2f0 in stlp_std::deque >::_M_pop_front_aux() () 
#7 0x080da0bd in NetworkService::httpsigpollWorkerThread(int) () 
#8 0x080da35f in NetworkService::httpsigpollWorkerThreadInit(void*) () 
#9 0x0024c5a8 in ACE_Thread_Adapter::invoke_i (this=0x984a25a8) at Thread_Adapter.cpp:151 
#10 0x0024c621 in ACE_Thread_Adapter::invoke (this=0x984a25a8) at Thread_Adapter.cpp:95 
#11 0x001c9541 in ace_thread_adapter (args=0x984a25a8) at Base_Thread_Adapter.cpp:137 
#12 0x00a286e1 in start_thread () from /lib/ 
#13 0x00c6834e in clone () from /lib/ 

++ TFTP service is crashing because of the following :

kill -9(SIGKILL)
kill (SIGTERM)

It seems the tftp process has been terminated by a kill command without -9.

Anyways tftp code do handle the SIGTERM scenarios. So in this case, it should be smooth termination of tftp rather a crash. While walking through the tftp code, We found an unsafe code block where we are handling this signal.
Bug details contain sensitive information and therefore require a 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.