Hi,
With Debian Jessie and systemd, we can have multiple instances of Tor. But I cannot find any documentation about how to do that.
Can someone tel me where to find some documentation (and not an alternative to have multiple instances). please? Else, can someone explain me how to do that if there is not documentation?
Thanks and best regards.
On Tue, 28 Jun 2016, Patrick ZAJDA wrote:
With Debian Jessie and systemd, we can have multiple instances of Tor. But I cannot find any documentation about how to do that.
Can someone tel me where to find some documentation (and not an alternative to have multiple instances). please? Else, can someone explain me how to do that if there is not documentation?
Have you tried the tor-instance-create manpage?
Hi Peter,
I strangely didn't find it before. Great, thanks!
The only thing I found before was the ticket talking about putting files in /etc/tor/enabled.
Best regards,
Patrick
Peter Palfrader:
On Tue, 28 Jun 2016, Patrick ZAJDA wrote:
With Debian Jessie and systemd, we can have multiple instances of Tor. But I cannot find any documentation about how to do that.
Can someone tel me where to find some documentation (and not an alternative to have multiple instances). please? Else, can someone explain me how to do that if there is not documentation?
Have you tried the tor-instance-create manpage?
Hi Patrick,
I do have the same issue with Debian, but didn’t find any documentation that worked really. Could you please let me know in detail what you did, if it is going well with you?
Thank you -best regards
Paul
Am 28.06.2016 um 10:37 schrieb Patrick ZAJDA:
Hi Peter,
I strangely didn't find it before. Great, thanks!
The only thing I found before was the ticket talking about putting files in /etc/tor/enabled.
Best regards,
Patrick
Peter Palfrader:
On Tue, 28 Jun 2016, Patrick ZAJDA wrote:
With Debian Jessie and systemd, we can have multiple instances of Tor. But I cannot find any documentation about how to do that.
Can someone tel me where to find some documentation (and not an alternative to have multiple instances). please? Else, can someone explain me how to do that if there is not documentation?
Have you tried the tor-instance-create manpage?
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi,
I do have the same issue with Debian, but didn’t find any documentation that worked really.
as previously pointed out already you might look at the tor-instance-create man page
https://gitweb.torproject.org/debian/tor.git/tree/debian/tor-instance-create...
If you have specific problem people might be able to give more specific help.
Could you please let me know in detail what you did, if it is going well with you?
Hi,
thank you for that link.
Unfortunately I have to out myself as I am a newbe and don’t know how to get it working.
I can see - the tool https://gitweb.torproject.org/debian/tor.git/tree/debian/tor-instance-create .
Do I have to download it? If so where to?
Sorry cant be more precise with my questions.
Am 01.07.2016 um 22:26 schrieb nusenu:
Hi,
I do have the same issue with Debian, but didn’t find any documentation that worked really.
as previously pointed out already you might look at the tor-instance-create man page
https://gitweb.torproject.org/debian/tor.git/tree/debian/tor-instance-create...
If you have specific problem people might be able to give more specific help.
Could you please let me know in detail what you did, if it is going well with you?
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
thank you for that link.
Unfortunately I have to out myself as I am a newbe and don’t know how to get it working.
I can see - the tool https://gitweb.torproject.org/debian/tor.git/tree/debian/tor-instance-create .
Do I have to download it? If so where to?
Sorry cant be more precise with my questions.
This "tool" comes with the tor package (from torproject debian repository), so if you installed tor from there you should have it already.
Ok - I do have it and I installed a second instance called "tor2".
I can control the first instance of Tor as usual with arm but how can I now control the running of "tor2" with arm?
When calling arm with "sudo -u _tor-tor2 arm" I get asked for a Controller password even while having a HashedControlPassword in place?
What are the other needed settings apart from the relay specific ones in the torrc file from "tor2" to get it controlled by arm?
Could somebody please give an example?
Thank you all, Paul.
these are my current settings:
SocksPort auto RunAsDaemon 0 Log notice file /var/log/tor/notices2.log ControlPort 9052 HashedControlPassword xx:xxxxxxxxxx Nickname test2 RelayBandwidthRate 500 KB RelayBandwidthBurst 800 KB
Am 01.07.2016 um 23:28 schrieb nusenu:
thank you for that link.
Unfortunately I have to out myself as I am a newbe and don’t know how to get it working.
I can see - the tool https://gitweb.torproject.org/debian/tor.git/tree/debian/tor-instance-create .
Do I have to download it? If so where to?
Sorry cant be more precise with my questions.
This "tool" comes with the tor package (from torproject debian repository), so if you installed tor from there you should have it already.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Ok - I do have it and I installed a second instance called "tor2".
I can control the first instance of Tor as usual with arm but how can I now control the running of "tor2" with arm?
When calling arm with "sudo -u _tor-tor2 arm"
don't run arm as the tor user, Roger tells you why: https://lists.torproject.org/pipermail/tor-relays/2016-May/009259.html
since your second tor instance waits on 9052 for incoming controlport connections you have to tell arm about it
arm -i 9052
don't run arm as the tor user, Roger tells you why: https://lists.torproject.org/pipermail/tor-relays/2016-May/009259.html
Interesting. I didn't know this, and I've always used "sudo -u" as well. Thanks for sharing.
For the archives, the link above ultimately leads here: https://www.torproject.org/docs/tor-relay-debian#after (See step 13). The crux of it:
as the user that will be running arm, run "sudo adduser $USER debian-tor"
to add your user to the debian-tor group so it can reach Tor's controlsocket. Then log out and log back in (so your user is actually in the group), and run "arm".
Does this apply only to Debian, or Linux in general?
On Saturday, July 2, 2016, Green Dream greendream848@gmail.com wrote:
don't run arm as the tor user, Roger tells you why:
https://lists.torproject.org/pipermail/tor-relays/2016-May/009259.html
Interesting. I didn't know this, and I've always used "sudo -u" as well. Thanks for sharing.
For the archives, the link above ultimately leads here: https://www.torproject.org/docs/tor-relay-debian#after (See step 13). The crux of it:
as the user that will be running arm, run "sudo adduser $USER debian-tor"
to add your user to the debian-tor group so it can reach Tor's controlsocket. Then log out and log back in (so your user is actually in the group), and run "arm".
Still unsuccessful, even after reboot -here is what I did:
sudo tor-instance-create tor2
sudo adduser xxx _tor-tor2
sudo systemctl start tor@tor2
Job for tor@tor2.service failed. See 'systemctl status tor@tor2.service' and 'journalctl -xn' for details.
xxx@xxx:~$ systemctl status tor@tor2.service ● tor@tor2.service - 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)
Process: 707 ExecStartPre=/usr/bin/tor --defaults-torrc /var/run/tor-instances/%i.defaults -f /etc/tor/instances/%i/torrc --verify-config (code=exited, status=0/SUCCESS)
Process: 704 ExecStartPre=/bin/sed -e s/@@NAME@@/%i/g; w /var/run/tor-instances/%i.defaults /usr/share/tor/tor-service-defaults-torrc-instances (code=exited, status=0/SUCCESS)
Process: 703 ExecStartPre=/usr/bin/install -Z -m 02750 -o _tor-%i -g _tor-%i -d /var/run/tor-instances/%i (code=exited, status=0/SUCCESS)
Main PID: 710 (code=exited, status=1/FAILURE)
Am 02.07.2016 um 16:02 schrieb pa011:
Ok - I do have it and I installed a second instance called "tor2".
I can control the first instance of Tor as usual with arm but how can I now control the running of "tor2" with arm?
When calling arm with "sudo -u _tor-tor2 arm" I get asked for a Controller password even while having a HashedControlPassword in place?
What are the other needed settings apart from the relay specific ones in the torrc file from "tor2" to get it controlled by arm?
Could somebody please give an example?
Thank you all, Paul.
these are my current settings:
SocksPort auto RunAsDaemon 0 Log notice file /var/log/tor/notices2.log ControlPort 9052 HashedControlPassword xx:xxxxxxxxxx Nickname test2 RelayBandwidthRate 500 KB RelayBandwidthBurst 800 KB
Am 01.07.2016 um 23:28 schrieb nusenu:
thank you for that link.
Unfortunately I have to out myself as I am a newbe and don’t know how to get it working.
I can see - the tool https://gitweb.torproject.org/debian/tor.git/tree/debian/tor-instance-create .
Do I have to download it? If so where to?
Sorry cant be more precise with my questions.
This "tool" comes with the tor package (from torproject debian repository), so if you installed tor from there you should have it already.
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
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@tor2.service failed. See 'systemctl status tor@tor2.service' and 'journalctl -xn' for details.
xxx@xxx:~$ systemctl status tor@tor2.service ● tor@tor2.service - 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
Ok - "Log notice file /var/log/tor/notices2.log" removed from torrc, but that doesn’t influence the error message from systemctl in no way.
Still not working !
Does the machine on which I like to add this second instance have more than one core??
I don’t want to use ansible at the moment - that seems far to much for me currently - maybe three steps ahead :-)
Is there possibly an other way instead of two Tor instances running to convince the bandwidth-authority to take more use of a 250Mbit/s line for an Exit instead of just 40-50 Mbit/s?
Am 02.07.2016 um 18:21 schrieb nusenu:
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@tor2.service failed. See 'systemctl status tor@tor2.service' and 'journalctl -xn' for details.
xxx@xxx:~$ systemctl status tor@tor2.service ● tor@tor2.service - 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
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Sat, 02 Jul 2016, pa011 wrote:
Ok - "Log notice file /var/log/tor/notices2.log" removed from torrc, but that doesn’t influence the error message from systemctl in no way.
Still not working !
Please try to provide at least some more useful information. (Also, please stop top posting and full quoting).
What does /var/log/syslog say?
What does journald -f say while you *restart* the service?
Am 02.07.2016 um 20:14 schrieb Peter Palfrader:
On Sat, 02 Jul 2016, pa011 wrote:
Ok - "Log notice file /var/log/tor/notices2.log" removed from torrc, but that doesn’t influence the error message from systemctl in no way.
Still not working !
Please try to provide at least some more useful information. (Also, please stop top posting and full quoting).
What does /var/log/syslog say?
What does journald -f say while you *restart* the service?
Hi Peter,
the system is Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u2 (2016-06-25) with Tor 0.2.7.6
"journald -f" brings up "command not found"
here is a copy of the syslog:
Jul 3 12:09:27 sed[4525]: DataDirectory /var/lib/tor-instances/tor2 Jul 3 12:09:27 sed[4525]: PidFile /var/run/tor-instances/tor2/tor.pid Jul 3 12:09:27 sed[4525]: RunAsDaemon 0 Jul 3 12:09:27 sed[4525]: User _tor-tor2 Jul 3 12:09:27 sed[4525]: SyslogIdentityTag tor2 Jul 3 12:09:27 sed[4525]: ControlSocket /var/run/tor-instances/tor2/control Jul 3 12:09:27 sed[4525]: ControlSocketsGroupWritable 1 Jul 3 12:09:27 sed[4525]: CookieAuthentication 1 Jul 3 12:09:27 sed[4525]: CookieAuthFileGroupReadable 1 Jul 3 12:09:27 sed[4525]: CookieAuthFile /var/run/tor-instances/tor2/control.authcookie Jul 3 12:09:27 sed[4525]: Log notice syslog Jul 3 12:09:27 tor[4528]: Jul 03 12:09:27.541 [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. Jul 3 12:09:27 tor[4528]: Jul 03 12:09:27.542 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jul 3 12:09:27 tor[4528]: Jul 03 12:09:27.542 [notice] Read configuration file "/var/run/tor-instances/tor2.defaults". Jul 3 12:09:27 tor[4528]: Jul 03 12:09:27.542 [notice] Read configuration file "/etc/tor/instances/tor2/torrc". Jul 3 12:09:27 tor[4528]: Jul 03 12:09:27.544 [notice] Based on detected system memory MaxMemInQueues is set to 370 MB. You can override this by setting MaxMemInQueues by hand. Jul 3 12:09:27 tor[4528]: Jul 03 12:09:27.545 [notice] Not disabling debugger attaching for unprivileged users. Jul 3 12:09:27 tor[4528]: Configuration was valid Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.583 [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. Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.583 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.584 [notice] Read configuration file "/var/run/tor-instances/tor2.defaults". Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.584 [notice] Read configuration file "/etc/tor/instances/tor2/torrc". Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.587 [notice] Based on detected system memory MaxMemInQueues is set to 370 MB. You can override this by setting MaxMemInQueues by hand. Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.588 [notice] Opening Socks listener on 127.0.0.1:0 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.588 [notice] Socks listener listening on port 52394. Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.589 [notice] Opening Control listener on 127.0.0.1:9052 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening Control listener on /var/run/tor-instances/tor2/control Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening OR listener on 0.0.0.0:443 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:443: Address already in use. Is Tor already running? Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening Directory listener on 0.0.0.0:80 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:80: Address already in use. Is Tor already running? Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.591 [notice] Closing partially-constructed Socks listener on 127.0.0.1:52394 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.591 [notice] Closing partially-constructed Control listener on 127.0.0.1:9052 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.591 [notice] Closing partially-constructed Control listener on /var/run/tor-instances/tor2/control:0 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.591 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.591 [err] Reading config failed--see warnings above. Jul 3 12:09:27 systemd[1]: tor@tor2.service: main process exited code=exited status=1/FAILURE Jul 3 12:09:27 systemd[1]: Failed to start Anonymizing overlay network for TCP (instance tor2). Jul 3 12:09:27 systemd[1]: Unit tor@tor2.service entered failed state. Jul 3 12:09:27 sed[4539]: DataDirectory /var/lib/tor-instances/tor2 Jul 3 12:09:27 sed[4539]: PidFile /var/run/tor-instances/tor2/tor.pid Jul 3 12:09:27 sed[4539]: RunAsDaemon 0 Jul 3 12:09:27 sed[4539]: User _tor-tor2 Jul 3 12:09:27 sed[4539]: SyslogIdentityTag tor2 Jul 3 12:09:27 sed[4539]: ControlSocket /var/run/tor-instances/tor2/control Jul 3 12:09:27 sed[4539]: ControlSocketsGroupWritable 1 Jul 3 12:09:27 sed[4539]: CookieAuthentication 1 Jul 3 12:09:27 sed[4539]: CookieAuthFileGroupReadable 1 Jul 3 12:09:27 sed[4539]: CookieAuthFile /var/run/tor-instances/tor2/control.authcookie Jul 3 12:09:27 sed[4539]: Log notice syslog Jul 3 12:09:27 tor[4542]: Jul 03 12:09:27.775 [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. Jul 3 12:09:27 tor[4542]: Jul 03 12:09:27.775 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jul 3 12:09:27 tor[4542]: Jul 03 12:09:27.775 [notice] Read configuration file "/var/run/tor-instances/tor2.defaults". Jul 3 12:09:27 tor[4542]: Jul 03 12:09:27.775 [notice] Read configuration file "/etc/tor/instances/tor2/torrc". Jul 3 12:09:27 tor[4542]: Jul 03 12:09:27.777 [notice] Based on detected system memory MaxMemInQueues is set to 370 MB. You can override this by setting MaxMemInQueues by hand. Jul 3 12:09:27 tor[4542]: Jul 03 12:09:27.779 [notice] Not disabling debugger attaching for unprivileged users. Jul 3 12:09:27 tor[4542]: Configuration was valid Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.812 [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. Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.812 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.813 [notice] Read configuration file "/var/run/tor-instances/tor2.defaults". Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.816 [notice] Read configuration file "/etc/tor/instances/tor2/torrc". Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.819 [notice] Based on detected system memory MaxMemInQueues is set to 370 MB. You can override this by setting MaxMemInQueues by hand. Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.820 [notice] Opening Socks listener on 127.0.0.1:0 Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.820 [notice] Socks listener listening on port 50855. Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.820 [notice] Opening Control listener on 127.0.0.1:9052 Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.820 [notice] Opening Control listener on /var/run/tor-instances/tor2/control Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.821 [notice] Opening OR listener on 0.0.0.0:443 Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.821 [warn] Could not bind to 0.0.0.0:443: Address already in use. Is Tor already running? Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.821 [notice] Opening Directory listener on 0.0.0.0:80 Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.821 [warn] Could not bind to 0.0.0.0:80: Address already in use. Is Tor already running? Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.821 [notice] Closing partially-constructed Socks listener on 127.0.0.1:50855 Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.821 [notice] Closing partially-constructed Control listener on 127.0.0.1:9052 Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.822 [notice] Closing partially-constructed Control listener on /var/run/tor-instances/tor2/control:0 Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.822 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Jul 3 12:09:27 tor[4545]: Jul 03 12:09:27.822 [err] Reading config failed--see warnings above. Jul 3 12:09:27 systemd[1]: tor@tor2.service: main process exited code=exited status=1/FAILURE Jul 3 12:09:27 systemd[1]: Failed to start Anonymizing overlay network for TCP (instance tor2). Jul 3 12:09:27 systemd[1]: Unit tor@tor2.service entered failed state. Jul 3 12:09:27 sed[4552]: DataDirectory /var/lib/tor-instances/tor2 Jul 3 12:09:27 sed[4552]: PidFile /var/run/tor-instances/tor2/tor.pid Jul 3 12:09:27 sed[4552]: RunAsDaemon 0 Jul 3 12:09:27 sed[4552]: User _tor-tor2 Jul 3 12:09:27 sed[4552]: SyslogIdentityTag tor2 Jul 3 12:09:27 sed[4552]: ControlSocket /var/run/tor-instances/tor2/control Jul 3 12:09:27 sed[4552]: ControlSocketsGroupWritable 1 Jul 3 12:09:27 sed[4552]: CookieAuthentication 1 Jul 3 12:09:27 sed[4552]: CookieAuthFileGroupReadable 1 Jul 3 12:09:27 sed[4552]: CookieAuthFile /var/run/tor-instances/tor2/control.authcookie Jul 3 12:09:27 sed[4552]: Log notice syslog Jul 3 12:09:28 tor[4555]: Jul 03 12:09:28.015 [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. Jul 3 12:09:28 tor[4555]: Jul 03 12:09:28.015 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jul 3 12:09:28 tor[4555]: Jul 03 12:09:28.015 [notice] Read configuration file "/var/run/tor-instances/tor2.defaults". Jul 3 12:09:28 tor[4555]: Jul 03 12:09:28.015 [notice] Read configuration file "/etc/tor/instances/tor2/torrc". Jul 3 12:09:28 tor[4555]: Jul 03 12:09:28.018 [notice] Based on detected system memory MaxMemInQueues is set to 370 MB. You can override this by setting MaxMemInQueues by hand. Jul 3 12:09:28 tor[4555]: Jul 03 12:09:28.019 [notice] Not disabling debugger attaching for unprivileged users. Jul 3 12:09:28 tor[4555]: Configuration was valid Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.047 [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. Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.047 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.048 [notice] Read configuration file "/var/run/tor-instances/tor2.defaults". Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.048 [notice] Read configuration file "/etc/tor/instances/tor2/torrc". Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.050 [notice] Based on detected system memory MaxMemInQueues is set to 370 MB. You can override this by setting MaxMemInQueues by hand. Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.051 [notice] Opening Socks listener on 127.0.0.1:0 Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.052 [notice] Socks listener listening on port 33251. Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.052 [notice] Opening Control listener on 127.0.0.1:9052 Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.053 [notice] Opening Control listener on /var/run/tor-instances/tor2/control Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.053 [notice] Opening OR listener on 0.0.0.0:443 Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.053 [warn] Could not bind to 0.0.0.0:443: Address already in use. Is Tor already running? Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.053 [notice] Opening Directory listener on 0.0.0.0:80 Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.054 [warn] Could not bind to 0.0.0.0:80: Address already in use. Is Tor already running? Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.054 [notice] Closing partially-constructed Socks listener on 127.0.0.1:33251 Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.054 [notice] Closing partially-constructed Control listener on 127.0.0.1:9052 Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.054 [notice] Closing partially-constructed Control listener on /var/run/tor-instances/tor2/control:0 Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.054 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Jul 3 12:09:28 tor[4558]: Jul 03 12:09:28.054 [err] Reading config failed--see warnings above. Jul 3 12:09:28 systemd[1]: tor@tor2.service: main process exited code=exited status=1/FAILURE Jul 3 12:09:28 systemd[1]: Failed to start Anonymizing overlay network for TCP (instance tor2). Jul 3 12:09:28 systemd[1]: Unit tor@tor2.service entered failed state. Jul 3 12:09:28 sed[4565]: DataDirectory /var/lib/tor-instances/tor2 Jul 3 12:09:28 sed[4565]: PidFile /var/run/tor-instances/tor2/tor.pid Jul 3 12:09:28 sed[4565]: RunAsDaemon 0 Jul 3 12:09:28 sed[4565]: User _tor-tor2 Jul 3 12:09:28 sed[4565]: SyslogIdentityTag tor2 Jul 3 12:09:28 sed[4565]: ControlSocket /var/run/tor-instances/tor2/control Jul 3 12:09:28 sed[4565]: ControlSocketsGroupWritable 1 Jul 3 12:09:28 sed[4565]: CookieAuthentication 1 Jul 3 12:09:28 sed[4565]: CookieAuthFileGroupReadable 1 Jul 3 12:09:28 sed[4565]: CookieAuthFile /var/run/tor-instances/tor2/control.authcookie Jul 3 12:09:28 sed[4565]: Log notice syslog Jul 3 12:09:28 tor[4568]: Jul 03 12:09:28.260 [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. Jul 3 12:09:28 tor[4568]: Jul 03 12:09:28.261 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jul 3 12:09:28 tor[4568]: Jul 03 12:09:28.261 [notice] Read configuration file "/var/run/tor-instances/tor2.defaults". Jul 3 12:09:28 tor[4568]: Jul 03 12:09:28.261 [notice] Read configuration file "/etc/tor/instances/tor2/torrc". Jul 3 12:09:28 tor[4568]: Jul 03 12:09:28.263 [notice] Based on detected system memory MaxMemInQueues is set to 370 MB. You can override this by setting MaxMemInQueues by hand. Jul 3 12:09:28 tor[4568]: Jul 03 12:09:28.264 [notice] Not disabling debugger attaching for unprivileged users. Jul 3 12:09:28 tor[4568]: Configuration was valid Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.302 [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. Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.302 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.302 [notice] Read configuration file "/var/run/tor-instances/tor2.defaults". Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.302 [notice] Read configuration file "/etc/tor/instances/tor2/torrc". Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.305 [notice] Based on detected system memory MaxMemInQueues is set to 370 MB. You can override this by setting MaxMemInQueues by hand. Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.306 [notice] Opening Socks listener on 127.0.0.1:0 Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.306 [notice] Socks listener listening on port 56650. Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.306 [notice] Opening Control listener on 127.0.0.1:9052 Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.308 [notice] Opening Control listener on /var/run/tor-instances/tor2/control Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.308 [notice] Opening OR listener on 0.0.0.0:443 Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.308 [warn] Could not bind to 0.0.0.0:443: Address already in use. Is Tor already running? Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.308 [notice] Opening Directory listener on 0.0.0.0:80 Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.309 [warn] Could not bind to 0.0.0.0:80: Address already in use. Is Tor already running? Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.309 [notice] Closing partially-constructed Socks listener on 127.0.0.1:56650 Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.309 [notice] Closing partially-constructed Control listener on 127.0.0.1:9052 Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.309 [notice] Closing partially-constructed Control listener on /var/run/tor-instances/tor2/control:0 Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.309 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Jul 3 12:09:28 tor[4571]: Jul 03 12:09:28.309 [err] Reading config failed--see warnings above. Jul 3 12:09:28 systemd[1]: tor@tor2.service: main process exited code=exited status=1/FAILURE Jul 3 12:09:28 systemd[1]: Failed to start Anonymizing overlay network for TCP (instance tor2). Jul 3 12:09:28 systemd[1]: Unit tor@tor2.service entered failed state. Jul 3 12:09:28 sed[4578]: DataDirectory /var/lib/tor-instances/tor2 Jul 3 12:09:28 sed[4578]: PidFile /var/run/tor-instances/tor2/tor.pid Jul 3 12:09:28 sed[4578]: RunAsDaemon 0 Jul 3 12:09:28 sed[4578]: User _tor-tor2 Jul 3 12:09:28 sed[4578]: SyslogIdentityTag tor2 Jul 3 12:09:28 sed[4578]: ControlSocket /var/run/tor-instances/tor2/control Jul 3 12:09:28 sed[4578]: ControlSocketsGroupWritable 1 Jul 3 12:09:28 sed[4578]: CookieAuthentication 1 Jul 3 12:09:28 sed[4578]: CookieAuthFileGroupReadable 1 Jul 3 12:09:28 sed[4578]: CookieAuthFile /var/run/tor-instances/tor2/control.authcookie Jul 3 12:09:28 sed[4578]: Log notice syslog Jul 3 12:09:28 tor[4581]: Jul 03 12:09:28.512 [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. Jul 3 12:09:28 tor[4581]: Jul 03 12:09:28.512 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jul 3 12:09:28 tor[4581]: Jul 03 12:09:28.513 [notice] Read configuration file "/var/run/tor-instances/tor2.defaults". Jul 3 12:09:28 tor[4581]: Jul 03 12:09:28.513 [notice] Read configuration file "/etc/tor/instances/tor2/torrc". Jul 3 12:09:28 tor[4581]: Jul 03 12:09:28.518 [notice] Based on detected system memory MaxMemInQueues is set to 370 MB. You can override this by setting MaxMemInQueues by hand. Jul 3 12:09:28 tor[4581]: Jul 03 12:09:28.519 [notice] Not disabling debugger attaching for unprivileged users. Jul 3 12:09:28 tor[4581]: Configuration was valid Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.550 [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. Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.550 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.550 [notice] Read configuration file "/var/run/tor-instances/tor2.defaults". Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.551 [notice] Read configuration file "/etc/tor/instances/tor2/torrc". Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.553 [notice] Based on detected system memory MaxMemInQueues is set to 370 MB. You can override this by setting MaxMemInQueues by hand. Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.554 [notice] Opening Socks listener on 127.0.0.1:0 Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.558 [notice] Socks listener listening on port 34276. Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.558 [notice] Opening Control listener on 127.0.0.1:9052 Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.558 [notice] Opening Control listener on /var/run/tor-instances/tor2/control Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.559 [notice] Opening OR listener on 0.0.0.0:443 Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.560 [warn] Could not bind to 0.0.0.0:443: Address already in use. Is Tor already running? Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.561 [notice] Opening Directory listener on 0.0.0.0:80 Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.561 [warn] Could not bind to 0.0.0.0:80: Address already in use. Is Tor already running? Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.561 [notice] Closing partially-constructed Socks listener on 127.0.0.1:34276 Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.561 [notice] Closing partially-constructed Control listener on 127.0.0.1:9052 Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.561 [notice] Closing partially-constructed Control listener on /var/run/tor-instances/tor2/control:0 Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.562 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Jul 3 12:09:28 tor[4584]: Jul 03 12:09:28.562 [err] Reading config failed--see warnings above. Jul 3 12:09:28 systemd[1]: tor@tor2.service: main process exited code=exited status=1/FAILURE Jul 3 12:09:28 systemd[1]: Failed to start Anonymizing overlay network for TCP (instance tor2). Jul 3 12:09:28 systemd[1]: Unit tor@tor2.service entered failed state. Jul 3 12:09:28 systemd[1]: tor@tor2.service start request repeated too quickly refusing to start. Jul 3 12:09:28 systemd[1]: Failed to start Anonymizing overlay network for TCP (instance tor2). Jul 3 12:09:28 systemd[1]: Unit tor@tor2.service entered failed state.
Let me read this for you.
On Sun, 03 Jul 2016, pa011 wrote:
Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening OR listener on 0.0.0.0:443 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:443: Address already in use. Is Tor already running? Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening Directory listener on 0.0.0.0:80 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:80: Address already in use. Is Tor already running?
HTH.
Am 03.07.2016 um 13:03 schrieb Peter Palfrader:
Let me read this for you.
On Sun, 03 Jul 2016, pa011 wrote:
Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening OR listener on 0.0.0.0:443 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:443: Address already in use. Is Tor already running? Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening Directory listener on 0.0.0.0:80 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:80: Address already in use. Is Tor already running?
HTH.
Hi Peter,
sorry that might bring light to you - I even have to https://www.acronymfinder.com/Slang/HtH.html , because I am new to this business :-(
Would be very kind if you could explain a bit what I should do and why if you got some spare time.
Thanks a lot - Paul
On Sun, 03 Jul 2016, pa011 wrote:
Am 03.07.2016 um 13:03 schrieb Peter Palfrader:
Let me read this for you.
On Sun, 03 Jul 2016, pa011 wrote:
Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening OR listener on 0.0.0.0:443 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:443: Address already in use. Is Tor already running? Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening Directory listener on 0.0.0.0:80 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:80: Address already in use. Is Tor already running?
HTH.
[Hope that helps]
Would be very kind if you could explain a bit what I should do and why if you got some spare time.
It appears you have told your (second?) tor to listen on port 443. You have something else on your machine already using Port 443.
(It's a bit hard to read, since you line wrapped the log output.)
Am 03.07.2016 um 13:31 schrieb Peter Palfrader:
On Sun, 03 Jul 2016, pa011 wrote:
Am 03.07.2016 um 13:03 schrieb Peter Palfrader:
Let me read this for you.
On Sun, 03 Jul 2016, pa011 wrote:
Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening OR listener on 0.0.0.0:443 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:443: Address already in use. Is Tor already running? Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening Directory listener on 0.0.0.0:80 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:80: Address already in use. Is Tor already running?
HTH.
[Hope that helps]
Would be very kind if you could explain a bit what I should do and why if you got some spare time.
It appears you have told your (second?) tor to listen on port 443. You have something else on your machine already using Port 443.
(It's a bit hard to read, since you line wrapped the log output.)
Sorry for the wrapping - I hopefully convinced Thunderbird not to do it any more :-)
Yes, the first tor instance is using the ports 80 and 443 - I thought they could be shared between the instances. So what setting should I use then in the second torrc please?
TAM ;-)
Op 03/07/16 om 13:52 schreef pa011:
Am 03.07.2016 um 13:31 schrieb Peter Palfrader:
On Sun, 03 Jul 2016, pa011 wrote:
Am 03.07.2016 um 13:03 schrieb Peter Palfrader:
Let me read this for you.
On Sun, 03 Jul 2016, pa011 wrote:
Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening OR listener on 0.0.0.0:443 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:443: Address already in use. Is Tor already running? Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening Directory listener on 0.0.0.0:80 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:80: Address already in use. Is Tor already running?
HTH.
[Hope that helps]
Would be very kind if you could explain a bit what I should do and why if you got some spare time.
It appears you have told your (second?) tor to listen on port 443. You have something else on your machine already using Port 443.
(It's a bit hard to read, since you line wrapped the log output.)
Sorry for the wrapping - I hopefully convinced Thunderbird not to do it any more :-)
Yes, the first tor instance is using the ports 80 and 443 - I thought they could be shared between the instances. So what setting should I use then in the second torrc please?
TAM ;-)
Try 81/444
Or 8080/9010
Or 9030/9010
Up to you, really :-)
Tom
On Sun, 03 Jul 2016, pa011 wrote:
Am 03.07.2016 um 13:31 schrieb Peter Palfrader:
On Sun, 03 Jul 2016, pa011 wrote:
Am 03.07.2016 um 13:03 schrieb Peter Palfrader:
Let me read this for you.
On Sun, 03 Jul 2016, pa011 wrote:
Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening OR listener on 0.0.0.0:443 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:443: Address already in use. Is Tor already running? Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening Directory listener on 0.0.0.0:80 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:80: Address already in use. Is Tor already running?
HTH.
[Hope that helps]
Would be very kind if you could explain a bit what I should do and why if you got some spare time.
It appears you have told your (second?) tor to listen on port 443. You have something else on your machine already using Port 443.
(It's a bit hard to read, since you line wrapped the log output.)
Sorry for the wrapping - I hopefully convinced Thunderbird not to do it any more :-)
Yes, the first tor instance is using the ports 80 and 443 - I thought they could be shared between the instances. So what setting should I use then in the second torrc please?
Pick different ports. Any that are free and that you like.
Am 03.07.2016 um 14:28 schrieb Peter Palfrader:
On Sun, 03 Jul 2016, pa011 wrote:
Am 03.07.2016 um 13:31 schrieb Peter Palfrader:
On Sun, 03 Jul 2016, pa011 wrote:
Am 03.07.2016 um 13:03 schrieb Peter Palfrader:
Let me read this for you.
On Sun, 03 Jul 2016, pa011 wrote:
Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening OR listener on 0.0.0.0:443 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:443: Address already in use. Is Tor already running? Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [notice] Opening Directory listener on 0.0.0.0:80 Jul 3 12:09:27 tor[4532]: Jul 03 12:09:27.590 [warn] Could not bind to 0.0.0.0:80: Address already in use. Is Tor already running?
HTH.
[Hope that helps]
Would be very kind if you could explain a bit what I should do and why if you got some spare time.
It appears you have told your (second?) tor to listen on port 443. You have something else on your machine already using Port 443.
(It's a bit hard to read, since you line wrapped the log output.)
Sorry for the wrapping - I hopefully convinced Thunderbird not to do it any more :-)
Yes, the first tor instance is using the ports 80 and 443 - I thought they could be shared between the instances. So what setting should I use then in the second torrc please?
Pick different ports. Any that are free and that you like.
Hey - great thanks especially to you Peter for your whole work on **tor-instance-create**
"top" and syslog and even atlas let me come to the conclusion that I have two running instances now :-)
Still open:
"arm -i 9052" - is asking for a Controller password while I have a HashedControlPassword in place ?
How to best separate the tor log files from both instances?
Still open:
"arm -i 9052" - is asking for a Controller password while I have a HashedControlPassword in place ?
if you configure tor to require a password for controlport access (that what HashedControlPassword is for), you will be asked for a password (expected behavior).
https://www.torproject.org/docs/tor-manual.html.en :
HashedControlPassword hashed_password
Allow connections on the control port if they present the password whose one-way hash is hashed_password. You can compute the hash of a password by running "tor --hash-password password". You can provide several acceptable passwords by using more than one HashedControlPassword line.
Am 03.07.2016 um 17:06 schrieb nusenu:
Still open:
"arm -i 9052" - is asking for a Controller password while I have a HashedControlPassword in place ?
if you configure tor to require a password for controlport access (that what HashedControlPassword is for), you will be asked for a password (expected behavior).
https://www.torproject.org/docs/tor-manual.html.en :
HashedControlPassword hashed_password
Allow connections on the control port if they present the password whose one-way hash is hashed_password. You can compute the hash of a password by running "tor --hash-password password". You can provide several acceptable passwords by using more than one HashedControlPassword line.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I do obviously have a different - maybe wrong - understanding of (expected behaviour).
I create with "tor --hash-password password" a hash and put it in my second instance /etc/tor/instances/tor2/torrc as "HashedControlPassword xx:xxxxxxx..". The ControlPort there is 9052
I do already have the same in my first instance /etc/tor/torrc where my ControlPort is 9051.
When I now start arm with just "arm" it is working well and showing up the usual window of my first instance -showing ControlPort 9051 in that window -without asking for a passwort, because it takes as I asume the hash out of the torrc file.
But if I do try to start arm with "arm -i 9051" I do get asked for a ControlPasswort - same if I do it with "arm -i 9052"?
So what is wrong in my understanding please?
Still open:
How to best separate the tor log files from both instances?
You can either 1) configure tor to log to specific log files (I wouldn't take that path since handling filesystem permissions properly for every instance is just messy [logrotate...]) or 2) you stick with the default configuration (all tor instances send their logs to syslog) and you tell syslog to create per-instance logfiles. 3) or keep them in a common file and use grep to look for the specific relevant instance.
On Debian tor instances tag their log entries with "Tor-<instancename>" by default. Something not available in vanilla tor 0.2.7.x (but will be in 0.2.8.x).
With that in mind you can go and tell syslog what to do:
:syslogtag, startswith, "Tor-tor2[" /var/log/tor/tor2.log
Note: The actual tag looks like Tor-tor2[1555] where 1555 is the process ID (PID), that is the reason you can*not* simply do :syslog, isequal, "Tor-tor2" /var/log/tor/tor2.log
Note2: That instance specific log file will "loose" the first ~10 log entries since they are not tagged.
https://www.torproject.org/docs/tor-manual-dev.html.en:
SyslogIdentityTag tag
When logging to syslog, adds a tag to the syslog identity such that log entries are marked with "Tor-tag". (Default: none)
On 07/02/2016 04:02 PM, pa011 wrote:
SocksPort auto RunAsDaemon 0 Log notice file /var/log/tor/notices2.log ControlPort 9052 HashedControlPassword xx:xxxxxxxxxx Nickname test2 RelayBandwidthRate 500 KB RelayBandwidthBurst 800 KB
This is lacking the configuration of a separate DataDirectory and PidFile, eg.:
DataDirectory /var/lib/tor/2 PidFile /var/run/tor/tor2.pid
On Sat, 02 Jul 2016, Moritz Bartl wrote:
On 07/02/2016 04:02 PM, pa011 wrote:
SocksPort auto RunAsDaemon 0 Log notice file /var/log/tor/notices2.log ControlPort 9052 HashedControlPassword xx:xxxxxxxxxx Nickname test2 RelayBandwidthRate 500 KB RelayBandwidthBurst 800 KB
This is lacking the configuration of a separate DataDirectory and PidFile, eg.:
DataDirectory /var/lib/tor/2 PidFile /var/run/tor/tor2.pid
These should not be added.
RunAsDaemon should also not be in that file, but at least it doesn't hurt.
SocksPort auto RunAsDaemon 0 Log notice file /var/log/tor/notices2.log ControlPort 9052 HashedControlPassword xx:xxxxxxxxxx Nickname test2 RelayBandwidthRate 500 KB RelayBandwidthBurst 800 KB
This is lacking the configuration of a separate DataDirectory and PidFile, eg.:
DataDirectory /var/lib/tor/2 PidFile /var/run/tor/tor2.pid
These should not be added.
To be a bit more verbose: On Debian the DataDirectory and PidFile settings are taken care of by the multi-instance systemd service file. The service generates a defaults torrc (--defaults-torrc) and the required folder before tor is started. That can be found at: /var/run/tor-instances/<instancename>.defaults
for the details you can have a look at the service file: https://gitweb.torproject.org/debian/tor.git/tree/debian/systemd/tor@.servic...
tor-relays@lists.torproject.org
-
Green Dream -
Marcel Krzystek -
Moritz Bartl -
nusenu -
pa011 -
Patrick ZAJDA -
Peter Palfrader -
Tom van der Woerdt