HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Cannot create socket because port is busy
Operating System - HP-UX
1834930
Members
2655
Online
110071
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
Go to solution
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
11-10-2000 09:59 PM
11-10-2000 09:59 PM
Hi,
We are trying bind a socket in our appication
it gives a bind error saying that port is
busy.This is on HPUX-11.0
When we do netstat -n , we cannot get any
information regarding that particular port is being used.
Do anyone have any clue what the problem is ?
Thanks and Regards
Deepak
We are trying bind a socket in our appication
it gives a bind error saying that port is
busy.This is on HPUX-11.0
When we do netstat -n , we cannot get any
information regarding that particular port is being used.
Do anyone have any clue what the problem is ?
Thanks and Regards
Deepak
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2000 12:23 AM
11-11-2000 12:23 AM
Re: Cannot create socket because port is busy
try using netstat -an to see if the port already exists and is in a LISTEN state.
have you attempted to telnet to the port?
# telnet host port_number
also look for the port number in /etc/services and /etc/inetd.conf
have you attempted to telnet to the port?
# telnet host port_number
also look for the port number in /etc/services and /etc/inetd.conf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2000 04:16 PM
11-11-2000 04:16 PM
Solution
Hi:
While 'netstat -an' will show you the ports in use, you will need 'lsof' to determine what process is bound to the port.
A very interesting site on UNIX socket programming is:
http://www.lcg.org/sock-faq/
It is generally easier if you don't bind() a port number in your client program, but rather let the system choose one with the connect() call. A discussion of this appears here:
http://www.lcg.org/sock-faq/detail.php3?id=37
Look also specifically at these:
http://www.lcg.org/sock-faq/detail.php3?id=40
http://www.lcg.org/sock-faq/detail.php3?id=44
http://www.lcg.org/sock-faq/detail.php3?id=235
The last two links deal specifically with SO_RESUSEADDR. Setting this may eliminate your problem.
...JRF...
While 'netstat -an' will show you the ports in use, you will need 'lsof' to determine what process is bound to the port.
A very interesting site on UNIX socket programming is:
http://www.lcg.org/sock-faq/
It is generally easier if you don't bind() a port number in your client program, but rather let the system choose one with the connect() call. A discussion of this appears here:
http://www.lcg.org/sock-faq/detail.php3?id=37
Look also specifically at these:
http://www.lcg.org/sock-faq/detail.php3?id=40
http://www.lcg.org/sock-faq/detail.php3?id=44
http://www.lcg.org/sock-faq/detail.php3?id=235
The last two links deal specifically with SO_RESUSEADDR. Setting this may eliminate your problem.
...JRF...
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