Re: Clock skew

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks guys

I was trying these things.
NTP looks well synced.. but drifts away after some hours.
I will soon check if this could be because the BIOS battery of the APU
boxes are empty.

Dominique

--
Your Swiss, Open Source and IPv6 Virtual Machine. Now on
www.datacenterlight.ch

On 8/15/18 10:13 PM, Sean Crosby wrote:
> Hi Dominique,
> 
> The clock skew warning shows up when your NTP daemon is not synced.
> 
> You can see the sync in the output of ntpq -p
> 
> This is a synced NTP
> 
>     # ntpq -p
>          remote           refid      st t when poll reach   delay 
>      offset  jitter
>     ==============================================================================
>      ntp.unimelb.edu <http://ntp.unimelb.edu> 210.9.192.50     2 u   24 
>      64   17    0.496   -6.421   0.181
>     *ntp2.unimelb.ed 202.6.131.118    2 u   26   64   17    0.613 
>     -11.998   0.250
>      ntp41.frosteri. .INIT.          16 u    -   64    0    0.000   
>     0.000   0.000
>      dns01.ntl02.pri .INIT.          16 u    -   64    0    0.000   
>     0.000   0.000
>      cosima.470n.act .INIT.          16 u    -   64    0    0.000   
>     0.000   0.000
>      x.ns.gin.ntt.ne <http://x.ns.gin.ntt.ne> .INIT.          16 u    - 
>      64    0    0.000    0.000   0.000
> 
> The *'s show that there is a sync with a NTP server. When you start or
> restart ntp, it takes a while for a sync to occur
> 
> Here's immediately after restarting the ntp daemon
> 
>     # ntpq -p
>          remote           refid      st t when poll reach   delay 
>      offset  jitter
>     ==============================================================================
>      ntp.unimelb.edu <http://ntp.unimelb.edu> 210.9.192.50     2 u    - 
>      64    1    0.496   -6.421   0.000
>      ntp2.unimelb.ed 202.6.131.118    2 u    -   64    1    0.474 
>     -11.678   0.000
>      ntp41.frosteri. .INIT.          16 u    -   64    0    0.000   
>     0.000   0.000
>      dns01.ntl02.pri .INIT.          16 u    -   64    0    0.000   
>     0.000   0.000
>      cosima.470n.act .INIT.          16 u    -   64    0    0.000   
>     0.000   0.000
>      x.ns.gin.ntt.ne <http://x.ns.gin.ntt.ne> .INIT.          16 u    - 
>      64    0    0.000    0.000   0.000
> 
> Make sure that nothing is regularly restarting ntpd. For us, we had
> puppet and dhcp regularly fight over the contents of ntp.conf, and it
> caused a restart of ntpd.
> 
> Sean
> 
> 
> On Wed, 15 Aug 2018 at 19:37, Dominque Roux <dominique.roux@xxxxxxxxxxx
> <mailto:dominique.roux@xxxxxxxxxxx>> wrote:
> 
>     Hi all,
> 
>     We recently facing clock skews from time to time.
>     This means that sometimes everything is fine but hours later the warning
>     appears again.
> 
>     NTPD is running and configured with the same pool.
> 
>     Did someone else already had the same issue and could probably help us
>     to fix this?
> 
>     Thanks a lot!
> 
>     Dominique
>     -- 
> 
>     Your Swiss, Open Source and IPv6 Virtual Machine. Now on
>     www.datacenterlight.ch <http://www.datacenterlight.ch>
> 
>     _______________________________________________
>     ceph-users mailing list
>     ceph-users@xxxxxxxxxxxxxx <mailto:ceph-users@xxxxxxxxxxxxxx>
>     http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> 
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux