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

Re: A tor error message prior to crash

Thanks.  I'll check it out.  

I have also since found that the problem is associated with being and exit 
rather than being a relay.  

I was using Vidalia default settings and set to be a relay (Vidalia in this 
regard appears to configure tor to be either/both(?).  I delved deeper into the 
Vidalia configuration options and deselected any settings that seemed to set me 
up to serve as an exit.  Since doing this, tor has not faltered on me at all.

On Tuesday 19 May 2009 13:54:51 Nick Mathewson wrote:
> On Mon, May 11, 2009 at 01:33:41PM -0400, Praedor Atrebates wrote:
> > I finally picked up a log entry that is associated with vidalia/tor
> > failing at random moments:
> >
> > May 11 13:30:49.177 [err] Error from libevent: event_queue_insert:
> > 0xa2e6d68(fd 33) already on queue 2
> >
> > What does this mean and how do I fix it?
> I have a patch in the repository that might fix it.  If you can build
> from source, please try out the latest maint-0.2.1 branch to see
> whether the bug is gone for you.
> (There might be some warning messages in the log that start with
> "Bug".  If there are, please let me know.)
> yrs,

"If we have Senators and Congressmen there that can't protect themselves 
against the evil temptations of lobbyists, we don't need to change our 
lobbies, we need to change our representatives." - Will Rogers