Re: [Fwd: (Probably) a known problem?] - cant run a relay node

[Praedor Atrebates <praedor@xxxxxxxxx>]

I had horrible troubles getting the latest tor 0.2.1.7 working after 
upgrading.  I use Tork, not Vidalia, but I suspect the problem is likely the 
same.

I deleted my existing tor directory (in linux, that is in /home/<your home 
directory>/.tor - I have no idea if there is an equivalent windows setup to 
this - the directory that contains your tor configuration file) and started 
tor up again and it worked fine.  I then had to manually edit the config file 
to add my server name, contact info, etc.  Since then, it has worked.

praedor

On Wednesday 03 December 2008 12:15:50 Alessandro Donnini wrote:
> Thanks for the response. I understand. Below, you will find the copy of the
> Vidalia generated torrc.
>
> The problem is occurring on a system running MS Windows XP SP2.
>
> Note that prior to the upgrade from 0.2.0.31 to 0.2.1.7 I had no problems.
> The problems started occurring as soon as I started Tor again via Vidalia
> after the upgrade. Also note that I do not have any problems running the
> Tor client.
>
> Thanks
>
>
> torrc from Document and Settings\<user name>\Application Data\Vidalia
> ======================================================================
> # This file was generated by Tor; if you edit it, comments will not be
> preserved # The old torrc file was renamed to torrc.orig.1 or similar, and
> Tor will ignore it
>
> # If set, Tor will accept connections from the same machine (localhost
> only) # on this port, and allow those connections to control the Tor
> process using # the Tor Control Protocol (described in control-spec.txt).
> ControlPort 9051
> # Where to send logging messages.  Format is minSeverity[-maxSeverity]
> # (stderr|stdout|syslog|file FILENAME).
> Log notice stdout
>
> phobos@xxxxxxxxxx wrote:
> > On Wed, Dec 03, 2008 at 09:34:40AM -0500, alexdonnini@xxxxxxxx wrote 2.1K 
bytes in 74 lines about:
> > : I would like to continue to run a Tor relay node but am unable to do so
> > : until I resolve the problem described below, and I need help in order
> > : to do that.
> > :
> > : > I just upgraded to versions
> > : >
> > : > 0.1.10 of Vidalia
> > : > and
> > : > 0.2.1.7 of Tor
> > : >
> > : > Vidalia is able to run Tor as a client without any problems.
> > : >
> > : > Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config
> > : > options left us in a broken state. Dying.
> > : > Nov 30 22:02:52.906 [Warning] eventdns: Didn't find any nameservers.
> > : > Nov 30 22:02:52.906 [Warning] Could not config nameservers.
> > : > Nov 30 22:02:52.906 [Error] set_options(): Bug: Acting on config
> > : > options left us in a broken state. Dying.
> >
> > A few things,  you probably haven't received a response because no one
> > has a good idea how to fix it.  You may have 2 issues, one is that
> > libevent can't find nameservers, and the other is that the config
> > options are broken.
> >
> > As for the dns issues:
> >
> > https://bugs.torproject.org/flyspray/index.php?do=details&id=813
> >
> > or
> >
> > https://bugs.torproject.org/flyspray/index.php?do=details&id=868
> >
> > Are you running Windows?
> >
> > For the config issues, which may be related to the dns issues, do you
> > have a copy of the torrc that's generated by Vidalia?
>
> gpgkeys: key DE3BBB9A8C295FD5 not found on keyserver