AnsweredAssumed Answered

CDM - InternalAlarm: Unable to get CPU data (error)

Question asked by gareth.roberts on Feb 5, 2018
Latest reply on Mar 1, 2018 by SHAWN WALSH

HI there.

 

This question was "Answered" previously, but no aparent solution was confirmed.

We have several machines across two hubs with the same issue. The CDM log file consistantly shows:

 

Feb  5 15:13:51:990 [3852] cdm: GetHostInfo - unable to get system uptime
Feb  5 15:13:53:028 [3852] cdm: ntgetuptime: Unable to get the 'System Up Time' counter of the 'System' performance object
Feb  5 15:13:53:294 [3852] cdm: ntgetuptime: Unable to get the 'System Up Time' counter of the 'System' performance object
Feb  5 15:13:53:559 [3852] cdm: ntgetuptime: Unable to get the 'System Up Time' counter of the 'System' performance object
Feb  5 15:13:53:559 [3852] cdm: GetHostInfo - unable to get system uptime
Feb  5 15:13:54:560 [3852] cdm: ntgetuptime: Unable to get the 'System Up Time' counter of the 'System' performance object
Feb  5 15:13:54:825 [3852] cdm: ntgetuptime: Unable to get the 'System Up Time' counter of the 'System' performance object
Feb  5 15:13:55:091 [3852] cdm: ntgetuptime: Unable to get the 'System Up Time' counter of the 'System' performance object
Feb  5 15:13:55:091 [3852] cdm: GetHostInfo - unable to get system uptime
...

Etc..

Has there been any further fix information on this issue? Restarting the Robot, or the probe by itself makes no difference.

The previous fix mentioning the Performance counter reset would need the seerver to be rebooted. At this time has anyone found this to be an effective fix, or should a case be raised, as we are missing some data, and want to avoid losing much more.

All assistance is appreciated. Many thanks.

Outcomes