Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

Hi Peter, sorry was off a week and couldn’t answer: /run/systemd/generator/tor.service.wants/tor@tor2.service /run/systemd/generator/tor.service.wants/tor@default.service Anyway with "steady hand" the system seems to have repaired itself in between. I updated my other multi-instance exits

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

On Sat, 06 Aug 2016, pa011 wrote: > The only instance in /etc/tor/instances/ is tor2 > There is no tor and nothing else in that directory > > And I do have a torrc file in /etc/tor/ What does find /run/systemd -name 'tor@*' list? What do those files look like? --

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

The only instance in /etc/tor/instances/ is tor2 There is no tor and nothing else in that directory And I do have a torrc file in /etc/tor/ Best Regards Paul Am 06.08.2016 um 22:30 schrieb Peter Palfrader: > On Sat, 06 Aug 2016, pa011 wrote: > >> Actually not - you are right Alexander! >>

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

On Sat, 06 Aug 2016, pa011 wrote: > Actually not - you are right Alexander! > But then the question are: > > - why do I need a user "_tor-tor" since the last update, when I didn’t need > that before > - why is it not self creating > - what do I have to do - really creating "_tor-tor" with the

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

I haven't used tor-instance-create yet, but looking at "man tor-instance-create", it sounds like the user should have been created automatically when creating the instance named "tor", like it did for "tor2". You could backup the "tor" instance's configuration and data files, create it again

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

Actually not - you are right Alexander! But then the question are: - why do I need a user "_tor-tor" since the last update, when I didn’t need that before - why is it not self creating - what do I have to do - really creating "_tor-tor" with the same privileges as "_tor-tor2"? Thanks Paul

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

The error message "Ungültiger Anwender „_tor-tor“" appears several times in your log, while there are no error messages about user "_tor-tor2". Does the first user exist? Best regards, Alexander --- PGP Key: https://dietrich.cx/pgp | 0x52FA4EE1722D54EB On 2016-08-06 14:56, pa011 wrote: Thank

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

Thank you Michael for your hint - corrected that, but still having that problem with main instance not running: Aug 6 14:30:02 systemd-sysctl[142]: Failed to write '10 # to reboot after kernel panic' to '/proc/sys/kernel/panic': Invalid argument Aug 6 14:30:02 systemd[1]:

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

Hi Paul, You have applied a wrong ExitPolicy entry somewhere in your torrc for the default instance. You wrote "ExitPolicy reject x.x.x.x/80" though most probably you wanted to block the port 80 on a specific address, so you have to provide "ExitPolicy reject x.x.x.x:80" instead, with a

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

I am inexperienced an have probably the same problem after upgrading to 0.2.8.6. Even after reboot my second instance Tor-tor2 is running while the default service is exiting - syslog looks like this: Aug 6 12:11:33 tor[542]: Aug 06 12:11:33.744 [notice] Tor v0.2.8.6 (git-b88847615faea7c8)

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

made a ticket: https://trac.torproject.org/projects/tor/ticket/19847 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

> So there is no way to disable the default instance using systemctl after all? To answer my own question: systemctl mask tor@default disables the default instance for real. ..but I'm still curious why tor@default is a static unit (without [Install] section)

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

Am 05.08.2016 um 18:27 schrieb tor relay: > Also: you can not start/stop/restart tor.service separately without > leaving all other tor instances untouched. tor.service is *not* the default service. tor.service is the collection of all service instances. >>> >>> >>> Gosh,

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

> > > > Also: you can not start/stop/restart tor.service separately without > > > > leaving all other tor instances untouched. > > > > > > tor.service is *not* the default service. tor.service is the collection > > > of all service instances. > > > > > > Gosh, you are right there is

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

On Fri, 05 Aug 2016, tor relay wrote: > > > On August 5, 2016 at 1:24 PM Peter Palfrader wrote: > > > > > > On Fri, 05 Aug 2016, tor relay wrote: > > > > > Also: you can not start/stop/restart tor.service separately without > > > leaving all other tor instances

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

> On August 5, 2016 at 1:24 PM Peter Palfrader wrote: > > > On Fri, 05 Aug 2016, tor relay wrote: > > > Also: you can not start/stop/restart tor.service separately without leaving > > all other tor instances untouched. > > tor.service is *not* the default service.

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

On Fri, 05 Aug 2016, tor relay wrote: > this has certainly not been the case with 0.2.7.6. You are mistaken. Nothing in that regard has changed for 0.2.8.x -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

On Fri, 05 Aug 2016, tor relay wrote: > Also: you can not start/stop/restart tor.service separately without leaving > all other tor instances untouched. tor.service is *not* the default service. tor.service is the collection of all service instances. HAND. -- |

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

> > Why this hack (disable a service by moving away its config) and not the > more clean approach like the one take by the RPM maintainer? > ..that allows one to manage (start/stop/enable/disable) each service separately using standard tools and methodologies (and not service specific

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

> > On August 4, 2016 at 10:23 AM Peter Palfrader > wrote: > > On Thu, 04 Aug 2016, tor relay wrote: > > > > > > > > > > > > On August 3, 2016 at 11:51 PM Green Dream > > > wrote: > > > > > >

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

On Thu, 04 Aug 2016, tor relay wrote: > > > On August 3, 2016 at 11:51 PM Green Dream wrote: > > > > Sorry, I didn't understand that your daemon didn't restart after the > > upgrade. I ran through the upgrade on 2 relays, and apt started the service > >

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

https://trac.torproject.org/projects/tor/ticket/19825___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

> On August 3, 2016 at 11:51 PM Green Dream wrote: > > Sorry, I didn't understand that your daemon didn't restart after the > upgrade. I ran through the upgrade on 2 relays, and apt started the service > post-upgrade on both. > > > Since it is reproducible in

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

Sorry, I didn't understand that your daemon didn't restart after the upgrade. I ran through the upgrade on 2 relays, and apt started the service post-upgrade on both. ___ tor-relays mailing list tor-relays@lists.torproject.org

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

> On August 3, 2016 at 11:04 PM Green Dream wrote: > > > > When upgrading, all running tor instances are stopped (not restarted, > as expected) > > > syslog shows: > > > Interrupt: we have stopped accepting new connections, and will shut > down in 30

Re: [tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

> When upgrading, all running tor instances are stopped (not restarted, as expected) > syslog shows: > Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now. > Clean shutdown finished. Exiting. > (problem is reproducible) I just

[tor-relays] experiences with debian tor 0.2.8.6 package from deb.torproject.org

Hi, I'm running a relay on debian jessie using packages from deb.torproject.org. I want to share the problems I had so others are aware of them when upgrading their relays. While upgrading from 0.2.7.6 to 0.2.8.6 via apt-get, I did a tail -f syslog to make sure I notice problems during the