ntpdate ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument

wademj · Post by **wademj** » Sat Sep 16, 2023 7:45 pm

ntpdate gives the following on X86 OpenVMS V9.2-1 Any ideas; works on my AlphaServer running VSI OpenVMS V8.4-2L1

$ @sys$startup:tcpip$ntp_shutdown

Code: Select all

%TCPIP-I-INFO, service disabled
%TCPIP-I-INFO, process TCPIP$NTP_1 (pid=0000049E) stopped
%TCPIP-I-INFO, logical names deleted
%TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$NTP.EXE deinstalled
%TCPIP-S-SHUTDONE, TCPIP$NTP shutdown completed
$ [b]ntpdate au.pool.ntp.org[/b]
Looking for host au.pool.ntp.org
ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument
ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument
ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument
ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument
 Interrupt

$ tcpip show vers

Code: Select all

 VSI TCP/IP Services for OpenVMS x86_64 Version 66.0
  on an innotek GmbH VirtualBox running OpenVMS V9.2-1

Have tried direct IP addresses and various switches with no luck. Network issues at my end perhaps although, with ntp client started, ntpq is working fine.

$ ntpq -p

Code: Select all

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 LOCAL(0)        .LOCL.           8 l    4   64    1    0.000   +0.000   7.812
 smtp.juneks.com .PPS.            1 u    4   64    1    9.930   +3.546   7.812

m_detommaso · Post by **m_detommaso** » Sun Sep 17, 2023 3:50 am

VSI TCP/IP Services Version X6.0 Release Notes

Document Number: DO-TCPRNT-01A
Publication Date: July 2023
Paragraph 6 "Know issuese"
Section 6.2 "NTPDATE is no longer supported"

https://vmssoftware.com/docs/VSI_TCPIP_ ... 22A_RN.pdf

NTPDATE is no longer supported and will be removed from an upcoming release of VSI TCP/IPServices. To perform the equivalent of NTPDATE, run NTPD making use of the -q and "-G" options.

6.2. NTPDATE No Longer Supported
NTPDATE is no longer supported and will be removed from an upcoming release of VSI TCP/IP
Services. To perform the equivalent of NTPDATE, run NTPD making use of the -q and "-G"
options.
$ ntpd :== $tcpip$ntp
$ ntpd "-G" -q
ntp.exe[538969120]: ntpd 4.2.8p15@1.3728 Fri Sep 22 07:00:58 UTC 2020 (2):
Starting
ntp.exe[538969120]: Command line: tbd$dka200:[sys0.syscommon.][sysexe]tcpip
$ntp.exe -G -q -4
ntp.exe[538969120]: ----------------------------------------------------
ntp.exe[538969120]: ntp-4 is maintained by Network Time Foundation,
ntp.exe[538969120]: Inc. (NTF), a non-profit 501(c)(3) public-benefit
ntp.exe[538969120]: corporation. Support and training for ntp-4 are
ntp.exe[538969120]: available at https://www.nwtime.org/support
ntp.exe[538969120]: ----------------------------------------------------
ntp.exe[538969120]: proto: precision = 1000.000 usec (-10)
ntp.exe[538969120]: proto: fuzz beneath 0.710 usec
ntp.exe[538969120]: basedate set to 2022-05-21
ntp.exe[538969120]: gps base set to 2022-05-22 (week 2211)
ntp.exe[538969120]: Listen and drop on 0 v4wildcard 0.0.0.0:123
ntp.exe[538969120]: Listen normally on 1 LO0 127.0.0.1:123
ntp.exe[538969120]: Listen normally on 2 WE0 10.10.116.182:123
ntp.exe[538969120]: Listening on routing socket on fd #4 for interface
updates
ntp.exe[538969120]: ntpd: time set -50.590756 s
ntpd: time set -50.590756s
$

/Maurizio

babydr · Post by **babydr** » Sun Sep 17, 2023 7:52 pm

@The present programming staff (& managers there of) that maintain the NTPD packages .

To date ntpdate has NOT been removed from the public domain ntp sources .

Why this "NTPDATE No Longer Supported" ?

The present source code from the original author of the NTP protocol has NOT removed the ntpdate sources from his own maintained listings . He even said . the same as you . Tho it is still there .

Please forgive my vehemence , Tho imo it is appropriate , in at lesat this case .

JimL

martinv · Post by **martinv** » Mon Sep 18, 2023 1:15 am

See Deprecating ntpdate from 2014, and Deprecate ntpdate usage, replace with ntpd in NTP Monitor from 2022 with the issue "closed as completed".

babydr · Post by **babydr** » Tue Sep 19, 2023 5:20 pm

@Martinv , Hmmm , Interesting ...

