[Xymon] FW: timediff

[Steve Kilduff]

We had this problem on windows machines, bbwin was analyzing the windows
event logs which took the length of time of the reported timediff. We had
100,000 log lines in the application log alone, these over-wrote themselves
every 20-30 minutes, even when you set a rule for bbwin to ignore these logs
it still must process the 100,000 lines in order to realize it can ignore
them. Our solution was to stop the application (mssql) logging these useless
"login succeeded" events to the application log.

For a short term test you could unload msgs.dll on the client side (if
possible) which I believe processes event logs, or you could clear or limit
the event log.

Steve

-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of
Cami
Sent: Tuesday, August 02, 2011 8:53 AM
To: xymon at xymon.com
Subject: [Xymon] timediff

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
______________________________
>
> _________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20110802/5ef99b41/attachment.html>