OK, I think I found the problem with ntpd not getting any peers from my server list.
I was starting ntpd from the command line with the following syntax:
ntpd -I eth0 -D 4 -n
eth0 is my internal network. I got to looking at the "no interface found for..."
messages and thought I would try adding a -I eth1 where eth1 is my external
outside network connection through the Cox cable modem. So now my command
syntax is:
ntpd -u ntp -I eth0 -I eth1 -D 4
Once I added the "-I eth1" I now seem to have the three external peers listed
when I run "ntpq -p"
This still does not explain why ntpdate hangs with no replies however. The
ntpdate command sequence I used does not list anything other than the
servers like this:
ntpdate -v -d dewey.lib.ci.phoenix.az.us ntp.drydog.com
no restrictions on the interface or anything so I am still not understanding
why that does not work. Plus when I try to start the ntp service from the init
script there is no restrictions on the interface like I was using from the
command line.
Anyway I think there is still some issue with the ntpdatge command hanging
and since the ntp init script always calls ntpdate before starting ntpd I am
still not going to be able to enable the ntp service on startup.
Some progress has been made however.
--
Steve
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)