[tor-relays] Tor relay is restarting every minute

Michael mctor at biographiks.com
Fri Jun 19 11:42:59 UTC 2015


My Tor relay interrupts and restarts every minute (without my
involvement), so it isn't usable by anyone. Nothing new in my
obfsproxy log. My relay was running fine until I moved and changed to
a new ISP (AT&T).


Jun 19 06:10:28.717 [notice] Tor v0.2.6.9 (git-145b2587d1269af4)
running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1f and Zlib
1.2.8.
Jun 19 06:10:28.717 [notice] Tor can't help you if you use it wrong!
Learn how to be safe at
https://www.torproject.org/download/download#warning
Jun 19 06:10:28.717 [notice] Read configuration file
"/usr/share/tor/tor-service-defaults-torrc".
Jun 19 06:10:28.717 [notice] Read configuration file "/etc/tor/torrc".
Jun 19 06:10:28.722 [notice] Based on detected system memory,
MaxMemInQueues is set to 2048 MB. You can override this by setting
MaxMemInQueues by hand.
Jun 19 06:10:28.722 [notice] We were compiled with headers from
version 2.0.19-stable of Libevent, but we're using a Libevent library
that says it's version 2.0.21-stable.
Jun 19 06:10:28.722 [notice] Opening Control listener on 127.0.0.1:9051
Jun 19 06:10:28.723 [notice] Opening Control listener on /var/run/tor/control
Jun 19 06:10:28.723 [notice] Opening OR listener on 0.0.0.0:9001
Jun 19 06:10:28.723 [notice] Opening Extended OR listener on 127.0.0.1:0
Jun 19 06:10:28.723 [notice] Extended OR listener listening on port 55831.
Jun 19 06:10:28.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Jun 19 06:10:28.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Jun 19 06:10:28.000 [notice] Configured to measure statistics. Look
for the *-stats files that will first be written to the data directory
in 24 hours from now.
Jun 19 06:10:29.000 [notice] Your Tor server's identity key
fingerprint is [REDACTED]
Jun 19 06:10:29.000 [notice] Your Tor bridge's hashed identity key
fingerprint is [REDACTED]
Jun 19 06:10:29.000 [notice] Bootstrapped 0%: Starting
Jun 19 06:10:33.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Jun 19 06:10:34.000 [warn] The communication stream of managed proxy
'/usr/local/bin/obfsproxy' is 'closed'. Most probably the managed
proxy stopped running. This might be a bug of the managed proxy, a bug
of Tor, or a misconfiguration. Please enable logging on your managed
proxy and check the logs for errors.
Jun 19 06:10:34.000 [notice] Failed to terminate process with PID
'13164' ('Success').
Jun 19 06:10:34.000 [notice] Bootstrapped 85%: Finishing handshake
with first hop
Jun 19 06:10:35.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Jun 19 06:10:36.000 [notice] Tor has successfully opened a circuit.
Looks like client functionality is working.
Jun 19 06:10:36.000 [notice] Bootstrapped 100%: Done
Jun 19 06:11:13.000 [notice] Interrupt: we have stopped accepting new
connections, and will shut down in 30 seconds. Interrupt again to exit
now.
Jun 19 06:11:43.000 [notice] Clean shutdown finished. Exiting.
Jun 19 06:11:43.000 [notice] Tor 0.2.6.9 (git-145b2587d1269af4)
opening log file.
Jun 19 06:11:43.958 [warn] OpenSSL version from headers does not match
the version we're running with. If you get weird crashes, that might
be why. (Compiled with 1000105f: OpenSSL 1.0.1e 11 Feb 2013; running
with 1000106f: OpenSSL 1.0.1f 6 Jan 2014).
Jun 19 06:11:43.958 [notice] Tor v0.2.6.9 (git-145b2587d1269af4)
running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1f and Zlib
1.2.8.


More information about the tor-relays mailing list