- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: CLOSE_WAIT killing connections (that old chest...
Operating System - HP-UX
1753814
Members
7613
Online
108805
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
Discussions
Discussions
Forums
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
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
тАО05-10-2007 09:44 PM
тАО05-10-2007 09:44 PM
CLOSE_WAIT killing connections (that old chestnut)
Hi all,
I've had this problem many times and there seems to be conflicting info out there. I have two processes that wont die. I have used lsof and can see that the processes have a number of connections related to them which are in CLOSE_WAIT state. Is there actually anyway of removing them. I've seen previous quite old threads that suggest its possible but I think the solution was 11.00 and this is 11.11 as the commands do not work.
Is this possible I appreciate it may not be a good idea anyway and suggests poor coding.
Cheers
I've had this problem many times and there seems to be conflicting info out there. I have two processes that wont die. I have used lsof and can see that the processes have a number of connections related to them which are in CLOSE_WAIT state. Is there actually anyway of removing them. I've seen previous quite old threads that suggest its possible but I think the solution was 11.00 and this is 11.11 as the commands do not work.
Is this possible I appreciate it may not be a good idea anyway and suggests poor coding.
Cheers
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-10-2007 09:53 PM
тАО05-10-2007 09:53 PM
Re: CLOSE_WAIT killing connections (that old chestnut)
Adam,
for 11.11, did you see these threads:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=671167
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1111687
for 11.11, did you see these threads:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=671167
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1111687
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-10-2007 10:31 PM
тАО05-10-2007 10:31 PM
Re: CLOSE_WAIT killing connections (that old chestnut)
Shalom,
On systems not exposed to the Internet its almost always bad application code. ndd can be used to change the timeout from the default 60 seconds.
On internet exposed systems it could be a malicious attempt to keep a network connection open even if a firewall has cut the IP off. This should be monitored and if possible the process killed.
SEP
On systems not exposed to the Internet its almost always bad application code. ndd can be used to change the timeout from the default 60 seconds.
On internet exposed systems it could be a malicious attempt to keep a network connection open even if a firewall has cut the IP off. This should be monitored and if possible the process killed.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2007 04:53 AM
тАО05-14-2007 04:53 AM
Re: CLOSE_WAIT killing connections (that old chestnut)
What has been used to try to terminate the processes?
there is no rest for the wicked yet the virtuous have no pillows
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP