Tor gets killed by OOM killer
Hi,
my relay has been killed a few times by my OS's OOM killer in the last few days.
https://metrics.torproject.org/rs.html#details/F2D6EB211744D41DC41CCB62BF1C3246D24B42A2
Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.31 as libc.
MaxMemInQueues was set to 3072 MB when the last crash happened. System is an Debian LXC container with currently 10 gigabytes of RAM.
OS is Debian GNU/Linux 11 (bullseye)
Tor is installed via official Debian repositories.
Oct 27 22:47:27 Tor systemd[1]: tor@default.service: A process of this unit has been killed by the OOM killer.
Oct 27 22:47:27 Tor systemd[1]: tor@default.service: Main process exited, code=killed, status=9/KILL
Oct 27 22:47:27 Tor systemd[1]: tor@default.service: Failed with result 'oom-kill'.
Oct 27 22:47:27 Tor systemd[1]: tor@default.service: Consumed 2d 13h 43min 1.409s CPU time.
Oct 27 22:47:28 Tor systemd[1]: tor@default.service: Scheduled restart job, restart counter is at 4.
Oct 27 22:47:28 Tor systemd[1]: Stopped Anonymizing overlay network for TCP.
Oct 27 22:47:28 Tor systemd[1]: tor@default.service: Consumed 2d 13h 43min 1.409s CPU time.
Oct 27 22:47:28 Tor systemd[1]: Starting Anonymizing overlay network for TCP...
MaxMemInQueues is now not specifically defined anymore, so automatically determined.
Complete startup sequence from current run:
Oct 27 22:47:28 Tor tor[6405]: Oct 27 22:47:28.248 [notice] Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.31 as libc.
Oct 27 22:47:28 Tor tor[6405]: Oct 27 22:47:28.248 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Oct 27 22:47:28 Tor tor[6405]: Oct 27 22:47:28.248 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Oct 27 22:47:28 Tor tor[6405]: Oct 27 22:47:28.248 [notice] Read configuration file "/etc/tor/torrc".
Oct 27 22:47:28 Tor tor[6405]: Oct 27 22:47:28.249 [warn] Skipping obsolete configuration option "SocksListenAddress".
Oct 27 22:47:28 Tor tor[6405]: Oct 27 22:47:28.251 [notice] Based on detected system memory, MaxMemInQueues is set to 4096 MB. You can override this by setting MaxMemInQueues by hand.
Oct 27 22:47:28 Tor tor[6405]: Configuration was valid
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.265 [notice] Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.31 as libc.
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.265 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.265 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.265 [notice] Read configuration file "/etc/tor/torrc".
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.265 [warn] Skipping obsolete configuration option "SocksListenAddress".
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.266 [notice] Based on detected system memory, MaxMemInQueues is set to 4096 MB. You can override this by setting MaxMemInQueues by hand.
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.267 [notice] I think we have 8 CPUS, but only 4 of them are available. Telling Tor to only use 4. You can override this with the NumCPUs option
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.267 [notice] You configured a non-loopback address '192.168.100.9:9050' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is wha>
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.267 [notice] Opening Socks listener on 192.168.100.9:9050
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.267 [notice] Opened Socks listener connection (ready) on 192.168.100.9:9050
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.267 [notice] Opening Control listener on 127.0.0.1:9051
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.267 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.267 [notice] Opening OR listener on 0.0.0.0:443
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.267 [notice] Opened OR listener connection (ready) on 0.0.0.0:443
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.267 [notice] Opening OR listener on [2003:a:1504:6000:a03a:d1ff:fea1:8062]:443
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.267 [notice] Opened OR listener connection (ready) on [2003:a:1504:6000:a03a:d1ff:fea1:8062]:443
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.267 [notice] Opening Directory listener on 0.0.0.0:80
Oct 27 22:47:28 Tor tor[6407]: Oct 27 22:47:28.267 [notice] Opened Directory listener connection (ready) on 0.0.0.0:80
Which more information is needed? Can you help me find the cause of this issue?
Edited by anong