xntpd problem

[Ben Salamon]

After configuring xntpd in /etc/ntp.conf and /etc/rc.config.d/netdeamons I start using /sbin/init.d/xntpd start. However xntpd daemon doesn't start and I get the following in syslog.log

xntpd version 3.5f: Sat Apr 14 15:04:53 IST 2001 PHNE_23697
tickadj = 625, tick = 10000, tvu_maxslew = 61875
precision = 6 usec
get interface configuration: Invalid argument

I have an almost identical box which runs xntpd fine with the same config. OS HP-UX 11.00

[RAC_1]

What time source you are pointing to? (/etc/ntp.conf file) Is your time source reachable?

[Ben Salamon]

Yes,

driftfile /etc/ntp.drift
server lntime1
server lntime2
# ping lntime1
PING lns00i-2701: 64 byte packets
64 bytes from 166.12.216.55: icmp_seq=0. time=0. ms
64 bytes from 166.12.216.55: icmp_seq=1. time=0. ms

[Dwyane Everts_1]

Ben,

What does "ntpq -p" reflect?

D

[RAC_1]

Is port 123 open on both nodes?

What is output of
ntpq -p "client_name"

does it point to your time source?

[Ben Salamon]

# ntpq -p
ntpq: read: Can't assign requested address

[RAC_1]

What are permissions on /etc/hosts and ownership? What is output of uname -n and hostname?

Is /etc/hosts set correctly?

What is the out put of ntpw -p "server_you_are_pointing_to"

[Fabio Ettore]

Hi Ben,

just a thought: I see that you configured NTP for redundancy because there are two NTP servers in /etc/ntp.conf of NTP client. Then I suggest you to try one before to add another one. Then restart xntpd.
If it works then try to add the second server.

I hope this helps you.
Ettore

[RAC_1]

Also try one at a time.Change as follows.
server xxxx
peer yyyy

[Ben Salamon]

Still doesn't work. I guess its something to do with the "get interface configuration: Invalid argument" message in syslog.log. Does anyone know what that means as I have double checked netconf and that all looks fine.

[RAC_1]

How many cards you have in this box? Are all those claimed in ioscan? Have all cards configured? Are the all LAN drive config files configured properly?-- /etc/rc.config.d/*lan*

[Ben Salamon]

I've resolved the issue but thanks for all the replies. It was something quite simple in the end. I checked netstat -in and realised there was a couple of unused virtual interfaces plumbed in on lan0 (lan0:1 & lan0:2). I unplumbed the lan0 interfaces and now it starts fine.