Matrix X f/w 2.x IOMs crashing at 497 days of uptime

  • 0
  • 2
  • Article
  • Updated 5 years ago
  • (Edited)
Article ID: 14527 

Products
Matrix X-Series, firmware 2.0.0.0 through 2.0.1.0 

Symptoms
IOMs are becoming unstable at 497 days of uptime. The 'ess' process is also crashing at this level of uptime, causing the IOM to restart. 

Cause
In release 2.0.0.0, the linux kernel on the Matrix X was upgraded to version 2.6. Part of this upgrade was to resolve a previous 497 day bug that would destabilize the system. Unfortunately there is a bug remaining at the 497 day mark for the 'ess' process. 

Solution/Workaround
Upgrade to firmware 2.0.2.1 or higher.
Release notes state, in the 'Issues Resolved in release 2.0.2.1' section:

After a system has been up for 497 days the ESS processes on each IOM and the
CM are very likely to terminate abnormally producing syslog messages similar
to the following:

essDistServer@iom2: <Alert> [hh:mm:ss] x_lock.3 semTake(12000) failed 3997700
syslog@iom2: <Critical> [mm:mm:ss] !! CID 58 [status = 0x803a1000]: x_lock.3
semTake(12000) failed 3997700 !! 
kernel@iom2: <Warning> Enterasys Crashlog: Fault detected, calling handler 
kernel@iom2: <Alert> --Enterasys System Error Logger: Crash detected-- 
kernel@iom2: <Alert> Name = /ens/bin/ess 
kernel@iom2: <Alert> PID = 
kernel@iom2: <Alert> TGID = 
kernel@iom2: <Alert> Error code = 6

This is often immediately preceded by messages indicating an unexpected
spanning tree topology change. This can cause general network instability
while the modules are rebooting.

In lieu of installing this release that contains the fix for this issue the
problem can be worked around by scheduling a controlled system reset before
the system has been up for 497 days.
Photo of FAQ User

FAQ User, Official Rep

  • 13,620 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 2

There are no replies.

This conversation is no longer open for comments or replies.