[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] Tor is Interrupting (?) OpenSSL Version Mismatch



I have the Raspberry Pi Model B 2, which has an ARM7 processor. As such, I am able to use the official Debian repository without issue. Current version of Tor is 0.2.7.6-1~d80.jessie+1. Systemd is at version 215-17+deb8u4.

I poked around in syslog, and found this:

systemd[1]: tor@xxxxxxxxxxxxxxx start operation timed out. Terminating.

After increasing the systemd timeout (from 90s to 300s) Tor is running properly. Thanks for the help! I'm guessing this happened because I just have too much running on this thing. (Plex Media Server, Deluge BitTorrent Client, Tor)

On 06/11/2016 03:13 AM, Peter Palfrader wrote:
On Fri, 10 Jun 2016, SuperSluether wrote:

After rebooting my Raspberry Pi for a few updates, Tor is not working
properly. From the logs,

[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 100010bf:
OpenSSL 1.0.1k 8 Jan 2015; running with 1000114f: OpenSSL 1.0.1t  3 May
2016).

Everything else in the log looks normal, but right after bootstrap 85%
(finishing handshake with first hop) it says this:

[notice] Interrupt: we have stopped accepting new connections, and will shut
down in 30 seconds. Interrupt again to exit now.
You did not say where you got your tor from.  I assume you are using
some version (or fork) of the debian package.  Which one?

At a guess, your system is too slow to start tor within the default
timeout of the systemd service.  Try raising the timeout.  (Which
systemd version are you using?)


_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays