Guest

Preview Tool

Cisco Bug: CSCut55913 - Fatal Signal 6: Aborted client_bounce()

Last Modified

Dec 24, 2016

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases

17.2.0

Description (partial)

Symptom:
sessmgr crash and  following error has been printed :
Failure: Command failed: Internal error - NO RSP


[local]ASR5000_2_MM2# sho crash num 19
********************* CRASH #19 ***********************
SW Version          : 17.2.0
Similar Crash Count : 8
Time of First Crash : 2015-Mar-25+14:53:07

Fatal Signal 6: Aborted
  PC: [0af8fe09/X] client_bounce()
  Signal from: sitmain pid=4058 uid=0
  Process: card=7 cpu=0 arch=X pid=5729 cpu=~100% argv0=sessmgr
  Crash time: 2015-Mar-25+13:53:11 UTC
  Recent errno: 11 Resource temporarily unavailable
  Stack (2840@0xffffd000):
    [0af8fe09/X] client_bounce() sp=0xffffd0e8
    [0af91ea9/X] xtcp_client_timer_tick() sp=0xffffd5e8
    [0afb9f2b/X] sn_loop_run() sp=0xffffda98
    [0ad28b7d/X] main() sp=0xffffdb08

Conditions:
in order to empty the ?mme-service db record?, customer has executed the following CLI:

     conf
     context mme_ingress
     mme-service mme-svc
     no bind s1-mme 
     bind s1-mme ipv4-address 172.20.70.8 ipv4-address 172.20.70.21
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.