Hi Peeps,
I’m helping a friend recover funds from his Umbrel. My friend lost access to the Umbrel dashboard.
He wants to send the on-chain and off-chain funds on the Umbrel to external wallets.
Umbrel runs on a Raspberry Pi 4 and is connected to the internet via Ethernet on a node in my home mesh network. The Pi has an SSD and a microSD card.
I’m thinking the easiest way to do this is to access the lnd lncli commands because I am familiar with running lnd.
When I run:
$ ./lncli getinfo
Result:
*** Deprecation notice ***
In a future version of Umbrel, ‘lncli’ will be removed.
Please instead use:
./scripts/app compose lightning exec lnd lncli
When I run:
$ ./scripts/app compose lightning exec lnd lncli -h
Or
$ ./app compose lightning exec lnd lncli getinfo
Both of these do not return anything (including errors).
Has anyone run into this before or can you help point me to another way to accomplish this?
Thanks!
Erik
The complete result from running the debug script is copied below.
=====================
= Umbrel debug info =
Umbrel version
0.5.3
Flashed OS version
v0.5.0
Raspberry Pi Model
Revision : d03114
Serial : 10000000070bc60e
Model : Raspberry Pi 4 Model B Rev 1.4
Firmware
Dec 1 2021 15:01:54
Copyright © 2012 Broadcom
version 71bd3109023a0c8575585ba87cbb374d2eeb038f (clean) (release) (start)
Temperature
temp=52.1’C
Throttling
throttled=0x0
Memory usage
total used free shared buff/cache available
Mem: 7.8G 1.1G 2.2G 376M 4.5G 6.3G
Swap: 4.1G 0B 4.1G
total: 13.5%
system: 13.5%
thunderhub: 0%
ride-the-lightning: 0%
mempool: 0%
lightning-terminal: 0%
lightning: 0%
electrs: 0%
core-lightning: 0%
btcpay-server: 0%
bitcoin: 0%
Memory monitor logs
2023-02-06 13:44:24 Memory monitor running!
2023-02-06 13:44:36 Memory monitor running!
2023-02-06 13:44:49 Memory monitor running!
2023-02-06 13:45:01 Memory monitor running!
2023-02-06 13:45:14 Memory monitor running!
2023-02-06 13:45:26 Memory monitor running!
2023-02-06 13:45:39 Memory monitor running!
2023-02-06 13:45:51 Memory monitor running!
2023-02-06 13:46:04 Memory monitor running!
2023-02-06 13:46:17 Memory monitor running!
Filesystem information
Filesystem Size Used Avail Use% Mounted on
/dev/root 117G 5.8G 107G 6% /
/dev/sda1 916G 870G 0 100% /home/umbrel/umbrel
Startup service logs
Feb 06 13:46:17 umbrel umbrel startup[7236]: Starting decoy backup trigger…
Feb 06 13:46:17 umbrel umbrel startup[7236]: Starting Docker services…
Feb 06 13:46:19 umbrel umbrel startup[7236]: auth is up-to-date
Feb 06 13:46:19 umbrel umbrel startup[7236]: dashboard is up-to-date
Feb 06 13:46:19 umbrel umbrel startup[7236]: tor_server is up-to-date
Feb 06 13:46:19 umbrel umbrel startup[7236]: manager is up-to-date
Feb 06 13:46:19 umbrel umbrel startup[7236]: tor_proxy is up-to-date
Feb 06 13:46:19 umbrel umbrel startup[7236]: Creating nginx …
Feb 06 13:46:19 umbrel umbrel startup[7236]: Creating nginx … error
Feb 06 13:46:19 umbrel umbrel startup[7236]: ERROR: for nginx Cannot create container for service nginx: Conflict. The container name “/nginx” is already in use by container “85e67584117b6b7a6e4c202f28dafc1a38155c3f83510c97e94bb45589c7a865”. You have to remove (or rename) that container to be able to reuse that name.
Feb 06 13:46:19 umbrel umbrel startup[7236]: Encountered errors while bringing up the project.
Feb 06 13:46:20 umbrel umbrel startup[7236]: Failed to start containers
Feb 06 13:46:20 umbrel systemd[1]: umbrel-startup.service: Control process exited, code=exited, status=1/FAILURE
Feb 06 13:46:20 umbrel systemd[1]: umbrel-startup.service: Failed with result ‘exit-code’.
Feb 06 13:46:20 umbrel systemd[1]: Failed to start Umbrel Startup Service.
Feb 06 13:46:30 umbrel systemd[1]: umbrel-startup.service: Service RestartSec=10s expired, scheduling restart.
Feb 06 13:46:30 umbrel systemd[1]: umbrel-startup.service: Scheduled restart job, restart counter is at 39078.
Feb 06 13:46:30 umbrel systemd[1]: Stopped Umbrel Startup Service.
Feb 06 13:46:30 umbrel systemd[1]: Starting Umbrel Startup Service…
Feb 06 13:46:30 umbrel umbrel startup[7793]: ======================================
Feb 06 13:46:30 umbrel umbrel startup[7793]: ============= STARTING ===============
Feb 06 13:46:30 umbrel umbrel startup[7793]: ============== UMBREL ================
Feb 06 13:46:30 umbrel umbrel startup[7793]: ======================================
Feb 06 13:46:30 umbrel umbrel startup[7793]: Setting environment variables…
Feb 06 13:46:30 umbrel umbrel startup[7793]: Starting karen…
Feb 06 13:46:30 umbrel umbrel startup[7793]: Starting status monitors…
Feb 06 13:46:30 umbrel umbrel startup[7793]: Starting memory monitor…
Feb 06 13:46:30 umbrel umbrel startup[7793]: Starting backup monitor…
Feb 06 13:46:30 umbrel umbrel startup[7793]: Starting decoy backup trigger…
Feb 06 13:46:30 umbrel umbrel startup[7793]: Starting Docker services…
External storage service logs
– Logs begin at Sat 2023-02-04 16:31:16 UTC, end at Mon 2023-02-06 13:46:30 UTC. –
– No entries –
External storage SD card update service logs
– Logs begin at Sat 2023-02-04 16:31:16 UTC, end at Mon 2023-02-06 13:46:30 UTC. –
– No entries –
Karen logs
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
karen is running in /home/umbrel/umbrel/events
Docker containers
NAMES STATUS
letsencrypt-nginx-proxy-companion Up 5 days
nginx-gen Up 5 days
generated_btcpayserver_1 Up 5 days
generated_clightning_bitcoin_rest_1 Up 5 days
generated_clightning_bitcoin_charge_1 Up 5 days
generated_clightning_bitcoin_spark_1 Up 5 days
btcpayserver_clightning_bitcoin Up 5 days
generated_nbxplorer_1 Up 5 days
btcpayserver_bitcoind Restarting (1) 46 seconds ago
tor-gen Up 5 days
generated_bitcoin_rtl_1 Up 5 days
tor Up 5 days
generated_postgres_1 Up 5 days
nginx Up 5 days
auth Up 5 days
tor_server Up 5 days
dashboard Up 7 days
manager Up 7 days
tor_proxy Up 5 days
Umbrel logs
Attaching to manager
manager | yarn run v1.22.18
manager | $ node ./bin/www
manager | Tue, 31 Jan 2023 20:35:21 GMT morgan deprecated morgan(options): use morgan(“default”, options) instead at app.js:49:9
manager | Tue, 31 Jan 2023 20:35:21 GMT morgan deprecated default format: use combined format at app.js:49:9
manager | Listening on port 3006
Tor Proxy logs
Attaching to tor_proxy
tor_proxy | Feb 06 06:35:16.000 [notice] Tor has been idle for 3600 seconds; assuming established circuits no longer work.
tor_proxy | Feb 06 07:35:16.000 [notice] Tor has been idle for 3600 seconds; assuming established circuits no longer work.
tor_proxy | Feb 06 08:35:10.000 [notice] Heartbeat: Tor’s uptime is 1 day 0:00 hours, with 0 circuits open. I’ve sent 970 kB and received 6.68 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 21 connections with IPv4 and 0 with IPv6.
tor_proxy | Feb 06 08:35:10.000 [notice] While bootstrapping, fetched this many bytes: 568170 (consensus network-status fetch); 14353 (authority cert fetch); 4851376 (microdescriptor fetch)
tor_proxy | Feb 06 08:35:10.000 [notice] While not bootstrapping, fetched this many bytes: 671353 (consensus network-status fetch)
tor_proxy | Feb 06 09:35:17.000 [notice] Tor has been idle for 3601 seconds; assuming established circuits no longer work.
tor_proxy | Feb 06 10:35:17.000 [notice] Tor has been idle for 3600 seconds; assuming established circuits no longer work.
tor_proxy | Feb 06 11:35:17.000 [notice] Tor has been idle for 3600 seconds; assuming established circuits no longer work.
tor_proxy | Feb 06 12:35:17.000 [notice] Tor has been idle for 3600 seconds; assuming established circuits no longer work.
tor_proxy | Feb 06 13:35:17.000 [notice] Tor has been idle for 3600 seconds; assuming established circuits no longer work.
App logs
bitcoin
Attaching to
btcpay-server
Attaching to
core-lightning
Attaching to
electrs
Attaching to
lightning
Attaching to
lightning-terminal
Attaching to
mempool
Attaching to
ride-the-lightning
Attaching to
thunderhub
Attaching to
==== Result ====
The debug script did not automatically detect any issues with your Umbrel.