On Tuesday 28 January 2003 08:04 am, Mike Vanecek wrote: > ---------- Original Message ----------- > From: Stephen Carville <carville@cpl.net> > To: psyche-list@redhat.com > Sent: Tue, 28 Jan 2003 07:35:37 -0800 > Subject: Re: ntpd doesn't or does it? > > > AFAIK the 'reject' has nothing to do With the connection. It is the > > judgement of the ntp algorithm whether the source is reliable. It > > usually takes several minutes for a newly started daemon to decide > > who to "trust." > > I thought the left hand column in the peers output would give an indication of > the connection? If it is blank, does it not mean ntp is having a problem? > > > Test for connections with ntpdate: > > > > # sudo ntpdate chimer.unt.edu > > > > If you see something like: > > > > 28 Jan 07:21:11 ntpdate[21270]: adjust time server 129.120.209.140 > > offset -0.006593 sec > > > > Then your are connectiing. > > [root@www log]# ntpdate chimer.unt.edu > 28 Jan 10:00:45 ntpdate[3438]: the NTP socket is in use, exiting > > [root@www log]# ntpdate otc1.psu.edu > 28 Jan 10:02:47 ntpdate[3444]: the NTP socket is in use, exiting You sometimes have to shut down ntpd to do this. Sorry, I forget that part. > > > > The 4000 for jitter may indicate you are not connecting. Use netstat > > to see if the ports are listening: > > > > # sudo netstat -nuap > > > > If ntp is running you will see something like: > > > > udp 0 0 192.168.1.1:123 0.0.0.0:* 28438/ntpd > > [root@www log]# netstat -naup > Active Internet connections (servers and established) > Proto Recv-Q Send-Q Local Address Foreign Address State > PID/Program name > udp 0 0 0.0.0.0:1024 0.0.0.0:* > 530/rpc.statd > udp 0 0 192.168.1.95:137 0.0.0.0:* > 843/nmbd > udp 0 0 0.0.0.0:137 0.0.0.0:* > 843/nmbd > udp 0 0 192.168.1.95:138 0.0.0.0:* > 843/nmbd > udp 0 0 0.0.0.0:138 0.0.0.0:* > 843/nmbd > udp 0 0 0.0.0.0:111 0.0.0.0:* > 511/portmap > udp 0 0 192.168.1.95:123 0.0.0.0:* > 3369/ntpd > udp 0 0 127.0.0.1:123 0.0.0.0:* > 3369/ntpd > udp 0 0 0.0.0.0:123 0.0.0.0:* > 3369/ntpd > > Actually, I do not want to act as a server, but rather just use external > servers to sync to an external server. Hence, maybe I am taking the wrong > approach?? > > Maybe I should shut down ntpd and just run ntpdate on a daily basis? For a few machines that works well. For a larger network it is etter to set up your own timeserver. > > > > On Monday 27 January 2003 09:18 pm, Mike Vanecek wrote: > > > If I understand what I am seeing from ntpq below, then ntpd is being > > rejected > > > by all of the servers I have configured? I have been able to > > connect to the > > > servers from a windows machine on the same intranet, so it should > > not be a > > > firewall issue. Am I interpreting the output correctly? > > > > > > Thank you, Mike. > > > > > > > > > ntpq> peers > > > remote refid st t when poll reach delay > > offset jitter > > > > > ============================================================================== > > > chimer.unt.edu 0.0.0.0 16 u - 64 0 0.000 > > 0.000 4000.00 > > > otc1.psu.edu 0.0.0.0 16 u - 64 0 0.000 > > 0.000 4000.00 > > > cudns.cit.corne 0.0.0.0 16 u - 64 0 0.000 > > 0.000 4000.00 > > > time.nist.gov 0.0.0.0 16 u - 64 0 0.000 > > 0.000 4000.00 > > > catapult.SGI.CO 0.0.0.0 16 u - 64 0 0.000 > > 0.000 4000.00 > > > ntpq> associations > > > ind assID status conf reach auth condition last_event cnt > > > =========================================================== > > > 1 3692 8000 yes yes none reject > > > 2 3693 8000 yes yes none reject > > > 3 3694 8000 yes yes none reject > > > 4 3695 8000 yes yes none reject > > > 5 3696 8000 yes yes none reject > > > ntpq> > > > > > > > > > > > > -- > > > Psyche-list mailing list > > > Psyche-list@redhat.com > > > https://listman.redhat.com/mailman/listinfo/psyche-list > > > > > > > > -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt Blessed are those who, in the face of death, think only of the front sight. -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
