GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- request socket connection not authorized: 15
Operating System - HP-UX
1843758
Members
2977
Online
110223
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
12-13-2002 07:14 AM
12-13-2002 07:14 AM
request socket connection not authorized: 15
Hello colleagues,
what can be the reasons of the error shown in the title?
the available sockets are exausted?
thanks
Enrico
what can be the reasons of the error shown in the title?
the available sockets are exausted?
thanks
Enrico
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2002 07:31 AM
12-13-2002 07:31 AM
Re: request socket connection not authorized: 15
Hi Enrico,
can you explain the context which give you this error ?
Regards,
Jerome
can you explain the context which give you this error ?
Regards,
Jerome
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2002 08:02 AM
12-13-2002 08:02 AM
Re: request socket connection not authorized: 15
Ok, in my platform there's HP OpenView NNM; I run a lot of processes so that about 750 sockets are engaged; at a certain moment the ovspmd (daemon of OV DM platform) stops accepting any more requests: the error is
ovstatus: No response from ovspmd. Check ovspmd.authfile on server xxxx.
By taking a look on nettl trace file I see the mentioned error.
It seems that the ovspmd doesn't accept anymore incoming requests. As soon as ai stop some process (and it frees its sockets) the ovspmd restarts accepting requests.
ovstatus: No response from ovspmd. Check ovspmd.authfile on server xxxx.
By taking a look on nettl trace file I see the mentioned error.
It seems that the ovspmd doesn't accept anymore incoming requests. As soon as ai stop some process (and it frees its sockets) the ovspmd restarts accepting requests.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2002 09:53 AM
12-14-2002 09:53 AM
Re: request socket connection not authorized: 15
(a) See http://openview.hp.com/sso/ecare/getsupportdoc?docid=S3100005790
In this particular case 'ovspmd.auth' has a short name and when the
fully qualified name is looked up it returns with the short name only.
A suggested resolution to this problem is to change 'nsswitch.conf' to
look at files first. Make sure the lookup works for ip, long name, and
short name. Then, kill the 'ovspmd' -newconfig process that is running
and run ovstart again.
(b) If the system is a multi-homed system then enables the NNM internal
process communication over loopback.
Here are the steps:
- ov.conf uncomment and enable
USE_LOOPBACK=ON
NNM_INTERFACE=10.10.10.10
IGNORE_NNM_IF_FOR_SNMP=ON
- ovspmd.auth uncomment
loopback +
localhost +
loghost +
- /etc/hosts, add the loopback entry:
127.0.0.1 localhost loghost loopback
- remove $OV_DB/openview/ovwdb/ovserver
- remove $OV_SOCKETS/OVsPMD_MGMT
Then run:
ovstart -d
Hope this helps.
In this particular case 'ovspmd.auth' has a short name and when the
fully qualified name is looked up it returns with the short name only.
A suggested resolution to this problem is to change 'nsswitch.conf' to
look at files first. Make sure the lookup works for ip, long name, and
short name. Then, kill the 'ovspmd' -newconfig process that is running
and run ovstart again.
(b) If the system is a multi-homed system then enables the NNM internal
process communication over loopback.
Here are the steps:
- ov.conf uncomment and enable
USE_LOOPBACK=ON
NNM_INTERFACE=10.10.10.10
IGNORE_NNM_IF_FOR_SNMP=ON
- ovspmd.auth uncomment
loopback +
localhost +
loghost +
- /etc/hosts, add the loopback entry:
127.0.0.1 localhost loghost loopback
- remove $OV_DB/openview/ovwdb/ovserver
- remove $OV_SOCKETS/OVsPMD_MGMT
Then run:
ovstart -d
Hope this helps.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP