Bug #9086
closed
Generic setup time not OK on Centos7
Description
Hi,
it would appear that it uses chrony somehow. I'm not totally sure how this happens.
I've checked a few systems by now and they seem to "mostly" have chrony instead of standard NTP.
Updated by Florian Heigl about 8 years ago
I verified with other people:
Yes, C7 has chrony by default, so the generic time setup technique needs fixing for what I assume all EL7 derivates.
Full example message from my logstash thinggie:
message:<179>Sep 23 17:19:14 dhcp205 rudder[31503]: CFEngine(agent) rudder Method 'check_clock_configuration' failed in some repairs syslog_message:CFEngine(agent) rudder Method 'check_clock_configuration' failed in some repairs @version:1 @timestamp:September 23rd 2016, 17:19:14.000 type:syslog host:192.168.122.198 syslog_timestamp:Sep 23 17:19:14 syslog_hostname:dhcp205 syslog_program:rudder syslog_pid:31503 received_at:September 23rd 2016, 17:19:14.652 received_from:192.168.122.198 syslog_severity_code:5 syslog_facility_code:1 syslog_facility:user-level syslog_severity:notice _id:AVdXoQwgqSGfs2I2j61n _type:syslog _index:logstash-2016.09.23 _score:
Updated by Alexis Mousset about 8 years ago
- Related to Bug #6772: clockConfiguration is not compatible with systemd-based systems added
Updated by Alexis Mousset over 7 years ago
- Related to deleted (Bug #6772: clockConfiguration is not compatible with systemd-based systems)
Updated by Alexis Mousset over 7 years ago
- Is duplicate of Bug #6772: clockConfiguration is not compatible with systemd-based systems added