On 14-3-2017 10:04, Marco Gaiarin wrote:
Seems there's also possible to relax ceph constraint in ceph.conf, eg:
http://docs.ceph.com/docs/jewel/rados/configuration/mon-config-ref/
option 'mon clock drift allowed'. But i've not tackle with that...
For now: I have configured both ntpd
Mandi! lists
In chel di` si favelave...
> Tips, trics? All my reading/google voodo suggests me to install NTP, but we
> are already.
Seems there's also possible to relax ceph constraint in ceph.conf, eg:
http://docs.ceph.com/docs/jewel/rados/configuration/mon-config-ref/
option 'mon
Am 13.03.2017 um 16:40 schrieb lists:
But I'm not sure. Could they both be running and interfering with each
other?
Yep. Just do the second part too and check if that helps.
As far as I know, timesyncd doesn't care about other locally running
ntp-services and queries its own configured
Hi
On 13-3-2017 16:29, proxmox-pve-user-l...@licomonch.net wrote:
Hi,
did you follow
https://pve.proxmox.com/wiki/Configuration_of_Time_Syncronization_(NTP) ?
If not, maybe the systemd-timesyncd is messing something up?
It did not follow that page, but my config is similar to the first
Hi Mark,
On 13-3-2017 16:21, Mark Schouten wrote:
Probably one of your hardwareclocks is a bit flaky, which causes things
to skew more than 0.5 seconds. I've 'fixed' this by doing
minpoll 4 maxpoll 6
I have done that. Since it happens not very often, we'll have to wait a
while to find out if
Hi,
did you follow
https://pve.proxmox.com/wiki/Configuration_of_Time_Syncronization_(NTP) ?
If not, maybe the systemd-timesyncd is messing something up?
Am 13.03.2017 um 16:13 schrieb lists:
Hi,
Occasionally (three times a month or so) we are getting "clock skew
detected" errors on our
On Mon, 2017-03-13 at 16:13 +0100, lists wrote:
> Occasionally (three times a month or so) we are getting "clock skew
> detected" errors on our 3-host proxmox 4.3-1/e7cdc165 cluster.
Ceph is pretty critical about timesync.
Probably one of your hardwareclocks is a bit flaky, which causes things
Hi,
Occasionally (three times a month or so) we are getting "clock skew
detected" errors on our 3-host proxmox 4.3-1/e7cdc165 cluster.
ntpd is running on all three hosts, all configured to use the same
internal ntp server to sync with. Ntpdc reporting like this:
root@pm1:~# ntpdc -p
