NTP synchronized: no

Tue Sep 8 09:52:02 UTC 2015

On 09/08/15 17:29, Patrick Dupre wrote:
> I cannot synchronize the date:
> My undestanding is that it should be set by:
> timedatectl set-ntp yes
>
> Here, the results of some commands:
>
> netstat -a |grep ntp
> udp        0      0 localhost.localdo:51314 ns346276.ip-94-23-3:ntp ESTABLISHED
> udp        0      0 localhost.localdo:39994 tomia.ordimatic.net:ntp ESTABLISHED
> udp        0      0 localhost.localdo:45035 ntp.tuxfamily.net:ntp   ESTABLISHED
> udp        0      0 localhost.localdo:49209 host3.nuagelibre.or:ntp ESTABLISHED
> warning, got bogus l2cap line.
>
> chronyc sources
> 210 Number of sources = 4
> MS Name/IP address         Stratum Poll Reach LastRx Last sample
> ===============================================================================
> ^? host3.nuagelibre.org          0   8     0   10y     +0ns[   +0ns] +/-    0ns
> ^? tomia.ordimatic.net           0   8     0   10y     +0ns[   +0ns] +/-    0ns
> ^? ntp.tuxfamily.net             0   8     0   10y     +0ns[   +0ns] +/-    0ns
> ^? ns346276.ip-94-23-32.eu       0   8     0   10y     +0ns[   +0ns] +/-    0ns

In the output above....

'M'
     This indicates the mode of the source.  '^' means a server, '='
     means a peer and '#' indicates a locally connected reference clock.

'S'
     This column indicates the state of the sources.  '*' indicates the
     source to which 'chronyd' is currently synchronised.  '+' indicates
     acceptable sources which are combined with the selected source.
     '-' indicates acceptable sources which are excluded by the
     combining algorithm.  '?' indicates sources to which connectivity
     has been lost or whose packets don't pass all tests.  'x' indicates
     a clock which 'chronyd' thinks is is a falseticker (i.e.  its time
     is inconsistent with a majority of other sources).  '~' indicates a
     source whose time appears to have too much variability.  The '?'
     condition is also shown at start-up, until at least 3 samples have
     been gathered from it.

>
>  chronyc sourcestats
> 210 Number of sources = 4
> Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
> ==============================================================================
> bunny.zeroloop.net          0   0     0     +0.000   2000.000     +0ns  4000ms
> ns0.hezzel.org              0   0     0     +0.000   2000.000     +0ns  4000ms
> server4.websters-computer   0   0     0     +0.000   2000.000     +0ns  4000ms
> net1.web.yas-online.net     0   0     0     +0.000   2000.000     +0ns  4000ms

Should look more like this....
Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
==============================================================================
sun.stu.edu.tw              5   4   69m     -0.612      4.655   -136us  1240us
venus.stu.edu.tw            6   4   86m     +0.888      0.853   -492us   334us
123-204-45-116.static.see  11   7  172m     -0.256      0.254  +1239us   475us
atelieralica.idv.tw         7   5  103m     +2.341      1.821  +9709us  1310us

So, it seems your system is having problems to communicate with the remote servers.

Is this system at home or a workplace?  Could be a firewall issue if it is in a workplace.

>
>
>
>  timedatectl 
>       Local time: Tue 2015-09-08 09:12:19 CEST
>   Universal time: Tue 2015-09-08 07:12:19 UTC
>         RTC time: Tue 2015-09-08 07:12:19
>        Time zone: Europe/Paris (CEST, +0200)
>      NTP enabled: yes
> NTP synchronized: no
>  RTC in local TZ: no
>       DST active: yes
>  Last DST change: DST began at
>                   Sun 2015-03-29 01:59:59 CET
>                   Sun 2015-03-29 03:00:00 CEST
>  Next DST change: DST ends (the clock jumps one hour backwards) at
>                   Sun 2015-10-25 02:59:59 CEST
>                   Sun 2015-10-25 02:00:00 CET
>
>
>  systemctl status chronyd
> ● chronyd.service - NTP client/server
>    Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled)
>    Active: active (running) since Tue 2015-09-08 09:00:52 CEST; 16min ago
>   Process: 4848 ExecStartPost=/usr/libexec/chrony-helper update-daemon (code=exited, status=0/SUCCESS)
>   Process: 4844 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, status=0/SUCCESS)
>  Main PID: 4846 (chronyd)
>    CGroup: /system.slice/chronyd.service
>            └─4846 /usr/sbin/chronyd
>
> Sep 08 09:00:52 localhost.localdomain systemd[1]: Starting NTP client/server...
> Sep 08 09:00:52 localhost.localdomain chronyd[4846]: chronyd version 2.1.1 st...
> Sep 08 09:00:52 localhost.localdomain chronyd[4846]: Frequency 0.000 +/- 1000...
> Sep 08 09:00:52 localhost.localdomain systemd[1]: Started NTP client/server.
> Sep 08 09:03:16 localhost.localdomain chronyd[4846]: Source 62.210.85.244 rep...
> Hint: Some lines were ellipsized, use -l to show in full.

Output with "-l" please....

>
>
> chronyc tracking
> Reference ID    : 0.0.0.0 ()
> Stratum         : 0
> Ref time (UTC)  : Thu Jan  1 00:00:00 1970
> System time     : 0.000000000 seconds fast of NTP time
> Last offset     : +0.000000000 seconds
> RMS offset      : 0.000000000 seconds
> Frequency       : 0.000 ppm fast
> Residual freq   : +0.000 ppm
> Skew            : 0.000 ppm
> Root delay      : 0.000000 seconds
> Root dispersion : 0.000000 seconds
> Update interval : 0.0 seconds
> Leap status     : Not synchronised
>
>
>
>  timedatectl set-time "2015-09-08 11:22:00"
> Failed to set time: NTP unit is active

This is normal since you can't set the date/time if you're relying on NTP to do it.

-- 
It seems most people that say they are "done talking about it" never really are until given the last word.