Tor is Interrupting (?) OpenSSL Version Mismatch
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. What do I do now? I have all the latest updates installed on this system, including the latest (stable) version of Tor.
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?) -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `- https://www.debian.org/
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@default.service 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?)
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. On 06/11/2016 09:35 AM, SuperSluether wrote:
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@default.service 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?)
Fixed it! And I feel like I'm going crazy. If I'm reading the logs correctly, Tor is signaling readiness to systemd /1 hundredth of a second (0.01)/ past the 120s limit. I changed the limit to 300s in the tor@default.service file, and all is well. Thanks Peter, you really steered me in the right direction. I should probably start checking logs first when something stops working... On 06/11/2016 09:50 AM, SuperSluether wrote:
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.
On 06/11/2016 09:35 AM, SuperSluether wrote:
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@default.service 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?)
Happy to read this! And thx for sharing this solution ;) Le 11/06/2016 à 20:11, SuperSluether a écrit :
Fixed it! And I feel like I'm going crazy. If I'm reading the logs correctly, Tor is signaling readiness to systemd /1 hundredth of a second (0.01)/ past the 120s limit. I changed the limit to 300s in the tor@default.service file, and all is well.
Thanks Peter, you really steered me in the right direction. I should probably start checking logs first when something stops working...
On 06/11/2016 09:50 AM, SuperSluether wrote:
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.
On 06/11/2016 09:35 AM, SuperSluether wrote:
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@default.service 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@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- Petrusko PubKey EBE23AE5 C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5
I like to try this chnage as well - where do I find this file/parameter exactly? Thanks Am 11.06.2016 um 20:11 schrieb SuperSluether:
Fixed it! And I feel like I'm going crazy. If I'm reading the logs correctly, Tor is signaling readiness to systemd /1 hundredth of a second (0.01)/ past the 120s limit. I changed the limit to 300s in the tor@default.service file, and all is well.
Thanks Peter, you really steered me in the right direction. I should probably start checking logs first when something stops working...
On 06/11/2016 09:50 AM, SuperSluether wrote:
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.
On 06/11/2016 09:35 AM, SuperSluether wrote:
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@default.service 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@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
If it can give some informations: My RPi updated, with Raspbian repo used for the system + Tor : tor --version Tor version 0.2.5.12 (git-3731dd5c3071dcba) openssl version OpenSSL 1.0.1t 3 May 2016 (looks like your!) I got no lines like yours in my log file... Humm, I remember some bugs with openssl and RPi firmware... not sure about the versions... It has been solved after a "rpi-update". If not recognized : apt-get install rpi-update then reboot. Le 11/06/2016 à 04:42, SuperSluether a écrit :
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.
What do I do now? I have all the latest updates installed on this system, including the latest (stable) version of Tor. _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- Petrusko PubKey EBE23AE5 C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5
Same problem here today after several updates... rpi-update doesn’t solve the issue unfortunately log-file looks like this: Jun 11 13:20:50.000 [notice] Clean shutdown finished. Exiting. Jun 11 13:20:53.000 [notice] Tor 0.2.7.6 (git-605ae665009853bd) opening log file. Jun 11 13:20:52.462 [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 with 100010bf: OpenSSL 1.0.1k 8 Jan 2015; running with 1000114f: OpenSSL 1.0.1t 3 May 2016). Jun 11 13:20:53.423 [notice] Tor v0.2.7.6 (git-605ae665009853bd) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1t and Zlib 1.2.8. Jun 11 13:20:56.000 [notice] Bootstrapped 0%: Starting Jun 11 13:20:58.000 [notice] Bootstrapped 5%: Connecting to directory server Jun 11 13:22:54.000 [notice] Bootstrapped 80%: Connecting to the Tor network Jun 11 13:22:54.000 [notice] Signaled readiness to systemd Jun 11 13:22:54.000 [notice] Bootstrapped 85%: Finishing handshake with first hop Jun 11 13:22:54.000 [notice] Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now. Jun 11 13:23:24.000 [notice] Clean shutdown finished. Exiting. Am 11.06.2016 um 11:45 schrieb Petrusko:
apt-get install rpi-update
Hey! I see in your logs the Tor 0.2.7.6 (git-605ae665009853bd) is used. This Tor version is running fine on my _Debian_ relay, 'cause I've set up the _Tor repo_ in the /etc/apt/sources.list But on _Raspbian_, I'm not sure if using the Tor repo is 100% ok... :s https://www.torproject.org/docs/debian.html.en#ubuntu : << *Raspbian is not Debian.* These packages will be confusingly broken for Raspbian users, since Raspbian called their architecture armhf but Debian already has an armhf.>> May be I'm wrong... I've to try Tor repo on a 2nd RPi I've got for spare, to be sure... Are you using the Tor repo as I guess ? and Raspbian 8 jessie ? Raspbian repo are ok, not as updated as the Tor repo, but it's working ;) Le 11/06/2016 à 13:32, pa011 a écrit :
Same problem here today after several updates... rpi-update doesn’t solve the issue unfortunately log-file looks like this:
Jun 11 13:20:50.000 [notice] Clean shutdown finished. Exiting. Jun 11 13:20:53.000 [notice] Tor 0.2.7.6 (git-605ae665009853bd) opening log file. Jun 11 13:20:52.462 [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 with 100010bf: OpenSSL 1.0.1k 8 Jan 2015; running with 1000114f: OpenSSL 1.0.1t 3 May 2016).
Jun 11 13:20:53.423 [notice] Tor v0.2.7.6 (git-605ae665009853bd) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1t and Zlib 1.2.8.
Jun 11 13:20:56.000 [notice] Bootstrapped 0%: Starting Jun 11 13:20:58.000 [notice] Bootstrapped 5%: Connecting to directory server Jun 11 13:22:54.000 [notice] Bootstrapped 80%: Connecting to the Tor network Jun 11 13:22:54.000 [notice] Signaled readiness to systemd Jun 11 13:22:54.000 [notice] Bootstrapped 85%: Finishing handshake with first hop Jun 11 13:22:54.000 [notice] Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now. Jun 11 13:23:24.000 [notice] Clean shutdown finished. Exiting.
Am 11.06.2016 um 11:45 schrieb Petrusko:
apt-get install rpi-update
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- Petrusko PubKey EBE23AE5 C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5
Hi Petrusko, yes I read this "Raspbian is not Debian" my /etc/apt/sources.list looks like this: deb http://archive.raspbian.org/raspbian jessie main contrib non-free deb-src http://archive.raspbian.org/raspbian jessie main contrib non-free deb http://ftp.debian.org/debian jessie main deb http://deb.torproject.org/torproject.org jessie main deb-src http://deb.torproject.org/torproject.org jessie main Thanks Am 11.06.2016 um 14:17 schrieb Petrusko:
Hey!
I see in your logs the Tor 0.2.7.6 (git-605ae665009853bd) is used.
This Tor version is running fine on my _Debian_ relay, 'cause I've set up the _Tor repo_ in the /etc/apt/sources.list
But on _Raspbian_, I'm not sure if using the Tor repo is 100% ok... :s https://www.torproject.org/docs/debian.html.en#ubuntu : << *Raspbian is not Debian.* These packages will be confusingly broken for Raspbian users, since Raspbian called their architecture armhf but Debian already has an armhf.>>
May be I'm wrong... I've to try Tor repo on a 2nd RPi I've got for spare, to be sure... Are you using the Tor repo as I guess ? and Raspbian 8 jessie ?
Raspbian repo are ok, not as updated as the Tor repo, but it's working ;)
Le 11/06/2016 à 13:32, pa011 a écrit :
Same problem here today after several updates... rpi-update doesn’t solve the issue unfortunately log-file looks like this:
Jun 11 13:20:50.000 [notice] Clean shutdown finished. Exiting. Jun 11 13:20:53.000 [notice] Tor 0.2.7.6 (git-605ae665009853bd) opening log file. Jun 11 13:20:52.462 [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 with 100010bf: OpenSSL 1.0.1k 8 Jan 2015; running with 1000114f: OpenSSL 1.0.1t 3 May 2016).
Jun 11 13:20:53.423 [notice] Tor v0.2.7.6 (git-605ae665009853bd) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1t and Zlib 1.2.8.
Jun 11 13:20:56.000 [notice] Bootstrapped 0%: Starting Jun 11 13:20:58.000 [notice] Bootstrapped 5%: Connecting to directory server Jun 11 13:22:54.000 [notice] Bootstrapped 80%: Connecting to the Tor network Jun 11 13:22:54.000 [notice] Signaled readiness to systemd Jun 11 13:22:54.000 [notice] Bootstrapped 85%: Finishing handshake with first hop Jun 11 13:22:54.000 [notice] Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now. Jun 11 13:23:24.000 [notice] Clean shutdown finished. Exiting.
Am 11.06.2016 um 11:45 schrieb Petrusko:
apt-get install rpi-update
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
So yes, your RPi is using the Tor repo ;) deb http://deb.torproject.org/torproject.org jessie main deb-src http://deb.torproject.org/torproject.org jessie main my sources.list got this only line : deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi I've to check with my 2nd RPi + Tor repo... Sadly not enough time for now, may be this evening... Le 11/06/2016 à 14:40, pa011 a écrit :
Hi Petrusko,
yes I read this "Raspbian is not Debian"
my /etc/apt/sources.list looks like this:
deb http://archive.raspbian.org/raspbian jessie main contrib non-free deb-src http://archive.raspbian.org/raspbian jessie main contrib non-free deb http://ftp.debian.org/debian jessie main deb http://deb.torproject.org/torproject.org jessie main deb-src http://deb.torproject.org/torproject.org jessie main
Thanks
Am 11.06.2016 um 14:17 schrieb Petrusko:
Hey!
I see in your logs the Tor 0.2.7.6 (git-605ae665009853bd) is used.
This Tor version is running fine on my _Debian_ relay, 'cause I've set up the _Tor repo_ in the /etc/apt/sources.list
But on _Raspbian_, I'm not sure if using the Tor repo is 100% ok... :s https://www.torproject.org/docs/debian.html.en#ubuntu : << *Raspbian is not Debian.* These packages will be confusingly broken for Raspbian users, since Raspbian called their architecture armhf but Debian already has an armhf.>>
May be I'm wrong... I've to try Tor repo on a 2nd RPi I've got for spare, to be sure... Are you using the Tor repo as I guess ? and Raspbian 8 jessie ?
Raspbian repo are ok, not as updated as the Tor repo, but it's working ;)
Le 11/06/2016 à 13:32, pa011 a écrit :
Same problem here today after several updates... rpi-update doesn’t solve the issue unfortunately log-file looks like this:
Jun 11 13:20:50.000 [notice] Clean shutdown finished. Exiting. Jun 11 13:20:53.000 [notice] Tor 0.2.7.6 (git-605ae665009853bd) opening log file. Jun 11 13:20:52.462 [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 with 100010bf: OpenSSL 1.0.1k 8 Jan 2015; running with 1000114f: OpenSSL 1.0.1t 3 May 2016).
Jun 11 13:20:53.423 [notice] Tor v0.2.7.6 (git-605ae665009853bd) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1t and Zlib 1.2.8.
Jun 11 13:20:56.000 [notice] Bootstrapped 0%: Starting Jun 11 13:20:58.000 [notice] Bootstrapped 5%: Connecting to directory server Jun 11 13:22:54.000 [notice] Bootstrapped 80%: Connecting to the Tor network Jun 11 13:22:54.000 [notice] Signaled readiness to systemd Jun 11 13:22:54.000 [notice] Bootstrapped 85%: Finishing handshake with first hop Jun 11 13:22:54.000 [notice] Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now. Jun 11 13:23:24.000 [notice] Clean shutdown finished. Exiting.
Am 11.06.2016 um 11:45 schrieb Petrusko:
apt-get install rpi-update
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- Petrusko PubKey EBE23AE5 C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5
participants (4)
-
pa011 -
Peter Palfrader -
Petrusko -
SuperSluether