https://archive.ntp.org/ntp4/ntp-4.2/nt ... p17.tar.gz

Code: Select all

# tar -tvf /home/archive/srcs/ntp-4_2_8p17.tgz | grep -i ntpdate
drwxr-xr-x ntpreleng/ntpreleng       0 2023-06-06 03:40 ntp-4.2.8p17/ntpdate/
-rw-rw-r-- ntpreleng/ntpreleng    1003 2023-05-31 02:31 ntp-4.2.8p17/ntpdate/Makefile.am
-rw-rw-r-- ntpreleng/ntpreleng    4236 2011-02-21 21:06 ntp-4.2.8p17/ntpdate/ntpdate.h
-rw-rw-r-- ntpreleng/ntpreleng   35459 2023-06-06 03:36 ntp-4.2.8p17/ntpdate/Makefile.in
-rw-rw-r-- ntpreleng/ntpreleng     324 2001-10-08 17:18 ntp-4.2.8p17/ntpdate/README
-rw-rw-r-- ntpreleng/ntpreleng   51566 2020-06-23 01:17 ntp-4.2.8p17/ntpdate/ntpdate.c
drwxrwsr-x ntpreleng/ntpreleng       0 2023-05-31 02:31 ntp-4.2.8p17/ports/winnt/vs2015/ntpdate/
-rw-rw-r-- ntpreleng/ntpreleng    6619 2023-05-31 02:31 ntp-4.2.8p17/ports/winnt/vs2015/ntpdate/ntpdate.vcxproj
-rw-rw-r-- ntpreleng/ntpreleng    2652 2023-05-31 02:31 ntp-4.2.8p17/ports/winnt/vs2015/ntpdate/ntpdate.vcxproj.filters
drwxrwsr-x ntpreleng/ntpreleng       0 2023-05-31 02:31 ntp-4.2.8p17/ports/winnt/vs2013/ntpdate/
-rw-rw-r-- ntpreleng/ntpreleng    2652 2023-05-31 02:31 ntp-4.2.8p17/ports/winnt/vs2013/ntpdate/ntpdate.vcxproj.filters
-rw-rw-r-- ntpreleng/ntpreleng   13958 2023-05-31 02:31 ntp-4.2.8p17/ports/winnt/vs2013/ntpdate/ntpdate.vcxproj
drwxrwsr-x ntpreleng/ntpreleng       0 2017-01-31 22:19 ntp-4.2.8p17/ports/winnt/vs2008/ntpdate/
-rw-rw-r-- ntpreleng/ntpreleng    8305 2015-04-19 02:38 ntp-4.2.8p17/ports/winnt/vs2008/ntpdate/ntpdate.vcproj
-rw-rw-r-- ntpreleng/ntpreleng    7069 2023-05-31 02:31 ntp-4.2.8p17/ports/winnt/vs2005/ntpdate.vcproj
-rw-rw-r-- ntpreleng/ntpreleng    8495 2018-08-14 03:51 ntp-4.2.8p17/html/ntpdate.html

cct · Post by **cct** » Tue Sep 19, 2023 6:57 pm

@Babydr

and the point is?

Chris

babydr · Post by **babydr** » Tue Sep 19, 2023 7:33 pm

@All , While it may be on its way to disuse , It is not disabled nor has the maintainer removed it as a TOOL .
It seems that the "suitable period of mourning" has not been reached as of this date .

While ntpdc (of the same vintage) is still a valid tool for doing some of the function(s) of ntpdate , it (iirc) requires a running ntpd to process data for .

I have found that the "ntpd -q" has had some interesting frailty and left the daemon to exit . I don't have the particulars any longer and the frailty may have been addressed since then .

I absolutely detest the abandonment of a valid tool , When only one of its functions has a difficulty .

My previous response was to show that the code for ntpdate was still part of the reference implementation of ntp , thus a valid tool until it's removal from the reference sources .

Nuf , Said , JimL

wademj · Post by **wademj** » Sat Sep 23, 2023 4:25 am

Thank you all. Suitable use of the TCPIP$NTP command with (in my case) -g "-G" -q in a SYS$STARTUP:TCPIP$SYSTARTUP.COM file has resolved the issue.

Have to stop and then restart NTP client afterwards too but all good. Multiple ways to do all that of course but it's all for home so simple is best.

Thanks,
Malcolm

VSI OpenVMS Forum

ntpdate ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument

ntpdate ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument

Re: ntpdate ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument

Re: ntpdate ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument

Re: ntpdate ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument

Re: ntpdate ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument

Re: ntpdate ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument

Re: ntpdate ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument

Re: ntpdate ntpdate.exe;1[1179]: select(): nfound = 0, error: invalid argument