[tor-relays] Tor uses up all available memory and eventually quits

[r1610091651]

I think the advice to create swap will get George kicked of VPS, as it goes
right against the wishes of hosting company, and directly affects their
hardware.

A better advice is to tune tor process to work within memory boundaries.
The "MaxMemInQueues 512 MB" is right direction, but from personal
experience, I don't think it goes "far" enough. Will need to be limited
further I think, but you could adjust further based on your observations.

Seb

On Sun, 28 Jan 2018 at 07:14 tor <tor at anondroid.com> wrote:

> I think running on 1 GB of RAM with no swap is going to be difficult,
> especially if you have decent bandwidth and your node is busy.
>
> You can create a small swap file on the existing file-system like so:
>
>   sudo fallocate -l 1G /swapfile
>   sudo chmod 600 /swapfile
>   sudo mkswap /swapfile
>   sudo swapon /swapfile
>
> and to make permanent:
>
>   echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab
>
> The swap file won't get used often, but will prevent your relay from going
> OOM and crashing. You can further reduce the likelihood of the swap getting
> used by setting something like "vm.swappiness = 10" in /etc/sysctl.conf.
>
> Also these two entries in your torrc might help:
>
>   DisableOOSCheck 0
>   MaxMemInQueues 512 MB
>
> ​The first line will enable the "out of sockets" check, and although it
> aggressively drops connections, tends to prevent the node from falling over
> instead. The second reduces the amount of memory used.
>
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20180128/34965006/attachment.html>