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

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



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I replaced the current ttorrc with the one labeled "old". Tor still cannot run
as a relay node but the error messages have changed. Here they are:

Dec 03 12:05:09.746 [Notice] Tor v0.2.1.7-alpha (r17216). This is experimental
software. Do not rely on it for strong anonymity. (Running on Windows XP Service
Pack 2 [workstation] {terminal services, single user})
Dec 03 12:05:09.746 [Notice] Initialized libevent version 1.4.7-stable using
method win32. Good.
Dec 03 12:05:09.746 [Notice] Opening Socks listener on 127.0.0.1:9050
Dec 03 12:05:09.746 [Notice] Opening Control listener on 127.0.0.1:9051
Dec 03 12:05:09.746 [Notice] Parsing GEOIP file.
Dec 03 12:15:34.902 [Notice] Tor v0.2.1.7-alpha (r17216). This is experimental
software. Do not rely on it for strong anonymity. (Running on Windows XP Service
Pack 2 [workstation] {terminal services, single user})
Dec 03 12:15:34.902 [Notice] Initialized libevent version 1.4.7-stable using
method win32. Good.
Dec 03 12:15:34.902 [Notice] Opening Socks listener on 127.0.0.1:9050
Dec 03 12:15:34.902 [Notice] Opening Control listener on 127.0.0.1:9051
Dec 03 12:15:34.902 [Notice] Parsing GEOIP file.
Dec 03 12:18:01.808 [Notice] Tor v0.2.1.7-alpha (r17216). This is experimental
software. Do not rely on it for strong anonymity. (Running on Windows XP Service
Pack 2 [workstation] {terminal services, single user})
Dec 03 12:18:01.808 [Notice] Initialized libevent version 1.4.7-stable using
method win32. Good.
Dec 03 12:18:01.808 [Notice] Opening OR listener on 0.0.0.0:443
Dec 03 12:18:01.808 [Notice] Opening Directory listener on 0.0.0.0:9030
Dec 03 12:18:01.808 [Notice] Opening Socks listener on 127.0.0.1:9050
Dec 03 12:18:01.808 [Notice] Opening Control listener on 127.0.0.1:9051
Dec 03 12:18:01.808 [Notice] Parsing GEOIP file.
Dec 03 12:18:03.121 [Warning] eventdns: Didn't find any nameservers.
Dec 03 12:18:03.121 [Warning] Could not config nameservers.
Dec 03 12:18:03.121 [Error] Error initializing dns subsystem; exiting


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?
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkk2wI8ACgkQ3ju7mowpX9UchACfQDiYtnb3iWusL1ka4U31BvJy
6fsAn1UdqWl4mWVuoN1K+bmApXAbV2tM
=SBt0
-----END PGP SIGNATURE-----