Re: [chrony-users] Chrony setup using RTC as fallback

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-users Archives ]


Unfortunately something is seriously wrong:
I get consistently "506 Cannot talk to daemon" to each and all chronyc commands I try (while being root).
Chronyd *is* running:
/ # ps ax | grep chro
  510 root     chronyd -r -s
  602 root     grep chro

.... but I do not see the AF_LOCAL socket:
/ # netstat -a
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address State
tcp        0      0 (null):www              (null):* LISTEN
tcp        0      0 (null):ssh              (null):* LISTEN
netstat: /proc/net/tcp6: No such file or directory
udp        0      0 (null):323              (null):*
udp        0      0 (null):ntp              (null):*
udp        0      0 (null):53703            (null):*
udp        0      0 (null):5353             (null):*
netstat: /proc/net/udp6: No such file or directory
netstat: /proc/net/raw6: No such file or directory
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags       Type       State         I-Node Path
unix  2      [ ]         DGRAM                      1166 /tmp/sockIo
unix  5      [ ]         DGRAM                       659 /dev/log
unix  2      [ ACC ]     SEQPACKET  LISTENING        670 /run/udev/control
unix  2      [ ACC ]     STREAM     LISTENING       1213 /var/run/avahi-daemon/socket
unix  2      [ ACC ]     STREAM     LISTENING       1226 /tmp/php.socket-0
unix  2      [ ACC ]     STREAM     LISTENING       1229 /tmp/php.socket-1
unix  2      [ ACC ]     STREAM     LISTENING       1234 /tmp/php.socket-2
unix  2      [ ACC ]     STREAM     LISTENING       1237 /tmp/php.socket-3
unix  3      [ ]         DGRAM                       680
unix  3      [ ]         DGRAM                       681
unix  2      [ ]         DGRAM                      1160
unix  2      [ ]         DGRAM                      1208
unix  2      [ ]         DGRAM                       662

What should I check?


Il 18/11/2015 14:03, Miroslav Lichvar ha scritto:
On Wed, Nov 18, 2015 at 01:39:40PM +0100, Mauro Condarelli wrote:
4) wait for network to go up
5) sync time THEN
5.1) IF net time > sysclock THEN sysclock = net time
5.2) IF net time < sysclock THEN slow sysclock TILL sysclock == net time
chronyd has only one step threshold for both directions, so you would
probably need to remove the makestep directive from the config and do
that step manually in the "up" script instead. E.g.
I assume You mean to add it to dhcpcd "BOUND" signal, right?
I'm not very familiar with the dhcpcd configuration. The commands
should be executed when the network is working, not sooner otherwise
the measurements would fail.

chronyc online
chronyc burst 4/4
sleep 10
chronyc tracking | grep -q 'System time.*slow' && chronyc makestep
Added, even if it's unclear to me what this burst command really does (I read the Manual!).
It tells chronyd to make four measurements with only 2 second interval
between them, so the clock is updated in few seconds instead of 3
minutes it would need with normal polling.



--
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.


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/