RE: setting up NTPd

James D. Parra Wed, 01 Oct 2003 11:21:25 -0700

Let's see if we can solve this one mod at a time.

First, uncomment;

#multicastclient # listen on default 224.0.1.1

change to;

multicastclient # listen on default 224.0.1.1

Restart ntpd and run ntptrace again.

James

-----Original Message-----
From: Jeff Silberberg [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2003 10:43 AM
To: James D. Parra
Cc: Redhat-List (E-mail)
Subject: RE: setting up NTPd

James,

        First thank you for your help here. I am new to RH Linux, after many years of AIX & FreeBSD ....

Now,

/etc/ntp.conf
# Added by JMS 9.29.03
#
server rolex.usg.edu prefer
server timex.usg.edu
server timex.cs.columbia.edu
#
# 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
#
#multicastclient                        # listen on default 224.0.1.1
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 no
#
# 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
#
logfile         /var/log/ntp.log

/etc/ntp/step-tickers
rolex.usg.edu
timex.usg.edu
timex.cs.columbia.edu

[EMAIL PROTECTED] etc]# ntpdate -d rolex.usg.edu
1 Oct 13:33:30 ntpdate[25449]: ntpdate 4.1.0 Wed Sep 5 06:54:31 EDT 2001 (1)
transmit(198.72.72.10)
receive(198.72.72.10)
transmit(198.72.72.10)
receive(198.72.72.10)
transmit(198.72.72.10)
receive(198.72.72.10)
transmit(198.72.72.10)
receive(198.72.72.10)
transmit(198.72.72.10)
server 198.72.72.10, port 123
stratum 2, precision -17, leap 00, trust 000
refid [130.207.244.240], delay 0.02878, dispersion 0.00018
transmitted 4, in filter 4
reference time:    c3258c51.e02ab000 Wed, Oct 1 2003 13:24:33.875
originate timestamp: c3258e6a.cd516000 Wed, Oct 1 2003 13:33:30.802
transmit timestamp: c3258e6a.c5bdd766 Wed, Oct 1 2003 13:33:30.772
filter delay: 0.02965 0.02887 0.02940 0.02878
         0.00000 0.00000 0.00000 0.00000
filter offset: 0.027505 0.027690 0.027460 0.027825
         0.000000 0.000000 0.000000 0.000000
delay 0.02878, dispersion 0.00018
offset 0.027825

1 Oct 13:33:30 ntpdate[25449]: adjust time server 198.72.72.10 offset 0.027825 sec

But,

[EMAIL PROTECTED] etc]# ntpd -A -c /etc/ntp.conf -l /var/log/ntp.log
[EMAIL PROTECTED] etc]# ntptrace
localhost: stratum 16, offset 0.000018, synch distance 0.00029
0.0.0.0:        *Not Synchronized*
[EMAIL PROTECTED] etc]#

An a little latter
[EMAIL PROTECTED] etc]# ntptrace
localhost: stratum 11, offset 0.000017, synch distance 0.94823
[EMAIL PROTECTED] etc]#

/var/log/ntp.log
1 Oct 13:37:47 ntpd[25459]: logging to file /var/log/ntp.log
1 Oct 13:37:47 ntpd[25459]: ntpd 4.1.0 Wed Sep 5 06:54:30 EDT 2001 (1)
1 Oct 13:37:47 ntpd[25459]: signal_no_reset: signal 13 had flags 4000000
1 Oct 13:37:47 ntpd[25459]: precision = 6 usec
1 Oct 13:37:47 ntpd[25459]: kernel time discipline status 0040
1 Oct 13:37:47 ntpd[25459]: frequency initialized 0.000 from /etc/ntp/drift
1 Oct 13:37:47 ntpd[25459]: logging to file /var/log/ntp.log
1 Oct 13:37:47 ntpd[25459]: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010)
1 Oct 13:37:47 ntpd[25460]: signal_no_reset: signal 17 had flags 4000000
1 Oct 13:38:00 ntpd[25459]: peer LOCAL(0) event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)

Any other ideas ????

JMS...

At 10:10 AM 10/1/2003 -0700, James D. Parra wrote:

Sorry about that. I should have proofed my e-mail.

You are correct; edit ntp.conf.

If step-tickers is empty, populate it with Stratum 2 IP address, or DNS resolvable names if you prefer. DNS resolvable names may be a better idea incase the addresses change.

James

-----Original Message-----
From: Jeff Silberberg [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 01, 2003 10:00 AM
To: James D. Parra
Subject: RE: setting up NTPd

Okay,

        I have been working with /etc/NTP.conf   what is ndb.conf ?

        An my Step-Tickers is currently empty :-)

        Lastly, IPs only ? Not DNS resolvable Names ??

        Thanks Again,

        JMS...

At 09:38 AM 10/1/2003 -0700, you wrote:

Hello Jeff,

I am not sure if NTP is broken on RH 7.2, but the following shows how I have it set up.

Edit /etc/nbd.conf as such;

server xxx.xxx.xxx.xxx prefer    ---> add stratum 2 server ip address here with the "prefer" comment (add others for redundancy)

server 127.127.1.0     # local clock

fudge   127.127.1.0 stratum 10

Edit or create file /etc/ntp/step-tickers with the Stratum 2 IP addresses as so;

xxx.xxx.xxx.xxx

Restart the ntp server;

# service ntpd restart

That should be all you need. Run ntptrace and check the results.

James

-----Original Message-----

From: Jeff Silberberg [mailto:[EMAIL PROTECTED]]

Sent: Wednesday, October 01, 2003 8:48 AM

To: [EMAIL PROTECTED]

Subject: RE: setting up NTPd

Hi James,

        I am having some similar issues with a Redhat 7.2 - "2.4.9-31enterprise" Server. But in my case I can't get NTP to see the time servers I have defined, even though the box under it in the rack running FreeBSD sees them fine.

        Since it's 7.2 I am using /etc/ntp.conf as the config base, but when I run ntptrace the only server I see is 127.0.0.1

        Can you maybe pass along some hints as to how you got this running, or did you just go to RH 9 ? Where NTP is supposedly fixed ?

        TIA,
        JMS.

Jeffrey Silberberg
CompuDesigns, Inc.
Atlanta, GA. 30350

Jeffrey Silberberg
CompuDesigns, Inc.
Atlanta, GA. 30350
(770) 399-9464

Jeffrey Silberberg
CompuDesigns, Inc.
Atlanta, GA. 30350
(770) 399-9464

RE: setting up NTPd

Reply via email to