Red Hat Bugzilla – Bug 74734
NTP server not verified?
Last modified: 2007-04-18 12:46:56 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20020812 Description of problem: I am not 100% sure that this really happens but I cannot explain what I see any other way. When selecting to use NTP in anaconda I selected one server down the list. Anaconda accepted it and wrote an appropriate ntp.conf file. But when the system was running the time went off. From what I could see the server wasn't responding at all. In fact, the server never responded any time in the following hours. It seems that anaconda does not verify the server is usable by looking at the ntpd status. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.During installation select one of the obscure NTP servers which don't work 2. 3. Actual Results: ntp doesn't work due to missing connection. Expected Results: anaconda should detect that the server isn't working correctly and request another ntp server to be selected. Additional info:
Anaconda does not support ntp configuration. Reassigning to firstboot.
I can reproduce this bug.
New default ntp.conf has a line "restrict default ignore". So, we need a "restrict" statement along with a "server" statement. like this. server my.ntp.example.com restrict 192.168.1.1 mask 255.255.255.255 nomodify notrap noquery But, firstboot dose not aware that.
aab36830, your post is referring to a different issue than was originally reported.
redhat-config-date actually does attempt to make sure that the ntp server can be contacted. My guess is that the server was available when you ran redhat-config-date and then later became unavailable. Also, I have previously tested all the servers to make sure that they work. Perhaps some have quit working since then. I'm going to close as 'worksforme'.