HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- vmunix allert
Operating System - HP-UX
1829576
Members
2785
Online
109992
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
10-04-2006 01:37 PM
10-04-2006 01:37 PM
vmunix allert
we are facing following vmunix allert in HP-UX
11.11 ,
bindresvport:loop_twice port assigned 512
bindresvport:loop_twice port assigned 512
please someone can let me know what is the cause,
11.11 ,
bindresvport:loop_twice port assigned 512
bindresvport:loop_twice port assigned 512
please someone can let me know what is the cause,
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2006 02:52 PM
10-04-2006 02:52 PM
Re: vmunix allert
The message referenced above is printed by kernel routines
bindresvport(), and
tcp_bindresvport()
when a binding to port 512 fails. Currently, three subsystems use these functions when creating a client handle, ie. nfs, autofs, and kernel lock mgr.
In general, the message may indicate that ports 512-1023 are in use. However, there are cases where, on non-busy systems, the reserved ports are still available while this message is printed. Possible reasons are:
a. Port 512 is bound to a tcp/udp of a client handle stored in nfs ch cache, or klm ch cache. If all entries are in use, then a new client handle will be created (but not cached); this raises the possibility of "d" below.
b. Port 512 is in use by autofs.
c. Port 512 is in use by a user application.
d. Multiple threads attempt to bind to port 512 at about same time.
If the system is slowed down, threads cannot proceed with their work. While the message is printed rapidly, this may indicate a real problem which will require a closer look to understand what is happening.
bindresvport(), and
tcp_bindresvport()
when a binding to port 512 fails. Currently, three subsystems use these functions when creating a client handle, ie. nfs, autofs, and kernel lock mgr.
In general, the message may indicate that ports 512-1023 are in use. However, there are cases where, on non-busy systems, the reserved ports are still available while this message is printed. Possible reasons are:
a. Port 512 is bound to a tcp/udp of a client handle stored in nfs ch cache, or klm ch cache. If all entries are in use, then a new client handle will be created (but not cached); this raises the possibility of "d" below.
b. Port 512 is in use by autofs.
c. Port 512 is in use by a user application.
d. Multiple threads attempt to bind to port 512 at about same time.
If the system is slowed down, threads cannot proceed with their work. While the message is printed rapidly, this may indicate a real problem which will require a closer look to understand what is happening.
Time has a wonderful way of weeding out the trivial
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2006 03:19 PM
10-04-2006 03:19 PM
Re: vmunix allert
Hi
use sh lsof -i:512 to check which process use the port 512
use sh lsof -i:512 to check which process use the port 512
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2006 05:48 PM
10-04-2006 05:48 PM
Re: vmunix allert
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