[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[warn] Error creating network socket: No buffer space available and numtcpsock
- To: or-talk@xxxxxxxxxxxxx
- Subject: [warn] Error creating network socket: No buffer space available and numtcpsock
- From: Tom Taler <casimir.taler@xxxxxxxxxxxxxx>
- Date: Thu, 2 Apr 2009 01:24:11 -0700
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Thu, 02 Apr 2009 04:24:14 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=cVvQqOvpChTUARrmCn4xEdDXIfcvPDiIW9Vu7wWXgDU=; b=Qt35gd56mX+68kMdBgUR2405pAEGxiCz7A9j6ER3VSFXbko+WyRqAwPMLFAHMCPk2J Jif/py/ujzXKcvR+mNQnvM9AQUVorDwM1wGFL6YoowNaQ0SsxJJA1xLv2+pg9qtfF39s LIijRF4dF9kTqUGLpylnl/BpW80dFp4A/pRhQ=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=vMepehpSYgIJ5hkYeZQzEnreMuAU6hAlYS9YfAa9OZI/HBPEZAViwmoFlLJa/WQWKn 1yQeLnf3oWE47sGXlVGxurAPWZQubWSLbAkliax2Lfzw0h8bu/gH0aEb4j5V21ZVYbXC PJWyzVw37KzUBL9/YZWfBqa93nIf3JkjJnHAE=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
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)