Enable RTC sync in chronyd.

[agcooke]

Issue #, if available:
The chronyd service was running but not syncing the RTC clock.

This alarm was still firing:

ALERT ClockSyncBroken
  IF          node_timex_sync_status != 1
  FOR         5m
  LABELS      { severity="warning" }
  ANNOTATIONS {
    summary = "The clock is not being synced.",
    impact = "Random things are about to break for our users",
    detail = "Node: {{$labels.node}}",
  }

as described in #130

Description of changes:
After comparing the configuration between an Ubuntu AMI and the AL2 AMI I saw that the chrony.conf differerd.

AL2 was configured to not sync the RTC clock.

After making the changes it does sync and the alarm disappeared:

[ec2-user@ip-10-0-19-151 ~]$ sudo systemctl start chronyd
[ec2-user@ip-10-0-19-151 ~]$ ./adjtimex 
    mode:         0
-o  offset:       0 us
-f  freq.adjust:  2155554 (65536 = 1ppm)
    maxerror:     1098
    esterror:     564
    status:       0 ()
-p  timeconstant: 7
    precision:    1 us
    tolerance:    32768000
-t  tick:         9994 us
    time.tv_sec:  1547032282
    time.tv_usec: 176261
    return value: 0 (clock synchronized)

Links:

• Chrony Configuration
• Prometheus Node Exporter timex metric

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[micahhausler]

Thanks! One small nit

[mattlandis]

Thanks for the changes.

[errordeveloper]

Thanks for digging into this, we've noticed the problem a while ago, but it wasn't clear to me whether it's how node exporter implements the probe is inappropriate for all NTP daemons.

[agcooke]

No problem. We have had lot's of head aches with our nodes. We got our Nodes stable now. But I am not an expert on getting Nodes healthy, thus some of the hand wavy pull requests I opened here, I just wanted them to work.

Now you guys can take a look into fluxcd/flux#1639 ;)

We love Flux by the way!

[errordeveloper]

Thanks, I will pass it on!

…

On Fri, 11 Jan 2019, 10:18 am Adrian Cooke, ***@***.***> wrote: No problem. We have had lot's of head aches with our nodes. We got our Nodes stable now. But I am not an expert on getting Nodes healthy, thus some of the hand wavy pull requests I opened here, I just wanted them to work. Now you guys can take a look into fluxcd/flux#1639 <fluxcd/flux#1639> ;) We love Flux by the way! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#142 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAPWSxCRUNl9m-S7yC4ChfaqYjOClqbSks5vCGULgaJpZM4Z3wGl> .