[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Libevent errors with running Tor on a virtual server


> On Fri, Aug 07, 2009 at 04:23:52PM +0200, d-503@xxxxxxxxx wrote 5.3K
> bytes in 117 lines about: : I'm running an entry-node on a
> virtual-server. I have usually a
> This is your first problem, the virtual server probably doesn't have
> enough tcp nor open files.

Yes I know that's the main problem :) 

> Also, how old is the libevent?

It's 1.3e-3 from debian lenny.

> : Aug 07 10:44:33.383 [warn] Failing because we have 994 connections
> : already. Please raise your ulimit -n. 
> Have you tried raising ulimit?

I'm not allowed to raise the ulimit above 1024. This certain message
also just appears once every 6 hours so I don't think it's that
important but the libevent errors come really often.

> This FAQ answer may guide you as well,
> https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#VServer

Yes I read this already and there is also the ConstrainedSockets
mentioned. But in the Tor-Manpage is written this should be used if I
get the:"Error creating network socket: No buffer space available"
message in the logs but my error is different. Or has this message been
replaced with the one I get? If this option is usefull what is a good
value? Is there any way except try and error to know which socketsize
shall be used with me?


Attachment: signature.asc
Description: PGP signature