54ec38e256
Incorporated patchset 8 review comments from Mary C. Conditionalized vendor-specific terms and converted code-block to parsed-literal as required Reformatted bulleted lists to definition lists Implemented abbreviation substitutions Deleted duplicate content Some minor edits for clarity Merged new abbreviation definitions in strings.txt Responding to Patch 5 comments. Change-Id: If6dd7c4cb802036445cb65853d8de7652df351c0 Signed-off-by: Stone <ronald.stone@windriver.com>
1.2 KiB
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.