- tor-relays - lists.torproject.org

OOM Bytes Cell
by Nyasaki Server 29 Aug '22

29 Aug '22

Hi, my node is running for a while now, today I noticed that the cell oom bytes has risen, which never happened before. Is this concerning? What does the cell value mean? Im thankful for every input! BR Nyasaki

1 0

Closing relay
by Ole Rydahl 29 Aug '22

29 Aug '22

Since 2014 I have run a non-exit relay at my premises. However ultimo July the system load increased abruptly. Idle-cpu -typically 60-70% - dropped to 30%, _and_ with frequent drops to 0! I reduced the max bandwidth to 1.2 Mbytes. That reduces the load somewhat but still with frequent spikes where the idle-cpu hits 0 and I get the "relay too slow" indication. Any suggestions? /Ole Rydahl https://metrics.torproject.org/rs.html#details/CE1FD7659F2DFE92B883083C0C6C9 74616D17F3D

2 1

Overload
by sysmanager7 27 Aug '22

27 Aug '22

Another New one: 19:01:09 [NOTICE] General overload -> Ntor dropped (176948) fraction 25.2668% is above threshold of 0.5000% â 17:19:32 [WARN] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth â config option or choosing a more restricted exit policy. Any Ideas?? What is the syntax for MaxAdvertisedBandwidth? Currently is: MaxAdvertisedBandwidth 3Mb Sysmanager Sent with [Proton Mail](https://proton.me/) secure email.

1 0

missing IPv6 close events
by Toralf Förster 27 Aug '22

27 Aug '22

Playing with Python and Stem I wrote a script to monitor the ORStatus.CLOSED event reasons [1]. A helper script [2] gives statistics from those data. From the last 2 days I got: $> orstatus-stats.sh /tmp/orstatus.29051 CONNECTRESET 6197 CONNECTRESET 13214 DONE 18769 IOERROR 58 NOROUTE 1661 TIMEOUT 2562 TLS_ERROR 42461 I was wondering if it is expected that DONE is just a 1/4 of all reasons. And I do wonder why all events are IPv4 only. [1] https://github.com/toralf/torutils/blob/main/orstatus.py [2] https://github.com/toralf/torutils/blob/main/orstatus-stats.sh -- Toralf

1 0

Warn:
by sysmanager7 24 Aug '22

24 Aug '22

I got the below message on my relay #2. It's been in operation for a year and a half. First time I've ever got one of these. 0re7:26:40 [WARN] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [505 similar message(s) suppssed in last 57840 seconds] OK > Both relays operate on Digital Ocean Droplets Bandwidth on both 2 MBs Burst 3MBs both relays have the same settings NEITHER is an exit: ExitPolicy reject I see relay #2 has been restarted. Last eve it had been up four days. As of this writing just over 2 hours. Or is this another way to muck up a relay? Sysmanager Sent with [Proton Mail](https://proton.me/) secure email.

1 0

We need much more bridges with obfs4 and iat-mode set to 1 or 2..barely can't find any.
by elise.toradin＠web.de 24 Aug '22

24 Aug '22

4 3

Strange entries in notices.log
by toritdown 23 Aug '22

23 Aug '22

I am suddenly finding numerous entries in my /var/log/tor/notices log that look like this: Aug 22 01:21:46.000 [warn] Unable to store router descriptor Aug 22 01:21:46.000 [warn] Error writing to "/var/lib/tor/cached-descriptors.new": No space left on device What does this mean? What do I need to do about? Sent with [Proton Mail](https://proton.me/) secure email.

4 3

Relays spamming my OR port
by Logforme 19 Aug '22

19 Aug '22

I run the relay 8F6A78B1EA917F2BF221E87D14361C050A70CCC3 I have tried to mitigate the current DoS by implemented connection limits in my iptables using Toralf's template: More than 25 connection during 10 mins and you end up on my naughty list. Lots of connection attempts from the naughty list dropped but still my relay gets "overloaded" However, I have noticed that a few relays also end up on the naughty list, and I wonder how that can happen. My understanding is that a relay will only open 1 connection to another relay so should therefore never end up on the list. Correct? D767979FE4C99D310A46EC49037E9FE7E3F64E9D is a particularly frequent naughty boy. Maybe these relays disconnect and reconnect to my relay frequently due to network issues (effect from the DoS?) or from not having enough connections available on the router? I guess my real question is if these connections are legit and I'm hurting the Tor network by using connection limits?

4 10

Metrics falsely showing my relay as offline
by Eddie 19 Aug '22

19 Aug '22

I have 1 relay (40D13096BBD11AF198CE61DEE4EAECCE5472F2E7) that according to the metrics is always bouncing between online and offline, sometimes multiple times per day. The logs show it running the whole time and when the metrics also show it running, the uptime continues to increase correctly. This hasn't always been the case, as the history shows this didn't happen prior to around June based on the guard flag usage. This relay is hosted at AWS if that makes any difference. Should I care about this, because the relay is running correctly. It's just that it never gets the stable (long running) and guard flags any more because of this yo-yo effect, which I'm sure is affecting how the relay is allocated circuits. I do have another relay (E823B5F000835A669E902EBAE5ECCB9A324F46C9) that sometimes exhibits the same issues, but to a much lesser extent. Like it will show offline (maybe) once a month for a very short period and any flags lost are quickly regained.

2 2

[New Initiative] Tor Weather: Improving the Tor Weather
by Sarthik Gupta 18 Aug '22

18 Aug '22

Hello everyone, As we all know, nodes are the building blocks of the tor-network. More often than not these nodes require some maintenance, which could be in the form of software upgrades, troubleshooting issues, rebooting the relays in case of failures, etc. As of today, if any relay disappears from the tor-network, no one will know. Tor-Weather aims at solving this by creating a notification service which relay operators can subscribe to in order to get various types of updates for their relays. The tor-weather service will offer a plethora of notifications options for the relays. These include, the node being down, running on EOL/Outdated version, losing a flag, ranking in top 20/50/100, etc. These notifications can be subscribed & customized by the relay operators to fit their needs using a web-frontend. Folks interested in the project can refer this <https://lists.torproject.org/pipermail/tor-dev/2022-May/014734.html> thread in the tor-dev mailing list for regular updates. Suggestions are always welcomed! Please reach out to us in irc (#tor-dev) for any ideas, questions, or suggestions you might have. Thanks, Sarthik Gupta

4 6