SecureStack/G-Series with many "XX_Call() failure in _checkTimers for queue 0" errors

  • 0
  • 1
  • Article
  • Updated 5 years ago
  • (Edited)
Article ID: 11984 

Products
SecureStack C3, firmware 1.01.04.0001 through 1.02.06.0004
SecureStack C2, firmware 5.02.03.0012 through 5.02.06.0004
G-Series, firmware 1.02.03.0010 through 1.02.06.0004 

Changes
Routing is enabled and OSPF has been configured, with VRRP. 

Symptoms
Hundreds of error messages, all with the same date/time stamp, seen in the current.log file (5487) and syslog. 

SecureStack f/w 1.02.02.0009 example, from the output of a 'show support':
<162>Jan 22 21:20:13 0.0.0.0-1 SIM[225076792]: timer.c(993) 88576 %%
XX_Call() failure in _checkTimers for queue 0 thread 0x8b55cc0
<162>Jan 22 21:20:13 0.0.0.0-1 SIM[225076792]: timer.c(993) 88577 %%
XX_Call() failure in _checkTimers for queue 0 thread 0x8b55cc0
<162>Jan 22 21:20:13 0.0.0.0-1 SIM[225076792]: timer.c(993) 88578 %%
XX_Call() failure in _checkTimers for queue 0 thread 0x8b55cc0
. . .
<162>Jan 22 21:20:13 0.0.0.0-1 SIM[225076792]: timer.c(993) 88830 %%
XX_Call() failure in _checkTimers for queue 0 thread 0x8b55cc0

G-Series f/w 1.02.04.0005 example, from the output of a 'show support':
<162>May 2 08:25:48 0.0.0.0-1 SIM[222550104]: timer.c(993) 583 %%
XX_Call() failure in _checkTimers for queue 0 thread 0xa62051
<162>May 2 08:25:48 0.0.0.0-1 SIM[222550104]: timer.c(993) 584 %%
XX_Call() failure in _checkTimers for queue 0 thread 0xa62051
<162>May 2 08:25:48 0.0.0.0-1 SIM[222550104]: timer.c(993) 585 %%
XX_Call() failure in _checkTimers for queue 0 thread 0xa62051
. . .
<162>May 2 08:25:48 0.0.0.0-1 SIM[222550104]: timer.c(993) 757 %%
XX_Call() failure in _checkTimers for queue 0 thread 0xa62051

A similar message is described in 10277

Solution
For the C3, upgrade to firmware 6.03.01.0008 or higher.
For the C2, upgrade to firmware 5.02.07.0006 or higher.
For the G-Series, upgrade to firmware 6.03.01.0008 or higher. 

Release notes state, in the 'Firmware Changes and Enhancements section:
12295   Corrected a potential buffer allocation issue associated with OSPF which could cause the unit to stop forwarding traffic.

Follow-up

Since the above-stated fix, there is a new permutation of this issue with a new phrase appended to the end of the message, seen with the C5/C3/C2/G-Series:
<161>Jan 6 06:15:56 10.1.1.80-1 SIM[88524840]: timer.c(995) 1288968 %%
XX_Call() failure in _checkTimers for queue 0 thread 0x847adb8. A timer
has fired but the message queue that holds the event has filled up.
Diagnostic code has been added to allow for a more in-depth study of the problem, and to limit message frequency:
For the C5/C3/G, upgrade to firmware 6.42.11.0006 (including 6.61.02.0007+) or higher.
Release notes state, in the 'Firmware Changes and Enhancements' section:
16067    Addressed an issue whereby the following CLI messages were scrolled continuously on the console "SIM[149535472]: timer.c(995) 1001 %% XX_Call() failure in _checkTimers for queue 0 thread 0xfc8ad00. A timer has fired but the message queue that holds the event has filled".

For the C5/C3/G, upgrade to 6.61 firmware 6.61.13.0006 or higher.
Release notes state, in the 'Firmware Changes and Enhancements' section:
18095   Corrected a message queuing issue that may have caused loss of management or loss of ospf adjacency, with the resulting log entry, "timer.c(995) 4278 %% XX_Call() failure in _checkTimers".

For the C5, upgrade to firmware 6.81.02.0007 or higher.
Release notes state, in the 'Firmware Changes and Enhancements' section:
18095    Corrected a message queuing issue that may have caused loss of management or loss of ospf adjacency, with the resulting log entry, "timer.c(995) 4278 %% XX_Call() failure in _checkTimers".
Photo of FAQ User

FAQ User, Official Rep

  • 13,620 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.