> Still unsuccessful, even after reboot -here is what I did: > > sudo tor-instance-create tor2 > > sudo adduser xxx _tor-tor2 no need to create that user manually, tor-instance-create does that > sudo systemctl start tor@tor2 > > Job for tor@xxxxxxxxxxxx failed. See 'systemctl status tor@xxxxxxxxxxxx' > and 'journalctl -xn' for details. > > xxx@xxx:~$ systemctl status tor@xxxxxxxxxxxx > â tor@xxxxxxxxxxxx - Anonymizing overlay network for TCP (instance tor2) > Loaded: loaded (/lib/systemd/system/tor@.service; disabled) > Active: failed (Result: start-limit) since Sat 2016-07-02 17:37:32 > CEST; 12s ago > > Process: 710 ExecStart=/usr/bin/tor --defaults-torrc > /var/run/tor-instances/%i.defaults -f /etc/tor/instances/%i/torrc > (code=exited, status=1/FAILURE) > >> these are my current settings: >> >> SocksPort auto >> RunAsDaemon 0 >> Log notice file /var/log/tor/notices2.log This is a bad idea (file permissions), why did you add that Log line? I recommend you stick with the default behaviour (syslog), just remove that line. If you simply want to setup multiple tor instances on a debian 8 target machine, you might also just use ansible https://github.com/nusenu/ansible-relayor
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays