From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: clock syncronisation
Date: Thu, 08 Nov 2012 10:04:21 +0100 [thread overview]
Message-ID: <509B7595.1010809@profihost.ag> (raw)
Hello list,
is there any prefered way to use clock syncronisation?
I've tried running openntpd and ntpd on all servers but i'm still getting:
2012-11-08 09:55:38.255928 mon.0 [WRN] message from mon.2 was stamped
0.063136s in the future, clocks not synchronized
2012-11-08 09:55:39.328639 mon.0 [WRN] message from mon.2 was stamped
0.063285s in the future, clocks not synchronized
2012-11-08 09:55:39.328833 mon.0 [WRN] message from mon.2 was stamped
0.063301s in the future, clocks not synchronized
2012-11-08 09:55:40.819975 mon.0 [WRN] message from mon.2 was stamped
0.063360s in the future, clocks not synchronized
Stefan
next reply other threads:[~2012-11-08 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 9:04 Stefan Priebe - Profihost AG [this message]
2012-11-08 12:00 ` clock syncronisation Wido den Hollander
2012-11-08 12:19 ` Andrey Korolyov
2012-11-08 12:20 ` Stefan Priebe - Profihost AG
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=509B7595.1010809@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox