| Author |
Message |
PDinCA
Joined: 25 Jul 2005 Posts: 464 Location: Costa Mesa, CA, USA
|
Posted: Wed Jun 06, 2012 1:21 am Post subject: 3.1.0.125: CLOCK SKEW Fixed over 35 minutes - still "Active" |
|
|
w32tm /config /update was issued on the problem node and on the Base Monitor server but the HIGH Alert is still "Active".
Why is this, please? |
|
| Back to top |
|
 |
PDinCA
Joined: 25 Jul 2005 Posts: 464 Location: Costa Mesa, CA, USA
|
Posted: Fri Jun 08, 2012 2:27 am Post subject: |
|
|
| Code: |
| Status: Ended Time raised: 5 Jun 2012 1:36 PM Time ended: 5 Jun 2012 9:41 PM |
It appears to have taken about 2 hrs 20 minutes after the time was sync'd on the base and node2 for SQL Monitor to realize there was no longer an issue... Is this a bit excessive a lag?
Strangely, we didn't reset the active node until today but on the same day (Jun 5), for 15 minutes there was an apparent skew between the base and node1 of 17 seconds that lasted for only 15 minutes. Curious  |
|
| Back to top |
|
 |
PDinCA
Joined: 25 Jul 2005 Posts: 464 Location: Costa Mesa, CA, USA
|
Posted: Fri Jun 08, 2012 5:40 pm Post subject: |
|
|
Per a very helpful response by Brian Donahue:
My situation is that the Base Monitor is on a VM and monitors a physical active-passive cluster.
There is reference within the post cited above to a VMWare "tinker" setting that I don't profess to understand but looks like it should always be in place for my kind of architecture.
Hope this helps someone else...  |
|
| Back to top |
|
 |
|
|
All times are GMT + 1 Hour
|
| Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group