NTP problems

[Tom Horan]

I have a HP 11 server setup as my NTP broadcast server. Everything looks fine from the server but one of my clients connecting to it is not syching the time, when I run ntpq -p is comes back with the message No associated ID's returned. The ntp.conf file on the client looks fine and the ntp.drift is in place. ANy ideas. The client is HP 11.00.

Cheers
Paul

[James R. Ferguson]

Hi Paul:

A couple of comments. It take about 320 seconds for synchronization to occur after startup. If the difference between your server's time and the time source provider is greater than 1000 seconds, the 'xntpd' daemon will die. Adjust the time on your server if/as necessary to meet this constraint.

If neither of the above conditions apply, it is possible that your server cannot see the time source. If a firewall is involved, make sure that ntp packets can cross it. Make sure, that the IP address of any external time source is correctly specified in any Network Address Translation (NAT) tables.

Regards!

...JRF...

[linuxfan]

Hi Paul,

You may have to run ntpdate on the client for the initial synchronization(make sure xntpd is down ) and once the clocks are synchronized, you may start the xntpd again.

Found this HP doc,

/Begin/
Error: no association id's and ntp DocId: KBRC00001953 Updated: 6/3/00 6:26:26 AM

PROBLEM
The error "no association ids" is being seen when trying to check on the
status of ntp syncronization by using the command "ntpq -p"


CONFIGURATION
10.x and 11.x systems
RESOLUTION
The ntpq command will display the status of the xntpd daemon running on
this system. When the error "no association ids" is seen, this means
that this unix system has not yet found or heard from a valid NTP server.

This is often caused by one of the following:
1) The NTP server selected in the /etc/ntp.conf file on this NTP client
cannot be reached thru the network.
2) The NTP server is not running the xntpd daemon
3) The NTP server selected is not sync'd up via NTP
ntp servers must be sync'd up to their own clocks or another NTP
server before they will respond to NTP clients trying to sync off of
them

Verify the server can be pinged, that its running the XNTPD daemon and
that its sync'd to itself or another NTP server (by using ntpq -p).

/End/

-HTH
Ramesh

[Sachin Patel]

Hi Paul,
If I am correct you do not have xntpd running.
start it using
#/sbin/init.d/xntpd
To start it at boot time
#vi /etc/rc.config.d/netdaemons
and XNTPD=1

Check your /var/adm/syslog/syslog file it will gives you some hint.

Sachin

[Deshpande Prashant]

Hi
Try manually using ntpdate command.
#ntpdate -Bvd
The xntpd needs to be down to run ntpdate command.

Prashant.

[Santosh Nair_1]

Paul,

As Bill Hassell mentioned in another thread:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xb6388ffa98a2d5118ff10090279cd0f9,00.html

you have to keep in mind the impact of changing the time under some applications. For example, databases and DCE are two applications that are very sensative to big changes in time. If you have these running on your system, make sure to shut down the application before running ntpupdate.

-Santosh