[warn] Error creating network socket: No buffer space available and numtcpsock

Tom Taler casimir.taler at googlemail.com
Thu Apr 2 08:24:11 UTC 2009


Hello,
since yesterday I'm running an entrynode on a virtual server. In my
tor-logs I have a lot of these messages:

[warn] Error creating network socket: No buffer space available


I looked in the tor-wiki
(https://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#VServer) for a
solution to this problem and took a look at my beancounters file:

resource                     held              maxheld
barrier                limit              failcnt
 tcpsndbuf                 4759936              4966208
16777216             25165824                    0
            tcprcvbuf                 2095600              2536120
        16777216             25165824                    0
othersockbuf                14064                15384
8388608             15728640                    0
numothersock                   12                   14
1792                 1792                    0


You see I have no problem with the limits which are described in the
wiki-article. My problem is the value numtcpsock:

resource                     held              maxheld
barrier                limit              failcnt
numtcpsock                   1792                 1792
1792                 1792                31240


Is Tor openeing more than 1792 Sockets for working? Or is there some
problem with closing opened sockets? Because my node is now running 14
hours and in the first 8 hours this limit wasn't hit!? At the moment
I'm therefor just relaying about 600-700 KB/s but I have a faster
connection. Is there something which I can do against it?


OS: Lenny
Tor-Version: v0.2.0.34 (r18423)



More information about the tor-talk mailing list