NTP trouble...

NTP trouble...

Post by Stuart Rau » Sat, 08 Jul 2000 04:00:00



Using Redhat 6.2 and Xntp-5.93-14 to keep the server clock on time.

Xntpd doesn't complain but doesn't update the clock either.  When trying
to update manually with "ntpdate clock.psu.edu" it responds with "No
server suitable for synchronization found".

I can ping clock.psu.edu from the Linux box.  An NTP client on a Win98
machine connected through IP masq on the Linux box updates fine.  I just
can't get the Linux box to sync up!

Any suggestions???
--

Stuart Rauh

 
 
 

NTP trouble...

Post by Quiney, Philip [HAL02:HH00:EXCH » Sat, 08 Jul 2000 04:00:00



> Using Redhat 6.2 and Xntp-5.93-14 to keep the server clock on time.

> Xntpd doesn't complain but doesn't update the clock either.  When trying
> to update manually with "ntpdate clock.psu.edu" it responds with "No
> server suitable for synchronization found".

> I can ping clock.psu.edu from the Linux box.  An NTP client on a Win98
> machine connected through IP masq on the Linux box updates fine.  I just
> can't get the Linux box to sync up!

Hi,

As root run ntpq...

If it fails then xntpd is not running - it will refuse to run if the
time is more than 50 mins (IIRC) from the network time. If this is the
case use 'date' to get the time nearer and then 'setclock' to write to
the BIOS clock. Once in ntpq you can display the status of xntpd and get
the 'peer' information. For example here is mine.


ntpq> rv
status=06f4 leap_none, sync_ntp, 15 events, event_peer/strat_chg
system="Linux", leap=00, stratum=3, rootdelay=6.39,
rootdispersion=23.56, peer=64377, refid=bhars1.europe.nortel.com,
reftime=bd10025c.61bb7000  Fri, Jul  7 2000  8:16:44.381, poll=10,
clock=bd10027a.c1003000  Fri, Jul  7 2000  8:17:14.753, phase=-1.012,
freq=-43355.36, error=4.79
ntpq> pe
     remote           refid      st t when poll reach   delay  
offset    disp
==============================================================================
 bhars1.europe.n zhars62a.europe  2 m  94h 1024    0     1.04   -1.166
16000.0
 LOCAL(0)        LOCAL(0)        10 l   60   64  377     0.00    0.000  
10.01
+bhars5a3.europe bhars1.europe.n  3 m   42   64  376     1.13  
2.339    2.33
*bhars1.europe.n zhars62a.europe  2 m   32   64  376     1.13  
-1.012    2.29
ntpq>

The important bit (from the rv command) is the 'sync_ntp' flag which
means what it says ;-)

You did add the server line to /etc/ntp.conf didn't you?

Mine is

server 47.101.114.205
#
# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available. The
# default stratum is usually 3, but in this case we elect to use stratum
# 0. Since the server line does not have the prefer keyword, this driver
# is never used for synchronization, unless no other other
# synchronization source is available. In case the local host is
# controlled by some external source, such as an external oscillator or
# another protocol, the prefer keyword would cause the local host
to            

Which is an internal address of a machine with a GPS receiver.

Be aware that some of the 'NTP' clients on Windows aren't actally using
NTP at all. They use the 'daytime' (13) and/or 'time' (37) ports rather
than the 'ntp' (123) port - WorldTime is an example of this - it had me
going for a while. It is possible your server is not allowing 'true' NTP
access - there is a list somewhere of suitable servers - in my case my
ISP has one which is stratum 3 which is good enough for what I need.

HTH

Regards

Phil Q

--

Phil Quiney                             CSIP Demonstrator

Telephone: +44 (1279) 402363            London Rd, Harlow,
Fax:       +44 (1279) 402885            Essex CM17 9NA,
                                        United Kingdom.

"This message may contain information proprietary to Northern
Telecom so any unauthorised disclosure, copying or distribution
of its contents is strictly prohibited."

 
 
 

NTP trouble...

Post by Tom East » Sat, 08 Jul 2000 04:00:00



>Using Redhat 6.2 and Xntp-5.93-14 to keep the server clock on time.

>Xntpd doesn't complain but doesn't update the clock either.  When trying
>to update manually with "ntpdate clock.psu.edu" it responds with "No
>server suitable for synchronization found".

>I can ping clock.psu.edu from the Linux box.  An NTP client on a Win98
>machine connected through IP masq on the Linux box updates fine.  I just
>can't get the Linux box to sync up!

>Any suggestions???

Is your ipchains ruleset blocking udp port 123 to/from the firewall
itself?

-Tom
--
Tom Eastep             \  Eastep's First Principle of Computing:
ICQ #60745924           \  "Any sane computer will tell you how it

Shoreline, Washington USA \___________________________________________

 
 
 

NTP trouble...

Post by Stuart Rau » Sat, 08 Jul 2000 04:00:00


