Raspberry Pi 4 running Umbrel is showing low resources:
- CPU never falls below 40%
- Committed memory is at 212% (16.38 GB of 7.71 GB)
I’m running bitcoind, lnd, and other items.
I wish I was able to decypher memory usage in the linux world so I could better diagnose but it is all very arcane.
Here are a few things that might help:
$ free -h
total used free shared buff/cache available
Mem: 3.7Gi 2.6Gi 245Mi 17Mi 896Mi 1.1Gi
Swap: 4.0Gi 2.0Gi 2.0Gi
I tried a reboot (uptime is ~5 hours)
$ ps -A --sort -rss -o pid,pmem:40,cmd:500 | head -n 6 | tr -s " " “;z”
;PID;%MEM;CMD
12535;13.5;bitcoind;-port=8333;-rpcport=8332;-rpcbind=10.21.21.8;-rpcbind=127.0.0.1;-rpcallowip=10.21.0.0/16;-rpcallowip=127.0.0.1;-rpcauth=umbrel:d2faee5d1ae2[[REDACTED]]71fbf391;-zmqpubrawblock=tcp://0.0.0.0:28332;-zmqpubrawtx=tcp://0.0.0.0:28333;-zmqpubhashblock=tcp://0.0.0.0:28334;-zmqpubsequence=tcp://0.0.0.0:28335;-blockfilterindex=1;-peerbloomfilters=1;-peerblockfilters=1;-rpcworkqueue=128
12664;4.8;mariadbd
12639;4.8;lnd;–listen=0.0.0.0:9735;–rpclisten=0.0.0.0:10009;–restlisten=0.0.0.0:8080;–tlsautorefresh;–accept-amp;–rpcmiddleware.enable;–bitcoind.rpchost=10.21.21.8;–bitcoind.rpcuser=umbrel;–bitcoind.rpcpass=1WKN2M[[REDACTED]]CeVgBY=;–bitcoind.zmqpubrawblock=tcp://10.21.21.8:28332;–bitcoind.zmqpubrawtx=tcp://10.21.21.8:28333;–bitcoin.active;–bitcoin.mainnet;–bitcoin.node=bitcoind;–tor.active;–tor.v3;–tor.control=10.21.21.11:29051;–tor.socks=10.21.21.11:9050;–tor.targetipaddress=10.21.21.9;–tor.password=Rrpv[[REDACTED]]yWeA=
20338;3.9;node;–unhandled-rejections=strict;/home/node/app/tracker/index.js
14775;2.5;java;-jar;/usr/local/whirlpool-cli/whirlpool-client-cli-run.jar;–listen;–cli.apiKey=43fecd[[REDACTED]]70c51971;–cli.api.http-enable=true;–cli.api.http-port=8898;–cli.tor=true;–cli.torConfig.coordinator.enabled=true;–cli.torConfig.coordinator.onion=true;–cli.torConfig.backend.enabled=false;–cli.torConfig.backend.onion=false;–cli.mix.liquidityClient=true;–cli.mix.clientsPerPool=1;–resync;–cli.torConfig.executable=/usr/local/bin/tor;–cli.server=MAINNET;–cli.dojo.enabled=true;–cli.dojo.url=http://10.21.21.22:80/v2/
I didn’t see a lot of posts mentioning this issue.
On the plus side, things are still operational… But I’ve noticed that eventually the unit goes unresponsive.
What else can I look at in order to help troubleshoot?