[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Tor relay on vserver exeeding numtcpsock
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Tor relay on vserver exeeding numtcpsock
- From: "Thomas S. Benjamin" <tomb@xxxxxxx>
- Date: Wed, 12 Jan 2011 12:59:44 -0500
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Wed, 12 Jan 2011 18:28:55 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Rlc6JeWusZVEQo30iDmlK2WxH9phB0AtXPT3LUbMgrc=; b=q3J/z/f5V1z3qLvsmK7k+4ha7fDYa9nnsJ+dCwOeIF7fZz1zYQ0ytiWb+TrIjOySSi PLmZ5LpkA1AWsvYPy2vszuijY1o69bBUOeafaVYj702G3t5TcFLZizRe/Im0PPjbjz4s WT9uqO1JXSGWU63KkQKsEfsrl9lHlGuMr1rFI=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=VZFj3kjeCzuCGZFLAZGx5bd2mTg+Bgmvakh/VN+sr5p5A2UHoQ8JSTh0nIzRmVHTFA 9YEwpHNheDJqfl3LR/qwxWVTdq7BsozEG8+K2mnH5RSu1V0Cp4j98rTQjpGAyslGXoeA j0UxfbzScRN5ExDTSPyol6DRzOFQdkkUku6UA=
- In-reply-to: <201101121658.00796.klaus.layer@xxxxxx>
- References: <201101121658.00796.klaus.layer@xxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
Klaus,
My relay (also Virtuozzo based) has a similar problem. Have you tried
running with the "ConstrainedSockets 1" option set in your torrc?
This may solve your problem.
You may want to experiment with different rate limits to tune your
relay to your available resources. I have to continually twiddle my
RelayBandwidthRate and RelayBandwidthBurst to support the most
bandwidth I can before my server starts to drop connections due to
insufficient tcp sockets.
I find that I can generally push about 1000KB before I swallow up my
current 600 numtcpsock limit.
On Wed, Jan 12, 2011 at 10:57 AM, Klaus Layer <klaus.layer@xxxxxx> wrote:
> Hi all,
>
> after running 2 tor relays over dialup connections for several weeks, I
> recently ordered a vserver (Hosteurope Virtual Server Linux L 4.0) and setup a
> middleman tor relay. Very fast the vserver run into shortage of tcp sockets
> which indicate lots of
>
> "Error creating network socket: No buffer space available"
>
> errors. The numtcpsocks parameter limit is set to 550 on the vserver. Before
> asking the ISP to increase the value I would like to ask you what a reasonable
> value of this parameter would be. The tor wiki describe several parameters
> and values for SWSoft's Virtuozzo here
> https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Virtualserver
>
> but for numtcpsock a recommendation is missing.
>
> Thanks for your help.
>
> Klaus
>
>
>
> --
> Klaus Layer
> Walldorf, Germany
> GPG Fingerprint: 466D 12F8 28A3 D137 A77E FC3B 271C 2D79 6F5E 94C9
>
--
Sincerely Yours,
---Thomas S. Benjamin
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk in the body. http://archives.seul.org/or/talk/