[tor-bugs] #9782 [Tor]: Tor crashes when setting relay

[Tor Bug Tracker & Wiki]

#9782: Tor crashes when setting relay
-----------------------+----------------------------------
 Reporter:  Alchemist  |          Owner:
     Type:  defect     |         Status:  new
 Priority:  normal     |      Milestone:
Component:  Tor        |        Version:  Tor: 0.2.4.17-rc
 Keywords:             |  Actual Points:
Parent ID:             |         Points:
-----------------------+----------------------------------
 OS: Linux Mint 13 - all updates - both the 64 and 32-bit editions.

 Tor in TBB 2.3.25.12-dev-en-US and 2.4.17-beta-1-dev-en.US crashes when
 setting relay. It happens whether or not contact info is set, and
 regardless of bandwith or exit/no exit settings. The following messages
 are generated:

 Unexpected Error
 Vidalia detected that the Tor software exited unexpectedly.
 Please check the message log for recent warning or error messages

 Error Applying Settings
 Vidalia was unable to apply your Server settings to Tor.
 Control socket is not connected.


 Here is the log output:

 Sep 19 11:33:25.143 [Notice] Tor v0.2.3.25 (git-17c24b3118224d65) running
 on Linux.
 Sep 19 11:33:25.143 [Notice] Tor can't help you if you use it wrong! Learn
 how to be safe at https://www.torproject.org/download/download#warning
 Sep 19 11:33:25.143 [Notice] Read configuration file "/home/al/Downloads
 /tor-browser_en-US-2.3.25.12-dev-en-US/App/../Data/Tor/torrc".
 Sep 19 11:33:25.143 [Notice] Initialized libevent version 2.0.21-stable
 using method epoll (with changelist). Good.
 Sep 19 11:33:25.143 [Notice] Opening Socks listener on 127.0.0.1:9150
 Sep 19 11:33:25.143 [Notice] Opening Control listener on 127.0.0.1:9151
 Sep 19 11:33:25.143 [Notice] Parsing GEOIP file ./Data/Tor/geoip.
 Sep 19 11:33:25.816 [Notice] No AES engine found; using AES_* functions.
 Sep 19 11:33:25.816 [Notice] This OpenSSL has a good implementation of
 counter mode; using it.
 Sep 19 11:33:25.816 [Notice] OpenSSL OpenSSL 1.0.0k 5 Feb 2013 looks like
 version 0.9.8m or later; I will try SSL_OP to enable renegotiation
 Sep 19 11:33:25.816 [Notice] Reloaded microdescriptor cache.  Found 4150
 descriptors.
 Sep 19 11:33:25.816 [Notice] We now have enough directory information to
 build circuits.
 Sep 19 11:33:25.816 [Notice] Bootstrapped 80%: Connecting to the Tor
 network.
 Sep 19 11:33:25.816 [Notice] New control connection opened.
 Sep 19 11:33:26.605 [Notice] Heartbeat: Tor's uptime is 0:00 hours, with 4
 circuits open. I've sent 0 kB and received 0 kB.
 Sep 19 11:33:26.718 [Notice] Bootstrapped 85%: Finishing handshake with
 first hop.
 Sep 19 11:33:27.137 [Notice] Bootstrapped 90%: Establishing a Tor circuit.
 Sep 19 11:33:28.806 [Notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Sep 19 11:33:28.806 [Notice] Bootstrapped 100%: Done.
 Sep 19 11:34:09.068 [Notice] Your ContactInfo config option is not set.
 Please consider setting it, so we can contact you if your server is
 misconfigured or something else goes wrong.
 Sep 19 11:34:09.069 [Notice] Opening Directory listener on 0.0.0.0:9030
 Sep 19 11:34:09.069 [Notice] Opening OR listener on 0.0.0.0:9001
 Sep 19 11:34:09.069 [Notice] Your Tor server's identity key fingerprint is
 'Unnamed C5CE8FB839424BA458834E6EEB52D739046A4C1D'
 Sep 19 11:34:09.071 [Notice] Now checking whether ORPort 99.29.28.231:9001
 and DirPort 99.29.28.231:9030 are reachable... (this may take up to 20
 minutes -- look for log messages indicating success)
 Sep 19 11:34:09.071 [Warning] Unable to stat resolver configuration in
 '/etc/resolv.conf': No such file or directory
 Sep 19 11:34:09.074 [Error] set_options(): Bug: Acting on config options
 left us in a broken state. Dying.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9782>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online