NTPQ on VMS V8.3 Alpha gives error: getaddrinfo() failed - verify that the NTP service is defined

[Jan van den Boogaard_1]

see attached

the date of NTPTRACE is odd....

[Jan van den Boogaard_1]

Look like the subprocess runs :
DSA1:[VMS$COMMON.SYSEXE]TCPIP$NTP_RES_CHILD.EXE;2

[Volker Halle]

Jan,

so you've installed the recent TCPIP V5.6 ECO 5 security patch QXCR1000910870_V56_ECO5_ALPHA !

See this ITRC thread from last week:
http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1417205

You'll find your question about TCPIP$NTPTRACE answered in there as well.

Please consider to back out this patch for a moment and try to run the original NTP from V5.6 ECO 5 - if you have not yet tried that.

Volker.

[Volker Halle]

Jan,

try: $ ntpq -dddd
Opening host LOCALHOST

ntpq> Exit

Maybe you'll get better error messages this way.

You can also try - after stopping NTP:

$ ntpd -dddd

to see if this brings up any unusual error messages.

Volker.

[Jan van den Boogaard_1]

Volker,

there is some signal_no_reset message in the NTP logfile:

$ !
$ ! start ntp server process
$ !
$ run:
$ run SYS$SYSTEM:TCPIP$NTP.EXE
2 Apr 17:28:12 ntp[538972264]: ntpd version = 4.2.0
2 Apr 17:28:12 ntp[538972264]: precision = 976.500 usec
2 Apr 17:28:12 ntp[538972264]: no IPv6 interfaces found
2 Apr 17:28:12 ntp[538972264]: frequency initialized 0.000 PPM from sys$specific:[tcpip$ntp]tcpip$ntp.drift
2 Apr 17:28:14 ntp[538972265]: signal_no_reset: signal 14 had flags 2


Oke, the office closes down for the weeknd.
Lets hope the easter bunny solves the problem!
Thanks for yr help!

[Volker Halle]

Jan,

after upgrading to TCPIP V5.6 ECO 5 + recent TCPIP NTP security patches, I could NOT reproduce this problem on my PersonalAlpha, which had a working NTP config (under TCPIP V5.6 SSB) to start with.

So it's pretty sure, that this must be a local TCPIP configuration problem.

Happy Eastern,

Volker.

[Volker Halle]

Jan,

I gave the wrong troubleshooting info for NTP. Please consider to DEFINE/SYS TCPIP$NTP_LOG_LEVEL 6 and restart NTP to see if any recognizeable problem shows up in TCPIP$NTP_RUN.LOG

For NTPQ, use $ NTPQ -dddddd to try to get more information.

Volker.

[Jan van den Boogaard_1]

$ run SYS$SYSTEM:TCPIP$NTP.EXE
ntpd version = 4.2.0
7 Apr 16:36:28 ntp[538972264]: ntpd version = 4.2.0
adding new filegen
adding new filegen
adding new filegen
adding new filegen
adding new filegen
adding new filegen
7 Apr 16:36:28 ntp[538972264]: set_process_priority: Leave priority alone: priority_done is <2>
7 Apr 16:36:28 ntp[538972264]: precision = 976.500 usec
create_sockets(123)
7 Apr 16:36:28 ntp[538972264]: no IPv6 interfaces found
address_okay: listen Virtual: 1, IF name: IE0, Up Flag: 1
address_okay: listen Virtual: 1, IF name: IE0, Up Flag: 1
address_okay: listen Virtual: 1, IF name: LO0, Up Flag: 1
address_okay: listen Virtual: 1, IF name: WE1, Up Flag: 1
bind() fd 3, family 2, port 123, addr 0.0.0.0, flags=8
bind() fd 4, family 2, port 123, addr xyz.xyz.9.12, flags=8
bind() fd 5, family 2, port 123, addr xyz.xyz.9.206, flags=8
bind() fd 6, family 2, port 123, addr 127.0.0.1, flags=0
bind() fd 7, family 2, port 123, addr xyz.xyz.9.13, flags=8
create_sockets: ninterfaces=5
interface 0: fd=3, bfd=-1, name=wildcard, flags=0x8
sin=0.0.0.0 bcast=0.0.0.0, mask=255.255.255.255
interface 1: fd=4, bfd=-1, name=IE0, flags=0x9
sin=xyz.xyz.9.12 bcast=xyz.xyz.9.255, mask=255.255.255.0
interface 2: fd=5, bfd=-1, name=IE0, flags=0x9
sin=xyz.xyz.9.206 bcast=xyz.xyz.9.255, mask=255.255.255.0
interface 3: fd=6, bfd=-1, name=LO0, flags=0x5
sin=127.0.0.1 mask=255.0.0.0
interface 4: fd=7, bfd=-1, name=WE1, flags=0x9
sin=xyz.xyz.9.13 bcast=xyz.xyz.9.255, mask=255.255.255.0
init_io: maxactivefd 7
local_clock: at 0 state 0
7 Apr 16:36:28 ntp[538972264]: frequency initialized 0.000 PPM from sys$specific:[tcpip$ntp]tcpip$ntp.drift
local_clock: at 0 state 1
getaddrinfo xyz.xyz.155.249
getaddrinfo: "xyz.xyz.155.249" invalid host address.
resolving xyz.xyz.155.249
config: xyz.xyz.155.249 3 3 6 10 0 0 0 *
getaddrinfo xyz.xyz.155.250
getaddrinfo: "xyz.xyz.155.250" invalid host address.
resolving xyz.xyz.155.250
config: xyz.xyz.155.250 3 3 6 10 0 0 0 *
7 Apr 16:36:28 ntp[538972264]: Parent - Starting Host Name Resolver
7 Apr 16:36:28 ntp[538972264]: Parent - Continuing on to NTP daemon duties


so:
getaddrinfo: "xyz.xyz.155.249" invalid host address.

[Volker Halle]

Jan,

as I said, some local name/address problem...

Check the server or peer entries in your SYS$SPECIFIC:TCPIP$NTP.conf

This section of the TCPIP debug output looks like the following on my E8.4 test system:

...
7 Apr 16:47:50 ntp[187]: frequency initialized 11.367 PPM from SYS$SPECIFIC:[TC
PIP$NTP]TCPIP$NTP.DRIFT
local_clock: at 0 state 1
getaddrinfo axpvms
getnetnum given axpvms, got 10.20.30.203
key_expire: at 0
peer_clear: at 0 assoc ID 51708 refid INIT
newpeer: 10.20.30.207->10.20.30.203 mode 1 vers 4 poll 6 10 flags 0x1 0x1 ttl 0
key 00000000
getaddrinfo i64vms
getnetnum given i64vms, got 10.20.30.200
key_expire: at 0
peer_clear: at 0 assoc ID 51709 refid INIT
newpeer: 10.20.30.207->10.20.30.200 mode 1 vers 4 poll 6 10 flags 0x1 0x1 ttl 0
key 00000000
...

It looks like NTP is obtaining the addresses of the NTP servers or peers in this section, in my case:

peer axpvms
peer i64vms

Volker.

[Hoff]

This whole area has a poor UI for a system administrator; it's primitive and entirely unforgiving to any errors.

Please post your NTP configuration, and any associated DNS translations.

I'd ask that you not obfuscate IP addresses and host names and DNS translations here, but you're probably going to do that anyway so please do it consistently so that we can try to sort that out with the configuration and the log files.