Fabian Keil <freebsd-listen@xxxxxxxxxxxxx> wrote: > phobos@xxxxxxxxxx wrote: > > > On Wed, Dec 03, 2008 at 09:34:40AM -0500, alexdonnini@xxxxxxxx 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
Attachment:
signature.asc
Description: PGP signature