ntpdate -B succeeds, xntp start fails

[Drew Roberts]

I'm trying to synch time from an HP-UX 11.11 NTP client to a Windows Server 2003 NTP server.

/etc/ntp.conf contains one line:
server 10.231.0.140 version 3 prefer

If I issue ntpdate command it works great:

>ntpdate -B 10.231.0.140
21 Feb 14:09:58 ntpdate[12599]: adjust time server 10.231.0.140 offset -0.002015 sec

When I try to start xntpd it fails:
>/sbin/init.d/xntpd start
21 Feb 14:11:43 ntpdate[12754]: no server suitable for synchronization found

What gives?

[Ivan Krastev]

Wait some time - about 15-20 minutes. See this docs for ntp troubleshooting - http://docs.hp.com/en/B2355-90685/ch07s03.html

regards,
ivan

[Drew Roberts]

I've been through that doc and it didn't find any resolution. The error message I'm seeing is in there but it suggests that the server specified is down or unavailable due to network congestion, et al.

This doesn't apply here as the ntpdate request goes through just fine.

What is the reasoning behind waiting 15 minutes? I've been at this for a couple hours now and the Windows NTP server has been up throughout.

[DavidJ]

Andy, try starting it in debug mode (-d -l logfilename) and see what goes into the log, else start it up with SAM > time > NTP Network Time Sources > tab action start ntp service. You should see the ip address of your ntp server in the NTPNetwork time sources window.

My config line reads :
server 999.888.777.1 key 2000 minpoll 6 prefer

Good luck

David

[DavidJ · Accepted solution]

Andy,
this is a "P.S" to the previous reply.

You also ahve to add the following lines to /etc/rc.config.d/netdaemons

export NTPDATE_SERVER=hostname.blabla.bla.com
XNTPD=1
export XNTPD_ARGS=

Waiting a few minutes as earlier advised by Ivan is because it could take a few minutes for xntpd daemon to stabalise.

Verify the NTP server config by typing ntpq -p

David

[Drew Roberts]

David, you nailed it.

I must have checked my /etc/rc.config.d/netdaemons file 5 times yesterday and it looked just great at the time. This morning, I realized that the IP address for the time server was entered incorrectly.

Fixed that and now xntpd is working like a champ.

[Drew Roberts]

Thanks for the help guys.

[rick jones]

FWIW, the gurus over in the NTP netnews group espouse having at least three time sources configured...