Re: [chrony-users] What's changed in chrony-2.2?

[Miroslav Lichvar <mlichvar@xxxxxxxxxx>]

On Mon, Nov 23, 2015 at 10:13:32AM +0000, Peter Humphrey wrote:
> Nov 23 09:46:02 serv chronyd[20169]: chronyd version 2.2 starting (+CMDMON 
> +NTP +REFCLOCK +RTC -PRIVDROP -SCFILTER -SECHASH +ASYNCDNS +IPV6 -
> DEBUG)
> Nov 23 09:46:02 serv chronyd[20169]: Frequency -28.615 +/- 0.000 ppm read 
> from /var/lib/chrony/drift
> Nov 23 09:46:02 serv /etc/init.d/chronyd[20166]: start-stop-daemon: caught 
> an interrupt
> Nov 23 09:46:02 serv /etc/init.d/chronyd[20166]: start-stop-daemon: 
> /usr/sbin/chronyd died
> Nov 23 09:46:02 serv /etc/init.d/chronyd[20149]: ERROR: chronyd failed to 
> start
> Nov 23 09:46:07 serv chronyd[20169]: Selected source 212.23.8.6
> Nov 23 09:48:18 serv chronyd[20169]: Selected source 176.126.242.239

Hm, so chronyd is running, but the init script says the process was
killed? That's odd.

Is the init system OpenRC? I'm not familiar with it. Maybe running the
init script command in strace -ff could show us something.

> pool uk.pool.ntp.org iburst
> server ntp0.zen.co.uk iburst
> server ntp1.zen.co.uk iburst
> driftfile /var/lib/chrony/drift
> makestep 1.0 3
> allow 192.168/16
> rtcsync
> port 0

This looks ok. BTW, port 0 disables NTP server, but some IP range is
allowed, was it supposed to run as an NTP server?

> Do you mean RTC_CMOS is a module? It's the same on both machines, and a 
> socket is indeed created:

I meant CONFIG_UNIX=m. But if you see the socket created, it's
probably not related to the problem.

-- 
Miroslav Lichvar

-- 
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.