Restore channels via back up

[SalmonSalad]

Hi, i m trying to get my node working again. I m following steps as described by Darthcoin-substack.com

I get stuck on the stem where I need to restore the channels via the back up file…
I thought I had backed up my channels, but cant find teh file on my computer. I read that it is possible to get a back up from the umbrel servers. Is there a dev who can help me out?

“You can also use the online backup of the Umbrel servers (you will need to contact the Umbrel developers for this)”

Your help is much appreciated!

This is the document I m referring to:

Recuperar fondos de un nodo Umbrel

[smolgrrr]

Yep! here’s the guide

@usernameisJim

You can run this command to grab your backup ID:

cat ~/umbrel/logs/karen.log | grep 'backup ID' | tail -n 1

And can provide me your backup ID that populates

If you’re comfortable sharing it here or you can direct message it to me, or at anytime anyone can paste their request in the Telegram Help and Support Channel here if it is more convenient and we can also DM it to you there on Telegram too, the Telegram is a little better for quicker real-time assistance

It helps as well if you provide as close as you can the day you believe your node went down so we can give you the last backup that would have been generated

We never have access to your seed phrase but automated recovery makes it easy so all you need is your seed phrase on your side and your backup file populates, we can check the date and if a backup file exists and we can provide that to you on-demand

Just curious, do you find out what the issue with your node was?

[SalmonSalad]

thanks, @smolgrrr. 2 weeks ago I got this screen after trying to sign in.

restarting or shutting down didnt do the trick.
I then flashed the SD with Balena etcher. That also didnt work, plus after that I was unable to enter my node via command line.

I will try to install a new instance of umbrel, enter with my seed, and then run this command:
cat ~/umbrel/logs/karen.log | grep ‘backup ID’ | tail -n 1
Do I understand that correct?

cheers!

[smolgrrr]

Hey @SalmonSalad, I saw your DM too, i don’t think it’s worth doing a fresh instance just yet.

It sounds like you can access your Umbrel again- ssh in and run the script to get your back-up first

cat ~/umbrel/logs/karen.log | grep ‘backup ID’ | tail -n 1

then to fix your issues with bitcoin starting syncing/starting try the following

@mayank

If you check your debug logs you may have the following:

"Error: Failed loading settings file:

bitcoind_1 | - Unable to parse settings file /data/.bitcoin/settings.json "

To resolve, first connect to your Umbrel device by following the instructions in How to SSH into Umbrel on a Raspberry Pi or by accessing a terminal on your Linux machine

This command is the quickest way to resolve the error, by deleting the file first:
rm ~umbrel/app-data/bitcoin/data/bitcoin/settings.json

Then you should restart Bitcoin:

~/umbrel/scripts/app restart bitcoin

If for any reason when attempting to delete the file you face a permission or other errors that prevent you from doing so, we can also edit the file with this command:

sudo nano umbrel/app-data/bitcoin/data/bitcoin/settings.json

Then it will take you to a blank file and just type and add two lines like this, with the two curly braces exactly like this:
{
}

Then hit CTRL+X to exit, Y to save, and enter to continue.

After completing the edit don’t forget the last step of restarting Bitcoin:

~/umbrel/scripts/app restart bitcoin

Upon restarting wait ~5 minutes and this will resolve the error with the settings.json file.

Fingers crossed this fixes everything, and then you should be able to keep running your node as is.

[SalmonSalad]

Hi @smolgrrr,

Im having the exact issues as described below:

SSH refuses password, web interface logs in fine

unfortunately no solution was given, do you know what to do in this situation?

cheers

[smolgrrr]

Have you tried with both the password ‘moneyprintergobrrr’ and your web umbrel password?

[SalmonSalad]

Yes I did!

No problem logging in via umbrel.local > webversion.

Neither moneyprintergobrrr / password works on ssh

[smolgrrr]

Let me look a little deeper for you, but just to be extra sure, double-check you are following this exactly

@mayank

Type in the following command* and press the Enter key:

ssh -t umbrel@umbrel.local

*In the command given above, you can replace umbrel.local with the local IP of your Umbrel if you prefer. If you are using PowerShell on Windows 10, you may need to run ssh umbrel@umbrel instead of the command given above.

if it’s not ssh ‘umbrel@umbrel.local’, it will be similar to ‘ssh umbrel@192.168.x.x’ for your local IP. i don’t see why moneyprintergobrrr wouldn’t work, but i will look into it

[SalmonSalad]

Cool, will double check tonight.

Appreciate your help

[SalmonSalad]

yep, still the same message:
“Permission denied, please try again.”

• typed in umbrel@umbrel.local and my 192.168… after ssh -t …
• moneyprintergobrrr and my original password

also tried typing in the passwords, pasting via command+v, right mouse Paste.

all same result. Browser, still oke to sign in with my password

[smolgrrr]

Hmmm that’s really strange, still looking into this.
Unfortunately I’m thinking you might need to do a reset of your node, but don’t do anything just yet.

btw, would you mind generating some troubleshooting logs from the settings tab on the web dashboard, and then posting them here?

[smolgrrr]

You can also try reflashing the microSD?

[SalmonSalad]

Did that last week…

[SalmonSalad]

Not sure if I understand. What is it you would like me to do? And whats the purpose?

Thanks

[SalmonSalad]

Hi @smolgrrr

did you possibly find anything?

below the log you asked for.

cheers

=====================
= Umbrel debug info =

Umbrel version

0.5.4

Flashed OS version

v0.5.4

Raspberry Pi Model

