topic Re: NTP issue in Operating System - HP-UX

NTP issue

James_Lau — Thu, 11 Jun 2009 02:58:41 GMT

Hi all , can any one help me on the HP unix 11.31 NTP issue , i have config is as told , when i run :
# ntpdate IP_sysclock
11 Jun 11:55:03 ntpdate[9566]: no server suitable for synchronization found

and run :
# /sbin/init.d/xntpd start IP_sysclock
11 Jun 11:56:00 ntpdate[9584]: no server suitable for synchronization found

please help , thanks.

Re: NTP issue

Suraj K Sankari — Thu, 11 Jun 2009 03:10:00 GMT

Hi,

Is this a client or a server ?

What is the output of "xntpd start" and "ntpq -p"

Suraj

Re: NTP issue

George_Dodds — Thu, 11 Jun 2009 03:39:14 GMT

What is the output of

cat /etc/ntp.conf

Re: NTP issue

James_Lau — Thu, 11 Jun 2009 04:11:58 GMT

is client setup , here is the outputfor ntp.conf , i only turn on :

server IP_ntpclock

and

#enable auth monitor # enable the good stuff
driftfile /etc/ntp.drift # path for drift file

Re: NTP issue

James_Lau — Thu, 11 Jun 2009 04:24:21 GMT

and when i run ntpdate is show:

# ntpdate IP_clock
11 Jun 13:25:04 ntpdate[10690]: the NTP socket is in use, exiting

Re: NTP issue

Md. Minhaz Khan — Thu, 11 Jun 2009 04:39:01 GMT

Dear James

>># ntpdate IP_sysclock
11 Jun 11:55:03 ntpdate[9566]: no server suitable for synchronization found
cause 1:
This message indicates that the NTP server is not responding for some reason. Packets were sent out, but no reply was returned. Perhaps the server is down, or the network link is broken or extremely congested. Or perhaps the NTP daemon died on the server and has not yet locked on to its time sources

cause 2:I think you run the above command from NTP client system.

For NTP SERVER machine, after you start /sbin/init.d/xntpd start , you have to wait 5-15 minutes because NTP version 3.5 and above take between 5 and 15 minutes after starting up the daemon to synchronize, and it will not respond to client requests during this time.

After 5-15 minutes, run the following commands:

#ntpdate -d -b IP_ADDR_NTP_SERVER

Thanks

Minhaz

Re: NTP issue

Suraj K Sankari — Thu, 11 Jun 2009 04:46:10 GMT

Hi,

Did you check you syslog.log file?
Cross check once that xntpd demon is running with "ps -aef| grep xntpd"

Suraj

Re: NTP issue

Md. Minhaz Khan — Thu, 11 Jun 2009 04:51:43 GMT

ntpdate will fail if xntpd is already running on the local system

So check

#ps -ef|grep ntp

if running dtop ntp :

#/sbin/init.d/xntpd stop
#ntpdate -d -b IP_sysclock

Thanks
Minhaz

Re: NTP issue

James_Lau — Thu, 11 Jun 2009 04:59:23 GMT

hi all , when i start it show:
# /sbin/init.d/xntpd start
11 Jun 13:56:01 ntpdate[11139]: no server suitable for synchronization found

and

# ntpdate IP_clock
11 Jun 14:00:12 ntpdate[11199]: the NTP socket is in use, exiting

and it show :

# ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
IP_clock 0.0.0.0 16 u 49 64 0 0.00 0.000 16000.0

Re: NTP issue

James_Lau — Thu, 11 Jun 2009 05:01:37 GMT

# ntpdate -d -b IP_clock
transmit(IP_clock)
receive(IP_clock)
transmit(IP_clock)
receive(IP_clock)
transmit(IP_clock)
receive(IP_clock)
transmit(IP_clock)
receive(IP_clock)
transmit(IP_clock)
server IP_clock, port 123
stratum 4, precision -20, leap 00, trust 000
refid [192.168.209.38], delay 0.02600, dispersion 0.00011
transmitted 4, in filter 4
reference time: cdd0afa8.f4d610a7 Wed, Jun 3 2009 16:15:36.956
originate timestamp: cddb1bfd.1259e34a Thu, Jun 11 2009 14:00:29.071
transmit timestamp: cddb1c60.fbbef000 Thu, Jun 11 2009 14:02:08.983
filter delay: 0.02794 0.02605 0.02602 0.02600
0.00000 0.00000 0.00000 0.00000
filter offset: -99.9109 -99.9119 -99.9119 -99.9119
0.000000 0.000000 0.000000 0.000000
delay 0.02600, dispersion 0.00011
offset -99.911906

11 Jun 14:02:08 ntpdate[11225]: no server suitable for synchronization found

Re: NTP issue

Sajjad Sahir — Thu, 11 Jun 2009 05:12:00 GMT

Dear James

This message indicates that the NTP server is not responding for some reason. Packets were sent out, but no reply was returned. Perhaps the server is down, or the network link is broken or extremely congested. Or perhaps the NTP daemon died on the server and has not yet locked on to its time sources. NTP version 3.5 and above take between 5 and 15 minutes after starting up the daemon to synchronize, and it will not respond to client requests during this time.

thanks and regards

Sajjad Sahir

Re: NTP issue

Suraj K Sankari — Thu, 11 Jun 2009 05:19:44 GMT

Hi,

Is your NTP server connected to other clients if yes then loggin into any clients and give ntpq -p see the status.

From client and server both end check this are you able to ping.

Suraj

Re: NTP issue

James_Lau — Thu, 11 Jun 2009 05:20:03 GMT

ok , i will check it out.

Re: NTP issue

James_Lau — Mon, 15 Jun 2009 01:20:41 GMT

Hi all , the NTP issue has resolve , btw , i have one more question , how to set more than one NTP server to be sync and how to set which one is prefer to be syncs , thanks.

Regards
James Lau

Re: NTP issue

Sajjad Sahir — Mon, 15 Jun 2009 08:54:33 GMT

Dear james

Please see the link

http://docs.hp.com/en/B2355-90774/ch04s01.html

thanks and regards

Sajjad Sahir