- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Socket not available after a process crash
Operating System - HP-UX
1825161
Members
2324
Online
109679
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
07-06-2007 12:21 AM
07-06-2007 12:21 AM
Socket not available after a process crash
Hi folks,
my process uses a socket; it crashed for some damned reasons; after the restart it cannot connect anymore to the socket since it's already in use (errno 226, address already in use) and actually I see:
ps -ef | grep ...
tcp 0 0 my_process
even if my_process isn't running!!
It seems that the socket isn't free after the process crash.
What should I do to make it free?
Thanks
Enrico
my process uses a socket; it crashed for some damned reasons; after the restart it cannot connect anymore to the socket since it's already in use (errno 226, address already in use) and actually I see:
ps -ef | grep ...
tcp 0 0 my_process
even if my_process isn't running!!
It seems that the socket isn't free after the process crash.
What should I do to make it free?
Thanks
Enrico
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2007 01:07 AM
07-06-2007 01:07 AM
Re: Socket not available after a process crash
See examples how to close socket - http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=528809
regards,
ivan
regards,
ivan
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
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP