<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><p>Hi,<br></p><p>I'm running a relay on debian jessie using packages from deb.torproject.org.<br></p><p>I want to share the problems I had so others are aware of them when upgrading their relays.<br></p><p>While upgrading from 0.2.7.6 to 0.2.8.6 via apt-get, I did a<br></p><p>tail -f syslog<br></p><p>to make sure I notice problems during the upgrade. (I expected a simple restart of all running tor instances)<br></p><p>I use debian's multi instance systemd service file.<br></p><p>When upgrading, all running tor instances are stopped (not restarted, as expected)</p><p>syslog shows: </p><p>Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now.</p><p>Clean shutdown finished. Exiting.</p><p><br></p><p>(problem is reproducible)<br></p><p><br></p><p>Side note (unrelated to the upgrade but also relevant for the debian tor package from deb.torproject.org repo):</p><p>Stopping the default instance stops all instances due to<br></p><p>/lib/systemd/system/tor@.service:</p><p>[...]<br></p><p>PartOf=tor.service<br>ReloadPropagatedFrom=tor.service<br></p><p><br></p><p>How about using the same way as the RPM maintainer does - so one can enable the default instance without affecting all others?<br></p><p>PartOf=tor-master.service<br>ReloadPropagatedFrom=tor-master.service<br></p></body></html>