- tor-relays - lists.torproject.org

Re: [tor-relays] Tor RAM usage (DoS or memory leaks?) - Flood of circuits
by petrarca＠protonmail.ch 03 Feb '19

03 Feb '19

There is something really strange going on indeed. What I noticed is an increase of circuits and my device running out of memory until it stopped working so I had to reboot it on 31. Jan. Then again the memory usage increased until it leveled out at a rather unusual, high usage. The actual bandwidth usage is not unusual though (always around 2Mbps on my relay). Attached a screenshot of my memory usage the last few days (I hope attachments do work here; it's in fact Tor using that memory as could be checked with ps and htop). Heartbeat messages of the log are: Jan 31 10:57:56.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 447 circuits open. I've sent 2.66 GB and received 2.65 GB. Jan 31 16:57:56.000 [notice] Heartbeat: Tor's uptime is 12:00 hours, with 19764 circuits open. I've sent 9.59 GB and received 9.54 GB. Jan 31 22:57:56.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 54178 circuits open. I've sent 12.36 GB and received 12.30 GB. Feb 01 04:57:56.000 [notice] Heartbeat: Tor's uptime is 23:50 hours, with 79333 circuits open. I've sent 14.89 GB and received 14.81 GB. Feb 01 10:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 5:50 hours, with 110815 circuits open. I've sent 19.55 GB and received 19.45 GB. Feb 01 16:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 11:50 hours, with 141724 circuits open. I've sent 24.03 GB and received 23.90 GB. Feb 01 22:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 17:50 hours, with 12829 circuits open. I've sent 29.96 GB and received 29.75 GB. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, 1. February 2019 23:50, Roman Mamedov <rm(a)romanrm.net> wrote: > Hello, > > There seems to be an issue with Tor's memory usage. > Earlier today, with Tor 3.5.7 and 1.5 GB of RAM running two Tor processes, the > machine got 430 MB into swap, slowing down to a crawl from iowait on accessing > the swapped out memory. Typically 1.5 GB is more than enough for these. "VIRT" > in top was ~1GB each, and "RES" was ~512MB each. Which is weird because that > doesn't add up to exhausting the 1.5 GB, and there are no other heavy > processes on the machine running. I rebooted it without further investigation. > > And right now on another machine running 2.9.16 I see: > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 22432 debian-+ 30 10 5806816 5.157g 10464 R 39.5 33.1 39464:19 tor > > But not sure if it just accumulated 5.1GB of RAM slowly over time, or shot up > recently. > > Feb 01 17:00:49.000 [notice] Heartbeat: Tor's uptime is 82 days 23:59 hours, > with 70705 circuits open. I've sent 66622.45 GB and received 65906.91 GB. > Feb 01 17:00:49.000 [notice] Circuit handshake stats since last time: > 11361/11361 TAP, 239752/239752 NTor. > Feb 01 17:00:49.000 [notice] Since startup, we have initiated 0 v1 > connections, 0 v2 connections, 10 v3 connections, and 3385644 v4 connections; > and received 14 v1 connections, 78592 v2 connections, 822108 v3 connections, > and 8779474 v4 connections. > Feb 01 17:00:49.000 [notice] DoS mitigation since startup: 2899572 circuits > rejected, 121 marked addresses. 561 connections closed. 21956 single hop clients refused. > Feb 01 17:08:20.000 [warn] connection_edge_process_relay_cell (at origin) > failed. > > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > With respect, > Roman > > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

4 3

FOSDEM Relay Operator Meetup
by relaya relaya 02 Feb '19

02 Feb '19

Hello! I read there is a Relay Operator Meetup organized by Colin at. I'm surprised it has not been announced on this list yet. Where and when does it take place exactly? thank you!

2 3

AS: "I.C.S. Trabia-Network S.R.L."
by nusenu 02 Feb '19

02 Feb '19

Hello, if you are the operator of the relays listed bellow, please set MyFamily and contactInfo in your torrc to avoid getting rejected. ornetradar(a)riseup.net: > 2019-02-01 > > | Up | Ext | JoinTime | IP | CC | ORp | Dirp | Version | Contact | Nickname | eFamMembers | FP | > |------+-------+------------+-----------------+------+-------+--------+-----------+---------------------------+--------------+---------------+------------------------------------------| > | 1 | 1 | 13:41:51 | 178.175.132.211 | md | 9001 | 8080 | 0.3.5.7 | chatter | chatter | 1 | E0259C34CEDF2D7A15271336EF65E21171EDF0FE | > | 1 | 1 | 13:44:58 | 178.175.132.210 | md | 9001 | 8080 | 0.3.5.7 | rendon | rendon | 1 | 14678AB26ED87E843B232EAEDF2A7BB384652473 | > | 1 | 1 | 13:44:58 | 178.175.143.158 | md | 9001 | 8080 | 0.3.5.7 | lincoln | lincoln | 1 | 56F55271722E2F8FFC3A77CA3F7F955B703CB027 | > | 1 | 1 | 13:44:59 | 178.175.132.212 | md | 9001 | 8080 | 0.3.5.7 | dossier | dossier | 1 | 1B2E31990B0F0A51920F40D5AB7598D41B214A20 | > | 1 | 1 | 13:44:59 | 178.175.132.213 | md | 9001 | 8080 | 0.3.5.7 | lark | lark | 1 | 1C3EE6E25868F0A8B816B62D81534146F2616008 | > | 1 | 1 | 13:44:59 | 178.175.143.156 | md | 9001 | 8080 | 0.3.5.7 | cuban | cuban | 1 | 1F25B74EF811858112DE18220B456F3CF6EE642E | > | 1 | 1 | 13:44:59 | 178.175.143.157 | md | 9001 | 8080 | 0.3.5.7 | charly | charly | 1 | 3722EEBB445B4E91B1A10CED86CD2E32B3C92D41 | > | 1 | 1 | 13:44:59 | 178.175.132.209 | md | 9001 | 8080 | 0.3.5.7 | matador | matador | 1 | 3E48BE2E2AC257D20546B5547729F4A5096BE39F | > | 1 | 1 | 13:44:59 | 178.175.132.214 | md | 9001 | 8080 | 0.3.5.7 | azorian | azorian | 1 | 72193825EE4EE6F9EF3243D8A7B49DB9122ADF21 | > | 1 | 1 | 13:44:59 | 178.175.143.155 | md | 9001 | 8080 | 0.3.5.7 | contras | contras | 1 | A67EB8AA880ACC94B716E178576142CB25D63B8C | > > https://nusenu.github.io/OrNetRadar/2019/02/01/a1 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Re: [tor-relays] Circuit storms
by starlight.2018q2＠binnacle.cx 02 Feb '19

02 Feb '19

Jan 26 Heartbeat: circuits 6666 sent 103gb received 100gb Jan 26 Heartbeat: circuits 5672 sent 101gb received 98gb Jan 26 Heartbeat: circuits 6156 sent 106gb received 103gb Jan 26 Heartbeat: circuits 5902 sent 92gb received 90gb Jan 27 Heartbeat: circuits 6171 sent 80gb received 78gb Jan 27 Heartbeat: circuits 5920 sent 85gb received 82gb Jan 27 Heartbeat: circuits 4841 sent 82gb received 79gb Jan 27 Heartbeat: circuits 5718 sent 77gb received 71gb Jan 28 Heartbeat: circuits 5676 sent 86gb received 80gb Jan 28 Heartbeat: circuits 5157 sent 84gb received 81gb Jan 28 Heartbeat: circuits 7548 sent 105gb received 102gb Jan 28 Heartbeat: circuits 16448 sent 88gb received 84gb Jan 29 Heartbeat: circuits 31521 sent 107gb received 97gb Jan 29 Heartbeat: circuits 6255 sent 90gb received 86gb Jan 29 Heartbeat: circuits 14920 sent 91gb received 89gb Jan 29 Heartbeat: circuits 21502 sent 75gb received 72gb Jan 30 Heartbeat: circuits 37649 sent 80gb received 76gb Jan 30 Heartbeat: circuits 69831 sent 84gb received 81gb Jan 30 Heartbeat: circuits 16740 sent 102gb received 99gb Jan 30 Heartbeat: circuits 59552 sent 105gb received 101gb Jan 31 Heartbeat: circuits 73727 sent 88gb received 84gb Jan 31 Heartbeat: circuits 12156 sent 74gb received 71gb Jan 31 Heartbeat: circuits 63624 sent 81gb received 79gb Jan 31 Heartbeat: circuits 89129 sent 77gb received 72gb Feb 1 Heartbeat: circuits 98432 sent 105gb received 80gb Feb 1 Heartbeat: circuits 97975 sent 69gb received 66gb Feb 1 Heartbeat: circuits 27443 sent 94gb received 91gb

1 0

Tor RAM usage (DoS or memory leaks?)
by Roman Mamedov 01 Feb '19

01 Feb '19

Hello, There seems to be an issue with Tor's memory usage. Earlier today, with Tor 3.5.7 and 1.5 GB of RAM running two Tor processes, the machine got 430 MB into swap, slowing down to a crawl from iowait on accessing the swapped out memory. Typically 1.5 GB is more than enough for these. "VIRT" in top was ~1GB each, and "RES" was ~512MB each. Which is weird because that doesn't add up to exhausting the 1.5 GB, and there are no other heavy processes on the machine running. I rebooted it without further investigation. And right now on another machine running 2.9.16 I see: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 22432 debian-+ 30 10 5806816 5.157g 10464 R 39.5 33.1 39464:19 tor But not sure if it just accumulated 5.1GB of RAM slowly over time, or shot up recently. Feb 01 17:00:49.000 [notice] Heartbeat: Tor's uptime is 82 days 23:59 hours, with 70705 circuits open. I've sent 66622.45 GB and received 65906.91 GB. Feb 01 17:00:49.000 [notice] Circuit handshake stats since last time: 11361/11361 TAP, 239752/239752 NTor. Feb 01 17:00:49.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 10 v3 connections, and 3385644 v4 connections; and received 14 v1 connections, 78592 v2 connections, 822108 v3 connections, and 8779474 v4 connections. Feb 01 17:00:49.000 [notice] DoS mitigation since startup: 2899572 circuits rejected, 121 marked addresses. 561 connections closed. 21956 single hop clients refused. Feb 01 17:08:20.000 [warn] connection_edge_process_relay_cell (at origin) failed. -- With respect, Roman

1 0

tor relay shutsdown
by Neelix 01 Feb '19

01 Feb '19

Hello, I have setup a tor exit but it seems like that is shutsdown after x hours. I can not find anything in the logs. Anyone knows how this might happen? Regards, Neelix fingerprint: 32A6 5D7A 955C 546C 0E9B F559 EB09 D028 36A3 79E

5 11

Circuit storms
by Felix 31 Jan '19

31 Jan '19

Hi everybody Circuit storms observed of up to 100k and 250k per relay for over hours. Consumed BW rises by about 10%. Number of stateful server connections is higher. Using Tor 356 to 401. Anybody else observes that? Switching to some paranoid server settings for some days :) -- Cheers, Felix

