- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: No buffer space available
Operating System - HP-UX
1753797
Members
9118
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
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
тАО10-28-2009 12:03 AM
тАО10-28-2009 12:03 AM
Solution
CBZ,
This has nothing to do with filesystem buffer cache (dbc_max_pct and dbc_min_pct) - it is simply a message telling you that when inetd tried to open sockets for these applications using the accept() system call, it returned an error code indicating "no buffer space available". This actually means that there is insufficient kernel memory available to create bufferes for these socket connections. These errors are usually transient and if you don't have a problem now can probably be ignored (all well behaved applications should re-try when they get ENOBUFS returned from accept() ). I'm sure Rick Jones can do a better job of explaining that than I can...
The fact you see the same message for a bunch of different ports in what looks (to me) like ascending order suggests that someone may be running a port scanner against this system - are you aware of anyone attempting that (e.g. using nmap or nessus or some other security scanning tool?)
HTH
Duncan
I am an HPE Employee
This has nothing to do with filesystem buffer cache (dbc_max_pct and dbc_min_pct) - it is simply a message telling you that when inetd tried to open sockets for these applications using the accept() system call, it returned an error code indicating "no buffer space available". This actually means that there is insufficient kernel memory available to create bufferes for these socket connections. These errors are usually transient and if you don't have a problem now can probably be ignored (all well behaved applications should re-try when they get ENOBUFS returned from accept() ). I'm sure Rick Jones can do a better job of explaining that than I can...
The fact you see the same message for a bunch of different ports in what looks (to me) like ascending order suggests that someone may be running a port scanner against this system - are you aware of anyone attempting that (e.g. using nmap or nessus or some other security scanning tool?)
HTH
Duncan
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2009 12:31 AM
тАО10-28-2009 12:31 AM
Re: No buffer space available
Seems to be related to high memory utilization as well, what is the memory utilization.
You may have to change various TCP parameters if some changes have been done your system recently.
BR,
Kapil+
You may have to change various TCP parameters if some changes have been done your system recently.
BR,
Kapil+
I am in this small bowl, I wane see the real world......
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2009 05:44 AM
тАО10-28-2009 05:44 AM
Re: No buffer space available
Thanks to all Super SAs....you \m/Rocks\m/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2009 04:50 PM
тАО10-28-2009 04:50 PM
Re: No buffer space available
What Duncan has said can be correct (BTW, while I see many Forum's postings, I don't see them all, and only chanced across this one) I'll repeat what was in the referenced entry from five years ago :)
99 times out of 10, a "No buffer space available" (aka ENOBUFS) on an accept() call means that by the time the server (again in this case inetd) got around to calling accept() on the listen endpoint, the remote end of the connection had given-up and gone away.
It means that your server was not keeping-up with the connection establishement rate.
Now, getting to the present, that they have appeared for all those services suggests that someone may have been bombarding your system with bogus connection requests - hardly anyone but crusty old network performance types :) connect to the chargen (character generator - spits-out a steady stream of bytes on the connection) or discard (bit buckets anything it is sent) services.
If your system is "external facing" on a (semi) public network you may want to look into disabling many of those services and doing other "hardening" things.
You can go into /etc/inetd.conf and disable chargen, discard and daytime straight away. You can *probably* disable ident. Some of the others will depend on whether or not you actually use those services on that server.
99 times out of 10, a "No buffer space available" (aka ENOBUFS) on an accept() call means that by the time the server (again in this case inetd) got around to calling accept() on the listen endpoint, the remote end of the connection had given-up and gone away.
It means that your server was not keeping-up with the connection establishement rate.
Now, getting to the present, that they have appeared for all those services suggests that someone may have been bombarding your system with bogus connection requests - hardly anyone but crusty old network performance types :) connect to the chargen (character generator - spits-out a steady stream of bytes on the connection) or discard (bit buckets anything it is sent) services.
If your system is "external facing" on a (semi) public network you may want to look into disabling many of those services and doing other "hardening" things.
You can go into /etc/inetd.conf and disable chargen, discard and daytime straight away. You can *probably* disable ident. Some of the others will depend on whether or not you actually use those services on that server.
there is no rest for the wicked yet the virtuous have no pillows
- « Previous
-
- 1
- 2
- Next »
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