ntpd on Red Hat

[gaf at blu.org (Jerry Feldman)]

It appears not to be taking the external servers. In contrast, I've 
included the same table from my home system below. (Note that at home I'm 
just using some secondary time servers). 

--------------------- BLU Server --------
[root at asgard gaf]# /usr/sbin/ntpq -p
 
    remote           refid      st t when poll reach   delay   offset  
jitter
============================================================================
==
*LOCAL(0)        LOCAL(0)        10 l   19   64  377    0.000    0.000   
0.000
 jj.cs.umb.edu   0.0.0.0         16 u    -   64    0    0.000    0.000 
4000.00
 ourconcord.net  0.0.0.0         16 u    -   64    0    0.000    0.000 
4000.00
 NAVOBS1.MIT.EDU 0.0.0.0         16 u    -   64    0    0.000    0.000 
4000.00
 sirius.ctr.colu 0.0.0.0         16 u    -   64    0    0.000    0.000 
4000.00
 mead.harvard.ed 0.0.0.0         16 u    -   64    0    0.000    0.000 
4000.00

--------------------------------- my home desktop -------------------------
gaf at gaf:~> /usr/sbin/ntpq -p
     remote           refid      st t when poll reach   delay   offset  
jitter
============================================================================
==
 LOCAL(0)        LOCAL(0)        10 l   45   64  377    0.000    0.000   
0.031
+jj.cs.umb.edu   dns1.autonet.ne  3 u  246 1024  377   46.661   16.431   
3.208
*ourconcord.net  w1bw.org         2 u  226 1024  343   62.846   -3.220  
18.542
On 4 Apr 2002 at 11:39, Kent Borg wrote:

> On Thu, Apr 04, 2002 at 11:27:15AM -0500, Jerry Feldman wrote:
> > It appears that ntpd is essentially a nop. It is running, but does
> > not appear to adjust the time based on the servers. I have the same
> > servers set up for my home system (SuSE running xntpd), which does
> > appear to time synch successfully.
> 
> What do you get from:
> 
>   $ /usr/sbin/ntpq -p
> 
> Do you get interesting and varying values for "delay", "offset", and
> "jitter"?  Are some of your reference servers marked with "*", "+",
> and "-"?  Do the values for "reach" have nearly as many 1's set as
> does the idea 0x377?  Does "when" increment until it hits the "poll"
> value and then update the other values?
> 
> If so, then ntpd is getting time information but for some reason isn't
> able to set the clock.  If not, then ntpd might be capable of setting
> the clock, but isn't getting out to your reference sources.
> 
> That might help you split your problem in two.
> 
> 
> -kb, the Kent whose ntpd daemon used not to be willing to serve time
> (was only willing to be a client) until upgrading to RH 7.2.


--
Jerry Feldman <gaf at blu.org>
Associate Director
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9