Clocks Not Synchronized

Clocks Not Synchronized

[Nick Couchman]

I'm setting up ceph and looking at the output of "ceph -w" and I'm seeing lots of warnings about messages from mon.X being stamped in the future (142 seconds), clocks not synchronized.  However, all of these systems use NTP, and if I use the "date" command to see the system time, they are definitely synchronized to within a second or so - definitely not out of sync 142 seconds.  What else should I check?

Thanks - Nick



--------

This e-mail may contain confidential and privileged material for the sole use of the intended recipient.  If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information.  In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way.  If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox.  Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

Re: Clocks Not Synchronized

[Greg Farnum]

On Wednesday, March 21, 2012 at 8:30 AM, Nick Couchman wrote:
> I'm setting up ceph and looking at the output of "ceph -w" and I'm seeing lots of warnings about messages from mon.X being stamped in the future (142 seconds), clocks not synchronized. However, all of these systems use NTP, and if I use the "date" command to see the system time, they are definitely synchronized to within a second or so - definitely not out of sync 142 seconds. What else should I check?
>  

All the check for future timestamps does is get the time and compare to the one in a lease message. The only thing I can think of is if you've set the "clock offset" parameter on one machine, which seems unlikely…The other possibilities are that
1) we somehow broke how we're passing timestamps along and nobody else has seen it. This is unlikely — we haven't made any changes to this in a long time that I'm aware of.
2) one of the Monitors is running gettimeofday() and seeing that the passed-along timestamp (from gettimeofday() on the other host) is 142 seconds in the future.
So…try running date on each of them again? :) Unless people are aware of date and gettimeofday() somehow not being in sync?
-Greg

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html