"chrony-wait.service" fails on OpenShift Nodes

Solution Verified - Updated -

Issue

  • On OpenShift Container Platform, when logging into the Node, the "chrony-wait.service" is failing:

    $ sudo systemctl status chrony-wait.service 
    × chrony-wait.service - Wait for chrony to synchronize system clock
     Loaded: loaded (/usr/lib/systemd/system/chrony-wait.service; disabled; preset: disabled)
     Active: failed (Result: timeout) since Wed 2025-07-09 12:27:39 UTC; 42min ago
       Docs: man:chronyc(1)
    Main PID: 1434 (code=exited, status=1/FAILURE)
        CPU: 113ms
    
    Jul 09 12:24:39 xxx-01-worker-az1-dp6ck systemd[1]: Starting Wait for chrony to synchronize system clock...
    Jul 09 12:27:39 xxx-01-worker-az1-dp6ck systemd[1]: chrony-wait.service: start operation timed out. Terminating.
    Jul 09 12:27:39 xxx-01-worker-az1-dp6ck systemd[1]: chrony-wait.service: Main process exited, code=exited, status=1/FAILURE
    Jul 09 12:27:39 xxx-01-worker-az1-dp6ck systemd[1]: chrony-wait.service: Failed with result 'timeout'.
    Jul 09 12:27:39 xxx-01-worker-az1-dp6ck systemd[1]: Failed to start Wait for chrony to synchronize system clock.
    
  • When executing the command from the systemd unit manually we can see the following output:

    # /usr/bin/chronyc -h 127.0.0.1,::1 waitsync 0 0.1 0.0 1
    506 Cannot talk to daemon
    506 Cannot talk to daemon
    

Environment

  • Red Hat OpenShift Container Platform (OCP) 4
  • Red Hat OpenShift Compliance Operator

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content