KRON Error

darren-mcleish · ‎06-03-2025

I am getting this message when using Kron

Job completes itself

sw1#sh kron schedule
Kron Occurrence Schedule
back active, will run once in ERROR - Timer Not Running

sw1#sh kron schedule
Kron Occurrence Schedule

M02@rt37 · ‎06-03-2025

Hello @darren-mcleish

What is the platform ?

Do you have time well configured on it ?

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

darren-mcleish · ‎06-03-2025

9300

M02@rt37 · ‎06-03-2025

Thanks.

Do you have time well configured on it ?

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

darren-mcleish · ‎06-03-2025

Clock has been set
Even using ntp windows domain controller

M02@rt37 · ‎06-03-2025

Ok @darren-mcleish

Please do #sh ntp status and be sure that clock in SYNC state.

Thanks.

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

darren-mcleish · ‎06-04-2025

Sw1#sh ntp status
Clock is synchronized, stratum 5, reference is 10.31.80.22
nominal freq is 250.0000 Hz, actual freq is 249.9959 Hz, precision is 2**10
ntp uptime is 2223542200 (1/100 of seconds), resolution is 4016
reference time is EBEB4725.E3958378 (08:28:53.889 AEST Thu Jun 5 2025)
clock offset is -14.4569 msec, root delay is 17.59 msec
root dispersion is 108.23 msec, peer dispersion is 1.05 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000016274 s/s
system poll interval is 1024, last update was 1569 sec ago.

VIC-130-L27N-01#sh ver | inc C9300
cisco C9300-48UN (X86) processor with 1301994K/6147K bytes of memory.
Model Number : C9300-48UN
* 1 65 C9300-48UN 17.12.03 CAT9K_IOSXE INSTALL
2 65 C9300-48UN 17.12.03 CAT9K_IOSXE INSTALL
3 65 C9300-48UN 17.12.03 CAT9K_IOSXE INSTALL
Model Number : C9300-48UN
Model Number : C9300-48UN

darren-mcleish · ‎06-04-2025

Still getting the error
back active, will run once in ERROR - Timer Not Running

sw#sh clock
10:37:24.311 AEST Thu Jun 5 2025
sw#sh ntp status
Clock is synchronized, stratum 5, reference is 10.31.80.22
nominal freq is 250.0000 Hz, actual freq is 249.9970 Hz, precision is 2**10
ntp uptime is 78000 (1/100 of seconds), resolution is 4016
reference time is EBEB6255.E6A7F218 (10:24:53.901 AEST Thu Jun 5 2025)
clock offset is -12.4986 msec, root delay is 19.65 msec
root dispersion is 270.68 msec, peer dispersion is 4.64 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000011931 s/s
system poll interval is 128, last update was 771 sec ago.
sw#conf t
Enter configuration commands, one per line. End with CNTL/Z.
sw(config)#kron policy-list back
sw(config-kron-policy)#cli copy run tftp://10.31.80.26/sw-confg.txt
sw(config-kron-policy)#exit
sw(config)#kron occurrence back at 10:40 5 oneshot
sw(config-kron-occurrence)#policy-list back
sw(config-kron-occurrence)#exit
sw(config)#exit
sw#sh run | sec kron
kron occurrence back at 10:40 5 oneshot
policy-list back
kron policy-list back
cli copy run tftp://10.31.80.26/sw-confg.txt
sw#sh kron schedule
Kron Occurrence Schedule
back inactive, will run once in 0 days 00:01:04 at 10:40 on day 5 of the month

sw#sh kron schedule
Kron Occurrence Schedule
back inactive, will run once in 0 days 00:00:40 at 10:40 on day 5 of the month

sw#sh kron schedule
Kron Occurrence Schedule
back inactive, will run once in 0 days 00:00:22 at 10:40 on day 5 of the month

sw#sh clock
10:39:41.740 AEST Thu Jun 5 2025
sw#sh kron schedule
Kron Occurrence Schedule
back inactive, will run once in 0 days 00:00:14 at 10:40 on day 5 of the month

sw#sh kron schedule
Kron Occurrence Schedule
back inactive, will run once in 0 days 00:00:05 at 10:40 on day 5 of the month

sw#sh kron schedule
Kron Occurrence Schedule
back active, will run once in ERROR - Timer Not Running

VIC-130-L24S-01#sh kron schedule
Kron Occurrence Schedule

