Comment 3 for bug 1470028

Revision history for this message
dino99 (9d9) wrote : Re: NSEC3: verify failed due to bad signature (keyid=33878): RRSIG validity period has not begun

As the NTP synchronization is no more done as ntpdate has been purged, i've installed ntp to compare with the previous ntpdate (which has no apparent installed active 'dependant').
After rebooting, i've also made that change to get around the RTC problem:

 timedatectl
      Local time: mar. 2015-06-30 11:00:57 CEST
  Universal time: mar. 2015-06-30 09:00:57 UTC
        RTC time: mar. 2015-06-30 11:00:57
       Time zone: Europe/Paris (CEST, +0200)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: yes

Warning: The system is configured to read the RTC time in the local time zone. This
         mode can not be fully supported. It will create various problems with time
         zone changes and daylight saving time adjustments. The RTC time is never updated,
         it relies on external facilities to maintain it. If at all possible, use
         RTC in UTC by calling 'timedatectl set-local-rtc 0'.
[11:00 - 0]
[u32 3] ~ > timedatectl set-local-rtc 0
[11:02 - 0]
[u32 4] ~ > timedatectl
      Local time: mar. 2015-06-30 11:03:00 CEST
  Universal time: mar. 2015-06-30 09:03:00 UTC
        RTC time: mar. 2015-06-30 09:03:00
       Time zone: Europe/Paris (CEST, +0200)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

***** i suppose that systemd-timesync should handle these issues *******