3.1.0.125: CLOCK SKEW Fixed over 35 minutes - still "Active"
PDinCA
Posts: 642 Silver 1
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?
Why is this, please?
Jesus Christ: Lunatic, liar or Lord?
Decide wisely...
Decide wisely...
Comments
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 :?
Decide wisely...
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...
Decide wisely...