Problem on Configuring NTP Server...

[haariseshu]

Dear Friends when i'm testing my client to syncronize time with NTP server0.
I have used ntpdate command to check But it's giving the following error:
28 Dec 17:24:05 ntpdate[3740]: the NTP socket is in use, exiting
But I don't know what's the error. My client couldn't syncronize with NTP server: Also i'm attaching my server and client configuration files: Please help me. Thank you.

Server ntp config. file:


# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.

restrict default nomodify notrap noquery

# 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.1.0 mask 255.255.255.0 nomodify notrap
restrict 151.2.119.31 mask 255.255.0.0 nomodify notrap


# --- OUR TIMESERVERS -----
#server 0.pool.ntp.org
#server 1.pool.ntp.org
#server 2.pool.ntp.org

server localhost

# --- NTP MULTICASTCLIENT ---
#multicastclient # listen on default 224.0.1.1
# restrict 224.0.1.1 mask 255.255.255.255 nomodify notrap
# restrict 192.168.1.0 mask 255.255.255.0 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.
#
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 /var/lib/ntp/drift
broadcastdelay 0.008

#
# 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



My client config. file:


# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.
server 151.2.119.30
restrict default nomodify notrap noquery

# 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.1.0 mask 255.255.255.0 nomodify notrap


# --- OUR TIMESERVERS -----


# --- NTP MULTICASTCLIENT ---
#multicastclient # listen on default 224.0.1.1
# restrict 224.0.1.1 mask 255.255.255.255 nomodify notrap
# restrict 192.168.1.0 mask 255.255.255.0 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.
#
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 /var/lib/ntp/drift
broadcastdelay 0.008

#
# 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
restrict 151.2.119.30 mask 255.255.255.255 nomodify notrap
server 151.2.119.30

[Sektion9]

The error you are seeing is for ntpdate which from my experience is not something you want running all the time on your clients. It is used to do a manual sync to set the date as well as the time. If you feel the need to run it, it should be run once at bootup before starting the NTP client and from there, the NTP client can handle the time changes and syncs.

-S9-

[s1gt3rm]

Try and comment out the line

restrict 151.2.119.30 mask 255.255.255.255 nomodify notrap

Then restart the ntp server on your client.
Also make sure there is no firewall blocking the ntp traffic (udp port 123)

[countach44]

You cannot run ntpd and ntpdate at the same time (they run on the same socket). ntpd slowly syncs your clock with the server's clock, and ntpdate instantly adjusts your clock immediately to the server's time. If you wish to run ntpdate on your client, you must stop ntpd on that client box first.

[haariseshu]

Thank you friend! Do you know is there any possibilities to run NTP Service in Master & Slave scenario? So that if primary Server goes down the secondary will takeplace of the primary.

[countach44]

no problem
I think this is what you are looking for...
http://www.openfree.org/forums/showthread.php?t=18410

Let me know if that does the trick

[haariseshu]

Good thank you! I have tried giving multiple servers for reference to my clients. ntpdate command is working. But if root ntp goes down no clients can synchronize their time to slave server directly. But still the ntpdate command from client side to the slave ntp is working. Are you having any about this.

[haariseshu]

And friend can you tell me the use of drift file. Actually what is drift file.

[countach44]

The drift file contains a calculation of the offset of the system clock.

http://www.cis.udel.edu/~mills/ntp/html/ntpd.html (look under Frequency Discipline)
http://h30097.www3.hp.com/docs/base_...4/0189____.HTM

[haariseshu]

Hello Friend in NTP scenario the client can have multiple servers and can choose its server to synchronize with it. But from where it will refer to check the accuracy of the server. Where it will get the source.