VIC-130-L24S-01#sh ver | inc C9300
cisco C9300-48UN (X86) processor with 1301994K/6147K bytes of memory.
Model Number : C9300-48UN
* 1 65 C9300-48UN 17.12.03 CAT9K_IOSXE INSTALL
2 65 C9300-48UN 17.12.03 CAT9K_IOSXE INSTALL
3 65 C9300-48UN 17.12.03 CAT9K_IOSXE INSTALL
Model Number : C9300-48UN
Model Number : C9300-48UN

M02@rt37 · ‎06-04-2025

Thanks for these outputs @darren-mcleish.

Do you try to delete your kron occurence and reconfigure it ? Same error ?

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

Yogeshraje · ‎06-03-2025

Please ensure that both the policy and occurrence are properly configured:

1. Define the kron policy list

conf t
kron policy-list backup
cli copy running-config tftp://<TFTP_SERVER_IP>/backup-config
exit

2. Schedule the kron job (occurrence), You need to create a recurring or one-time occurrence:

conf t
kron occurrence back in 5 recurring
policy-list backup
exit

This schedules the backup job to start in 5 minutes and run periodically.

After configuration, check:

show kron schedule

darren-mcleish · ‎06-04-2025

Still getting the error

back active, will run once in ERROR - Timer Not Running

sw#sh clock

10:37:24.311 AEST Thu Jun 5 2025

sw#sh ntp status

Clock is synchronized, stratum 5, reference is 10.31.80.22

nominal freq is 250.0000 Hz, actual freq is 249.9970 Hz, precision is 2**10

ntp uptime is 78000 (1/100 of seconds), resolution is 4016

reference time is EBEB6255.E6A7F218 (10:24:53.901 AEST Thu Jun 5 2025)

clock offset is -12.4986 msec, root delay is 19.65 msec

root dispersion is 270.68 msec, peer dispersion is 4.64 msec

loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000011931 s/s

system poll interval is 128, last update was 771 sec ago.

sw#conf t

Enter configuration commands, one per line. End with CNTL/Z.

sw(config)#kron policy-list back

sw(config-kron-policy)#cli copy run tftp://10.31.80.26/sw-confg.txt

sw(config-kron-policy)#exit

sw(config)#kron occurrence back at 10:40 5 oneshot

sw(config-kron-occurrence)#policy-list back

sw(config-kron-occurrence)#exit

sw(config)#exit

sw#sh run | sec kron

kron occurrence back at 10:40 5 oneshot

policy-list back

kron policy-list back

cli copy run tftp://10.31.80.26/sw-confg.txt

sw#sh kron schedule

Kron Occurrence Schedule

back inactive, will run once in 0 days 00:01:04 at 10:40 on day 5 of the month

sw#sh kron schedule

Kron Occurrence Schedule

back inactive, will run once in 0 days 00:00:40 at 10:40 on day 5 of the month

sw#sh kron schedule

Kron Occurrence Schedule

back inactive, will run once in 0 days 00:00:22 at 10:40 on day 5 of the month

sw#sh clock

10:39:41.740 AEST Thu Jun 5 2025

sw#sh kron schedule

Kron Occurrence Schedule

back inactive, will run once in 0 days 00:00:14 at 10:40 on day 5 of the month

sw#sh kron schedule

Kron Occurrence Schedule

back inactive, will run once in 0 days 00:00:05 at 10:40 on day 5 of the month

sw#sh kron schedule

Kron Occurrence Schedule

back active, will run once in ERROR - Timer Not Running

VIC-130-L24S-01#sh kron schedule

Kron Occurrence Schedule

VIC-130-L24S-01#sh ver | inc C9300

cisco C9300-48UN (X86) processor with 1301994K/6147K bytes of memory.

Model Number : C9300-48UN

* 1 65 C9300-48UN 17.12.03 CAT9K_IOSXE INSTALL

2 65 C9300-48UN 17.12.03 CAT9K_IOSXE INSTALL

3 65 C9300-48UN 17.12.03 CAT9K_IOSXE INSTALL

Model Number : C9300-48UN

##- Please type your reply above this line -##

Yogeshraje · ‎06-05-2025

Use an embedded TCL script instead of KRON for interactive or file transfer commands.

Remove the KRON config:

no kron occurrence back
no kron policy-list back

Configure an EEM applet:

conf t
event manager applet save-config
event timer absolute time 10:45 recurring
action 1.0 cli command "enable"
action 2.0 cli command "copy running-config tftp://10.31.80.26/sw-confg.txt"
end
write memory

Ensure TFTP server is reachable and allows write access.