cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2826
Views
0
Helpful
1
Replies

%SCHED-3-STUCKTMR: Sleep with expired timer error logs is existing with version 15.5(3)Sla

Hi Team,

 %SCHED-3-STUCKTMR: Sleep with expired timer error logs is existing with version 15.5(3)Sla in cisco ISR4331/K9

Version detail:

Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(3)S1a, RELEASE SOFTWARE (fc1)

Error logs:

Oct  3 09:41:50.901: %SCHED-3-STUCKTMR: Sleep with expired timer 7FBF428B5EC0, time 0x2 (31w0d ago). -Process= "Crypto CA", ipl= 2, pid= 363
-Traceback= 1#fab6c02b06d7c08491ca8b7e6d06ee5a  :7FBFA277E000+9E2E19A :7FBFA277E000+9E3176D :7FBFA277E000+A1E198A
Oct  3 09:42:50.907: %SCHED-3-STUCKTMR: Sleep with expired timer 7FBF428B5EC0, time 0x2 (31w0d ago). -Process= "Crypto CA", ipl= 2, pid= 363
-Traceback= 1#fab6c02b06d7c08491ca8b7e6d06ee5a  :7FBFA277E000+9E2E19A :7FBFA277E000+9E3176D :7FBFA277E000+A1E198A
Oct  3 09:43:50.917: %SCHED-3-STUCKTMR: Sleep with expired timer 7FBF428B5EC0, time 0x2 (31w0d ago). -Process= "Crypto CA", ipl= 2, pid= 363
-Traceback= 1#fab6c02b06d7c08491ca8b7e6d06ee5a  :7FBFA277E000+9E2E19A :7FBFA277E000+9E3176D :7FBFA277E000+A1E198A
Oct  3 09:44:50.924: %SCHED-3-STUCKTMR: Sleep with expired timer 7FBF428B5EC0, time 0x2 (31w0d ago). -Process= "Crypto CA", ipl= 2, pid= 363
-Traceback= 1#fab6c02b06d7c08491ca8b7e6d06ee5a  :7FBFA277E000+9E2E19A :7FBFA277E000+9E3176D :7FBFA277E000+A1E198A
us-nasm-rtr001#

I need to fix this issue or errors occuring from this device cisco ISR4331/K9, if anybody have idea please share it

 

 

1 Reply 1

Mark Malone
VIP Alumni
VIP Alumni

Hi

looks to be cosmetic should not be effecting your device , you will need to upgrade/downgrade if you want to avoid it as its software related or use logging discriminator and try block it from flooding the logs

SCHED-3-STUCKMTMR

A process can register to be notified when various events occur in the router. This specific message appears whenever a registered timer expires and the timer value is unchanged after the process executes two successive times. This is always a cosmetic software-related issue.

These messages on the console indicate such a problem:

%SCHED-3-STUCKMTMR: Sleep with expired managed timer 1C7410, 
time 0x1063F9C52 (00:00:00 ago).
-Process= "IP SNMP", ipl= 6, pid= 44
-Traceback= 31BC79A 31BC9C0 323E130
Review Cisco Networking for a $25 gift card