FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After starting ntpd with "service start ntpd" I can check to see that it's running with "ps -ef | grep ntpd" and see that it's running. After some random amount of time, I will see that it's no longer running. Is there some reason ntpd would just die? I'm using FC 10.
You can check the ntp logs for errors. If the time difference between your computer and the ntp server(s) is greater then 1000 seconds it assumes something is wrong and will exit.
Look at the output of the command ntpq -p. This will show you the statistics including the offset in milliseconds. If it is a large number then something is wrong.
The logs did show something about being 1200 seconds off. I wouldn't expect ntpd to exit though. I also don't understand how ntpd could connect to the ntp server, adjust the time of the local clock to be in sync, stay that way for hours, and then suddenly be off by 1200 seconds.... on a LAN!
I'm using all real machines. I realize FC10 is no longer supported, but it's not like it's from 1990. It came out in 2008, which wasn't that long ago. I'd be surprised if ntpd changed much since 2000, let alone 2008.
ntp (or ntpdate depending on version) should sync with the server at start up but if the clock has a high drift rate the offset will become greater then 1000 seconds and so will quit. ntp will automatically adjust the poll interval.
The default min is 64 seconds and max is 1024 seconds but can be manually adjusted from 4 seconds to 36.4 hours). Basically the more stable the clock the longer the poll interval.
st t when poll reach delay offset jitter
===============================================
6 u 10 128 377 0.403 -0.237 0.146
Keep in mind, I started ntpd again when I created this thread because it wasn't running.
Quote:
Was ntp working previously?
That depends on what you mean by working. It's always been able to connect to the ntp server and sync the times. But it also has always died after a little while.
How is the ntp server configured? i.e post its ntp.conf. With a stratum level of 6 the client might not think the server's time is good enough and since the client is not configured to fall back to its local time as a source it quits.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.