On Sat, May 28, 2016 at 09:59:11PM +0100, ael wrote:
On Sat, May 28, 2016 at 10:10:54PM +0200, Vincent Blut wrote:
Hi,

On Sat, May 28, 2016 at 08:33:48PM +0100, ael wrote:
> Package: chrony
> Version: 2.3-2
> Severity: normal
>
> Since I upgraded to the latest version today, chronyc does not seem to
> be displaying the server status correctly. Example:

Tracking shows you aren’t synchronized to any external source and that you
are using the “local” mode. Do you have any network issue? Could you show
what “journalctl -u chrony” returns?

Ok. Appended. (I had restarted a few times via /etc/init.d/chrony restart
).

Last line seems to report sync with
$ host 82.219.4.30
30.4.219.82.in-addr.arpa domain name pointer ntp1.exa-networks.co.uk.

I just ran chronyc again and got a sensible display:

chronyc> sources -v
210 Number of sources = 6

 .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
/ .- Source state '*' = current synced, '+' = combined , '-' = not combined,
| /   '?' = unreachable, 'x' = time may be in error, '~' = time too variable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^? cpc2-oxfd6-0-0-gw.4-3.cab     0  10     0     -     +0ns[   +0ns] +/-    0ns
^* ntp1.exa-networks.co.uk       2   9   377   358  +2071us[+2115us] +/-   23ms
^+ gw-01.darksky.io              2   9   377   363   -306us[ -262us] +/-   52ms
^+ sip.dicode.nl                 2   9   377   351  -3664us[-3664us] +/-   38ms
^+ roliath.nonexiste.net         3   9   377   361   +255us[ +299us] +/-   87ms
^- ns2.bvc-cloud.de              3   9   377   353   -817us[ -817us] +/-   81ms

So it seems to be working now. I don't understand what was happening
before: I had successfully pinged a source or two before reporting so it
wasn't a network issue.

According to the log you just sent, chronyd was in offline mode. That means that it didn’t try to poll the server(s). Next time, you could manually put it online by using “chronyc online” or removing the “offline” subfield if front of the pool/server directive in “chrony.conf”.

Note that I’m writing some scripts to put chronyd online/offline depending on the connection state. I’ve good hope that that will be available in the next upload.

ael

Cheers,
Vincent

Attachment: signature.asc
Description: PGP signature

Reply via email to