- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- buffer overflow in access log
Operating System - HP-UX
1752634
Members
6063
Online
108788
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
тАО07-05-2001 06:56 AM
тАО07-05-2001 06:56 AM
buffer overflow in access log
We've been running apache with no problem but recently we've been getting the following message occasionally:
[error] (233)No buffer space available: accept: (client socket)
Can anyone tell me exactly what the problem is (and maybe how to fix it?)
Thanks.
[error] (233)No buffer space available: accept: (client socket)
Can anyone tell me exactly what the problem is (and maybe how to fix it?)
Thanks.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2001 07:05 AM
тАО07-05-2001 07:05 AM
Re: buffer overflow in access log
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2001 07:58 AM
тАО07-05-2001 07:58 AM
Re: buffer overflow in access log
Hi Francoise
Essentially form the previous link .
HP ERROR 233 .
When a new connect request arricves at the local tcp and it is immediately followed by a RESET from the remote system , the server application is awakened twice by the request to perform ( accept ( ) calls ) . Each is returned bu ENOBUFS or HP Error 233. The problem is the acceptin server application should not be awakened twice . This was caused by mishandling the connection id in the TPI messages . The problem is fixed by correctly tracking the connection id between the socket and TCP layers.
There is a PATCH also which HP recommends loading PHNE_23456 to resolve this problem
Manoj Srivastava
Essentially form the previous link .
HP ERROR 233 .
When a new connect request arricves at the local tcp and it is immediately followed by a RESET from the remote system , the server application is awakened twice by the request to perform ( accept ( ) calls ) . Each is returned bu ENOBUFS or HP Error 233. The problem is the acceptin server application should not be awakened twice . This was caused by mishandling the connection id in the TPI messages . The problem is fixed by correctly tracking the connection id between the socket and TCP layers.
There is a PATCH also which HP recommends loading PHNE_23456 to resolve this problem
Manoj Srivastava
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