Re: [tor-relays] relay load increase (was: note to Falback Directory operators: bandwidth wasting bot)

[Felix]

Hi everybody

Tor relay load increase is going on.

1) Not normal: Some relays see much more circuits (ie the normal number 
of circuits was about 15-20k and is 100k-400k today).


2) Not normal: Fallbacks receive extensive use today. We are writing too 
much.


Am 09.11.2018 um 17:17 schrieb starlight.201...@binnacle.cx:

For the last year a bot of some kind has loaded Fallback
Directory relays with excessive directory document requests.
Some detail can be found in ticket #27921 at
https://trac.torproject.org/projects/tor/ticket/27921.

To determine if your relay is affected, look the relay up in
https://metrics.torproject.org/rs.html, click the 6-Month history
tab, and examine the graph for significantly higher "write bytes
per second" relative to "read bytes per second".

I find this annoying (since I pay for the wasted bandwidth) and
came up with a one-line hack that mitigates the abuse without
impairing the usefulness of the DIR service to normal relays
and clients.  If you compile your daemon from source and are
interested contact me directly for the patch.


https://metrics.torproject.org/rs.html#details/
1AE039EE0B11DB79E4B4B29CBA9F752864A0259E
A2E6BB5C391CD46B38C55B4329C35304540771F1
B86137AE9681701901C6720E55C16805B46BD8E3

3) Not normal: 
https://metrics.torproject.org/hidserv-rend-relayed-cells.html?start=2017-01-01


--
Cheers, Felix
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Tor RAM usage (DoS or memory leaks?) - Flood of circuits

[grarpamp]

A week or two ago someone was scanning
entire 80-bit onion space in big parallel.
They later said they stopped upon advisement
of the futility. But you never know.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Tor RAM usage (DoS or memory leaks?) - Flood of circuits

[David Goulet]

On 02 Feb (04:10:02), petra...@protonmail.ch wrote:

Hi, thanks for the report!

> 
> 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.

Do you see some sort of increase during that time period of the DoS
mitigation stats? It would be the heartbeat line that starts with:

"DoS mitigation since startup:" ...

Burst of circuits are possible for many reasons. But, if that leads to
high memory usage and that doesn't come back down to a normal level once
the bursts are over, we may have a problem.

If you end up with any more logs about this or if your relay gets OOMed,
please share so we can investigate what is going on.

Thanks!
David

> 
> ‐‐‐ Original Message ‐‐‐
> On Friday, 1. February 2019 23:50, Roman Mamedov  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.
> >
> > 

Re: [tor-relays] FOSDEM Relay Operator Meetup

[Colin Childs]

Hi everyone,

The meetup will be held on Sunday, February 3rd @ 15:00 in room H.3244.

I hope all of you at FOSDEM can make it! 

> On Jan 25, 2019, at 1:05 PM, Colin Childs  wrote:
> 
> Hello everyone,
> 
> We have put the current FOSDEM relay operator meet-up details at 
> https://blog.torproject.org/events/fosdem-brussels 
> , I have also included 
> the text below:
> 
> — BEGIN POST ---
> 
> During FOSDEM 2019, the Tor Project will also be hosting a relay operator 
> meetup.
> 
> We will discuss common issues operators face, potential solutions, as well as 
> how we can all help to grow the relay operator community both locally and 
> globally. We'll be on hand to answer questions and want to hear your feedback 
> about the community, running relays, and what we can do to better support you.
>  
> The date, time, and location for the meetup will be posted the morning 
> (GMT+1) of February 2nd. We are aiming to hold this event on Sunday, February 
> 3rd; however we will not be able to book the room until FOSDEM begins.
>  
> We look forward to seeing you there.
> 
> --- END POST ——
> 
> Once we have confirmed the room on the morning of February 2nd, I will send a 
> follow-up email to this thread with the currently missing details. 
> 
> If you have any questions or concerns, please do not hesitate to reach out.
> 
>> On Jan 22, 2019, at 5:47 PM, Colin Childs > > wrote:
>> 
>> Hi everyone,
>> 
>> I just wanted to let everyone know I’ve seen this email, and will be 
>> responding in full shortly. 
>> 
>> There are a couple details still being worked out, and as soon as this is 
>> done I will update the list.
>> 
>> Thanks for your patience! 
>> 
>>> On Jan 19, 2019, at 2:31 PM, relaya relaya >> > wrote:
>>> 
>>> 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! 
>>> ___
>>> 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

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] AS: "I.C.S. Trabia-Network S.R.L."

[nusenu]

Hello,

if you are the operator of the relays listed bellow,
please set MyFamily and contactInfo in your torrc
to avoid getting rejected.




ornetra...@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



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