Revision : d03114
Serial : 10000000f7cf70bc
Model : Raspberry Pi 4 Model B Rev 1.4

Firmware

May 9 2023 12:16:34
Copyright (c) 2012 Broadcom
version 30aa0d70ab280427ba04ebc718c81d4350b9d394 (clean) (release) (start)

Temperature

temp=62.8’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 7.8G 2.0G 1.3G 377M 4.5G 5.4G
Swap: 4.1G 0B 4.1G

total: 25.0%
lightning: 9.9%
electrs: 7.9%
bitcoin: 4.5%
system: 2.7%

Memory monitor logs

2019-02-14 10:31:11 Memory monitor running!
2019-02-14 10:31:25 Memory monitor running!
2019-02-14 10:31:38 Memory monitor running!
2019-02-14 10:31:52 Memory monitor running!
2019-02-14 10:32:05 Memory monitor running!
2019-02-14 10:32:19 Memory monitor running!
2023-08-05 16:26:15 Memory monitor running!
2218 ? S 0:00 bash ./scripts/memory-monitor
Memory monitor is already running
2023-08-10 16:17:29 Memory monitor running!

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 60G 4.4G 53G 8% /
/dev/sda1 916G 619G 251G 72% /home/umbrel/umbrel

Startup service logs

– Logs begin at Sun 2023-08-13 02:50:24 UTC, end at Tue 2023-08-15 17:59:53 UTC. –
Aug 15 17:08:02 umbrel passwd[21738]: pam_unix(passwd:chauthtok): password changed for umbrel
Aug 15 17:55:20 umbrel passwd[14535]: pam_unix(passwd:chauthtok): password changed for umbrel

External storage service logs

– Logs begin at Sun 2023-08-13 02:50:24 UTC, end at Tue 2023-08-15 17:59:53 UTC. –
– No entries –

External storage SD card update service logs

– Logs begin at Sun 2023-08-13 02:50:24 UTC, end at Tue 2023-08-15 17:59:53 UTC. –
– No entries –

Karen logs

karen is getting triggered!
Deriving keys…
Creating backup…
Adding random padding…
1+0 records in
1+0 records out
2240 bytes (2.2 kB, 2.2 KiB) copied, 0.000267756 s, 8.4 MB/s
Creating encrypted tarball…
backup/
backup/channel.backup
backup/.padding
Uploading backup…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:01 --:–:-- 0
100 5379 0 0 100 5379 0 2094 0:00:02 0:00:02 --:–:-- 2093
100 5525 100 146 100 5379 48 1793 0:00:03 0:00:03 --:–:-- 1841
{“message”:“Successfully uploaded backup 1692070754349.tar.gz.pgp for backup ID f76e4df08cc0adff97f0cefa38c325efba8c17c5ce1ae233771cc3ac0032ebaa”}

====== Backup success =======

Got signal: backup
karen is getting triggered!
Deriving keys…
Creating backup…
Adding random padding…
1+0 records in
1+0 records out
2907 bytes (2.9 kB, 2.8 KiB) copied, 0.000248461 s, 11.7 MB/s
Creating encrypted tarball…
backup/
backup/channel.backup
backup/.padding
Uploading backup…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
100 6189 100 146 100 6043 96 4009 0:00:01 0:00:01 --:–:-- 4104
100 6189 100 146 100 6043 96 4007 0:00:01 0:00:01 --:–:-- 4101
{“message”:“Successfully uploaded backup 1692105472015.tar.gz.pgp for backup ID f76e4df08cc0adff97f0cefa38c325efba8c17c5ce1ae233771cc3ac0032ebaa”}

====== Backup success =======

Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: debug
karen is getting triggered!
Debug result file generated
Got signal: debug
karen is getting triggered!

Docker containers

NAMES STATUS
bitcoin_server_1 Up 5 days
electrs_app_1 Up 5 days
bitcoin_bitcoind_1 Restarting (1) 14 seconds ago
bitcoin_i2pd_daemon_1 Up 5 days
bitcoin_tor_server_1 Up 5 days
bitcoin_app_proxy_1 Up 5 days
bitcoin_tor_1 Up 5 days
lightning_tor_1 Up 5 days
lightning_app_proxy_1 Up 5 days
lightning_app_1 Up 5 days
lightning_tor_server_1 Up 5 days
lightning_lnd_1 Up 5 days
electrs_tor_server_1 Up 5 days
electrs_tor_1 Up 5 days
electrs_app_proxy_1 Up 5 days
electrs_electrs_1 Up 10 seconds
nginx Up 5 days
dashboard Up 5 days
manager Up 5 days
tor_server Up 5 days
auth Up 5 days
tor_proxy Up 5 days

Umbrel logs

Attaching to manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/system/temperature HTTP/1.0” 200 2 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/apps HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/apps?installed=1 HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/system/storage HTTP/1.0” 200 486 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/system/memory HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/system/info HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:03 GMT] “GET /v1/system/get-update HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:03 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:05 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager

Tor Proxy logs

