Reset Search
 

 

Article

ERS4800/ERS4900 - tCDTMain task loop causes stack breakup

« Go Back

Information

 
TitleERS4800/ERS4900 - tCDTMain task loop causes stack breakup
Symptoms
  • Messages 'CDT:call to cdt api function failed due to lock timeout' displayed in the syslog or log file continuously
  • May be preceded by port flapping
  • Messages indicate some intense activity on the CDT database
  • This causes other applications trying to access the CDT database to timeout and not complete the operation.
 
Feb  3 08:48:50 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=79,errno=3d0004)
Feb  3 08:48:47 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=78,errno=3d0004)
Feb  3 08:48:44 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=77,errno=3d0004)
Feb  3 08:48:41 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=76,errno=3d0004)
Feb  3 08:48:38 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=75,errno=3d0004)
Feb  3 08:48:35 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=74,errno=3d0004)
Feb  3 08:48:32 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=73,errno=3d0004)
Feb  3 08:48:29 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=72,errno=3d0004)
Feb  3 08:48:26 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=71,errno=3d0004)
Feb  3 08:48:23 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=70,errno=3d0004)
Feb  3 08:48:20 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=69,errno=3d0004)
Feb  3 08:48:17 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=68,errno=3d0004)
Feb  3 08:48:14 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=67,errno=3d0004)
Feb  3 08:48:11 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=66,errno=3d0004)
Feb  3 08:48:08 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=65,errno=3d0004)
Feb  3 08:48:05 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=64,errno=3d0004)
Feb  3 08:48:02 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=63,errno=3d0004)
Feb  3 08:47:59 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=62,errno=3d0004)
Feb  3 08:47:56 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=61,errno=3d0004)
Feb  3 08:47:53 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=60,errno=3d0004)
Feb  3 08:47:50 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=59,errno=3d0004)
Feb  3 08:47:47 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=58,errno=3d0004)
Feb  3 08:47:44 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=57,errno=3d0004)
Feb  3 08:47:41 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=56,errno=3d0004)
Feb  3 08:47:38 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=55,errno=3d0004)
Feb  3 08:47:35 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=54,errno=3d0004)
Feb  3 08:47:32 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=53,errno=3d0004)
Feb  3 08:47:29 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=52,errno=3d0004)
Feb  3 08:47:26 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=51,errno=3d0004)
Feb  3 08:47:22 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=50,errno=3d0004)
Feb  3 08:47:19 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=49,errno=3d0004)
Feb  3 08:47:16 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=48,errno=3d0004)
Feb  3 08:47:13 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=47,errno=3d0004)
Feb  3 08:47:10 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=46,errno=3d0004)
Feb  3 08:47:07 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=45,errno=3d0004)
Feb  3 08:47:04 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=44,errno=3d0004)
Feb  3 08:47:01 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=43,errno=3d0004)
Feb  3 08:45:39 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=20,errno=3d0004)
Feb  3 08:46:58 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=42,errno=3d0004)
Feb  3 08:46:55 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=41,errno=3d0004)
Feb  3 08:46:52 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=40,errno=3d0004)
Feb  3 08:46:49 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=39,errno=3d0004)
Feb  3 08:46:46 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=38,errno=3d0004)
Feb  3 08:46:43 SW-M06-E01-4-2-A CDT:call to cdt api function failed due to lock timeout (code=4798,total failures=37,errno=3d0004)


  • ERS4800 or ERS4900 stack breaking up and affecting attached devices and management of stack.
 
SW1-17-101-8-A#show stack-health
% Failed to query stack health for units 1 and 3.

SW1-17-101-8-A#show cpu-utilization 
----------------------------------------------------------------
                      CPU Utilization
----------------------------------------------------------------

Unit  Last 10 Sec, 1 Min, 10 Min, 60 Min, 24 Hrs, System Boot-Up
----------------------------------------------------------------
1          NA       NA      NA      NA      NA      NA       <<<
2          29%      29%     23%     23%     22%     22%      
3          NA       NA      NA      NA      NA      NA       <<< 
SW1-17-101-8-A#
  • It can affect the base unit or non-base-unit.

 
Environment
  • ERS4800 platform
  • BOSS release 5.10x and 5.11.x (or earlier)
  • ERS4900 platform
  • BOSS release 7.6.0 and 7.6.1 (or earlier)
Cause
Software malfunction that affected multiple logical paths such as sorting, traversing, inserting, deleting MAC address entries in the CDT database causing a tCDTMain task loop.
Resolution
For ERS 4800 platform upgrade to BOSS release 5.12.3 once released.
For ERS 4900 platform upgrade to BOSS release 7.6.2 
 
Additional notes
Tracking Jiras ERS454800-3014 & ERS495900-5212.

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255