I have a machine where Kudu failed to start: F1116 05:02:00.173629 71098 tablet_server_main.cc:64] Check failed: _s.ok() Bad status: Service unavailable: Cannot initialize clock: Error reading clock. Clock considered unsynchronized
https://kudu.apache.org/docs/troubleshooting.html says: "For the master and tablet server daemons, the server’s clock must be synchronized using NTP. In addition, the maximum clock error (not to be mistaken with the estimated error) be below a configurable threshold. The default value is 10 seconds, but it can be set with the flag --max_clock_sync_error_usec." and "If NTP is installed the user can monitor the synchronization status by running ntptime. The relevant value is what is reported for maximum error." ntptime reports: ntp_gettime() returns code 0 (OK) time dbd66a6a.59bca948 Wed, Nov 16 2016 5:17:30.350, (.350535824), maximum error 197431 us, estimated error 71015 us, TAI offset 0 ntp_adjtime() returns code 0 (OK) modes 0x0 (), offset 74989.459 us, frequency 19.950 ppm, interval 1 s, maximum error 197431 us, estimated error 71015 us, status 0x2001 (PLL,NANO), time constant 6, precision 0.001 us, tolerance 500 ppm, So it looks like this error is anticipated, but the expected conditions for it to occur are absent. Any ideas what could be going on here? This is with a recent checkout of Impala master.