Attaching to tor_proxy
tor_proxy | Aug 14 22:29:42.000 [notice] While not bootstrapping, fetched this many bytes: 2966320 (consensus network-status fetch); 54104 (authority cert fetch); 7636765 (microdescriptor fetch)
tor_proxy | Aug 15 04:29:42.000 [notice] Heartbeat: Tor’s uptime is 4 days 12:00 hours, with 2 circuits open. I’ve sent 7.09 MB and received 29.22 MB. I’ve received 21 connections on IPv4 and 0 on IPv6. I’ve made 131 connections with IPv4 and 0 with IPv6.
tor_proxy | Aug 15 04:29:42.000 [notice] While bootstrapping, fetched this many bytes: 678967 (consensus network-status fetch); 14102 (authority cert fetch); 11108440 (microdescriptor fetch)
tor_proxy | Aug 15 04:29:42.000 [notice] While not bootstrapping, fetched this many bytes: 3140257 (consensus network-status fetch); 54104 (authority cert fetch); 7995769 (microdescriptor fetch)
tor_proxy | Aug 15 10:29:42.000 [notice] Heartbeat: Tor’s uptime is 4 days 18:00 hours, with 0 circuits open. I’ve sent 7.14 MB and received 29.45 MB. I’ve received 21 connections on IPv4 and 0 on IPv6. I’ve made 137 connections with IPv4 and 0 with IPv6.
tor_proxy | Aug 15 10:29:42.000 [notice] While bootstrapping, fetched this many bytes: 678967 (consensus network-status fetch); 14102 (authority cert fetch); 11108440 (microdescriptor fetch)
tor_proxy | Aug 15 10:29:42.000 [notice] While not bootstrapping, fetched this many bytes: 3323200 (consensus network-status fetch); 54104 (authority cert fetch); 7995769 (microdescriptor fetch)
tor_proxy | Aug 15 16:29:42.000 [notice] Heartbeat: Tor’s uptime is 5 days 0:00 hours, with 0 circuits open. I’ve sent 7.42 MB and received 30.27 MB. I’ve received 22 connections on IPv4 and 0 on IPv6. I’ve made 143 connections with IPv4 and 0 with IPv6.
tor_proxy | Aug 15 16:29:42.000 [notice] While bootstrapping, fetched this many bytes: 678967 (consensus network-status fetch); 14102 (authority cert fetch); 11108440 (microdescriptor fetch)
tor_proxy | Aug 15 16:29:42.000 [notice] While not bootstrapping, fetched this many bytes: 3465926 (consensus network-status fetch); 54104 (authority cert fetch); 8410950 (microdescriptor fetch)

App logs

bitcoin

