Add more time sources; NTP needs sources to maintain good accuracy. A simple way to do this is to include repeated references to []. Another option you can try is chrony. In our testing it performs more stably than ntpd and handles time skew experienced in virtual environments better.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 6 years, 2 months ago. Active 6 years, 1 month ago. Viewed 4k times. Improve this question. Which os and version? Is there a hids running? How many ntp-servers are configured?
What ntpd options are aktive? You could try remove your ntp. Add a comment. Active Oldest Votes. I would say there is no 1-minute method to find the exact reason.
I've started ntpd on my RHEL3. Hi there -- I ran the service ntpd restart command, and it generated the same error message that was mentioned in a previous e-mail. I also ran the ps -ef grep ntp command, and the output was the following: nptd -U ntp Regarding the service patches for Red Hat 8. It looks like your system time is too far off from network time so ntpd cannot synchronise your system time with network time.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
End of content United States. Hewlett Packard Enterprise International. It may be very helpful to someone who doesn't understand network time protocols very well if there was a suggestion to explain potential conflicts between ntpd and chronyd in the documentation, or even to take a second to check which if any you already have installed. Maybe it won't be an issue for most people, but for me, assuming that I didn't have chrony already running cost me a bunch of time getting my cluster healthy.
I would check, find ntpd dead, see no problems reported on Host Monitor, wonder why the hell ntpd died, kill ntpd, run ntpdate, restart ntpdate, restart scm-agent, and that would "fix" it, but on reboot it would go back to using chrony and exit ntpd, and host monitor would report failure to query ntp service, even though the machine was using chrony and synced just fine all along. I appreciate your help!
Support Questions. Find answers, ask questions, and share your expertise. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for. Search instead for. Did you mean:. Why does it ke Solved Go to solution. It's time we have a talk about NTP. Why does it keep dying even though I followed the documentation exactly? Labels: Labels: Cloudera Manager. Reply Views.
0コメント