Xymon Mailing List Archive search

timediff

2 messages in this thread

list Cami · Tue, 02 Aug 2011 08:52:46 +0200 ·
Hi all,

Could someone explain why the following would be occuring

Tue Aug 02 08:30:43 2011 NOT ok

yellow System clock is 138 seconds off (max 60)

local: Tue Aug 02 08:30:43 2011
UTC: Tue Aug 02 06:30:43 2011

Both the Xymon server and client machine (Windows) are syncing off the 
same router/source. The times look identical so where does the 138 
seconds skew come from?

Regards,
Cami
list Henrik Størner · Tue, 02 Aug 2011 10:22:38 +0200 ·
quoted from Cami
On 02-08-2011 08:52, Cami wrote:
Could someone explain why the following would be occuring

Tue Aug 02 08:30:43 2011 NOT ok

yellow System clock is 138 seconds off (max 60)

local: Tue Aug 02 08:30:43 2011
UTC: Tue Aug 02 06:30:43 2011

Both the Xymon server and client machine (Windows) are syncing off the
same router/source. The times look identical so where does the 138
seconds skew come from?
First, see the explanation of the CLOCK setting in the analysis.cfg man-page.

The client inserts a timestamp in the client message, usually just before it transmits the message to the Xymon server (not sure if that is the case with BBWin, though - it might add the timestamp when it begins collecting data, which could explain it if the eventlog scanning takes a long time). This timestamp is then compared with the time that Xymon receives the message. In your case, they are 138 seconds different.


Regards,
Henrik