Attaching to bitcoin_server_1, bitcoin_bitcoind_1, bitcoin_i2pd_daemon_1, bitcoin_tor_server_1, bitcoin_app_proxy_1, bitcoin_tor_1
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
i2pd_daemon_1 | 17:41:28@300/error - Tunnels: Can’t select next hop for CfQSrcwAzB~aSc58DUPyXTCEAg-7ZowKwIVolsobz6w=
i2pd_daemon_1 | 17:41:28@300/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 17:42:28@300/error - Tunnels: Can’t select next hop for bqhVgrEHQP5t2-gSMq-LNOrwby3X~whpyR-eW5TwZCI=
i2pd_daemon_1 | 17:42:28@300/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 17:43:28@300/error - Tunnels: Can’t select next hop for Yw7IC7K5IeyTyyWNqjjvZWKN3Lq15xhH6ZAcgSOAWNA=
i2pd_daemon_1 | 17:43:28@300/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 17:46:28@761/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 17:47:23@300/error - Tunnels: Can’t select next hop for tz9RhdJsIguypvBBVH4A40EOf8uWYKGG756ZNPv-wNs=
i2pd_daemon_1 | 17:47:23@300/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 17:49:58@761/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.9 - - [Tue, 15 Aug 2023 17:49:45 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (iPhone; CPU iPhone OS 16_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/115.0.5790.160 Mobile/15E148 Safari/604.1”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.9 - - [Tue, 15 Aug 2023 17:55:13 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (iPhone; CPU iPhone OS 16_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/115.0.5790.160 Mobile/15E148 Safari/604.1”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.9 - - [Tue, 15 Aug 2023 17:55:16 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (iPhone; CPU iPhone OS 16_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/115.0.5790.160 Mobile/15E148 Safari/604.1”
server_1 |
server_1 | umbrel-middleware
bitcoind_1 |
bitcoind_1 | Error: Failed loading settings file:
bitcoind_1 | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoind_1 |
bitcoind_1 | Error: Failed loading settings file:
bitcoind_1 | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoind_1 |
bitcoind_1 | Error: Failed loading settings file:
bitcoind_1 | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoind_1 |
tor_1 | Aug 15 10:29:56.000 [notice] Heartbeat: Tor’s uptime is 4 days 18:00 hours, with 20 circuits open. I’ve sent 92.47 MB and received 91.84 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 54 connections with IPv4 and 0 with IPv6.
tor_1 | Aug 15 10:29:56.000 [notice] While bootstrapping, fetched this many bytes: 678744 (consensus network-status fetch); 11092 (authority cert fetch); 11097985 (microdescriptor fetch)
tor_1 | Aug 15 10:29:56.000 [notice] While not bootstrapping, fetched this many bytes: 3301654 (consensus network-status fetch); 59268 (authority cert fetch); 8888261 (microdescriptor fetch)
tor_1 | Aug 15 13:47:28.000 [notice] No circuits are opened. Relaxed timeout for circuit 6643 (a Hidden service: Establishing introduction point 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 53100 seconds]
tor_1 | Aug 15 16:29:56.000 [notice] Heartbeat: Tor’s uptime is 5 days 0:00 hours, with 15 circuits open. I’ve sent 96.27 MB and received 95.72 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 56 connections with IPv4 and 0 with IPv6.
tor_1 | Aug 15 16:29:56.000 [notice] While bootstrapping, fetched this many bytes: 678744 (consensus network-status fetch); 11092 (authority cert fetch); 11097985 (microdescriptor fetch)
tor_1 | Aug 15 16:29:56.000 [notice] While not bootstrapping, fetched this many bytes: 3437712 (consensus network-status fetch); 59268 (authority cert fetch); 9149292 (microdescriptor fetch)
tor_1 | Aug 15 17:03:28.000 [warn] Received http status code 404 (“Not found”) from server 217.79.181.76:8443 while fetching “/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97”.

electrs

Attaching to electrs_app_1, electrs_tor_server_1, electrs_tor_1, electrs_app_proxy_1, electrs_electrs_1
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → http://10.21.22.4:3006
app_proxy_1 | Waiting for 10.21.22.4:3006 to open…
app_proxy_1 | Electrs is now ready…
app_proxy_1 | Listening on port: 2102
app_1 | > umbrel-electrs@1.0.1 dev:backend
app_1 | > npm run start -w umbrel-electrs-backend
app_1 |
app_1 |
app_1 | > umbrel-electrs-backend@0.1.12 start
app_1 | > node ./bin/www
app_1 |
app_1 | Thu, 10 Aug 2023 16:30:26 GMT morgan deprecated morgan(options): use morgan(“default”, options) instead at app.js:28:9
app_1 | Thu, 10 Aug 2023 16:30:26 GMT morgan deprecated default format: use combined format at app.js:28:9
app_1 | Listening on port 3006
tor_1 | Aug 15 10:29:54.000 [notice] Heartbeat: Tor’s uptime is 4 days 18:00 hours, with 9 circuits open. I’ve sent 58.45 MB and received 82.15 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 59 connections with IPv4 and 0 with IPv6.
tor_1 | Aug 15 10:29:54.000 [notice] While bootstrapping, fetched this many bytes: 678744 (consensus network-status fetch); 11092 (authority cert fetch); 11097985 (microdescriptor fetch)
tor_1 | Aug 15 10:29:54.000 [notice] While not bootstrapping, fetched this many bytes: 3925647 (consensus network-status fetch); 41150 (authority cert fetch); 8688061 (microdescriptor fetch)
tor_1 | Aug 15 12:22:29.000 [notice] No circuits are opened. Relaxed timeout for circuit 3673 (a Hidden service: Uploading HS descriptor 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [3 similar message(s) suppressed in last 33240 seconds]
tor_1 | Aug 15 16:29:54.000 [notice] Heartbeat: Tor’s uptime is 5 days 0:00 hours, with 9 circuits open. I’ve sent 61.33 MB and received 85.46 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 62 connections with IPv4 and 0 with IPv6.
tor_1 | Aug 15 16:29:54.000 [notice] While bootstrapping, fetched this many bytes: 678744 (consensus network-status fetch); 11092 (authority cert fetch); 11097985 (microdescriptor fetch)
tor_1 | Aug 15 16:29:54.000 [notice] While not bootstrapping, fetched this many bytes: 4080579 (consensus network-status fetch); 42924 (authority cert fetch); 8876917 (microdescriptor fetch)
electrs_1 | Error: electrs failed
electrs_1 |
electrs_1 | Caused by:
electrs_1 | 0: failed to open bitcoind cookie file: /data/.bitcoin/.cookie
electrs_1 | 1: No such file or directory (os error 2)
electrs_1 | Starting electrs 0.9.10 on aarch64 linux with Config { network: Bitcoin, db_path: “/data/db/bitcoin”, daemon_dir: “/data/.bitcoin”, daemon_auth: CookieFile(“/data/.bitcoin/.cookie”), daemon_rpc_addr: 10.21.21.8:8332, daemon_p2p_addr: 10.21.21.8:8333, electrum_rpc_addr: 0.0.0.0:50001, monitoring_addr: 127.0.0.1:4224, wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: None, reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, disable_electrum_rpc: false, server_banner: “Umbrel Electrs (0.9.10)”, signet_magic: 3652501241, args: }
electrs_1 | [2023-08-15T18:00:04.496Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
electrs_1 | [2023-08-15T18:00:04.496Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001
electrs_1 | [2023-08-15T18:00:04.565Z INFO electrs::db] “/data/db/bitcoin”: 167 SST files, 40.988140253 GB, 5.140242179 Grows
electrs_1 | [2023-08-15T18:00:09.531Z INFO electrs::chain] loading 793219 headers, tip=00000000000000000003f5ccbd928f0f45dfb53c9c224390c848208ca9264c2f

lightning

Attaching to lightning_tor_1, lightning_app_proxy_1, lightning_app_1, lightning_tor_server_1, lightning_lnd_1
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
lnd_1 | 2023-08-10 16:29:57.250 [INF] RPCS: RPC server listening on 0.0.0.0:10009
lnd_1 | 2023-08-10 16:29:57.392 [INF] RPCS: gRPC proxy started at 0.0.0.0:8080
lnd_1 | 2023-08-10 16:29:57.392 [INF] LTND: Opening the main database, this might take a few minutes…
lnd_1 | 2023-08-10 16:29:57.392 [INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
lnd_1 | 2023-08-10 16:30:36.445 [INF] LTND: Creating local graph and channel state DB instances
lnd_1 | 2023-08-10 16:30:39.380 [INF] CHDB: Checking for schema update: latest_version=29, db_version=29
lnd_1 | 2023-08-10 16:30:39.380 [INF] CHDB: Checking for optional update: prune_revocation_log=false, db_version=empty
lnd_1 | 2023-08-10 16:30:39.380 [INF] LTND: Database(s) now open (time_to_open=41.987798664s)!
lnd_1 | 2023-08-10 16:30:39.381 [INF] LTND: We’re not running within systemd or the service type is not ‘notify’
lnd_1 | 2023-08-10 16:30:39.381 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.
tor_1 | Aug 15 10:10:28.000 [notice] No circuits are opened. Relaxed timeout for circuit 6505 (a Measuring circuit timeout 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway.
tor_1 | Aug 15 10:29:56.000 [notice] Heartbeat: Tor’s uptime is 4 days 18:00 hours, with 20 circuits open. I’ve sent 91.72 MB and received 91.36 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 68 connections with IPv4 and 0 with IPv6.
tor_1 | Aug 15 10:29:56.000 [notice] While bootstrapping, fetched this many bytes: 678744 (consensus network-status fetch); 11092 (authority cert fetch); 11097985 (microdescriptor fetch)
tor_1 | Aug 15 10:29:56.000 [notice] While not bootstrapping, fetched this many bytes: 3290753 (consensus network-status fetch); 13333 (authority cert fetch); 9093450 (microdescriptor fetch)
tor_1 | Aug 15 16:29:56.000 [notice] Heartbeat: Tor’s uptime is 5 days 0:00 hours, with 20 circuits open. I’ve sent 96.15 MB and received 95.20 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 71 connections with IPv4 and 0 with IPv6.
tor_1 | Aug 15 16:29:56.000 [notice] While bootstrapping, fetched this many bytes: 678744 (consensus network-status fetch); 11092 (authority cert fetch); 11097985 (microdescriptor fetch)
tor_1 | Aug 15 16:29:56.000 [notice] While not bootstrapping, fetched this many bytes: 3460989 (consensus network-status fetch); 13333 (authority cert fetch); 9361021 (microdescriptor fetch)
tor_1 | Aug 15 17:13:32.000 [notice] No circuits are opened. Relaxed timeout for circuit 6894 (a Measuring circuit timeout 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway.

==== Result ====

The debug script did not automatically detect any issues with your Umbrel.

[SalmonSalad]

hi smolgrrr,

Did you have a chance to look into it?

below the log you asked for

Cheers

=====================
= Umbrel debug info =

Umbrel version

0.5.4

Flashed OS version

v0.5.4

Raspberry Pi Model

Revision : d03114
Serial : 10000000f7cf70bc
Model : Raspberry Pi 4 Model B Rev 1.4

Firmware

May 9 2023 12:16:34
Copyright (c) 2012 Broadcom
version 30aa0d70ab280427ba04ebc718c81d4350b9d394 (clean) (release) (start)

Temperature

temp=62.8’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 7.8G 2.0G 1.3G 377M 4.5G 5.4G
Swap: 4.1G 0B 4.1G

total: 25.0%
lightning: 9.9%
electrs: 7.9%
bitcoin: 4.5%
system: 2.7%

Memory monitor logs

2019-02-14 10:31:11 Memory monitor running!
2019-02-14 10:31:25 Memory monitor running!
2019-02-14 10:31:38 Memory monitor running!
2019-02-14 10:31:52 Memory monitor running!
2019-02-14 10:32:05 Memory monitor running!
2019-02-14 10:32:19 Memory monitor running!
2023-08-05 16:26:15 Memory monitor running!
2218 ? S 0:00 bash ./scripts/memory-monitor
Memory monitor is already running
2023-08-10 16:17:29 Memory monitor running!

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 60G 4.4G 53G 8% /
/dev/sda1 916G 619G 251G 72% /home/umbrel/umbrel

Startup service logs

– Logs begin at Sun 2023-08-13 02:50:24 UTC, end at Tue 2023-08-15 17:59:53 UTC. –
Aug 15 17:08:02 umbrel passwd[21738]: pam_unix(passwd:chauthtok): password changed for umbrel
Aug 15 17:55:20 umbrel passwd[14535]: pam_unix(passwd:chauthtok): password changed for umbrel

External storage service logs

– Logs begin at Sun 2023-08-13 02:50:24 UTC, end at Tue 2023-08-15 17:59:53 UTC. –
– No entries –

External storage SD card update service logs

– Logs begin at Sun 2023-08-13 02:50:24 UTC, end at Tue 2023-08-15 17:59:53 UTC. –
– No entries –

Karen logs

karen is getting triggered!
Deriving keys…
Creating backup…
Adding random padding…
1+0 records in
1+0 records out
2240 bytes (2.2 kB, 2.2 KiB) copied, 0.000267756 s, 8.4 MB/s
Creating encrypted tarball…
backup/
backup/channel.backup
backup/.padding
Uploading backup…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:01 --:–:-- 0
100 5379 0 0 100 5379 0 2094 0:00:02 0:00:02 --:–:-- 2093
100 5525 100 146 100 5379 48 1793 0:00:03 0:00:03 --:–:-- 1841
{“message”:“Successfully uploaded backup 1692070754349.tar.gz.pgp for backup ID f76e4df08cc0adff97f0cefa38c325efba8c17c5ce1ae233771cc3ac0032ebaa”}

====== Backup success =======

Got signal: backup
karen is getting triggered!
Deriving keys…
Creating backup…
Adding random padding…
1+0 records in
1+0 records out
2907 bytes (2.9 kB, 2.8 KiB) copied, 0.000248461 s, 11.7 MB/s
Creating encrypted tarball…
backup/
backup/channel.backup
backup/.padding
Uploading backup…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
100 6189 100 146 100 6043 96 4009 0:00:01 0:00:01 --:–:-- 4104
100 6189 100 146 100 6043 96 4007 0:00:01 0:00:01 --:–:-- 4101
{“message”:“Successfully uploaded backup 1692105472015.tar.gz.pgp for backup ID f76e4df08cc0adff97f0cefa38c325efba8c17c5ce1ae233771cc3ac0032ebaa”}

====== Backup success =======

Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: debug
karen is getting triggered!
Debug result file generated
Got signal: debug
karen is getting triggered!

Docker containers

NAMES STATUS
bitcoin_server_1 Up 5 days
electrs_app_1 Up 5 days
bitcoin_bitcoind_1 Restarting (1) 14 seconds ago
bitcoin_i2pd_daemon_1 Up 5 days
bitcoin_tor_server_1 Up 5 days
bitcoin_app_proxy_1 Up 5 days
bitcoin_tor_1 Up 5 days
lightning_tor_1 Up 5 days
lightning_app_proxy_1 Up 5 days
lightning_app_1 Up 5 days
lightning_tor_server_1 Up 5 days
lightning_lnd_1 Up 5 days
electrs_tor_server_1 Up 5 days
electrs_tor_1 Up 5 days
electrs_app_proxy_1 Up 5 days
electrs_electrs_1 Up 10 seconds
nginx Up 5 days
dashboard Up 5 days
manager Up 5 days
tor_server Up 5 days
auth Up 5 days
tor_proxy Up 5 days

Umbrel logs

Attaching to manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/system/temperature HTTP/1.0” 200 2 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/apps HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/apps?installed=1 HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/system/storage HTTP/1.0” 200 486 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/system/memory HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/system/info HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:02 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:03 GMT] “GET /v1/system/get-update HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:03 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 18:00:05 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager

Tor Proxy logs

Attaching to tor_proxy
tor_proxy | Aug 14 22:29:42.000 [notice] While not bootstrapping, fetched this many bytes: 2966320 (consensus network-status fetch); 54104 (authority cert fetch); 7636765 (microdescriptor fetch)
tor_proxy | Aug 15 04:29:42.000 [notice] Heartbeat: Tor’s uptime is 4 days 12:00 hours, with 2 circuits open. I’ve sent 7.09 MB and received 29.22 MB. I’ve received 21 connections on IPv4 and 0 on IPv6. I’ve made 131 connections with IPv4 and 0 with IPv6.
tor_proxy | Aug 15 04:29:42.000 [notice] While bootstrapping, fetched this many bytes: 678967 (consensus network-status fetch); 14102 (authority cert fetch); 11108440 (microdescriptor fetch)
tor_proxy | Aug 15 04:29:42.000 [notice] While not bootstrapping, fetched this many bytes: 3140257 (consensus network-status fetch); 54104 (authority cert fetch); 7995769 (microdescriptor fetch)
tor_proxy | Aug 15 10:29:42.000 [notice] Heartbeat: Tor’s uptime is 4 days 18:00 hours, with 0 circuits open. I’ve sent 7.14 MB and received 29.45 MB. I’ve received 21 connections on IPv4 and 0 on IPv6. I’ve made 137 connections with IPv4 and 0 with IPv6.
tor_proxy | Aug 15 10:29:42.000 [notice] While bootstrapping, fetched this many bytes: 678967 (consensus network-status fetch); 14102 (authority cert fetch); 11108440 (microdescriptor fetch)
tor_proxy | Aug 15 10:29:42.000 [notice] While not bootstrapping, fetched this many bytes: 3323200 (consensus network-status fetch); 54104 (authority cert fetch); 7995769 (microdescriptor fetch)
tor_proxy | Aug 15 16:29:42.000 [notice] Heartbeat: Tor’s uptime is 5 days 0:00 hours, with 0 circuits open. I’ve sent 7.42 MB and received 30.27 MB. I’ve received 22 connections on IPv4 and 0 on IPv6. I’ve made 143 connections with IPv4 and 0 with IPv6.
tor_proxy | Aug 15 16:29:42.000 [notice] While bootstrapping, fetched this many bytes: 678967 (consensus network-status fetch); 14102 (authority cert fetch); 11108440 (microdescriptor fetch)
tor_proxy | Aug 15 16:29:42.000 [notice] While not bootstrapping, fetched this many bytes: 3465926 (consensus network-status fetch); 54104 (authority cert fetch); 8410950 (microdescriptor fetch)

App logs

bitcoin

Attaching to bitcoin_server_1, bitcoin_bitcoind_1, bitcoin_i2pd_daemon_1, bitcoin_tor_server_1, bitcoin_app_proxy_1, bitcoin_tor_1
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
i2pd_daemon_1 | 17:41:28@300/error - Tunnels: Can’t select next hop for CfQSrcwAzB~aSc58DUPyXTCEAg-7ZowKwIVolsobz6w=
i2pd_daemon_1 | 17:41:28@300/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 17:42:28@300/error - Tunnels: Can’t select next hop for bqhVgrEHQP5t2-gSMq-LNOrwby3X~whpyR-eW5TwZCI=
i2pd_daemon_1 | 17:42:28@300/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 17:43:28@300/error - Tunnels: Can’t select next hop for Yw7IC7K5IeyTyyWNqjjvZWKN3Lq15xhH6ZAcgSOAWNA=
i2pd_daemon_1 | 17:43:28@300/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 17:46:28@761/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 17:47:23@300/error - Tunnels: Can’t select next hop for tz9RhdJsIguypvBBVH4A40EOf8uWYKGG756ZNPv-wNs=
i2pd_daemon_1 | 17:47:23@300/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 17:49:58@761/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.9 - - [Tue, 15 Aug 2023 17:49:45 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (iPhone; CPU iPhone OS 16_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/115.0.5790.160 Mobile/15E148 Safari/604.1”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.9 - - [Tue, 15 Aug 2023 17:55:13 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (iPhone; CPU iPhone OS 16_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/115.0.5790.160 Mobile/15E148 Safari/604.1”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.9 - - [Tue, 15 Aug 2023 17:55:16 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (iPhone; CPU iPhone OS 16_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/115.0.5790.160 Mobile/15E148 Safari/604.1”
server_1 |
server_1 | umbrel-middleware
bitcoind_1 |
bitcoind_1 | Error: Failed loading settings file:
bitcoind_1 | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoind_1 |
bitcoind_1 | Error: Failed loading settings file:
bitcoind_1 | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoind_1 |
bitcoind_1 | Error: Failed loading settings file:
bitcoind_1 | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoind_1 |
tor_1 | Aug 15 10:29:56.000 [notice] Heartbeat: Tor’s uptime is 4 days 18:00 hours, with 20 circuits open. I’ve sent 92.47 MB and received 91.84 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 54 connections with IPv4 and 0 with IPv6.
tor_1 | Aug 15 10:29:56.000 [notice] While bootstrapping, fetched this many bytes: 678744 (consensus network-status fetch); 11092 (authority cert fetch); 11097985 (microdescriptor fetch)
tor_1 | Aug 15 10:29:56.000 [notice] While not bootstrapping, fetched this many bytes: 3301654 (consensus network-status fetch); 59268 (authority cert fetch); 8888261 (microdescriptor fetch)
tor_1 | Aug 15 13:47:28.000 [notice] No circuits are opened. Relaxed timeout for circuit 6643 (a Hidden service: Establishing introduction point 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 53100 seconds]
tor_1 | Aug 15 16:29:56.000 [notice] Heartbeat: Tor’s uptime is 5 days 0:00 hours, with 15 circuits open. I’ve sent 96.27 MB and received 95.72 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 56 connections with IPv4 and 0 with IPv6.
tor_1 | Aug 15 16:29:56.000 [notice] While bootstrapping, fetched this many bytes: 678744 (consensus network-status fetch); 11092 (authority cert fetch); 11097985 (microdescriptor fetch)
tor_1 | Aug 15 16:29:56.000 [notice] While not bootstrapping, fetched this many bytes: 3437712 (consensus network-status fetch); 59268 (authority cert fetch); 9149292 (microdescriptor fetch)
tor_1 | Aug 15 17:03:28.000 [warn] Received http status code 404 (“Not found”) from server 217.79.181.76:8443 while fetching “/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97”.

electrs

Attaching to electrs_app_1, electrs_tor_server_1, electrs_tor_1, electrs_app_proxy_1, electrs_electrs_1
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → http://10.21.22.4:3006
app_proxy_1 | Waiting for 10.21.22.4:3006 to open…
app_proxy_1 | Electrs is now ready…
app_proxy_1 | Listening on port: 2102
app_1 | > umbrel-electrs@1.0.1 dev:backend
app_1 | > npm run start -w umbrel-electrs-backend
app_1 |
app_1 |
app_1 | > umbrel-electrs-backend@0.1.12 start
app_1 | > node ./bin/www
app_1 |
app_1 | Thu, 10 Aug 2023 16:30:26 GMT morgan deprecated morgan(options): use morgan(“default”, options) instead at app.js:28:9
app_1 | Thu, 10 Aug 2023 16:30:26 GMT morgan deprecated default format: use combined format at app.js:28:9
app_1 | Listening on port 3006
tor_1 | Aug 15 10:29:54.000 [notice] Heartbeat: Tor’s uptime is 4 days 18:00 hours, with 9 circuits open. I’ve sent 58.45 MB and received 82.15 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 59 connections with IPv4 and 0 with IPv6.
tor_1 | Aug 15 10:29:54.000 [notice] While bootstrapping, fetched this many bytes: 678744 (consensus network-status fetch); 11092 (authority cert fetch); 11097985 (microdescriptor fetch)
tor_1 | Aug 15 10:29:54.000 [notice] While not bootstrapping, fetched this many bytes: 3925647 (consensus network-status fetch); 41150 (authority cert fetch); 8688061 (microdescriptor fetch)
tor_1 | Aug 15 12:22:29.000 [notice] No circuits are opened. Relaxed timeout for circuit 3673 (a Hidden service: Uploading HS descriptor 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [3 similar message(s) suppressed in last 33240 seconds]
tor_1 | Aug 15 16:29:54.000 [notice] Heartbeat: Tor’s uptime is 5 days 0:00 hours, with 9 circuits open. I’ve sent 61.33 MB and received 85.46 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 62 connections with IPv4 and 0 with IPv6.
tor_1 | Aug 15 16:29:54.000 [notice] While bootstrapping, fetched this many bytes: 678744 (consensus network-status fetch); 11092 (authority cert fetch); 11097985 (microdescriptor fetch)
tor_1 | Aug 15 16:29:54.000 [notice] While not bootstrapping, fetched this many bytes: 4080579 (consensus network-status fetch); 42924 (authority cert fetch); 8876917 (microdescriptor fetch)
electrs_1 | Error: electrs failed
electrs_1 |
electrs_1 | Caused by:
electrs_1 | 0: failed to open bitcoind cookie file: /data/.bitcoin/.cookie
electrs_1 | 1: No such file or directory (os error 2)
electrs_1 | Starting electrs 0.9.10 on aarch64 linux with Config { network: Bitcoin, db_path: “/data/db/bitcoin”, daemon_dir: “/data/.bitcoin”, daemon_auth: CookieFile(“/data/.bitcoin/.cookie”), daemon_rpc_addr: 10.21.21.8:8332, daemon_p2p_addr: 10.21.21.8:8333, electrum_rpc_addr: 0.0.0.0:50001, monitoring_addr: 127.0.0.1:4224, wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: None, reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, disable_electrum_rpc: false, server_banner: “Umbrel Electrs (0.9.10)”, signet_magic: 3652501241, args: }
electrs_1 | [2023-08-15T18:00:04.496Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
electrs_1 | [2023-08-15T18:00:04.496Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001
electrs_1 | [2023-08-15T18:00:04.565Z INFO electrs::db] “/data/db/bitcoin”: 167 SST files, 40.988140253 GB, 5.140242179 Grows
electrs_1 | [2023-08-15T18:00:09.531Z INFO electrs::chain] loading 793219 headers, tip=00000000000000000003f5ccbd928f0f45dfb53c9c224390c848208ca9264c2f

lightning

Attaching to lightning_tor_1, lightning_app_proxy_1, lightning_app_1, lightning_tor_server_1, lightning_lnd_1
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
app_proxy_1 | Validating token: c6b0ab964297 …
lnd_1 | 2023-08-10 16:29:57.250 [INF] RPCS: RPC server listening on 0.0.0.0:10009
lnd_1 | 2023-08-10 16:29:57.392 [INF] RPCS: gRPC proxy started at 0.0.0.0:8080
lnd_1 | 2023-08-10 16:29:57.392 [INF] LTND: Opening the main database, this might take a few minutes…
lnd_1 | 2023-08-10 16:29:57.392 [INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
lnd_1 | 2023-08-10 16:30:36.445 [INF] LTND: Creating local graph and channel state DB instances
lnd_1 | 2023-08-10 16:30:39.380 [INF] CHDB: Checking for schema update: latest_version=29, db_version=29
lnd_1 | 2023-08-10 16:30:39.380 [INF] CHDB: Checking for optional update: prune_revocation_log=false, db_version=empty
lnd_1 | 2023-08-10 16:30:39.380 [INF] LTND: Database(s) now open (time_to_open=41.987798664s)!
lnd_1 | 2023-08-10 16:30:39.381 [INF] LTND: We’re not running within systemd or the service type is not ‘notify’
lnd_1 | 2023-08-10 16:30:39.381 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.
tor_1 | Aug 15 10:10:28.000 [notice] No circuits are opened. Relaxed timeout for circuit 6505 (a Measuring circuit timeout 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway.
tor_1 | Aug 15 10:29:56.000 [notice] Heartbeat: Tor’s uptime is 4 days 18:00 hours, with 20 circuits open. I’ve sent 91.72 MB and received 91.36 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 68 connections with IPv4 and 0 with IPv6.
tor_1 | Aug 15 10:29:56.000 [notice] While bootstrapping, fetched this many bytes: 678744 (consensus network-status fetch); 11092 (authority cert fetch); 11097985 (microdescriptor fetch)
tor_1 | Aug 15 10:29:56.000 [notice] While not bootstrapping, fetched this many bytes: 3290753 (consensus network-status fetch); 13333 (authority cert fetch); 9093450 (microdescriptor fetch)
tor_1 | Aug 15 16:29:56.000 [notice] Heartbeat: Tor’s uptime is 5 days 0:00 hours, with 20 circuits open. I’ve sent 96.15 MB and received 95.20 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 71 connections with IPv4 and 0 with IPv6.
tor_1 | Aug 15 16:29:56.000 [notice] While bootstrapping, fetched this many bytes: 678744 (consensus network-status fetch); 11092 (authority cert fetch); 11097985 (microdescriptor fetch)
tor_1 | Aug 15 16:29:56.000 [notice] While not bootstrapping, fetched this many bytes: 3460989 (consensus network-status fetch); 13333 (authority cert fetch); 9361021 (microdescriptor fetch)
tor_1 | Aug 15 17:13:32.000 [notice] No circuits are opened. Relaxed timeout for circuit 6894 (a Measuring circuit timeout 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway.

==== Result ====

The debug script did not automatically detect any issues with your Umbrel.

[smolgrrr]

Apologies for the delayed response @SalmonSalad, have you tried the password mentioned in the logs there under start-up service logs? (That shouldn’t be in the logs, I will raise that with the team, but don’t worry this can’t be used to access your Umbrel outside of home)

At least we can see the issue that needs to be fixed with your Bitcoin node once we can SSH in

[SalmonSalad]

Hi,

Strange that password (plus log), never gave the command to change it and also the password itselve was not created by me. unfortunately that also does not give me access.

[smolgrrr]

Ok, well at least we definitely have your backup ID, and I assume you have the seed phrase.

It is best now that we do a fresh instance of Umbrel. You can reformat your SSD How to easily reformat an ext4 / Umbrel drive and then use your reflashed SD card to start again.
Once, you have the bitcoin app and lightning up again, you should be able to restore with your seed phrase. This should display recent lightning back-ups, but if it doesn’t let us know and we will send the encrypted file to you.

[SalmonSalad]

Hi @smolgrrr, have the apps running again (BTC&Lightning).

I do not see my channels yet. I had 4 channels, can you help me out?

cheers and have a good weekend!