[tor-bugs] #15421 [Core Tor/Tor]: Relay crash when reloading and resolv.conf is empty
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Jul 26 15:14:21 UTC 2017
#15421: Relay crash when reloading and resolv.conf is empty
----------------------------------------+----------------------------------
Reporter: TvdW | Owner:
Type: defect | Status: new
Priority: High | Milestone: Tor: unspecified
Component: Core Tor/Tor | Version: Tor:
| 0.2.7.1-alpha
Severity: Normal | Resolution:
Keywords: tor-relay resolv.conf dns | Actual Points:
Parent ID: #21900 | Points: small
Reviewer: | Sponsor:
----------------------------------------+----------------------------------
Comment (by atagar):
Hi there, yesterday I ran into an issue that looks like this too. Here's
the repro steps I provided from #23036 with the latest git tip (tor commit
bb66a48).
**Repro steps:**
* Start system without a network connection.
* Start tor, torrc I used was...
{{{
% cat ~/.tor/torrc
ControlPort 9051
ExitPolicy reject *:*
}}}
* Set the ORPort with "SETCONF ORPort=9090".
**Result:**
Tor process terminates with...
{{{
Jul 25 19:21:33.000 [warn] ControlPort is open, but no authentication
method has been configured. This means that any program on your computer
can reconfigure your Tor. That's bad! You should upgrade your Tor
controller as soon as possible.
Jul 25 19:21:33.000 [notice] Opening OR listener on 0.0.0.0:9090
Jul 25 19:21:33.000 [notice] You are running a new relay. Thanks for
helping the Tor network! If you wish to know what will happen in the
upcoming weeks regarding its usage, have a look at
https://blog.torproject.org/blog/lifecycle-of-a-new-relay
Jul 25 19:21:33.000 [notice] It looks like I need to generate and sign a
new medium-term signing key, because I don't have one. To do that, I need
to load (or create) the permanent master identity key. If the master
identity key was not moved or encrypted with a passphrase, this will be
done automatically and no further action is required. Otherwise, provide
the necessary data using 'tor --keygen' to do it manually.
Jul 25 19:21:33.000 [notice] Your Tor server's identity key fingerprint is
'Unnamed 4853AB6F9215A837EA3562CF4AF00713737FDF01'
Jul 25 19:21:33.000 [warn] Unable to parse '/etc/resolv.conf', or no
nameservers in '/etc/resolv.conf' (6)
Jul 25 19:21:33.000 [err] set_options(): Bug: Acting on config options
left us in a broken state. Dying. (on Tor 0.3.2.0-alpha-dev
bb66a48541aa5110)
}}}
Cheers! -Damian
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15421#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list