Squid: "Socket error... (55) no buffer space available
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Squid: "Socket error... (55) no buffer space available
Squid on the firewall machine sends the above error message when I want to get a webpage.
Netstat on the firewall showed me that there are hundreds of connections in TIME_WAIT state from port 3128 of the firewall machine to different ports of an other internal server of ours named "castor".
Netstat on "castor" does not show these connections. How is it possible?
I restarted our firewall machine (where squid is located), but the connections in TIME_WAIT state were there in some minutes, again.
What can I do to get rid of those unclosed connections?
Edit:
OK, problem solved: it was a download accelerator on a client behind "castor" that opened so many connections that they filled squid's buffer space.
The great experience was that such events are hardly traceable in our network topology: nat on castor hides (masquerades) the ip of the traitor, whilst netstat on castor does not seem to show connections forwarded by nat there. (So I had to run tcpdump on oif of castor to find the culprit).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.