Sorry, germin because of your torrc-example:
I added MaxMemInQueues 1024 MB
LimitNOFile 5000 doesn't work, neither does LimitNOFILE = 5000 and I deleted it.
Nyx didn't start anymore and then I first had to "chown <authcookie-file>".
Tor is running again and nyx says "Relay unresponsive - Relay resumed - 3, no 4 duplicates hidden.
I have traffic, some flags and everything seems fine except those nyx-notices.


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Am Samstag, 9. März 2019 23:49 schrieb digitalist00 <digitalist00@protonmail.com>:

OK: chown <datei in der authcookie liegt> hat's gebracht.
Nyx läuft wieder, Tor auch.
Das mit LimitNOFILE ist mir noch nicht ganz klar.


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Am Samstag, 9. März 2019 23:45 schrieb digitalist00 <digitalist00@protonmail.com>:

MaxMemInQueues 1024 MB hab ich eingetragen.
LimitNOFile 5000 - geht nicht.
LimitNOFILE = 5000 - geht auch nicht, hab's daher wieder gelöscht und Tor wieder neu gestartet.

Jetzt startet Nyx nich mehr. Kann also nicht sagen, ob Tor jetzt läuft oder nicht.


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Am Samstag, 9. März 2019 23:30 schrieb niftybunny <abuse@to-surf-and-protect.net>:

Ups sorry, its in your torrc. You can modify how many relays can connect to your relay.

its in your torrc file

mine looks something like this:

SocksPort 0                                                    # disable local usage
CookieAuthentication 1                                         # method for controller authentication
ORPort 21001                                                   # ORPort angepasst
DirPort 11001                                                  # DirPort angepasst
Nickname niftycastoroides                                      # Solltest du auf jeden Fall anpassen
ContactInfo  abuse@to-surf-and-protect.net                     # Solltest du auf jeden Fall anpassen
RelayBandwidthRate 100 MB                                      # Bandbreite die du zur Verfügung stellst
RelayBandwidthBurst 100 MB                                     # Bandbreite die du zur Verfügung stells
MaxMemInQueues 1024 MB                                         # DDOS
ExitRelay 0                                                    # This is an Exit
# ORPort [2a01:4f9:2a:98c:0000:0000:50cf:a8ba]:21001

Try to limit you men usage with MaxMemInQueues 1024 MB and your connection LimitNOFile 5000 or something like this.
Its mostly try and error how much a Pie can handle. In my experience: ARM mostly suxx with AES and thats the most important part
of a Tor relay. Just try different settings :)


On 9. Mar 2019, at 23:24, digitalist00 <digitalist00@protonmail.com> wrote:

Is this a command?


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Am Samstag, 9. März 2019 23:22 schrieb niftybunny <abuse@to-surf-and-protect.net>:

Next step: try LimitNOFILE = 1000

On 9. Mar 2019, at 23:20, digitalist00 <digitalist00@protonmail.com> wrote:

No no: CPU is about 10 - 15 % an RAM (mem) at about 15 % too (143 MB).


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Am Samstag, 9. März 2019 21:14 schrieb niftybunny <abuse@to-surf-and-protect.net>:

What does top say? CPU 100% and/or ram full?

On 9. Mar 2019, at 20:14, digitalist00 <digitalist00@protonmail.com> wrote:

Dear helpers!
Nyx says that my relay is unresponsive and that it was resumed. As I write this mail I have already 334 duplicates hidden.
What's my problem and how can I solve this?
The relay runs on a Raspberry Pi and is connected via LAN.
Yours
Digitalist

<Unbenannt.JPG>


Sent with ProtonMail Secure Email.

_______________________________________________
tor-relays mailing list

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