running a relay on a pi/pi2 and it stopped working after upgrading to 0.2.8.6/0.2.8.6-2 ? read this (bugfix)
Hi,
I ran into some tor restart loop issues after upgrading to 0.2.8.6 on my pi2 relay.
In short, it takes too long to read router_parse_list_from_string and hits the systemd start timeout limit causing a restart (and loop)
Full story in the ticket here: https://trac.torproject.org/projects/tor/ticket/19819
quick fix:
edit /lib/systemd/system/tor@default.service and change TimeoutStartSec= from 120 to 300
Hope i'm not "spamming" the list, just trying to help.
Have a good one.
* Hack-Tic schrieb am 2016-08-05 um 21:19 Uhr:
edit /lib/systemd/system/tor@default.service and change TimeoutStartSec=
Please don't write in /lib. Better create a new file /etc/systemd/system/tor@default@default.service.d/override.conf and add your change there. When you update Tor at some point, your settings won't be overwritten with this method.
On Fri, 05 Aug 2016, Jens Kubieziel wrote:
- Hack-Tic schrieb am 2016-08-05 um 21:19 Uhr:
edit /lib/systemd/system/tor@default.service and change TimeoutStartSec=
Please don't write in /lib. Better create a new file /etc/systemd/system/tor@default@default.service.d/override.conf and add your change there. When you update Tor at some point, your settings won't be overwritten with this method.
I just changed git to raise it to 300 too. So maybe this once changing /lib was actually ok :)
On 6 Aug 2016, at 06:24, Peter Palfrader weasel@torproject.org wrote:
On Fri, 05 Aug 2016, Jens Kubieziel wrote:
- Hack-Tic schrieb am 2016-08-05 um 21:19 Uhr:
edit /lib/systemd/system/tor@default.service and change TimeoutStartSec=
Please don't write in /lib. Better create a new file /etc/systemd/system/tor@default@default.service.d/override.conf and add your change there. When you update Tor at some point, your settings won't be overwritten with this method.
I just changed git to raise it to 300 too. So maybe this once changing /lib was actually ok :)
Hi weasel,
It looks like you changed it in https://gitweb.torproject.org/debian/tor.git/tree/debian/systemd/tor@.servic... but not in: https://gitweb.torproject.org/debian/tor.git/tree/debian/systemd/tor@default...
Is this intentional?
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
On Wed, 10 Aug 2016, teor wrote:
I just changed git to raise it to 300 too. So maybe this once changing /lib was actually ok :)
It looks like you changed it in https://gitweb.torproject.org/debian/tor.git/tree/debian/systemd/tor@.servic... but not in: https://gitweb.torproject.org/debian/tor.git/tree/debian/systemd/tor@default...
Is this intentional?
Good catch, thanks.
tor-relays@lists.torproject.org
-
Hack-Tic -
Jens Kubieziel -
Peter Palfrader -
teor