[tor-talk] Fedora repo Tor broken?

BM-2cTjsegDfZQNGQWUQjSwro6jrWLC9B3MN3 at bitmessage.ch BM-2cTjsegDfZQNGQWUQjSwro6jrWLC9B3MN3 at bitmessage.ch
Fri Dec 9 17:20:52 UTC 2016


Tor recently removed their Fedora repos, which leaves the fedora native
repo. However, it's not working for me, and never has. Any help would be
appreciated, since I depend heavily on the system tor, and the Tor project
repos are gone!

What I'm doing:

sudo dnf install tor (from fedora)

sudo service tor start (or systemctl start tor.service)

produces:

Job for tor.service failed because the control process exited with error
code. See "systemctl status tor.service" and "journalctl -xe" for details.

systemctl status tor.service

 tor.service - Anonymizing overlay network for TCP
   Loaded: loaded (/usr/lib/systemd/system/tor.service; disabled; vendor
preset: disabled)
   Active: inactive (dead)

Dec 09 11:59:12 localhost tor[4096]: Dec 09 11:59:12.070 [notice] Read
configuration file "/etc/tor/torrc".
Dec 09 11:59:12 localhost tor[4096]: Dec 09 11:59:12.073 [notice] Opening
Socks listener on 127.0.0.1:9050
Dec 09 11:59:12 localhost systemd[1]: tor.service: Main process exited,
code=exited, status=1/FAILURE
Dec 09 11:59:12 localhost systemd[1]: Failed to start Anonymizing overlay
network for TCP.
Dec 09 11:59:12 localhost systemd[1]: tor.service: Unit entered failed state.
Dec 09 11:59:12 localhost systemd[1]: tor.service: Failed with result
'exit-code'.
Dec 09 11:59:13 localhost systemd[1]: tor.service: Service hold-off time
over, scheduling restart.
Dec 09 11:59:13 localhost systemd[1]: Stopped Anonymizing overlay network
for TCP.
Dec 09 11:59:13 localhost systemd[1]: tor.service: Start request repeated
too quickly.
Dec 09 11:59:13 localhost systemd[1]: Failed to start Anonymizing overlay
network for TCP.

journalctl -xe

-- 
-- Unit tor.service has begun starting up.
Dec 09 11:59:11 localhost tor[4093]: Dec 09 11:59:11.946 [notice] Tor
v0.2.8.9 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2j-fips
and Zlib 1.2.8.
Dec 09 11:59:11 localhost tor[4093]: Dec 09 11:59:11.946 [notice] Tor
can't help you if you use it wrong! Learn how to be safe at
https://www.torproject.org/download/download#warning
Dec 09 11:59:11 localhost tor[4093]: Dec 09 11:59:11.946 [notice] Read
configuration file "/usr/share/tor/defaults-torrc".
Dec 09 11:59:11 localhost tor[4093]: Dec 09 11:59:11.946 [notice] Read
configuration file "/etc/tor/torrc".
Dec 09 11:59:11 localhost tor[4093]: Configuration was valid
Dec 09 11:59:12 localhost tor[4096]: Dec 09 11:59:12.070 [notice] Tor
v0.2.8.9 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2j-fips
and Zlib 1.2.8.
Dec 09 11:59:12 localhost tor[4096]: Dec 09 11:59:12.070 [notice] Tor
can't help you if you use it wrong! Learn how to be safe at
https://www.torproject.org/download/download#warning
Dec 09 11:59:12 localhost tor[4096]: Dec 09 11:59:12.070 [notice] Read
configuration file "/usr/share/tor/defaults-torrc".
Dec 09 11:59:12 localhost tor[4096]: Dec 09 11:59:12.070 [notice] Read
configuration file "/etc/tor/torrc".
Dec 09 11:59:12 localhost tor[4096]: Dec 09 11:59:12.073 [notice] Opening
Socks listener on 127.0.0.1:9050
Dec 09 11:59:12 localhost Tor[4096]: OpenSSL version from headers does not
match the version we're running with. If you get weird crashes, that might
be why. (Compiled with 100020af: OpenSSL
Dec 09 11:59:12 localhost Tor[4096]: Tor v0.2.8.9 running on Linux with
Libevent 2.0.21-stable, OpenSSL 1.0.2j-fips and Zlib 1.2.8.
Dec 09 11:59:12 localhost Tor[4096]: Tor can't help you if you use it
wrong! Learn how to be safe at
https://www.torproject.org/download/download#warning
Dec 09 11:59:12 localhost Tor[4096]: Read configuration file
"/usr/share/tor/defaults-torrc".
Dec 09 11:59:12 localhost Tor[4096]: Read configuration file
"/etc/tor/torrc".
Dec 09 11:59:12 localhost Tor[4096]: Opening Socks listener on 127.0.0.1:9050
Dec 09 11:59:12 localhost Tor[4096]: Couldn't open "/var/lib/tor/lock" for
locking: Permission denied
Dec 09 11:59:12 localhost Tor[4096]: set_options(): Bug: Acting on config
options left us in a broken state. Dying. (on Tor 0.2.8.9 )
Dec 09 11:59:12 localhost systemd[1]: tor.service: Main process exited,
code=exited, status=1/FAILURE
Dec 09 11:59:12 localhost systemd[1]: Failed to start Anonymizing overlay
network for TCP.
-- Unit tor.service has failed.

Just running tor produces:

Dec 09 12:19:11.594 [notice] Tor v0.2.8.9 running on Linux with Libevent
2.0.21-stable, OpenSSL 1.0.2j-fips and Zlib 1.2.8.
Dec 09 12:19:11.595 [notice] Tor can't help you if you use it wrong! Learn
how to be safe at https://www.torproject.org/download/download#warning
Dec 09 12:19:11.595 [notice] Read configuration file "/etc/tor/torrc".
Dec 09 12:19:11.598 [notice] Opening Socks listener on 127.0.0.1:9050
Dec 09 12:19:11.598 [warn] Directory /run/tor cannot be read: Permission
denied
Dec 09 12:19:11.598 [warn] Before Tor can create a control socket in
"/run/tor/control", the directory "/run/tor" needs to exist, and to be
accessible only by the user and group account that is running Tor.  (On
some Unix systems, anybody who can list a socket can connect to it, so Tor
is being careful.)
Dec 09 12:19:11.598 [notice] Closing partially-constructed Socks listener
on 127.0.0.1:9050
Dec 09 12:19:11.598 [warn] Failed to parse/validate config: Failed to bind
one of the listener ports.
Dec 09 12:19:11.598 [err] Reading config failed--see warnings above.

any ideas?




More information about the tor-talk mailing list