Support Questions

Find answers, ask questions, and share your expertise
Check out our newest addition to the community, the Cloudera Data Analytics (CDA) group hub.

KUDU time sync error

New Contributor



I have deployed kudu service in My CDH Cluster.

Though chronyd is active in all cluster host am getting time sync issue in kudu 


This is what am getting in log


Check failed: _s.ok() Bad status: Service unavailable: Cannot initialize clock: Error reading clock. Clock considered unsynchronized


can some one suggest me solution to activate kudu



hi @Amritha ,
when you're running the command ntpq -np ,
(ntp should be already installed I guess )
what does it give as result?

greetings .

New Contributor

@Bildervic The "ntpq -np" commands gives me error

-bash: ntpq: command not found


But chronyd is active I have checked the status of it


chronyd.service - NTP client/server

   Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled)

   Active: active (running) since Fri 2019-08-02 03:03:41 EDT; 1 day 22h ago

     Docs: man:chronyd(8)


 Main PID: 1474 (chronyd)

   CGroup: /system.slice/docker-d9d5006ce9ac375bcfc928d5cd82657e0e5097b12e234849053c49aecd838217.scope/system.slice/chronyd.service

           └─1474 /usr/sbin/chronyd


I have installed chronyd while creating bin. 


as I have checked  some  Kudu  manuals, 

Chrony is not fully tested with KUDU for network time synchronization.

 "Kudu releases are only tested with NTP. Other time synchronization providers like Chrony may or may not work."

so you can either try to install NTP.

or just try this tip I've found :

"In order to use chrony for synchronization (for KUDU), chrony.conf must be configured with the rtcsync option"

good luck




Kudu requires the machine clock of master and tablet servers nodes is synchronized using NTP :


Kudu is tested with ntpd, but I guess chronyd might work as well.  Whether using ntpd or chronyd, it's necessary to make sure the machine's clock is synchronized so ntp_adjtime() Linux system call doesn't return an error (see for more technical details).


It's not enough just to have ntpd (or chronyd) running.  It's necessary to make sure the clock is synchronized.  I would verify that the NTP daemon is properly configured and tracks the clocks of the reference servers.  For the instructions to check the sync status of machine's clock, see if using ntpd or for chronyd.


Hope this helps,




Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.