[ale] Clueless on ntp

[cfowler]

After I let ntpd -d run a little while it seems that I was able to
sync.  I guess this is normal.

[root at moses root]# ntpdate 192.168.2.8
26 Aug 11:06:13 ntpdate[3729]: step time server 192.168.2.8 offset
-79.657160 sec


On Mon, 2002-08-26 at 10:57, cfowler wrote:
> 
> I have an ntp server running on my machine at 192.168.2.8
> 
> Whenever I try to get a date on 192.168.2.5 I get an error message
> [root at moses root]# ntpdate 192.168.2.8
> 26 Aug 10:53:43 ntpdate[3688]: no server suitable for synchronization
> found
> 
> Help as usual would be greatly appreciated.
> 
> 
> Daemon running on 192.168.2.8 in debug mode.
> 
> [root at cfowler etc]# ntpd -d
> create_sockets(123)
> interface <lo> OK
> interface <eth0> OK
> bind() fd 4, family 2, port 123, addr 0.0.0.0, flags=1
> bind() fd 5, family 2, port 123, addr 127.0.0.1, flags=0
> bind() fd 6, family 2, port 123, addr 192.168.2.8, flags=1
> init_io: maxactivefd 6
> resolving time
> resolving nist1.datum.com
> peer_clear: at 0 assoc ID 0
> newpeer: 127.0.0.1->127.127.1.0 mode 3 vers 4 poll 6 6 flags 21 1 ttl 0
> key 00000000
> report_event: system event 'event_restart' (0x01) status 'sync_alarm,
> sync_unspec, 1 event, event_unspec' (0xc010)
> auth_agekeys: at 1 keys 1 expired 0
> peer_clear: at 2 assoc ID 0
> newpeer: 192.168.2.8->204.34.198.41 mode 3 vers 4 poll 6 10 flags 1 1
> ttl 0 key 00000000
> peer_clear: at 2 assoc ID 0
> newpeer: 192.168.2.8->63.149.208.50 mode 3 vers 4 poll 6 10 flags 1 1
> ttl 0 key 00000000
> refclock_transmit: at 3 127.127.1.0
> refclock_receive: at 3 127.127.1.0
> peer LOCAL(0) event 'event_reach' (0x84) status 'unreach, conf, 1 event,
> event_reach' (0x8014)
> refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000000
> clock_filter: n 1 off 0.000000 del 0.000000 dsp 7.937515 jit 0.000015,
> age 0
> receive: at 8 192.168.2.8<-192.168.2.5 mode 3 code 2
> transmit: at 8 192.168.2.8->192.168.2.5 mode 4
> receive: at 8 192.168.2.8<-192.168.2.5 mode 3 code 2
> transmit: at 8 192.168.2.8->192.168.2.5 mode 4
> receive: at 8 192.168.2.8<-192.168.2.5 mode 3 code 2
> transmit: at 8 192.168.2.8->192.168.2.5 mode 4
> receive: at 8 192.168.2.8<-192.168.2.5 mode 3 code 2
> transmit: at 8 192.168.2.8->192.168.2.5 mode 4
> transmit: at 9 192.168.2.8->63.149.208.50 mode 3
> transmit: at 9 192.168.2.8->204.34.198.41 mode 3
> auth_agekeys: at 60 keys 1 expired 0
> refclock_transmit: at 67 127.127.1.0
> refclock_receive: at 67 127.127.1.0
> refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000000
> clock_filter: n 2 off 0.000000 del 0.000000 dsp 3.937763 jit 0.000015,
> age 0
> transmit: at 73 192.168.2.8->63.149.208.50 mode 3
> 
> ntpd.conf file on 192.168.2.8# Prohibit general access to this service.
> restrict default ignore
> 
> # Permit all access over the loopback interface.  This could
> # be tightened as well, but to do so would effect some of
> # the administrative functions.
> restrict 127.0.0.1 
> 
> 
> # -- CLIENT NETWORK -------
> # Permit systems on this network to synchronize with this
> # time service.  Do not permit those systems to modify the
> # configuration of this service.  Also, do not use those
> # systems as peers for synchronization.
> restrict 192.168.2.0 mask 255.255.255.0 notrust nomodify notrap
> 
> 
> # --- OUR TIMESERVERS ----- 
> # or remove the default restrict line 
> # Permit time synchronization with our time source, but do not
> # permit the source to query or modify the service on this system.
> 
> # restrict mytrustedtimeserverip mask 255.255.255.255 nomodify notrap
> noquery
> server time
> server nist1.datum.com
> 
> 
> 
> # --- NTP MULTICASTCLIENT ---
> #multicastclient                        # listen on default 224.0.1.1
> # restrict 224.0.1.1 mask 255.255.255.255 notrust nomodify notrap
> # restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap
> 
> 
> 
> # --- GENERAL CONFIGURATION ---
> #
> # 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
> # disregard all other synchronization sources, unless the kernel
> # modifications are in use and declare an unsynchronized condition.
> #
> server  127.127.1.0     # local clock
> fudge   127.127.1.0 stratum 10  
> 
> #
> # Drift file.  Put this in a directory which the daemon can write to.
> # No symbolic links allowed, either, since the daemon updates the file
> # by creating a temporary in the same directory and then rename()'ing
> # it to the file.
> #
> driftfile /etc/ntp/drift
> broadcastdelay  0.008
> 
> #
> # Authentication delay.  If you use, or plan to use someday, the
> # authentication facility you should make the programs in the auth_stuff
> # directory and figure out what this number should be on your machine.
> #
> authenticate yes
> 
> #
> # Keys file.  If you want to diddle your server at run time, make a
> # keys file (mode 600 for sure) and define the key number to be
> # used for making requests.
> #
> # PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote
> # systems might be able to reset your clock at will. Note also that
> # ntpd is started with a -A flag, disabling authentication, that
> # will have to be removed as well.
> #
> keys            /etc/ntp/keys
> 
> 
> 
> 
> 
> 
> ---
> This message has been sent through the ALE general discussion list.
> See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
> sent to listmaster at ale dot org.
> 
> 
> 



---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.