Another option would be adding a boot time script which uses ntpdate (or
something) to force an immediate sync with your timeservers before ntpd
starts - this is actually suggested in ntpdate's man page!

Rich

On 15/05/2019 13:00, Marco Stuurman wrote:
> Hi Yenya,
> 
> You could try to synchronize the system clock to the hardware clock
> before rebooting. Also try chrony, it catches up very fast.
> 
> 
> Kind regards,
> 
> Marco Stuurman
> 
> 
> Op wo 15 mei 2019 om 13:48 schreef Jan Kasprzak <k...@fi.muni.cz
> <mailto:k...@fi.muni.cz>>
> 
>             Hello, Ceph users,
> 
>     how do you deal with the "clock skew detected" HEALTH_WARN message?
> 
>     I think the internal RTC in most x86 servers does have 1 second resolution
>     only, but Ceph skew limit is much smaller than that. So every time I 
> reboot
>     one of my mons (for kernel upgrade or something), I have to wait for 
> several
>     minutes for the system clock to synchronize over NTP, even though ntpd
>     has been running before reboot and was started during the system
>     boot again.
> 
>     Thanks,
> 
>     -Yenya

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to