Guest

Preview Tool

Cisco Bug: CSCuo94296 - qos_ea process crashes continously

Last Modified

Jul 16, 2019

Products (1)

  • Cisco 12000 Series Routers

Known Affected Releases

4.1.2.LC

Description (partial)

Symptom:
qos_ea process crashes continuously and will enters into an unrecoverable state.

We have seen multiple occurrence. In all the instances, we believe the trigger is interface flap (Multi link interface flap)

Every time a interface flap, a BW change notification is send to the qos_ea process.

LC/0/1/CPU0:May  4 00:11:07.278 : sysdb_svr_local[314]: %SYSDB-SYSDB-6-TIMEOUT_EDM : EDM request for 'oper/qos_ma/node/10/stats/interface/Multilink0_1_0_0_4/dir/input/' from 'mibd_interface' (jid 1094, node 0/7/CPU0). No response from 'qos_ma' (jid 282, node 0/1/CPU0) within the timeout period (100 seconds) 
<snip>
LC/0/1/CPU0:May  4 00:11:21.766 : ifmgr[182]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Serial0/1/0/0/12/12:0, changed state to Down 
LC/0/1/CPU0:May  4 00:11:22.008 : qos_ea[281]: %QOS-QOSEA-3-ERROR : QoSEA-Err: QoS EA is in unrecoverable state, exiting.  : pkg/bin/qos_ea : (PID=1491023) :  -Traceback= 8031d38 802009c
LC/0/1/CPU0:May  4 00:11:22.513 : qos_ea[281]: %QOS-QOSEA-3-ERROR : QoSEA-Err: QoS EA is in unrecoverable state, exiting.  : pkg/bin/qos_ea : (PID=1495119) :  -Traceback= 8031d38 802009c
LC/0/1/CPU0:May  4 00:11:22.064 : sysmgr[82]: qos_ea(1) (jid 281) (pid 1491023) (fail_count 1) abnormally terminated, restart scheduled 
LC/0/1/CPU0:May  4 00:11:23.010 : qos_ea[281]: %QOS-QOSEA-3-ERROR : QoSEA-Err: QoS EA is in unrecoverable state, exiting.  : pkg/bin/qos_ea : (PID=1499215) :  -Traceback= 8031d38 802009c
LC/0/1/CPU0:May  4 00:11:22.572 : sysmgr[82]: qos_ea(1) (jid 281) (pid 1495119) (fail_count 2) abnormally terminated, restart scheduled 
LC/0/1/CPU0:May  4 00:11:23.486 : qos_ea[281]: %QOS-QOSEA-3-ERROR : QoSEA-Err: QoS EA is in unrecoverable state, exiting.  : pkg/bin/qos_ea : (PID=1503311) :  -Traceback= 8031d38 802009c
LC/0/1/CPU0:May  4 00:11:23.058 : sysmgr[82]: qos_ea(1) (jid 281) (pid 1499215) (fail_count 3) abnormally terminated, restart scheduled 
LC/0/1/CPU0:May  4 00:11:23.800 : ifmgr[182]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Serial0/1/0/0/9/3:0, changed state to Up 
LC/0/1/CPU0:May  4 00:11:23.813 : ifmgr[182]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Serial0/1/0/0/9/3:0, changed state to Down 
LC/0/1/CPU0:May  4 00:11:23.541 : sysmgr[82]: qos_ea(1) (jid 281) (pid 1503311) (fail_count 4) abnormally terminated, restart scheduled 
LC/0/1/CPU0:May  4 00:11:24.022 : qos_ea[281]: %QOS-QOSEA-3-ERROR : QoSEA-Err: QoS EA is in unrecoverable state, exiting.  : pkg/bin/qos_ea : (PID=1507407) :  -Traceback= 8031d38 802009c
LC/0/1/CPU0:May  4 00:11:24.041 : ifmgr[182]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Serial0/1/0/0/11/7:0, changed state to Up 
LC/0/1/CPU0:May  4 00:11:24.050 : ifmgr[182]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Serial0/1/0/0/11/7:0, changed state to Down 
LC/0/1/CPU0:May  4 00:11:24.126 : sysmgr[82]: %OS-SYSMGR-3-ERROR : qos_ea(1) (jid 281) exited, will be respawned with a delay (slow-restart)   
LC/0/1/CPU0:May  4 00:11:24.130 : sysmgr[82]: %OS-SYSMGR-3-ERROR : qos_ea(281) (fail count 5) will be respawned in 120 seconds  
LC/0/1/CPU0:May  4 00:11:24.125 : sysmgr[82]: qos_ea(1) (jid 281) (pid 1507407) (fail_count 5) abnormally terminated, restart scheduled 
LC/0/1/CPU0:May  4 00:11:24.722 : ifmgr[182]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Serial0/1/0/0/9/4:0, changed state to Up 
LC/0/1/CPU0:May  4 00:11:24.735 : ifmgr[182]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Multilink0/1/0/0/51, changed state to Up 
<snip>
LC/0/1/CPU0:May  4 00:12:47.343 : sysdb_svr_local[314]: %SYSDB-SYSDB-6-TIMEOUT_EDM : EDM request for 'oper/qos_ma/node/10/stats/interface/Serial0_1_0_0_11_8:0/dir/input/' from 'mibd_interface' (jid 1094, node 0/7/CPU0). No response from 'qos_ma' (jid 282, node 0/1/CPU0) within the timeout period (100 seconds)

Conditions:
qos_ea process will crash continuously, generating core dump files.
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.