| Re: [chrony-users] Chrony Server Not Listening |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
*****
$ cat /usr/lib/systemd/system/chrony.service
[Unit]
Description=Chrony Network Time Daemon
After=network.target
Conflicts=systemd-timesyncd.service
[Service]
Type=forking
ExecStart=/usr/bin/chronyd -u chrony
PIDFile=/var/run/chronyd.pid
*****
Shell1:
*****
$ sudo /usr/bin/chronyd -u chrony -d -f /etc/chrony.conf
2016-03-04T13:46:42Z chronyd version 2.3 starting (+CMDMON +NTP
+REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH +ASYNCDNS +IPV6 -DEBUG)
2016-03-04T13:46:42Z Frequency 0.000 +/- 1000000.000 ppm read from
/var/lib/chrony/drift
*****
Shell2:
$ sudo chronyc -h 127.0.0.1 tracking
Reference ID : 127.127.1.1 ()
Stratum : 10
Ref time (UTC) : Fri Mar 4 13:46:49 2016
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.000001 seconds
Update interval : 0.0 seconds
Leap status : Not synchronised
On Fri, Mar 4, 2016 at 7:07 AM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> That's odd. If the socket() or bind() system call failed, chronyd
> would loudly complain, so I assume the sockets are somewhere, but they
> are not visible. Any chance chronyd has a separate network namespace
> (e.g. PrivateNetwork=True set in the chronyd unit file)?
>
> If you start chronyd manually in the shell and try "chronyc -h
> 127.0.0.1 tracking", does it print anything?
>
> --
> 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.
--
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.