Re: [Fwd: (Probably) a known problem?] - cant run a relay node
On Wed, Dec 03, 2008 at 06:35:19PM +0100, Fabian Keil wrote: [...] > While we're talking about DNS issues, I recently got: > > Nov 30 06:25:02.803 [notice] Tor 0.2.1.6-alpha (r17011) opening new log file. > Nov 30 06:25:02.818 [warn] eventdns: Unable to add nameserver 164.148.169.81: > error 2 > Nov 30 06:25:02.818 [warn] eventdns: Unable to add nameserver 34.148.169.81: > error 2 > Nov 30 06:25:02.818 [warn] Unable to parse '/etc/resolv.conf', or no > nameservers in '/etc/resolv.conf' (6) > Nov 30 06:25:02.819 [err] set_options(): Bug: Acting on config options left > us in a broken state. Dying. > > The nameservers were indeed unreachable at that time > (the traffic limit was reached and the system offline), > but earlier Tor versions continued to run and started > working again once the system was back on the net. This was bug 691; it should be fixed in 0.2.1.9-alpha when it comes out. https://bugs.torproject.org/flyspray/index.php?id=691&do=details This is probably a good time for me to encourage people to use the bugtracker at bugs.torproject.org to report and track bugs. It lets us do a better job of collecting and consolidating information about each bug, and of making sure that nobody forgets about it until it gets fixed. yrs, -- Nick
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
On Wed, Dec 03, 2008 at 11:52:50AM -0500, pho...@rootme.org wrote: [...] > 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 These bugs are now fixed in svn trunk, I think. The fixes should be in 0.2.1.9-alpha, assuming that the fix was really a fix. -- Nick
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
Fabian Keil <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > > On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] wrote 2.1K > > bytes in 74 lines about: > > > : > 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. > > While we're talking about DNS issues, I recently got: > > Nov 30 06:25:02.803 [notice] Tor 0.2.1.6-alpha (r17011) opening new log file. > Nov 30 06:25:02.818 [warn] eventdns: Unable to add nameserver 164.148.169.81: > error 2 > Nov 30 06:25:02.818 [warn] eventdns: Unable to add nameserver 34.148.169.81: > error 2 > Nov 30 06:25:02.818 [warn] Unable to parse '/etc/resolv.conf', or no > nameservers in '/etc/resolv.conf' (6) > Nov 30 06:25:02.819 [err] set_options(): Bug: Acting on config options left > us in a broken state. Dying. > > The nameservers were indeed unreachable at that time > (the traffic limit was reached and the system offline), > but earlier Tor versions continued to run and started > working again once the system was back on the net. It's probably worth mentioning that this is a relay server running on a GNU/Linux system. Fabian signature.asc Description: PGP signature
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
On Wed, Dec 03, 2008 at 06:35:19PM +0100, [EMAIL PROTECTED] wrote 2.0K bytes in 56 lines about: For those experiencing issues with nameservers and win32, I've built a Tor package based on r17477. This is just Tor, not vidalia, not privoxy. The goal is to try to fix the issues, currently bugs 868 and 813. Nick made some changes to try to figure out what's going on. This I signed it with the same key I sign the "real" tor packages. It's available at: http://moria.seul.org/~phobos/tor-0.2.1.7-alpha-dev-win32.exe and http://moria.seul.org/~phobos/tor-0.2.1.7-alpha-dev-win32.exe.asc -- Andrew
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
I was not online for fiew days but i think i might have a solution for Your problem (worked for me) 1) in torrc add following line ServerDNSResolvConfFile c:\resolv.conf and inside of resolv.conf put following 3 lines nameserver xxx.xxx.xxx.xxx nameserver yyy.yyy.yyy.yyy search your.primary.domain where xxx.xxx.xxx.xxx and yyy.yyy.yyy.yyy are ip adresses of Your DNS servers the third line is optional and is used to instruct linux computers for what domain above DNS servers are authoritative (not sure if its needed but i added it) after those changes everything started to work (im not using vidalia to run Tor i configured it as a service so its running whenewer my mashine is up Hope this will be helpfull for You 2008/12/3 Praedor Atrebates <[EMAIL PROTECTED]>: > I erred. I am no longer using 0.2.1.7. I had to give up because I could not > get it working properly. Doing what I mention below allowed me to run tor via > Vidalia but not via Tork (my preferred tor manager). There was an issue with > the config file that I could never figure out so I went back to a previous > version of tor that worked (currently that is 0.2.0.31. > > Don't think I will mess with 0.2.1.7 again. Since you use Vidalia, you might > manage to get it working more than temporarily. > > praedor > > On Wednesday 03 December 2008 12:26:51 Praedor Atrebates wrote: >> 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/> 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\\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 >> > >> > [EMAIL PROTECTED] wrote: >> > > On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] 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 > >
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
I erred. I am no longer using 0.2.1.7. I had to give up because I could not get it working properly. Doing what I mention below allowed me to run tor via Vidalia but not via Tork (my preferred tor manager). There was an issue with the config file that I could never figure out so I went back to a previous version of tor that worked (currently that is 0.2.0.31. Don't think I will mess with 0.2.1.7 again. Since you use Vidalia, you might manage to get it working more than temporarily. praedor On Wednesday 03 December 2008 12:26:51 Praedor Atrebates wrote: > 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/ 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\\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 > > > > [EMAIL PROTECTED] wrote: > > > On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] 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
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
[EMAIL PROTECTED] wrote: > On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] wrote 2.1K bytes > in 74 lines about: > : > 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. While we're talking about DNS issues, I recently got: Nov 30 06:25:02.803 [notice] Tor 0.2.1.6-alpha (r17011) opening new log file. Nov 30 06:25:02.818 [warn] eventdns: Unable to add nameserver 164.148.169.81: error 2 Nov 30 06:25:02.818 [warn] eventdns: Unable to add nameserver 34.148.169.81: error 2 Nov 30 06:25:02.818 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (6) Nov 30 06:25:02.819 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. The nameservers were indeed unreachable at that time (the traffic limit was reached and the system offline), but earlier Tor versions continued to run and started working again once the system was back on the net. Fabian signature.asc Description: PGP signature
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
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//.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\\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 > > [EMAIL PROTECTED] wrote: > > On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] 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
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
[EMAIL PROTECTED] wrote:
> On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] 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-
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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\\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 [EMAIL PROTECTED] wrote: > On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] 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 iEYEARECAAYFAkk2vsYACgkQ3ju7mowpX9VyXwCfXEdV2r6N+q9YE9FcQysb+h+F uEkAoNTgor2oNzLXyY0sND1qeBINyHqn =dp76 -END PGP SIGNATURE-
Re: [Fwd: (Probably) a known problem?] - cant run a relay node
On Wed, Dec 03, 2008 at 09:34:40AM -0500, [EMAIL PROTECTED] 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? -- Andrew
[Fwd: (Probably) a known problem?] - cant run a relay node
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, A few days ago I posted the message below asking for help to resolve a problem that prevents me from running a Tor relay node. I have not received any responses. 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. Any help would be greatly appreciated. thanks. Alex Donnini Alessandro Donnini wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello, > > 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. > > However, when I try to configure and run it as a relay node Vidalia is not > able > to run Tor and reports the warnings and error you will find below. > > Please note that up until I upgraded the software, Tor was running as a relay > node. I made no configuration changes either before or after the upgrade. > > The only two attempts at trying to fix the problems were: > 1) Rename the Tor configuration file > 2) Re-start the system > > 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. > > > I would appreciate any help and advice for the resolution of this problem. > > Thanks. > > Alex Donnini > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkkzWBwACgkQ3ju7mowpX9XvPgCfcKA9whVSZ3Uyc+XBoMXW+pFz > jKkAn3AMffP08tl++uMcSg5HZ5p5rMQA > =IS2P > -END PGP SIGNATURE- > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk2mQAACgkQ3ju7mowpX9X3ZQCff5sXGocu3uTapnLSdsG3vtRk Or4AoI6zkpdMyK6w/QY+JLVefBbb7PZl =t486 -END PGP SIGNATURE-
