<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Fixed it! And I feel like I'm going crazy. If I'm reading the logs
correctly, Tor is signaling readiness to systemd <i>1 hundredth of
a second (0.01)</i> past the 120s limit. I changed the limit to
300s in the <a class="moz-txt-link-abbreviated" href="mailto:tor@default.service">tor@default.service</a> file, and all is well.<br>
<br>
Thanks Peter, you really steered me in the right direction. I should
probably start checking logs first when something stops working...<br>
<br>
<div class="moz-cite-prefix">On 06/11/2016 09:50 AM, SuperSluether
wrote:<br>
</div>
<blockquote cite="mid:575C2552.8030904@gmail.com" type="cite">Ok
maybe I spoke too soon. After running rpi-update and rebooting,
it's still having trouble starting. I'll poke around and see if I
can find anything. Worst case scenario, I don't have enough RAM
and need to turn something off, which means I'm wasting everyone's
time with this.
<br>
<br>
On 06/11/2016 09:35 AM, SuperSluether wrote:
<br>
<blockquote type="cite">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.
<br>
<br>
I poked around in syslog, and found this:
<br>
<br>
systemd[1]: <a class="moz-txt-link-abbreviated" href="mailto:tor@default.service">tor@default.service</a> start operation timed out.
Terminating.
<br>
<br>
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)
<br>
<br>
On 06/11/2016 03:13 AM, Peter Palfrader wrote:
<br>
<blockquote type="cite">On Fri, 10 Jun 2016, SuperSluether
wrote:
<br>
<br>
<blockquote type="cite">After rebooting my Raspberry Pi for a
few updates, Tor is not working
<br>
properly. From the logs,
<br>
<br>
[warn] OpenSSL version from headers does not match the
version we're running
<br>
with. If you get weird crashes, that might be why. (Compiled
with 100010bf:
<br>
OpenSSL 1.0.1k 8 Jan 2015; running with 1000114f: OpenSSL
1.0.1t 3 May
<br>
2016).
<br>
<br>
Everything else in the log looks normal, but right after
bootstrap 85%
<br>
(finishing handshake with first hop) it says this:
<br>
<br>
[notice] Interrupt: we have stopped accepting new
connections, and will shut
<br>
down in 30 seconds. Interrupt again to exit now.
<br>
</blockquote>
You did not say where you got your tor from. I assume you are
using
<br>
some version (or fork) of the debian package. Which one?
<br>
<br>
At a guess, your system is too slow to start tor within the
default
<br>
timeout of the systemd service. Try raising the timeout.
(Which
<br>
systemd version are you using?)
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>