Could not load channels from the database - update v0.10.2 to v0.11.0.1-7

[TRIGEMTECH]

Performed c-lightning update from v0.10.2 to v0.11.0.1-7-ge516a5d on Ubuntu 20.04 OS following steps to 'Build on Ubuntu'. Appeared to complete without error. After update encountered error when running lightningd:

2022-05-03T15:26:49.436Z INFO lightningd: Updating database from version 190 to 197
2022-05-03T15:26:52.311Z INFO connectd: Static Tor service onion address: "sjslusyyflv3i39jex5w7jdi3eojwwtbvyrxgbhyvjn3gnuf3zis6rid.onion:9735,127.0.0.1:9735" bound from extern port 9735
2022-05-03T15:26:52.340Z INFO plugin-bcli: bitcoin-cli initialized and connected to bitcoind.
Could not load channels from the database

Observed 'lightningd.sqlite3' was reduced in size from 936.3 MB to 397.7 MB.

Added debug to config and executed again to create attached 'debug-D1.log'.
debug-D1.log

Last line in 'debug-D1.log' shows 'Loaded 14 channels from DB'
Node has over 200 channels
Please advise.

[5satoshi]

I have exactly the same issue, how did you proceed?

[TRIGEMTECH]

I decided to go back to v0.10.2 and am now formulating how best to move forward.

[TRIGEMTECH]

Error occurs in 'load_channels_from_wallet' method, line 1851, peer_control.c
if (!wallet_init_channels(ld->wallet))
fatal("Could not load channels from the database");
Further inquiry reveals:
'wallet_init_channels' calls 'set_max_channel_dbid' and returns 'wallet_channels_load_active' where the db query is prepared and executed. I suspect the channel state is not being handled fully...

[honc-online]

After some investigation in my case, I found the issue caused from within wallet.c line 822:
My peers address is a tor2 and if (!parse_wireaddr_internal(addrstr, &addr, DEFAULT_PORT, false, false, true, true, NULL)) seems not to be able to parse it and returns false
This lead to a break of the channel loading into the wallet

[Chrisse68]

I decided to go back to v0.10.2 and am now formulating how best to move forward.

How do you deal with the new database format? On the first run, cl converts the database to a new version:

2022-05-03T15:26:49.436Z INFO lightningd: Updating database from version 190 to 197
(from you first comment)

I also had trouble with the new cl v0.11 and tried to downgrade but on the first start, cl exits with an error message because it cant open the database (wrong format). It would be an option to close allchannels, transfer everything to my BTC wallet and rebuild the whole node again and install cl v10.3 again. But I wouldnt mijnd to avoid the extra mile. Maybe you have found a better and easier way to downgrade?

[heyambob]

I decided to go back to v0.10.2 and am now formulating how best to move forward.

How do you deal with the new database format? On the first run, cl converts the database to a new version:

2022-05-03T15:26:49.436Z INFO lightningd: Updating database from version 190 to 197
(from you first comment)

I also had trouble with the new cl v0.11 and tried to downgrade but on the first start, cl exits with an error message because it cant open the database (wrong format). It would be an option to close allchannels, transfer everything to my BTC wallet and rebuild the whole node again and install cl v10.3 again. But I wouldnt mijnd to avoid the extra mile. Maybe you have found a better and easier way to downgrade?

Maybe you could try to restore from your backup with 0.10.3, because looks like it died before finish loading, the backup should still be on the old format,

[TRIGEMTECH]

Prior to starting update I backed up the database (lightningd.sqlite3).
Failing to successfully update c-lightning and being unsure of its state I proceeded as follows:

1 Deleted lightning folder
2 git clone https://github.com/ElementsProject/lightning.git
3 git checkout v0.10.2
4 ./configure
5 make
6 sudo make install (fatal error generated with resolution)
7 sudo git config --global --add safe.directory /home/x-ubuntu/lightning/external/libwally-core
8 sudo make install (success)
9 lightningd --version (ok)
10 restored database
11 lightningd

Step 6 produced an error that was resolved in Step 7.
Successful startup!

[rustyrussell]

Hmm, if someone is prepared to send me their lightningd.sqlite3 file I'd love to fix this. That means losing your privacy though (I can't steal funds, however).

You can GPG email me or however you prefer.

[cdecker]

I had at least one user report privately today that the deprecation of onion v2 (and removal of parser support) was to be blamed. Removing the onion address in the peers table seems to have addressed the issue. So possible solutions may include dropping all onion v2 addresses in a migration or re-add parser support and then filter them out after loading.

[TRIGEMTECH]

lightning-cli listpeers | grep onion reveals 66 peers with onion address.
"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.onion:9735"
cdecker analysis would make sense, as well as previous comment from honc-online.
However, I cannot confirm existence of an onion v2 address when executing May 3rd update.