2 2

Installing Tor As Windows Service And Updating Via Script (was RE: Having Trouble With Speed Of OBFS4 Bridge)
by Keifer Bly 30 Jan '19

30 Jan '19

Darn, I just restarted the relay because tor 0.3.5.7 came out today before seeing this email. I have been playing with the Windows Powershell regarding this and made some interesting discoveries. So, I found that the Windows Powershell equivalent to linux's "apt-get" is "install-package -Name". And so, I tried running "install-package -name tor" and got this error (see the attached screenshot). The error is that tor project is not in the list for Windows to install packages from on Windows (it's not finding tor packages as a result), as I discovered at the other attached image. However, according to my research at https://docs.microsoft.com/en-us/powershell/module/packagemanagement/regist… Windows Powershell can register sources to install packages from via Register-PackageSource -Name command listed. So Something along the lines of PS C:\> Register-PackageSource -Name "tor" -Location "http://torurl" -ProviderName "TorProject" may have interesting results possibly. What is the tor packages download url so I may try this? Once this is returned to me I will return to the list with my findings. Cheers. -----Original Message----- From: tor-relays <tor-relays-bounces(a)lists.torproject.org> On Behalf Of teor Sent: Monday, January 28, 2019 10:24 PM To: tor-relays(a)lists.torproject.org Subject: Re: [tor-relays] Having Trouble With Speed Of OBFS4 Bridge On January 29, 2019 3:45:55 AM UTC, Keifer Bly <keifer.bly(a)gmail.com> wrote: >Thanks. I also wanted to ask, is there a way to upgrade tor using >Windows Powershell? The way I am doing that is downloading the tor >expert bundle when a new one is released and manually replacing both >tor.exe and obfs4.exe with the new versions. I have tor installed as a >Windows service via powershell, so is there a way to do this? I am >asking because the current tor expert bundle is tor 0.3.4.8 whereas I >believe 0.3.5.7 has been released. Thank you. Hmm, I thought someone answered this question already, but I can't find the answer in the list archives. 0.3.4.8 is still a supported version. You don't need to update. One simple way to keep Tor up to date on Windows is to use the Chocolatey package manager to install the tor package: https://chocolatey.org/packages/tor It has Tor 0.3.3.9, which is still a recommended version. You can script chocolately using the "choco" command. Otherwise, you can script powershell to download and install packages. I can't help you with the details, because I don't do a lot of work on Windows. But maybe someone else on the list can. If you work out how to do it, please write back to the list with the scripts you used. T -- teor ---------------------------------------------------------------------- _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

