Bug 78025
| Summary: | Default ntp.conf does not work | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <jaco_botha> |
| Component: | redhat-config-date | Assignee: | Brent Fox <bfox> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | CC: | k.georgiou, ksnider, mike |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-05-22 02:36:49 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Need Real Name
2002-11-17 22:22:03 UTC
I have a laptop, which since installing RH8, has a significantly slow clock (another bug perhaps?). I was trying to use ntp to keep the time proper, at least while plugged into a network, but no matter what, ntpd did not synchronize at all. The ntpdate command would work, but it would drift from there such that after a day of uptime, the clock would be half an hour behind, even with ntp running. After following the hint above (using "restrict default nomodify notrap noquery") ntpd keeps the clock synchronized. Therefore, I confirm both jaco_botha's problem, and his fix. I can verify this fact. This is also true of RedHat 7.3 I only allow connections to and from my time servers.. from ntpd.conf, modified for my needs... .... # --- OUR TIMESERVERS ----- # or remove the default restrict line # Permit time synchronization with our time source, but do not # permit the source to query or modify the service on this system. restrict 172.16.2.2 mask 255.255.255.255 nomodify notrap noquery server 172.16.2.2 ... WHAT???? First of all, harald, I don't understand a word you are saying. What does modifying your ntpd.conf file for your needs have to do with the fact that the Red Hat supplied file and configuration tool does not work? Secondly, how can you just close this report saying it is not a bug? Again, the Red Hat supplied configuration file does not work, and using the Red Hat supplied configuration tool does not make it work either. Two other people confirmed my report within a day. What about the hundreds of other people who have similar problems but have not said anything because they haven't found a bug in bugzilla on this topic yet? I am shocked!!!! oops, did overread, that you used redhat-config-date... otherwise, I would say: "User configuration error" assigning to right component... sorry.. btw, you have to _edit_ ntpd.conf to fit it to your needs! I am not responsible, if someone can control your ntpd due to misconfiguration. You can test security by using ntpdc. $ /usr/sbin/ntpdc myhost then you may be able to add other peers or remove them.. Apology accepted. I could've been more explicit about the redhat-config-date. Edit ntpd.conf? This bug is about ntp.conf isn't it? I must admit that I am unable to tell what this report is truly about. The default ntp.conf file seems to work for me and many other users once you use redhat-config-date to select an NTP server. This bug is about ntp not working when choosing any of the timeservers from the
list in redhat-config-date or typing in the name of another timeserver. The
only way I have found to make it work is to change the line
restrict default ignore
to
restrict default nomodify notrap noquery.
This is 100% repeatable for me and I suppose for the two other people who
posted their comments as well.
I also tried with redhat-config-date-1.5.5-1 from Rawhide. Same result.
I would like to add my experience: ntpd synchronization with time servers does _not_ work in Redhat 7.3 and 8.0 with default configuration and time servers chosen with redhat-config-date. I'll try with the options "nomodify notrap noquery" and test if the behaviour changes. Ntpd worked fine in redhat 7.1. Thanks, Alex I didn't use redhat-config-date to set my time servers. I used 3 others from the public time server list web site, and mine wouldn't sync up either. I added a restrict line for each server I wanted to use and then it was able to sync up, and allow my internal machine(s) to sync up to it as well. example.. restrict 1.2.3.4 restrict 1.2.3.5 restrict 1.2.3.6 Then below that is.. server 1.2.3.4 server 1.2.3.5 server 1.2.3.6 I've made redhat-config-date-1.5.7-3 (in Rawhide) write the IP of the NTP server to the 'restrict' line and the domain name to the 'server' line. Please try with this version and reopen if this doesn't fix the problem. I'm currently using redhat-config-date-1.5.7-1 from Rawhide 1/3/2003 and that works fine, thanks! I believe -3 is essentially the same? Yeah, I think -3 fixed some other unrelated problems. |