NTP Sync Issue
This document (000021102) is provided subject to the disclaimer at the end of this document.
Environment
Situation
Resolution
1. Add the following line to the beginning of the "/etc/ntp.conf" file
tinker panic 02. Remove the following line from the "/etc/ntp.conf" file.
driftfile /var/lib/ntp/drift/ntp.drift # path for drift file3. Restart the ntpd.service
# /bin/systemctl restart ntpd.service
Cause
"offset" and "jitter" reported high values, which is an indication of latency between the client and the NTP servers.
Below is an example of high "offset" and "jitter" values.
# /usr/sbin/ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== [ntpserver1].s xxx.xxx.xxx.xxx 3 u 775 1024 377 2.555 +3181.1 35728.0 [ntpserver2].S xxx.xxx.xxx.xxx 3 u 786 1024 377 5.272 +2875.1 35848.2
The offset column references the difference between the NTP-server's clock and the server’s clock.
The jitter column refers to the network latency reaching the NTP servers.
Additional Information
https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-ntp.html#
https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-ntp.html#sec-netz-xntp-netcon
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000021102
- Creation Date: 15-Jun-2023
- Modified Date:16-Jun-2023
-
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Server for SAP Applications
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com