Occasionally, you may see the following entry in the Event Log of your VTrak or Vess:
SeqNo: xxx1
Device: Subsys
EventId: 0x00240002 Severity: Warning
TimeStamp: April 1, 2017 02:05:15 DefaultId: 0x00240002
SpecData: 0002200100BBB8BB58 0000000000000000 0000000000000000 00000000000000
Description: Scheduled task failed
SeqNo: xxx2
Device: Subsys
EventId: 0x00240002 Severity: Warning
TimeStamp: April 1, 2017 02:06:23 DefaultId: 0x00240002
SpecData: 0002200100BBB8BB58 0000000000000000 0000000000000000 00000000000000
Description: Scheduled task failed
If you have the NTP service enabled on your VTrak or Vess, the most common cause is that the NTP service could not reach the configured NTP server or servers.
By default, the first attempt to reach the NTP server is made at 02:05, and the second attempt to reach the NTP server is made one minute later at 02:06.
NTP: Enabled
TimeZone: (GMT -5:00) Eastern Time(US & Canada),New York,Toronto,Havana,Indiana
NumberOfTimeServer: 1
Server1: 192.168.0.20
DST: Enabled
DSTStartTime: Mar 2nd Sun
DSTEndTime: Nov 1st Sun
Last Synchronization Time: April 1, 2017 02:06:23
Last Synchronization Result: Failed on server 192.168.0.20
Next Synchronization Time: April 2, 2017 02:05 AM
The above example shows that the NTP service is enabled, and that it will synchronize the time with the server at 192.168.0.20 at 02:05 AM each day.
The Last Synchronization Time will match the TimeStamp of the Event Log entry, and the Last Synchronization Result shows that the update with the server was unsuccessful.
If these errors occur every day, it can mean that the NTP service on the VTrak or Vess is not configured correctly, the server cannot be reached due to incorrect network configuration, network configuration issues, or some physical problem in between.
Some things to check would be:
- Ensure that the NTP service is running on the designated server(s), and it is reachable from the VTrak or Vess. (Use the “ping” command from the CLI)
- Check the logs on that server to see if there are any error entries around that time.
- Check your network for any events at that time (if you have the facility to do so).
