[chrony ntp] time sync not possible any more

[fmessmer]

From @ipa-fmw on February 27, 2018 11:13

happens primarily in Ingolstadt only. error message is error nunning ntpdate.

Manual solution is:

robot@cob4-2-b1:~$ timedatectl 
      Local time: Di 2018-02-27 12:10:01 CET
  Universal time: Di 2018-02-27 11:10:01 UTC
        Timezone: Europe/Berlin (CET, +0100)
     NTP enabled: yes
NTP synchronized: no
 RTC in local TZ: no
      DST active: no
 Last DST change: DST ended at
                  So 2017-10-29 02:59:59 CEST
                  So 2017-10-29 02:00:00 CET
 Next DST change: DST begins (the clock jumps one hour forward) at
                  So 2018-03-25 01:59:59 CET
                  So 2018-03-25 03:00:00 CEST

robot@cob4-2-b1:~$ sudo service chrony restart
Restarting time daemon: Starting /usr/sbin/chronyd...
chronyd is running and offline.

robot@cob4-2-b1:~$ timedatectl 
      Local time: Di 2018-02-27 12:10:23 CET
  Universal time: Di 2018-02-27 11:10:23 UTC
        Timezone: Europe/Berlin (CET, +0100)
     NTP enabled: yes
NTP synchronized: no
 RTC in local TZ: no
      DST active: no
 Last DST change: DST ended at
                  So 2017-10-29 02:59:59 CEST
                  So 2017-10-29 02:00:00 CET
 Next DST change: DST begins (the clock jumps one hour forward) at
                  So 2018-03-25 01:59:59 CET
                  So 2018-03-25 03:00:00 CEST

chrony.conf is the same as for other robots.

@ipa-bnm any idea how to investigate that?

Copied from original issue: ipa320/msh#1020

[fmessmer]

From @ipa-fmw on February 28, 2018 14:2

https://github.com/ipa320/setup_cob4/pull/201 allows all users to restart the chrony service, thus INCATEC can solve the ntpdate error. Is already updated on all robots.

still we need to investigate why the error occurs at all

[floweisshardt]

did not happen again recently. we'll reopen if it's relevant again