Reese Knowledgebase

No buffer space available

View Kristian Reese's profile on LinkedIn


If you like this article, please +1 or Recommend via FB with the provided buttons above:

Article ID: 124
by: Reese K.
Posted: 04 Sep, 2013
Last updated: 04 Sep, 2013
Views: 3448

[warn] (105)No buffer space available: connect to listener on 0.0.0.0:80

Symptoms:

/var/log/http/error_log contains the following message:

[warn] (105)No buffer space available: connect to listener on 0.0.0.0:80

In virtuozzo / openvz, TCP buffer space is controlled by two parameters: tcpsndbuf and tcprcvbuf

Check the user_beancounters to see if the buffer space is being exceeded via the following command:

-bash-3.2# watch -n 1 cat /proc/user_beancounters

It will provide realtime output like this (I've truncated the output)

Every 1.0s: cat /proc/user_beancounters                                                                                             Wed Sep  4 12:51:27 2013

Version: 2.5
       uid  resource           held         maxheld       barrier     limit            failcnt
    15470:  kmemsize       14234630        15913854      36858240     42598400               0
            tcpsndbuf        692352         1100064       5365760     10485760     86735869724
            tcprcvbuf        376832          475136       5365760     10485760               0
           

I've highlighted the problem configuration in red.  The held column shows the current utilized buffer space, and it's clear it's exceeding the barrier, resulting in increased failcnt.

Resolution

Increase the tcpsndbuf on the hwnode.  If you don't have access to the hwnode, contact your provider:

[root@vps09 ~]# vzctl set 15470 --tcpsndbuf 10485760:15728640 --save

apache is mostly sending data as opposed to receiving data so increasing the tcprcvbuf may not be necessary.

END

This article was:   Helpful | Not Helpful
Prev   Next
Owner check failed while attempting to register a container     How to make a copy of a container and change the CTID / VEID

RSS