starlingx/docs
Code Issues Proposed changes
docs/doc/source/system_configuration/kubernetes/resynchronizing-a-host-to-the-ntp-server.rst
Stone ecae991cca System Configuration reorg 
Organized SysConf Kubernetes and OpenStack content into subdirs and modified
index along lines of Planning layout.

Signed-off-by: Stone <ronald.stone@windriver.com>
Change-Id: Ia17c015b2083a39fcae4ac545fa10cb5445b4cb2
2021-01-29 09:41:28 -05:00

1.2 KiB
Raw Blame History

Resynchronize a Host to the NTP Server

If host synchronization is lost for any reason, you must lock and then unlock the host to restore the synchronization safely.

If a large time discrepancy (greater than 1000 seconds, or about 17 minutes) develops between the clock time on a host and the time as reported by an server, the ntpd service on the host stops, and Alarm 200.006 (<hostname> 'ntpd' process has failed) is logged in the Alarm Log and the Customer Log. This can occur if the clock on the host is inadvertently set incorrectly, or cannot access the server for the correct time at initialization and defaults to an incorrect time.

  • To recover, lock and then unlock the host.

    Caution

    Do not attempt to recover by restarting the ntpd service. This can cause problems for other running services.

The time is automatically synchronized to the server when the host is unlocked and alarm 200.006 for this host will be cleared.