Dear Ramain,
Thaks a lot for your help about. I already had tried the configuration you
recommended me without any success. I'm including the configurations I have
and some other information. Do you have any idea of what might be wrong? or
How to configure a Red Hat Linux box as an NTP server having its internal
clock as the time reference?.........
Thanks,
Mario Siller.
The IP address of my NTP server is 20.0.0.1. The configuration I have on the
clients ntp.conf file is:
server 20.0.0.1
authenticate no
On the other hand the ntpd daemon on the server seem to be working ok. When
I do a ntptrace on the server this is what I get:
----------------------------------------------------------------------------
----------------------------------------------------------------------------
--------------------
[root@localhost root]# ntptrace
localhost.localdomain: stratum 1, offset 0.000074, synch distance 0.01485,
refid 'LCL'
[root@localhost root]#
----------------------------------------------------------------------------
----------------------------------------------------------------------------
--------------------
When I run a ntpdate from any client this is what I get:
----------------------------------------------------------------------------
----------------------------------------------------------------------------
--------------------
[root@localhost log]# ntpdate -b -v -d -u 20.0.0.1
23 May 12:03:05 ntpdate[15169]: ntpdate 4.1.0 Wed Sep 5 06:54:31 EDT 2001
(1)
transmit(20.0.0.1)
transmit(20.0.0.1)
transmit(20.0.0.1)
transmit(20.0.0.1)
transmit(20.0.0.1)
server 20.0.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 Thu, Feb 7 2036 6:28:16.000
originate timestamp: 00000000.00000000 Thu, Feb 7 2036 6:28:16.000
transmit timestamp: c0974aec.ae66dbd7 Thu, May 23 2002 12:03:08.681
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
23 May 12:03:09 ntpdate[15169]: no server suitable for synchronization found
[root@localhost log]#
----------------------------------------------------------------------------
----------------------------------------------------------------------------
--------------------
Finally if I start up the ntpd daemon on any client and run the commands
"ech rv | ntp" and ntpq -p this is what I get:
[root@localhost log]# echo rv | ntpq
status=c011 sync_alarm, sync_unspec, 1 event, event_restart,
version="ntpd 4.1.0 Wed Sep 5 06:54:30 EDT 2001 (1)", processor="i686",
system="Linux2.4.7-10", leap=11, stratum=16, precision=-16,
rootdelay=0.000, rootdispersion=6.720, peer=0, refid=0.0.0.0,
reftime=00000000.00000000 Thu, Feb 7 2036 6:28:16.000, poll=4,
clock=c0974fd1.6db78cc9 Thu, May 23 2002 12:24:01.428, state=0,
offset=0.000, frequency=0.000, jitter=0.015, stability=0.000
[root@localhost log]#
[root@localhost log]# ntpq -p
remote refid st t when poll reach delay offset
jitter
============================================================================
==
taplab 0.0.0.0 16 u - 64 0 0.000 0.000
4000.00
[root@localhost log]#
----------------------------------------------------------------------------
------------------
The message that concerns me the most from the CLIENTs log is "May 23
18:08:34 localhost ntpdate[15492]: no server suitable for synchronization
found".
Heres is what I get for the ntptrace -v -v 20.0.0.1 command (taplab is the
hostname of 20.0.0.1):
----------------------------------------------------------------------
[root@localhost log]# ntptrace -v -v 20.0.0.1
taplab: *Timeout*
[root@localhost log]#
----------------------------------------------------------------------
I included a ping send to "taplap" just to show that there is connectivity
to this server.
----------------------------------------------------------------------
[root@localhost log]# ping taplab
PING taplab (20.0.0.1) from 172.16.50.1 : 56(84) bytes of data.
Warning: time of day goes back, taking countermeasures.
64 bytes from taplab (20.0.0.1): icmp_seq=0 ttl=254 time=4.434 msec
64 bytes from taplab (20.0.0.1): icmp_seq=1 ttl=254 time=3.221 msec
--- taplab ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/mdev = 3.221/3.827/4.434/0.609 ms
[root@localhost log]#
----------------------------------------------------------------------
In the other hand this is what is stored in /var/logs/messages when stopping
and restarting the ntpd daemon but NOW IN THE SERVER:
----------------------------------------------------------------------
[root@localhost root]#
May 23 18:15:46 localhost ntpd[2806]: ntpd exiting on signal 15
May 23 18:15:47 localhost ntpd: ntpd shutdown succeeded
May 23 18:17:17 localhost ntpdate[2863]: no server suitable for
synchronization found
May 23 18:17:17 localhost ntpd: succeeded
May 23 18:17:17 localhost ntpd: ntpd startup succeeded
May 23 18:17:17 localhost ntpd[2868]: ntpd 4.1.0 Wed Sep 5 06:54:30 EDT
2001 (1)
May 23 18:17:18 localhost ntpd[2868]: precision = 24 usec
May 23 18:17:18 localhost ntpd[2868]: kernel time discipline status 0040
May 23 18:20:43 localhost ntpd[2868]: time set 0.000000 s
May 23 18:20:43 localhost ntpd[2868]: synchronisation lost
----------------------------------------------------------------------
-----Original Message-----
From: Romain Kang [mailto:[EMAIL PROTECTED]]
Sent: 23 May 2002 22:11
To: [EMAIL PROTECTED]
Subject: Re: NTP Server/Client Configuration
If your local NTP master is actually connected to the Internet,
then you can use one of the public open servers as your master.
See
http://www.eecis.udel.edu/~mills/ntp/servers.htm
If you don't have continual Internet access, you set give your local
master's NTP stratum with the lines
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
You can add some real NTP servers in there, too -- whenever you are
connected to the Internet, your local master should be able to sync
to public servers.
The local NTP slaves can do something similar, but use a higher
stratum number (e.g., stratum >= 12). So they will follow the
local master's clock.
Romain Kang Disclaimer: I speak for myself
alone,
[EMAIL PROTECTED] except when indicated otherwise.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