2 1

IRC relay operator meetups
by Colin Childs 29 Jan '19

29 Jan '19

Hi everyone, The IRC Tor relay operator meetups are beginning again! To get started, we are going to be holding these meetups once per month. The meetups will be held the first Thursday of the month, at 2:00UTC. This means the February meetup will be held next week, on the 7th. To allow us to use meetbot for recording the meetup, we will be holding them in #tor-meeting. On the first Monday of the month, I will send out a reminder email with the date and time, along with a pad that people can add discussion topics to. For February, the reminder email will go out on the 4th. I look forward to seeing everyone there!

1 0

Hetzner - "no.spam@example.com" relays
by nusenu 29 Jan '19

29 Jan '19

Hi, to the operator of the relays listed bellow. You care currently not setting the MyFamily option on your relays, which puts tor users at risk. Please configure your relays with MyFamily to avoid getting your relays rejected. more information: https://medium.com/@nusenu/some-tor-relays-you-might-want-to-avoid-5901597a… https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays#Whatis… 2019-01-28 | Up | Ext | JoinTime | Nickname | Version | IP | AS | CC | ORp | Dirp | OS | Contact | eFamMembers | FP | |------+-------+------------+---------------------+-----------+----------------+---------------------+------+-------+--------+-------+---------------------+---------------+------------------------------------------| | 0 | 0 | 01:34:19 | somerelay | 0.3.3.7 | 116.203.57.161 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | 24C3BC672621D6FCB7923DE031738B23EE0C1819 | | 0 | 0 | 01:48:53 | somerelay | 0.3.3.7 | 116.203.57.161 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | CBDCA8B16E2D4111A6618BAB3F114C358B8E35DB | | 1 | 0 | 05:00:50 | somerelay1IHcuer9Cn | 0.3.3.7 | 116.203.57.161 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | CA307A53194D6DE8B033226C541654117AFCF5F2 | | 1 | 0 | 02:54:44 | somerelayId8wPoBbRJ | 0.3.3.7 | 116.203.57.160 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | F9578C192A76062C2B49F938A53291AA5CE3CFBF | | 1 | 0 | 02:54:49 | somerelayT7WbYRznBW | 0.3.3.7 | 116.203.59.81 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | CFDF026F3FC52BF347A395A1224D70D9ACBEF9C5 | | 1 | 0 | 02:55:45 | somerelayung2AiqzXu | 0.3.3.7 | 116.203.66.45 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | 97F47C07A3DEA4C1A885C2C15008592635DA54B6 | | 1 | 0 | 02:54:46 | somerelayvpoDStFnGZ | 0.3.3.7 | 94.130.184.189 | Hetzner Online GmbH | de | 9001 | 9030 | Linux | no.spam(a)example.com | 1 | 5CD0F83B59229F86419757FE54CFF6EE859EA0ED | https://nusenu.github.io/OrNetRadar/2019/01/28/a7 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0