Background
I was running some commit with 0.4.2 and tried to update to 0.5.0-beta and since more than 24 hours lnd is 100% busy with one CPU core and this log output:
2018-09-15 15:06:09.631 [INF] LTND: Version 0.5.0-beta commit=3b2c807288b1b7f40d609533c1e96a510ac5fa6d
2018-09-15 15:06:09.632 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2018-09-15 15:06:09.694 [INF] CHDB: Checking for schema update: latest_version=6, db_version=4
2018-09-15 15:06:09.694 [INF] CHDB: Performing database schema migration
2018-09-15 15:06:09.695 [INF] CHDB: Applying migration #5
2018-09-15 15:06:09.695 [INF] CHDB: Migrating database to support payment statuses
2018-09-15 15:06:09.696 [INF] CHDB: Marking all known circuits with status InFlight
2018-09-15 15:06:10.655 [INF] CHDB: Marking all existing payments with status Completed
2018-09-15 15:06:10.656 [INF] CHDB: Applying migration #6
2018-09-15 15:06:10.675 [INF] CHDB: Migrating database to properly prune edge update index
2018-09-15 16:16:58.189 [INF] LTND: Version 0.5.0-beta commit=3b2c807288b1b7f40d609533c1e96a510ac5fa6d
2018-09-15 16:16:58.189 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2018-09-15 16:16:58.190 [INF] CHDB: Checking for schema update: latest_version=6, db_version=4
2018-09-15 16:16:58.190 [INF] CHDB: Performing database schema migration
2018-09-15 16:16:58.190 [INF] CHDB: Applying migration #5
2018-09-15 16:16:58.190 [INF] CHDB: Migrating database to support payment statuses
2018-09-15 16:16:58.190 [INF] CHDB: Marking all known circuits with status InFlight
2018-09-15 16:16:58.191 [INF] CHDB: Marking all existing payments with status Completed
2018-09-15 16:16:58.192 [INF] CHDB: Applying migration #6
2018-09-15 16:16:58.192 [INF] CHDB: Migrating database to properly prune edge update index
On first startup of 0.5.0-beta I ran into #1843 because I had noencryptwallet=1 in the config which I removed. On the next try I killed lnd after more than one hour being stuck at the step mentioned above in the log. Then I found #1913 where someone mentioned the db migration took more than 4 hours and let it run again (now with debuglevel=debug). It's been running for about 24 hours since then with one CPU core 100% busy. With iotop I see single digits K/s disk reads and 0 B/s disk writes from lnd.
During the last two updates I ran into #1010 and had to apply the patch from #975 in order to start lnd, could this be related? I didn't patch this time with 0.5.0.
Should I wait more since the CPU is kind of slow? Would it be possible to add a note to the release notes that the db migration might take days?
Your environment
- lnd 0.4.2 --> 0.5.0-beta 3b2c807
- Ubuntu 18.04 Bionic with kernel 4.15.0-34-generic
- bitcoind 0.16.2 with txindex=1
- CPU: Intel Atom S1260 @2.00GHz
- size of .lnd directory is about 511MB
Background
I was running some commit with 0.4.2 and tried to update to 0.5.0-beta and since more than 24 hours lnd is 100% busy with one CPU core and this log output:
On first startup of 0.5.0-beta I ran into #1843 because I had noencryptwallet=1 in the config which I removed. On the next try I killed lnd after more than one hour being stuck at the step mentioned above in the log. Then I found #1913 where someone mentioned the db migration took more than 4 hours and let it run again (now with debuglevel=debug). It's been running for about 24 hours since then with one CPU core 100% busy. With iotop I see single digits K/s disk reads and 0 B/s disk writes from lnd.
During the last two updates I ran into #1010 and had to apply the patch from #975 in order to start lnd, could this be related? I didn't patch this time with 0.5.0.
Should I wait more since the CPU is kind of slow? Would it be possible to add a note to the release notes that the db migration might take days?
Your environment