Re: [tor-relays] Tor Relay Software Warns When Current RunningVersion Of Tor Is No Longer Recommended, But Not When A Newer Version IsAvailable?
So does this mean any version of tor is safe to use as long as it is not considered “obsolete”? Thanks. From: teor Sent: Wednesday, September 19, 2018 5:04 PM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Tor Relay Software Warns When Current RunningVersion Of Tor Is No Longer Recommended, But Not When A Newer Version IsAvailable? On 20 Sep 2018, at 07:02, Keifer Bly wrote: Hello, A few days ago, I upgraded my version of tor from 0.3.3.9 to tor 0.3.4.8. I noticed, however, that tor does not tell me when a new version is available. But in the past when I was a few versions behind, it popped up with a message saying “WARNING: this version of tor is out of date or no longer recommended.” So, I am just wondering, why is it that the tor software warns when the current version is “no longer recommended” but does not warn when an update is available? Tor only warns about obsolete versions. It doesn't warn when there is a new release or "new in series" version available. Definitions here: https://gitweb.torproject.org/torspec.git/tree/version-spec.txt#n53 T ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor Relay Software Warns When Current Running Version Of Tor Is No Longer Recommended, But Not When A Newer Version Is Available?
On 20 Sep 2018, at 07:02, Keifer Bly wrote: > > Hello, > > A few days ago, I upgraded my version of tor from 0.3.3.9 to tor 0.3.4.8. I > noticed, however, that tor does not tell me when a new version is available. > But in the past when I was a few versions behind, it popped up with a message > saying “WARNING: this version of tor is out of date or no longer recommended.” > > So, I am just wondering, why is it that the tor software warns when the > current version is “no longer recommended” but does not warn when an update > is available? Tor only warns about obsolete versions. It doesn't warn when there is a new release or "new in series" version available. Definitions here: https://gitweb.torproject.org/torspec.git/tree/version-spec.txt#n53 T___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Tor Relay Software Warns When Current Running Version Of Tor Is No Longer Recommended, But Not When A Newer Version Is Available?
Hello, A few days ago, I upgraded my version of tor from 0.3.3.9 to tor 0.3.4.8. I noticed, however, that tor does not tell me when a new version is available. But in the past when I was a few versions behind, it popped up with a message saying “WARNING: this version of tor is out of date or no longer recommended.” So, I am just wondering, why is it that the tor software warns when the current version is “no longer recommended” but does not warn when an update is available? Thanks. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Help! TOR Relat dead after upgrading Ubuntu to 18.04
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 . I hope I got you right. Good luck! [] https://www.torproject.org/docs/tor-manual.html.en -- One person's moral compass is another person's face in the dirt. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Help! TOR Relat dead after upgrading Ubuntu to 18.04
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 . I hope I got you right. Good luck! [] https://www.torproject.org/docs/tor-manual.html.en -- Cheers, Felix ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] New Exit-Relay / First abuse issues
On 19.09.18 15:04, tor-markus wrote: > After a little search through my mails I found out that Contabo shuts > down all services within 24h if there is no reply. That kinda sucked > because I run some private services on this machine (different ip). No surprise there, see https://contabo.de/agb.html §5 (4). All ISPs I have had business dealings with do this to counter abuse, with Hetzner reducing the reaction time before shutdown depending on the number of abuse complaints, down to 4h. > Contabo's mail claimed that a 30€ fee would be due in order to cover > their work for disabling and enabling the server. Sounds like scare tactics to me, but like you wrote, that's nonsense. -Ralph ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] New Exit-Relay / First abuse issues
thanks for sharing your experience with your hoster. tor-markus: > Hey *, > > I run C65EF5E06B8338CF976D376048BE2C8FBD499C9C for about a month. On > Monday I received the first abuse ticket from my ISP (Contabo GmbH). > The ticket contained lots and lots of log information from a fail2ban > system so GMail sent it right into the spam folder. 24 hours later I > received a monitoring e-mail that my server was down. After a little > search through my mails I found out that Contabo shuts down all > services within 24h if there is no reply. That kinda sucked because I > run some private services on this machine (different ip). strongly recommended: do NOT mix tor exit relay services with other services you depend on on the same operating system. for multiple reasons: - don't suffer as much when the server gets shutdown or seized - easier to argue that the server was a tor exit and only a tor exit - smaller attack surface -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] New Exit-Relay / First abuse issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey *, I run C65EF5E06B8338CF976D376048BE2C8FBD499C9C for about a month. On Monday I received the first abuse ticket from my ISP (Contabo GmbH). The ticket contained lots and lots of log information from a fail2ban system so GMail sent it right into the spam folder. 24 hours later I received a monitoring e-mail that my server was down. After a little search through my mails I found out that Contabo shuts down all services within 24h if there is no reply. That kinda sucked because I run some private services on this machine (different ip). Contabo's mail claimed that a 30€ fee would be due in order to cover their work for disabling and enabling the server. A very very unfriendly e-mail and about an hour of time later my server was back online :) (Note: the e-mail was sent around 10 PM and I received the answer at about 11 PM, so the abuse department is there 24/7. Their hotline however, can't deal with abuse complaints, they can only be handled via e-mail.) Contabo sent me a (probably) automated e-mail that the issue was resolved and no further action is needed. Overall I think its a little unprofessional to shutdown servers within 24 hours without trying to call a customer, or at least several e-mail reminders over a day or two. Markus This is my new abuse e-mail template for German speaking hosting providers: Sehr geehrte Damen und Herren, Auf dem Server wird eine Tor-Exit Node betrieben. NachTMG §8ist der Betreiber von jeder Haftung für die durchgeleiteten Daten befreit, dies gilt für mich als Ihren Kunden sowohl als auch für Sie als mein ISP. Die IP X.X.X.X leitet ausschließlich Tor-Exit Traffic durch. Diese Übermittlungen sind weder von mir veranlasst noch wird der Adressant oder die zu übermittelnden Informationen ausgesucht und oder verändert. Unter der IP Adresse X.X.X.X werden keinerlei Daten bereitgestellt. Diese Ports werden durchgeleitet: 20-21, 43, 53, 80-81, 88, 110, 143, 194, 220, 389, 443, 464-465, 531, 543-544, 554, 563, 587, 636, 706, 749, 853, 873, 902-904, 981, 989-995, 1194, 1220, 1293, 1500, 1533, 1677, 1723, 1755, 1863, 2082-2083, 2086-2087, 2095-2096, 2102-2104, 3128, 3389, 3690, 4321, 4643, 5050, 5190, 5222-5223, 5228, 5900, 6660-6669, 6679, 6697, 8000, 8008, 8074, 8080, 8082, 8087-8088, 8232-8233, 8332-8333, 8443, , 9418, -1, 11371, 19294, 19638, 50002, 64738. Im Falle von Spam / Brute Force empfehlen ich dem Absender der abuse E-Mail seine Systeme mit Tools wieFail2Ban,reCAPTCHA zu schützen. Im Falle von gehäuften (D)DoS Attacken gibt es die Möglichkeit das gesamte Tor Netzwerk zu blockieren. Hierfür steht ein eine jederzeit aktuelle Blacklist aller Tor-ExitNodes bereit: https://www.torproject.org/projects/tordnsel.html Falls ausschließlich über die IP X.X.X.X bösartiger Traffic ausgeht kann der Absender der abuse E-Mail diesen mithilfe von iptables blockieren: iptables -A INPUT -s X.X.X.X -j DROP Falls der Absender diese Möglichkeit nicht hinnehmen möchte, kann von meiner Seite aus jeder Traffic zu seiner IP bzw. zu einzelnen Ports unterbunden werden. Dem Absender der Abuse E-Mail können sie in meinem Namen folgende Nachricht zukommen lassen: > Dear Sir or Madame, > > we would like to forward this message on behalf of our customer who is > responsible for this particular server with the IP X.X.X.X. > > The IP address in question is a Tor exit > node.https://www.torproject.org/overview.html > > There is little we can do to trace this matter further. As can be seen from > theoverview page, the Tor network is designed to make tracing of users > impossible. The Tor network is run by some 5000 volunteers who use the free > software provided by the Tor Project to run Tor routers. Client connections > are routed through multiple relays, and are multiplexed together on the > connections between relays. The system does not record logs of client > connections or previous hops. This is because the Tor network is a censorship > resistance, privacy, and anonymity system used by whistle blowers, > journalists, Chinese dissidents skirting the Great Firewall, abuse victims, > stalker targets, the US military, and law enforcement, just to name a few. > Seehttps://www.torproject.org/about/torusers.html.enfor more info. > Unfortunately, some people misuse the network. However, compared to the rate > of legitimate use, abuse complaints are > rare.https://www.torproject.org/docs/faq-abuse.html.en > This does not mean that nothing can be done, however. The Tor project > provides an automated DNSRBL for you to query to flag traffic coming from Tor > nodes.https://www.torproject.org/projects/tordnsel.html.en. In general, we > believe that problems like this are best solved by improving your service to > defend against the attack from the Internet at large. > > As a German individual I fully comply with the Germantelemedia law §15. This > prohibits logging any personally
Re: [tor-relays] Help! TOR Relat dead after upgrading Ubuntu to 18.04
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 tcp0 0 127.0.0.1:5939 0.0.0.0:* LISTEN 1342/teamviewerd tcp0 0 127.0.0.53:53 0.0.0.0:* LISTEN 747/systemd-resolve tcp0 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 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-to-0-0-0-09050-address-already-in-use-i > > > > 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 > ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Help! TOR Relat dead after upgrading Ubuntu to 18.04
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-to-0-0-0-09050-address-already-in-use-i > > 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 signature.asc Description: PGP signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Help! TOR Relat dead after upgrading Ubuntu to 18.04
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-to-0-0-0-09050-address-already-in-use-i 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