I ran "ntpq rv" and got the following:

status=c011 sync_alarm, sync_unspec, 1 event, event_restart
system="Linux", leap=11, stratum=16, rootdelay=0.00,
rootdispersion=0.00, peer=0, refid=0.0.0.0,
reftime=00000000.00000000  Thu, Feb  7 2036  0:28:16.000, poll=4,
clock=bd107d18.e7cce000  Fri, Jul  7 2000 11:00:24.905, phase=0.000,
freq=0.00, error=0.00

As you can see xntp is running but having troubles.  My ntp.conf is as
follows...

server clock.psu.edu

Concerned about my IP masqerading led me to try an ntp client on a Win98
box connected through the Linux box in question to the net.  Win98 syncs
to clock.psu.edu just fine!  I think that says my masqerading setup is
ok???

I'm running user profiles through samba.  I need to have the windows
machines on my internal network time sync to the Linux machine while the
Linux machine syncs to external time.  As I understand it this is to
maintain the integrity of the user profiles.  Syncing my internal
machines to Linux is working fine.  The trouble is the time on all the
machines drifts because I can't get xntpd working properly on Linux!

I appreciate your help on this!!!

--

Stuart Rauh

 
 
 

NTP trouble...

Post by David Efflan » Sat, 08 Jul 2000 04:00:00



>Using Redhat 6.2 and Xntp-5.93-14 to keep the server clock on time.

>Xntpd doesn't complain but doesn't update the clock either.  When trying
>to update manually with "ntpdate clock.psu.edu" it responds with "No
>server suitable for synchronization found".

You cannot run ntpdate while xntpd is running.  But I have only used
ntpdate (and not xntpd) so I am not sure how to set up xntpd.  Do you have
multiple stratum 2 time servers listed in /etc/ntp.conf so xntpd will
still work in case one is down or busy?

>I can ping clock.psu.edu from the Linux box.  An NTP client on a Win98
>machine connected through IP masq on the Linux box updates fine.  I just
>can't get the Linux box to sync up!

>Any suggestions???
>--

>Stuart Rauh


--

http://www.autox.chicago.il.us/  http://www.berniesfloral.net/
http://hammer.prohosting.com/~cgi-wiz/  http://cgi-help.virtualave.net/
 
 
 

NTP trouble...

Post by Stuart Rau » Sat, 08 Jul 2000 04:00:00



says...

Quote:> You cannot run ntpdate while xntpd is running.  But I have only used
> ntpdate (and not xntpd) so I am not sure how to set up xntpd.  Do you have
> multiple stratum 2 time servers listed in /etc/ntp.conf so xntpd will
> still work in case one is down or busy?

I haven't added other servers yet because clock.psu.edu works when I try
a windows client from a Win98 machine on my internal network.  That
machine connects to the net via IP masquerading and it's requests for
time service go through just fine!  Now if I can just get the server to
work!
--

Stuart Rauh

 
 
 

NTP trouble...

Post by Stuart Rau » Mon, 10 Jul 2000 04:00:00



Quote:> Using Redhat 6.2 and Xntp-5.93-14 to keep the server clock on time.

> Xntpd doesn't complain but doesn't update the clock either.  When trying
> to update manually with "ntpdate clock.psu.edu" it responds with "No
> server suitable for synchronization found".

> I can ping clock.psu.edu from the Linux box.  An NTP client on a Win98
> machine connected through IP masq on the Linux box updates fine.  I just
> can't get the Linux box to sync up!

> Any suggestions???

--
The answer to this was in ipchains.  For some reason an NTP client on the
internal net is allowed to get through but the server was not.

I added a chain to allow UDP traffic on port 123 and the problem is
resolved!

Thanks for everyone's help.

Stuart Rauh

 
 
 

1. ntp.conf ntp config file setup

I want to sync my server to time standards. I'm looking for a general
ntp.conf file example that I can drop into my system and get it to work.
I'm not looking for anything fancy here. I just want it to be close and
not have to fool with it.

Does anyone have a sample you can post?

--
Supreme Commander * Nerd Liberation Movement
"We're coming out of the back room!"

http://www.perkel.com
http://www.ctyme.com

Sent via Deja.com http://www.deja.com/
Before you buy.

2. Unzipping Apache file on HPux1

3. Need NTP (ntp/xntp) for Solaris 2.x

4. File Size Limits

5. NTP client not synchronised with NTP server

6. Kernel 2.5.70 compile errors

7. Problem with ntp on solaris (also posted on comp.protocols.time.ntp)

8. HELP: Fdisk no longer works

9. How to Configure Linux machine as NTP server and Solaris machine as NTP client

10. NTP: Where can I get binaries for NTP?

11. Trouble Connecting to Local ntp Server

12. More@!!.. Panasonic/SB-CD troubles, trouble, trouble...

13. Trouble, trouble, trouble - SCSI ?