My nostr:nprofile1qqs9df4h2deu3aae83fmet5xmrlm4w5l9gdnsy3q2n7dklem7ezmwfc6c32nl sever is 99% full. I will be swapping ssd for 2TB. Don’t zap me for w while. All services are barely working. Shit, as always I had to wait till the last minute.
FAFO time.
So far so good.
New SSD swapped, system installed, data copied frim old ssd. Bitcoind syncing, LND running, AlbyHub running, I can zap!
CLN, electrs in progress
nostr:nprofile1qqs0sxxdz722j74u5kvzym4chlualjx0jef32llvdveg98jpqs0tmlgfwhsdd how could you fuck it up? Even such a stupid lefthanded monkey as humble myself could do it flawlessly. 7hours or so and done.
Huge shoutout to nostr:nprofile1qqs9df4h2deu3aae83fmet5xmrlm4w5l9gdnsy3q2n7dklem7ezmwfc6c32nl for great software. You know when something is properly developed and tested when it just works like charm.
Now I think I know what to do with old SSD with start9 data. I haven’t finished yet with fucking around. Night is long.
Stay frosty
7 hours or so and done ; .... this is one reason a cloud-based node like Alby Hub or Rizful can be a good thing to try.. Rizful can spin up an node in 30 seconds!
7 hours for Bitcoind, electrs LND, CLN
Not only lightning
😎
Since manually editing files is not recommended with start9, I was wondering if there was a way to replicate the db from cln.
By editing the config file it is enough to add this line:
wallet=sqlite3:///home/user/.lightning/bitcoin/lightningd.sqlite3:/my/backup/lightningd.sqlite3
Is there any available option to do it? I've checked long ago and didn't find it in the UI.
Just FYI, I run a mynodeBTC in a VM. In the process of migrating from one host to another all of my lightning channels got force closed. I never did figure out why/ what happened. But urge you to tread cautiously when playing around with two copies of the same node.
I know that. There are no two copies. This was moving node from one ssd to another. But I was cautious and drained my channels before this operation. At least this was what I could do.
Yeah FAFO as always.
Don't get me wrong. Everything what happend is mine. No issues with software. On the plus side, I am learning a lot for example how to back up and restore start9 server.
Current state of affairs:
1. My server with new 2TB disk kept on crashing like before the swap. So I wondered if this might be some issue with the machine itself rather than SSD ... or both? I tried to look into the logs which was hard as it was crashing actually when I was not watching. I am not that advanced in Linux to check what is going on and I could not find the clue (was looking for weny erros related to SSD in dmesg and nothing found) until I thought about bips the machine plays when started and maybe there may be something with the memory (memory parity).
2. In the meantime my old SSD was syncing on another machine where I wanted to put pruned Knots + Datum.
3. So I decided to swap the discs back to have new disk on new machine and old one back on old machine. It was going fine from the start. I synced Core, put LND, CLN back to work, elcrtrs was synced to. I could have stopped on this but no, when you FAFO you FAFO till the end. Switched from Core to Knots with the purpose to have it pruned later. It was still working and then I thought maybe, just maybe I will not prune it and it will be working for some time more since I had still 60GB free space. And then elctrs crashed and whole machine crashed.
4. When I booted it up Knots asked me gently to resync the chain and so now I am here - 86% synced, LND, CLN stopped and I do not know how they will handle that. I am prepared to have all my channels closed. Since that it crashed again. Now it is working for 2 days. And in the meantime there is new machine with 2TB syncing from zero.
The new machine with 2TB is fine and I will put there bitcoin + lightning stack eventually but I would also like to bring the old one to life and than have it for Knots + Datum.
FAFO, FAFO and then FAFO
It took some time but everything is back and working fine. The main issue was actually bring back offline channels on CLN while LND had no problem with that. For CLN I had to reconnect the peers.
Now I’ve got 2 nostr:nprofile1qqs9df4h2deu3aae83fmet5xmrlm4w5l9gdnsy3q2n7dklem7ezmwfc6c32nl servers: one for lightning and the other for onchain bitcoin.
But I think I need #3 for other stuff like Vaultwarden, Simplex, Nextcloud.
