Red Hat Insights : leap second issue

Latest response

I am trying to resolve the leap second issue as documented here -> https://access.redhat.com/discussions/2795581
Although the leap second detector script gives the information that the clock will be stepped by the chrony daemon,
Red Hat Insights shows : System clock inaccurate when a leap second event happens ... for both registered systems.
Now I am wondering which information is correct - the one given from the script or that one from Red Hat Insights ?

Responses

Hi there!

I've had a look at this rule and it's based on the latest version of the 'tzdata' package on the machine. So once that's been upgraded past tzdata-2016f-1 on RHEL 6 or RHEL 7 this problem should be solved.

The reason this is still showing up in Insights is that the Insights client updates only once per day by default. This is so that it doesn't update too frequently and so has minimal impact on the server's performance and your bandwidth. You can update it manually by running the command:

redhat-access-insights

Note that this will then make sure that the cron job is installed to run the client again, as per:

https://access.redhat.com/solutions/2161911

Hope this helps,

Paul

Hi Paul,

Thanks for your feedback ! :)
I am having tzdata-j-1 installed on RHEL 7.3 and I ran /usr/bin/redhat-access-insights manually before writing the post. Please excuse me that I did not mention it.

We had a bug in the parsing of the ps command that was causing us to create false positives even though chronyd or ntpd was running. We have since fixed this and activated the rule again. Thanks for your feedback!

Thank you, Chris ! :) I ran redhat-access-insights on both systems manually and can confirm that the bug is fixed - result : 0 Actions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.