Your message dated Mon, 14 Dec 2015 16:13:11 +0100
with message-id <[email protected]>
and subject line Re: chronyd doesn't see any of my sources
has caused the Debian Bug report #183745,
regarding chronyd doesn't see any of my sources
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
183745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=183745
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 1.19-4
chronyd doesn't "see" any of the sources in my /etc/chrony/chrony.conf. Here
is chrony.conf:
--
server tick.jrc.us
server ntp-1.ece.cmu.edu
server fuzz.psc.edu
commandkey 1
keyfile /etc/chrony/chrony.keys
driftfile /var/lib/chrony/drift
log tracking measurements statistics
logdir /var/log/chrony
logchange 0.1
dumpdir /var/log/chrony
dumponexit
maxupdateskew 100.0
initstepslew 30
local stratum 10
--
I know that chronyd reads this file, because if I put a syntax error in it I
get error messages in syslog. chrony starts normally:
# tail /var/log/syslog
Mar 6 21:17:28 arsenic chronyd[10024]: chronyd version V1_19 starting
Mar 6 21:17:28 arsenic chronyd[10024]: Initial txc.tick=10000 txc.freq=0
(0.00000000) txc.offset=0 => hz=100 shift_hz=7
Mar 6 21:17:28 arsenic chronyd[10024]: Linux kernel major=2 minor=4 patch=18
Mar 6 21:17:28 arsenic chronyd[10024]: calculated_freq_scale=0.99902439
freq_scale=0.99902439
But it doesn't see any of the servers in chrony.conf:
# echo sources | chronyc
210 Number of sources = 0
MS Name/IP address Stratum Poll LastRx Last sample
============================================================================
#
I don't think this is a firewall problem, because
- I allow outbound packets to pass to 123/udp
- I allow all traffic to pass on the loopback interface
- the "sources" output above doesn't show servers that can't be reached; it
shows no servers at all.
Replacing the server names by IP addresses, or using different servers,
doesn't help.
I originally had this problem in stable, v. 1.14-7. Upgraded to unstable but
the problem is the same.
Any help would be appreciated.
Andrew.
--- End Message ---
--- Begin Message ---
Version: 1.20-1
Closing as it has been fixed some years ago. Thanks for the report!
Cheers,
Vincent
--- End Message ---
