[PVE-User] HEALTH_WARN clock skew detected on mon.1
lists
lists at merit.unu.edu
Mon Mar 13 16:13:45 CET 2017
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 at pm1:~# ntpdc -p
> remote local st poll reach delay offset disp
> =======================================================================
> *dns.internal.server 192.x.y.5 3 1024 375 0.00015 0.010197 0.12566
> root at pm1:~#
and
> root at pm2:~# ntpdc -p
> remote local st poll reach delay offset disp
> =======================================================================
> *dns.internal.server 192.x.y.6 3 1024 377 0.00014 0.004051 0.00836
> root at pm2:~#
and
> root at pm3:~# ntpdc -p
> remote local st poll reach delay offset disp
> =======================================================================
> *dns.internal.server 192.x.y.7 3 1024 377 0.00009 -0.000008 0.01028
> root at pm3:~#
It it seems to me that everything IS in sync??
Why would this happen? Sometimes it auto-disappears after 15 minutes,
but the longest has been three hours.
Tips, trics? All my reading/google voodo suggests me to install NTP, but
we are already.
Best regards,
MJ
More information about the pve-user
mailing list