Error in the controller.log: "The next admin check time is too far into the future"
search cancel

Error in the controller.log: "The next admin check time is too far into the future"

book

Article ID: 34362

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Error in the robot controller logs about the next admin check is too far in the future.

The controller log shows:

The next admin check time is too far into the future (xxx s)
This indicates that the clock has been changed and a robot restart is needed.


The controller then restarts resulting in the robot going up and down continuously.
 

Environment

UIM 9.x or later

Resolution

Usually this is an indication that the time on the robot is being changed or the clock synchronization is broken on the server where the robot is installed
This could be due to a bad clock or a syncronization issue.

To confirm this you would need to collect two things from the affected robot

  1.  Complete level 3 robot / controller log from start to the controller restarts
  2.  A file containing a time stamp every ten seconds from controller start to restart



Ensure that the timestamp in the output from the batch file is every 10 seconds and doesn't 'leak time'
If it does then it could be a broken clock.
If it is a VM, then ensure you do not have time synchronization enabled on it.

Stop the robot, then correct the clock on the server and then start the robot.

Ensure the time on the server remains correct.