First off, will outline that I am very much a newbie, but was able to get a relay up and running on a Ubuntu machine. It was running fine for maybe 12 months (MelbTorBox), with a few resets and software updates along the way.
Just doing my bit to help the network.
Anyway, after the Ubuntu upgrade, I had to re-install TOR and I believed I did it basically the same way.
Unfortunately, that appears not to be the case. I've posted the error messages on the Ubuntu forum hoping to get assistance, but no joy: https://askubuntu.com/questions/1070469/18-04-tor-relay-error-could-not-bind...
I'm now coming to the experts to see if I can resurrect relay before I pull the pin on the idea.
I have BASIC Unix knowledge (I can type commands and that's about it). I think I might have a couple of copies installed in different places and I know I have the TOR browser installed (it works fine).
When I type 'nyx' it replies with: Unable to connect to tor. Maybe it's running without a ControlPort?
So I type 'tor' and get Sep 19 21:34:24.819 [notice] Tor 0.3.4.8 (git-5da0e95e4871a0a1) running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.0g, Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3. Sep 19 21:34:24.819 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Sep 19 21:34:24.819 [notice] Read configuration file "/etc/tor/torrc". Sep 19 21:34:24.823 [notice] Based on detected system memory, MaxMemInQueues is set to 2862 MB. You can override this by setting MaxMemInQueues by hand. Sep 19 21:34:24.824 [notice] Scheduler type KIST has been enabled. Sep 19 21:34:24.824 [notice] Opening Socks listener on 127.0.0.1:9050 Sep 19 21:34:24.824 [notice] Opening Control listener on 127.0.0.1:9051 Sep 19 21:34:24.824 [notice] Opening OR listener on 0.0.0.0:9001 Sep 19 21:34:24.824 [notice] Opening Directory listener on 0.0.0.0:9050 Sep 19 21:34:24.824 [warn] Could not bind to 0.0.0.0:9050: Address already in use. Is Tor already running? Sep 19 21:34:24.824 [notice] Closing partially-constructed Socks listener on 127.0.0.1:9050 Sep 19 21:34:24.824 [notice] Closing partially-constructed Control listener on 127.0.0.1:9051 Sep 19 21:34:24.824 [notice] Closing partially-constructed OR listener on 0.0.0.0:9001 Sep 19 21:34:24.824 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Sep 19 21:34:24.824 [err] Reading config failed--see warnings above.
I 'think' my original torrc file may have somehow survived the Ubuntu upgrade, but I don't know how as I did a wipe and re-install of Ubuntu. But when I edited it, there were my contact details sitting there.
Very appreciative of any help!
Thanks Ben.
Hi.
(Tor not TOR)
The log line:
Sep 19 21:34:24.824 [warn] Could not bind to 0.0.0.0:9050: Address already in use. Is Tor already running?
This means that tor cannot start because some other process is already bound to port 9050. Why not see which other process is bound to port 9050?
sudo netstat -tlpn or lsof -iTCP | grep 9050
btw typing "tor" into a server isn't the correct way to start tor. Usually on linux people use systemd to start tor:
systemctl start tor
I think the nyx error is pretty clear. Perhaps your tor isn't configured with a control port.
I hope this helps but if it doesn't then I hope someone else will be more helpful than I.
Cheers, David
On Wed, Sep 19, 2018 at 09:56:52PM +1000, Ben Riley wrote:
First off, will outline that I am very much a newbie, but was able to get a relay up and running on a Ubuntu machine. It was running fine for maybe 12 months (MelbTorBox), with a few resets and software updates along the way.
Just doing my bit to help the network.
Anyway, after the Ubuntu upgrade, I had to re-install TOR and I believed I did it basically the same way.
Unfortunately, that appears not to be the case. I've posted the error messages on the Ubuntu forum hoping to get assistance, but no joy: https://askubuntu.com/questions/1070469/18-04-tor-relay-error-could-not-bind...
I'm now coming to the experts to see if I can resurrect relay before I pull the pin on the idea.
I have BASIC Unix knowledge (I can type commands and that's about it). I think I might have a couple of copies installed in different places and I know I have the TOR browser installed (it works fine).
When I type 'nyx' it replies with: Unable to connect to tor. Maybe it's running without a ControlPort?
So I type 'tor' and get Sep 19 21:34:24.819 [notice] Tor 0.3.4.8 (git-5da0e95e4871a0a1) running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.0g, Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3. Sep 19 21:34:24.819 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Sep 19 21:34:24.819 [notice] Read configuration file "/etc/tor/torrc". Sep 19 21:34:24.823 [notice] Based on detected system memory, MaxMemInQueues is set to 2862 MB. You can override this by setting MaxMemInQueues by hand. Sep 19 21:34:24.824 [notice] Scheduler type KIST has been enabled. Sep 19 21:34:24.824 [notice] Opening Socks listener on 127.0.0.1:9050 Sep 19 21:34:24.824 [notice] Opening Control listener on 127.0.0.1:9051 Sep 19 21:34:24.824 [notice] Opening OR listener on 0.0.0.0:9001 Sep 19 21:34:24.824 [notice] Opening Directory listener on 0.0.0.0:9050 Sep 19 21:34:24.824 [warn] Could not bind to 0.0.0.0:9050: Address already in use. Is Tor already running? Sep 19 21:34:24.824 [notice] Closing partially-constructed Socks listener on 127.0.0.1:9050 Sep 19 21:34:24.824 [notice] Closing partially-constructed Control listener on 127.0.0.1:9051 Sep 19 21:34:24.824 [notice] Closing partially-constructed OR listener on 0.0.0.0:9001 Sep 19 21:34:24.824 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Sep 19 21:34:24.824 [err] Reading config failed--see warnings above.
I 'think' my original torrc file may have somehow survived the Ubuntu upgrade, but I don't know how as I did a wipe and re-install of Ubuntu. But when I edited it, there were my contact details sitting there.
Very appreciative of any help!
Thanks Ben.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Thanks for the reply! ha ha - is TOR like shouting Tor? :P
sudo netstat -tlpn returned the following:
Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:5939 0.0.0.0:* LISTEN 1342/teamviewerd tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 747/systemd-resolve tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 984/cupsd tcp6 0 0 ::1:631 :::* LISTEN 984/cupsd
On Wed, Sep 19, 2018 at 10:14 PM dawuud dawuud@riseup.net wrote:
Hi.
(Tor not TOR)
The log line:
Sep 19 21:34:24.824 [warn] Could not bind to 0.0.0.0:9050: Address already in use. Is Tor already running?
This means that tor cannot start because some other process is already bound to port 9050. Why not see which other process is bound to port 9050?
sudo netstat -tlpn or lsof -iTCP | grep 9050
btw typing "tor" into a server isn't the correct way to start tor. Usually on linux people use systemd to start tor:
systemctl start tor
I think the nyx error is pretty clear. Perhaps your tor isn't configured with a control port.
I hope this helps but if it doesn't then I hope someone else will be more helpful than I.
Cheers, David
On Wed, Sep 19, 2018 at 09:56:52PM +1000, Ben Riley wrote:
First off, will outline that I am very much a newbie, but was able to
get a
relay up and running on a Ubuntu machine. It was running fine for maybe
12
months (MelbTorBox), with a few resets and software updates along the
way.
Just doing my bit to help the network.
Anyway, after the Ubuntu upgrade, I had to re-install TOR and I believed
I
did it basically the same way.
Unfortunately, that appears not to be the case. I've posted the error messages on the Ubuntu forum hoping to get assistance, but no joy:
https://askubuntu.com/questions/1070469/18-04-tor-relay-error-could-not-bind...
I'm now coming to the experts to see if I can resurrect relay before I
pull
the pin on the idea.
I have BASIC Unix knowledge (I can type commands and that's about it). I think I might have a couple of copies installed in different places and I know I have the TOR browser installed (it works fine).
When I type 'nyx' it replies with: Unable to connect to tor. Maybe it's running without a ControlPort?
So I type 'tor' and get Sep 19 21:34:24.819 [notice] Tor 0.3.4.8 (git-5da0e95e4871a0a1) running
on
Linux with Libevent 2.1.8-stable, OpenSSL 1.1.0g, Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3. Sep 19 21:34:24.819 [notice] Tor can't help you if you use it wrong!
Learn
how to be safe at https://www.torproject.org/download/download#warning Sep 19 21:34:24.819 [notice] Read configuration file "/etc/tor/torrc". Sep 19 21:34:24.823 [notice] Based on detected system memory, MaxMemInQueues is set to 2862 MB. You can override this by setting MaxMemInQueues by hand. Sep 19 21:34:24.824 [notice] Scheduler type KIST has been enabled. Sep 19 21:34:24.824 [notice] Opening Socks listener on 127.0.0.1:9050 Sep 19 21:34:24.824 [notice] Opening Control listener on 127.0.0.1:9051 Sep 19 21:34:24.824 [notice] Opening OR listener on 0.0.0.0:9001 Sep 19 21:34:24.824 [notice] Opening Directory listener on 0.0.0.0:9050 Sep 19 21:34:24.824 [warn] Could not bind to 0.0.0.0:9050: Address
already
in use. Is Tor already running? Sep 19 21:34:24.824 [notice] Closing partially-constructed Socks listener on 127.0.0.1:9050 Sep 19 21:34:24.824 [notice] Closing partially-constructed Control
listener
on 127.0.0.1:9051 Sep 19 21:34:24.824 [notice] Closing partially-constructed OR listener on 0.0.0.0:9001 Sep 19 21:34:24.824 [warn] Failed to parse/validate config: Failed to
bind
one of the listener ports. Sep 19 21:34:24.824 [err] Reading config failed--see warnings above.
I 'think' my original torrc file may have somehow survived the Ubuntu upgrade, but I don't know how as I did a wipe and re-install of Ubuntu. But when I edited it, there were my contact details sitting there.
Very appreciative of any help!
Thanks Ben.
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
Hi Ben
Am 19.09.2018 um 13:56 schrieb Ben Riley:
So I type 'tor' and get Sep 19 21:34:24.819 [notice] Tor 0.3.4.8 (git-5da0e95e4871a0a1) running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.0g, Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3. Sep 19 21:34:24.819 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Sep 19 21:34:24.819 [notice] Read configuration file "/etc/tor/torrc". Sep 19 21:34:24.823 [notice] Based on detected system memory, MaxMemInQueues is set to 2862 MB. You can override this by setting MaxMemInQueues by hand. Sep 19 21:34:24.824 [notice] Scheduler type KIST has been enabled. Sep 19 21:34:24.824 [notice] Opening Socks listener on 127.0.0.1:9050
First listener to port 9050 for localhost
Sep 19 21:34:24.824 [notice] Opening Control listener on 127.0.0.1:9051 Sep 19 21:34:24.824 [notice] Opening OR listener on 0.0.0.0:9001 Sep 19 21:34:24.824 [notice] Opening Directory listener on 0.0.0.0:9050
Second listener to port 9050 for all ips
Sep 19 21:34:24.824 [warn] Could not bind to 0.0.0.0:9050: Address already in use. Is Tor already running?--
Your torrc wants tor to expect both socks AND directory requests at port 9050. Only one can.
Check the torrc file and move the Dirport to 9030. Restart tor and check the log again if it works better. Somewhere should be the entry "Self-testing indicates your DirPort is reachable from the outside. Excellent." Same for Orport. If you dont't need socks you can change it to <SocksPort 0>.
I hope I got you right. Good luck!
[] https://www.torproject.org/docs/tor-manual.html.en
I've had a similar situation in the past and my problem was that tor was actually running but not functional. Try pidof tor to see if it's running with another user. If yes, you can kill it and restart.
Arisbe
On 9/19/2018 10:56 AM, Felix wrote:
Hi Ben
Am 19.09.2018 um 13:56 schrieb Ben Riley:
So I type 'tor' and get Sep 19 21:34:24.819 [notice] Tor 0.3.4.8 (git-5da0e95e4871a0a1) running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.0g, Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3. Sep 19 21:34:24.819 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Sep 19 21:34:24.819 [notice] Read configuration file "/etc/tor/torrc". Sep 19 21:34:24.823 [notice] Based on detected system memory, MaxMemInQueues is set to 2862 MB. You can override this by setting MaxMemInQueues by hand. Sep 19 21:34:24.824 [notice] Scheduler type KIST has been enabled. Sep 19 21:34:24.824 [notice] Opening Socks listener on 127.0.0.1:9050
First listener to port 9050 for localhost
Sep 19 21:34:24.824 [notice] Opening Control listener on 127.0.0.1:9051 Sep 19 21:34:24.824 [notice] Opening OR listener on 0.0.0.0:9001 Sep 19 21:34:24.824 [notice] Opening Directory listener on 0.0.0.0:9050
Second listener to port 9050 for all ips
Sep 19 21:34:24.824 [warn] Could not bind to 0.0.0.0:9050: Address already in use. Is Tor already running?--
Your torrc wants tor to expect both socks AND directory requests at port 9050. Only one can.
Check the torrc file and move the Dirport to 9030. Restart tor and check the log again if it works better. Somewhere should be the entry "Self-testing indicates your DirPort is reachable from the outside. Excellent." Same for Orport. If you dont't need socks you can change it to <SocksPort 0>.
I hope I got you right. Good luck!
tor-relays@lists.torproject.org
-
arisbe -
Ben Riley -
dawuud -
Felix