l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
November 4: Social gathering
Next Installfest:
TBD
Latest News:
Oct. 24: LUGOD election season has begun!
Page last updated:
2002 Apr 24 22:05

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] I'm also having ntp problems :-(
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] I'm also having ntp problems :-(



On Wednesday 24 April 2002 08:16 pm, msimons@moria.simons-clan.com wrote:
> On Wed, Apr 24, 2002 at 06:03:56PM -0700, Ryan wrote:
> > I just set up ntpd on my firewall, and am trying to use it as a ntp relay
> > to sync my local lan to.
>
> [...]
>
> > The port's open and it will tell me about it's peers when i connect to it
> > with ntpq...
>
>   For a few minutes after restarting the ntpd it will tell clients not
> to synchronize off of itself.  You may have to wait (about 5 mins) for
> the server to get itself happy.

Nope, that's not it :-(

> > [root@bob root]# ntpq -c peers nat
> >      remote           refid      st t when poll reach   delay   offset 
> > jitter
> > =========================================================================
> >===== LOCAL(0)        LOCAL(0)        10 l    -   64  377    0.000   
> > 0.000   0.000 *time.nist.gov   .ACTS.           1 u    -   64  377  
> > 66.324   11.718   1.090 +step.mother.com ntp1.usno.navy.  2 u   14   64 
> > 377   26.117   -0.109   0.941
>
>                                    ^^ stratum column
>
>   From what I understand you have the "nat" machine synchronizing off of
> three sources, itself and two remote time servers, it has picked
> time.nist.gov to use as it's reference (probably because it has a lower
> stratum level). When I last played around with ntp clients I found that
> regardless of how close different sources are from localtime, the clients
> would first sort by stratum, then all the machines with the lowest stratum
> would be selected for "closest to me".
>
>   You don't have a reliable local time source so you shouldn't sync against
> the local machine, I've seen ntp servers that have themselves in their
> peers list rule out the other servers (because of network connections),
> then go around reporting themselves as stratum 0 machines, which can
> totally other clients using that machine's clock (because of the block
> above).
>
>   I would recommend you drop localhost from your configuration then pick
> a series of time servers which are the same stratum.

Ok, didn't help...

> > [root@bob root]# ntpdate nat
> > 24 Apr 18:02:18 ntpdate[3482]: no server suitable for synchronization
> > found
>
>   If you add -q it will show you the results from each machines it tried,
> and which one it would pick.  A -d to see what it's doing, in the
> output look for a line like this:
> # stratum 16, precision -17, leap 11, trust 000
>   When a machine reports itself at stratum 16, it is basically saying
> don't trust me, I don't think I'm synchronized against anything.

[root@bob root]# ntpdate -q nat24 Apr 21:30:47 ntpdate[7067]: ntpdate 
4.1.1@1.786 Wed Feb 27 16:42:53 CET 2002 (1)
transmit(192.168.0.1)
transmit(192.168.0.1)
transmit(192.168.0.1)
transmit(192.168.0.1)
transmit(192.168.0.1)
192.168.0.1: Server dropped: no data
server 192.168.0.1, port 123
stratum 0, precision 0, leap 00, trust 000
refid [0.0.0.0], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time:    00000000.00000000  Wed, Feb  6 2036 22:28:16.000
originate timestamp: 00000000.00000000  Wed, Feb  6 2036 22:28:16.000
transmit timestamp:  c07204fa.dcaf9229  Wed, Apr 24 2002 21:30:50.862
filter delay:  0.00000  0.00000  0.00000  0.00000
         0.00000  0.00000  0.00000  0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
         0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000

24 Apr 21:30:51 ntpdate[7067]: no server suitable for synchronization found

>   If you try this stuff and are still having problems post some more
> details.
>
>     Later,
>       Mike
> _______________________________________________
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Appahost Applications
For a significant contribution towards our projector, and a generous donation to allow us to continue meeting at the Davis Library.