lnd: LND OOM killed

Background

I found out that LND was killed by OOM killer

Your environment

version of lnd: 0.5.1-beta
which operating system (uname -a on *Nix): Centos Linux para-01.virtual 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
version of btcd, bitcoind, or other backend: bitcoind 0.17.0.1 - custom compiled w/o wallet and w/o GUI
any other relevant environment details: 8GB RAM

Steps to reproduce

Run lnd long enough; 19 channels open, sorry, I don’t know any other relevant specifics

Expected behaviour

LND not consuming so much memory to trigger OOM killer

Actual behaviour

LND triggered OOM killer with message: Killed process 21904 (lnd) total-vm:7369304kB, anon-rss:5696000kB, file-rss:0kB, shmem-rss:0kB

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 18 (13 by maintainers)

Most upvoted comments

lnd is meant to only start after bitcoind has synced.

On Sat, Feb 23, 2019, 3:32 AM David Parrish notifications@github.com wrote:

LND wasn’t killed on my system but it did use 13 GB of RAM which was all available non swap memory. It happened just after bitcoind fully synced.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/lightningnetwork/lnd/issues/2551#issuecomment-466640758, or mute the thread https://github.com/notifications/unsubscribe-auth/AA87LpfZX2rnoXFvWIZxNhIbOsqnBks4ks5vQSa3gaJpZM4aV4jj .

Roasbeef on Feb 23, 2019