AnsweredAssumed Answered

This clock skew is too large to handle without a restart, so to maintain internal consistency of time-oriented metric data, the EM will now exit.

Question asked by lkabamba1.1 on Feb 3, 2015
Latest reply on Feb 6, 2015 by attcr02

CA APM 9.5.

We are regularely getting the following messages:

 

2/02/15 09:29:59.659 PM AST [ERROR] [master clock] [Manager.Clock] The system clock, previously set at 1422919444752 mS, has been reset to 1422901799659 mS.   This clock skew is too large to handle without a restart, so to maintain internal consistency of time-oriented metric data, the EM will now exit.  

2/02/15 09:30:01.706 PM AST [INFO] [Thread-7447] [Manager] Beginning orderly shutdown...

 

This causes our EM to shutdown an lose valuable performance data. Can you please advise how to permanently resolve this?

 

Thanks,

Luke

Outcomes