Closed modnarwolf closed 1 year ago
Thanks for reporting! We've merged a fix for this a couple days ago -- it should be coming out in the next release, but we're not planning to push any more fixes to the Phase 3 network at this time.
@hughy This was fixed in #3629, right?
Yeah, #3629 will resolve this issue!
If you continue to run into this issue on v0.1.70 you can run ironfish wallet:rescan --reset
command seemed to get the sync to finsh again... but ran ironfish migration
and got this
Checking migrations: Checking 014-blockchain... ERROR OpenError: IO error: lock /home/clos/.ironfish/databases/chain/LOCK: Resource temporarily unavailable at /home/clos/.nvm/versions/node/v18.13.0/lib/node_modules/ironfish/node_modules/levelup/lib/levelup.js:119:23 at /home/clos/.nvm/versions/node/v18.13.0/lib/node_modules/ironfish/node_modules/abstract-leveldown/abstract-leveldown.js:38:14 at /home/clos/.nvm/versions/node/v18.13.0/lib/node_modules/ironfish/node_modules/deferred-leveldown/deferred-leveldown.js:31:21 at /home/clos/.nvm/versions/node/v18.13.0/lib/node_modules/ironfish/node_modules/abstract-leveldown/abstract-leveldown.js:38:14 OpenError: IO error: lock /home/clos/.ironfish/databases/chain/LOCK: Resource temporarily unavailable at /home/clos/.nvm/versions/node/v18.13.0/lib/node_modules/ironfish/node_modules/levelup/lib/levelup.js:119:23 at /home/clos/.nvm/versions/node/v18.13.0/lib/node_modules/ironfish/node_modules/abstract-leveldown/abstract-leveldown.js:38:14 at /home/clos/.nvm/versions/node/v18.13.0/lib/node_modules/ironfish/node_modules/deferred-leveldown/deferred-leveldown.js:31:21 at /home/clos/.nvm/versions/node/v18.13.0/lib/node_modules/ironfish/node_modules/abstract-leveldown/abstract-leveldown.js:38:14
thanks you both, and again not sure if this is related at all.
@modnarwolf you might see this error if you run ironfish migration
while you have a node running. I'll see if we can improve the error output in this case!
You can stop the node and run ironfish migration
again to check the status of migrations.
You can also start the node with ironfish start --upgrade
or run ironfish migrations:start
to apply migrations
@hughy ohh I see... thanks again 😇
What happened?
mining was fine in 1.66 but think 1.69/1,70 I get this error on
ironfish start
right after syncing.also i ran ironfish migrations and i see only up to
024-unspent-notes
but idk if this is relevant or it should be higherThank you!
Version
1.70
Debug output
Relevant log output
Graffiti
MW