ntp not starting up correctly...

Hello all, i am having a hard time getting ntp up and running. Right
now i am trying to just set up the server machine (which will get its
time from teh internet and then server that time to nodes in my
cluster) the /etc/ntp.conf file looks like:

restrict 127.0.0.1
restrict 128.180.38.0 mask 255.255.255.0 nomodify notrap
server -4 clock.redhat.com
server -4 us.pool.ntp.org
server -4 louie.udel.edu
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 3 refid NIST
driftfile /etc/ntp/drift
keys /etc/ntp/keys



the server is sitting on ip 180.128.38.200 and running fedora core 2

now when i have ntpd stopped and issue something like:

[[root@grid00 etc]# ntpq -p louie.udel.edu
remote refid st t when poll reach delay offset
jitter
================================================== ============================
-huey.udel.edu 128.175.60.175 2 u 83 1024 377 0.784 -0.512
0.733
-128.4.40.20 .GPS1. 1 u 11 64 377 0.680 -29.389
0.638
-128.4.40.19 .GPS2. 1 u 6 64 377 0.750 -29.523
0.585
*rackety.udel.ed .PPS. 1 u 231 1024 377 0.905 0.397
0.279
+ntp1.nss.udel.e .GPS. 1 u 684 1024 377 2.477 0.498
0.109
+NAVOBS1.MIT.EDU .PSC. 1 u 332 1024 377 10.441 0.780
0.202
-otc1.psu.edu .WWV. 1 u 327 1024 377 21.123 -21.654
1.752
-ntp0.usno.navy. .USNO. 1 u 221 1024 237 53.363 21.150
0.756


and it correctly sets my clock....

however when i do a service start i get:

[root@grid00 etc]# service ntpd start
ntpd: Synchronizing with time server: [FAILED]
Starting ntpd: [ OK ]

now in /var/log/messages i have the following lines regarding this
startup...

Jun 16 13:50:24 grid00 ntpdate[10622]: no server suitable for
synchronization found
Jun 16 13:50:24 grid00 ntpd: failed
Jun 16 13:50:24 grid00 ntpd[10627]: ntpd 4.2.0@1.1161-r Thu Mar 11
11:46:39 EST 2004 (1)
Jun 16 13:50:24 grid00 ntpd[10627]: precision = 1.000 usec
Jun 16 13:50:24 grid00 ntpd[10627]: kernel time sync status 0040
Jun 16 13:50:24 grid00 ntpd: ntpd startup succeeded
Jun 16 13:50:24 grid00 ntpd[10627]: frequency initialized 0.000 PPM
from /etc/ntp/drift


i am not sure why these arent suitable for sync, since it can sync with
them when i try and do it manually. or am i just making some weird
mistake? i just want it synced up with an EST server. thanks.


Cheers,

Adam.

On Thu, 16 Jun 2005 10:52:34 -0700, balgach wrote:
> i am not sure why these arent suitable for sync, since it can sync with
> them when i try and do it manually. or am i just making some weird
> mistake? i just want it synced up with an EST server. thanks.

Dunno why it does this, but mine fails to sync on startup too - then
it syncs up just fine within a few minutes. Its possible the firewall is
blocking the first request (have not checked for when the firewall rules
opening up that port happen in my boot sequence)

Since it does eventually work, and I personally don't reboot all that
often, I've not bothered to troubleshoot it anymore.

In article <(E-Mail Removed) .com>,
<(E-Mail Removed)> wrote:
:
:[root@grid00 etc]# service ntpd start
:ntpd: Synchronizing with time server: [FAILED]
:Starting ntpd: [ OK ]
:
:now in /var/log/messages i have the following lines regarding this
:startup...
:
:Jun 16 13:50:24 grid00 ntpdate[10622]: no server suitable for
:synchronization found
:Jun 16 13:50:24 grid00 ntpd: failed
:Jun 16 13:50:24 grid00 ntpd[10627]: ntpd 4.2.0@1.1161-r Thu Mar 11
:11:46:39 EST 2004 (1)
:Jun 16 13:50:24 grid00 ntpd[10627]: precision = 1.000 usec
:Jun 16 13:50:24 grid00 ntpd[10627]: kernel time sync status 0040
:Jun 16 13:50:24 grid00 ntpd: ntpd startup succeeded
:Jun 16 13:50:24 grid00 ntpd[10627]: frequency initialized 0.000 PPM
:from /etc/ntp/drift
:
:
:i am not sure why these arent suitable for sync, since it can sync with
:them when i try and do it manually. or am i just making some weird
:mistake? i just want it synced up with an EST server. thanks.

That initial synchronization not being done by the ntpd daemon. It is
performed by "ntpdate -b", so that's what you need to debug. If the
file /etc/ntp/step-tickers exists it will use the servers listed in that
file and not the ones from /etc/ntp.conf . You can take a look at
/etc/rc.d/init.d/ntpd script to see what is being done.

The above applies to recent Red Hat and Fedora Core distributions.
If you're running something else, it may be all wrong.

--
Bob Nichols AT comcast.net I am "rnichols42"