- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- TCPIP$NTP failing to bind socket
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-10-2014 08:45 AM
01-10-2014 08:45 AM
TCPIP$NTP failing to bind socket
Folks,
VMS IA64 8.4, TCPIP 5.7 ECO2
Trying to set up a simple NTP client to talk to an external timeserver.
I've added 'server x.x.x.x' to TCPIP$NTP.CONF to query said timeserver.
tcpip$ntp_run.log is showing this:
10 Jan 15:23:22 ntp[1853269]: bind() fd 3, family 2, port 123, addr 0.0.0.0, in_
classd=0 flags=8 fails: permission denied
10 Jan 15:23:22 ntp[1853269]: bind() fd 3, family 2, port 123, addr 10.197.113.1
32, in_classd=0 flags=8 fails: permission denied
10 Jan 15:23:22 ntp[1853269]: bind() fd 3, family 2, port 123, addr 127.0.0.1, i
n_classd=0 flags=0 fails: permission denied
followed by:
10 Jan 15:23:26 ntp[1853269]: adj_systime: not owner
every second.
Other services are fine and obviously IP itself it working. Anyone seen this before? All SYSTEM or TCPIP account based.
Cheers
Adrian
- Tags:
- NTP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2014 07:26 PM
01-11-2014 07:26 PM
Re: TCPIP$NTP failing to bind socket
Hello,
I also use ntp as client and works fine.
Have you restarted ntp service.
$ @sys$manager:TCPIP$NTP_SHUTDOWN
$ @sys$manager:TCPIP$NTP_STARTUP
I use this in my configureation file of ntp.
# Client Mode
#
# Client mode indicates that the local host wants to obtain time from
# the remote server but it is not willing to provide time to the
# remote server. Indicate client mode with the server statement.
# Identify each server with a fully-qualified DNS host name or with an
# IP address in dotted-decimal notation.
server 10.240.5.1
server 10.243.0.1
also try this.
$ sho sym ntpdc
NTPDC == "$SYS$SYSTEM:TCPIP$NTPDC"
$ ntpdc
ntpdc> peer
remote local st poll reach delay offset disp
=======================================================================
=hkgrt001.hkg.vo 10.240.5.33 16 1024 0 0.00000 0.000000 0.00000
*chers001vl108sb 10.240.5.33 4 1024 377 0.00098 0.000120 0.01581
ntpdc> sysinfo
system peer: chers001vl108sb.che.bestcarcompany.net
system peer mode: client
leap indicator: 00
stratum: 5
precision: -10
root distance: 0.25122 s
root dispersion: 0.08299 s
reference ID: [10.240.5.1]
reference time: d67c8418.2f4095ad Sun, Jan 12 2014 11:01:44.184
system flags: auth monitor ntp kernel stats
jitter: 0.000977 s
stability: 0.023 ppm
broadcastdelay: 0.003998 s
authdelay: 0.000000 s
ntpdc>
/Toine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2014 07:06 AM
01-13-2014 07:06 AM
Re: TCPIP$NTP failing to bind socket
Hi Toine,
As is quite often the case with things like this they had to reboot the blade over the weekend and all is well!
Cheers
Adrian