Power outage last night & for some reason my UPS didn't prevent my node from turning off.
I restarted it about 4hrs ago.
Core is synched again but lightning channels still haven't come online.
Running Umbrel on Ubuntu server. Decent hardware.
Anyone got any ideas why it takes so long for my channels to come back online? I don't remember it being this long.
After syncing it shouldn’t take much time at all unless they were closed or something. Have you tried to connect from a mobile wallet just to make sure your LN is reachable?
I've never been able to connect to it with Zeus. I tried again recently with no luck (over tor).
I managed to connect with Zap a while back but I eventually uninstalled it when it became depreciated.
I've just restarted Umbrel. Fingers crossed it comes back online quickly.
Do you need to unlock the lightning node wallet for it to finish startup perhaps?
Not familiar with the Umbrel setup at all
It usually just comes back online eventually, but the pain of waiting is horrible.
Power is still off and generator is running.
Need to look at why the UPS didn't save a shutdown. I also need to take the routers off the UPS so that i get longer than 90 mins from it.
The onchain balance is missing about 3 million sats. It looks like it's still trying to find the UTxOs.
Urgh
Is your lightning node somehow out of sync with bitcoin core?
No idea. It's the problem with these node packages.
Everything is so easy but I'm also reluctant to start playing around in the console.
Been feeling like creating a new lightning node and decommissioning my Umbrel.
This is the way
In Linux terminal (ctrl+alt+t) shut down your umbrel with this command: sudo ./umbrel/scripts/stop . See if while doing this it produces any errors. Once done, start 8t again with this command: sudo ./umbrel/scripts/start . See if that produces any errors.
I restarted it already.
From the logs:
lightning
Attaching to lightning_app_proxy_1, lightning_app_1, lightning_lnd_1, lightning_tor_server_1, lightning_tor_1
app_proxy_1 | Validating token: b43e1f6b2f45 ...
app_proxy_1 | Validating token: b43e1f6b2f45 ...
app_proxy_1 | Validating token: b43e1f6b2f45 ...
app_proxy_1 | Validating token: b43e1f6b2f45 ...
app_proxy_1 | Validating token: b43e1f6b2f45 ...
app_proxy_1 | Validating token: b43e1f6b2f45 ...
app_proxy_1 | Validating token: b43e1f6b2f45 ...
app_proxy_1 | Validating token: b43e1f6b2f45 ...
app_proxy_1 | Validating token: b43e1f6b2f45 ...
app_proxy_1 | Validating token: b43e1f6b2f45 ...
app_1 | [backup-monitor] Checking channel backup...
app_1 | [backup-monitor] Sleeping...
app_1 | Checking LND status...
app_1 | LND already unlocked!
app_1 | Checking LND status...
app_1 | LND already unlocked!
app_1 | Checking LND status...
app_1 | LND already unlocked!
app_1 | Checking LND status...
app_1 | LND already unlocked!
lnd_1 | 2023-12-01 21:24:58.219 [ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: server is still in the process of starting
lnd_1 | 2023-12-01 21:24:58.234 [ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: server is still in the process of starting
lnd_1 | 2023-12-01 21:24:58.287 [ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: server is still in the process of starting
lnd_1 | 2023-12-01 21:24:58.300 [ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: server is still in the process of starting
lnd_1 | 2023-12-01 21:24:58.348 [ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: server is still in the process of starting
lnd_1 | 2023-12-01 21:24:58.362 [ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: server is still in the process of starting
lnd_1 | 2023-12-01 21:24:58.574 [ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: server is still in the process of starting
lnd_1 | 2023-12-01 21:24:58.587 [ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: server is still in the process of starting
lnd_1 | 2023-12-01 21:24:58.720 [ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: server is still in the process of starting
lnd_1 | 2023-12-01 21:24:58.739 [ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: server is still in the process of starting
tor_1 | Dec 01 20:37:07.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
tor_1 | Dec 01 20:37:08.000 [notice] Bootstrapped 63% (loading_descriptors): Loading relay descriptors
tor_1 | Dec 01 20:37:09.000 [notice] Bootstrapped 71% (loading_descriptors): Loading relay descriptors
tor_1 | Dec 01 20:37:09.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_1 | Dec 01 20:37:09.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_1 | Dec 01 20:37:09.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_1 | Dec 01 20:37:10.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_1 | Dec 01 20:37:11.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_1 | Dec 01 20:37:11.000 [notice] Bootstrapped 95% (circuit_create): Establis
Looks like it should finish starting eventually. If it still does not after a day - in the old days Umbrel support used to respond to queries in less than a week. They helped me once with a stuck channel. Maybe they still do, try them. Also, chating with chatGPT 4 is not a bad idea. You can ask it how to diagnose, then feed back to it the results of diagnosis, and see where that takes you. But all that is, yes, a console work.
It eventually did what it needed to do & all my channels came back up. It took about 18hrs and I suspect that I prolonged this with my tinkering.
I tweaked some settings to hopefully reduce the start up time for next time.
My UPS now only runs the little NUC so I should only lose the data connection if the power goes out. The power was out for almost as long as my node was.
Time to investigate my new node.
