ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
CA UIM -Error in the controller.log: "The next admin check time is too far into the future"
Article ID: 34362
Updated On:
Products
DX Unified Infrastructure Management (Nimsoft / UIM)
NIMSOFT PROBES
Issue/Introduction
Error in the CA UIM 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
Release: CNMSPP99000-8.47-Unified Infrastructure Mgmt-Server Pack-- On Prem
Component:
Component:
Resolution
Usually this is an indication that the time on the robot is being changed.
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
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.
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
- Complete level 3 robot / controller log from start to the controller restarts
- 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.
Feedback
Yes
No
Powered by
