Troubleshooting "ERROR: Clock drift" Errors Reported on a BDA Server During Node Reprovision and Generally
(Doc ID 2143786.1)
Last updated on JANUARY 28, 2020
Applies to:Big Data Appliance Integrated Software - Version 3.0 and later
This note provides troubleshooting tips on resolving cluster checks errors regarding clock drift on a BDA server. Output reported may look like:
INFO: Checking for clock drift on all nodes
ERROR: Clock drift on node bdanode01 is too much (30 seconds)
ERROR: Local time: 1463420307 Node bdanode01 time: 1463420277
This can happen during a bdacheckcluster, node reprovision, or during other Mammoth actions during a health check.
Verifying with 'dcli -C date' shows one node is more that 30 seconds off from the rest of the nodes in the cluster.
The example in this note is from a Node 1 Step 1 reprovision failure. In this case Node 1, being added back into the cluster, is more than 30 seconds off from the rest of the cluster. This causes the Node 1 reprovision to fail during the prerequisite checks.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document