Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v0.106.0] Issues on upgrading to Neuron@v0.106.0 #2557

Closed
yanguoyu opened this issue Dec 28, 2022 · 7 comments
Closed

[v0.106.0] Issues on upgrading to Neuron@v0.106.0 #2557

yanguoyu opened this issue Dec 28, 2022 · 7 comments

Comments

@yanguoyu
Copy link
Collaborator

yanguoyu commented Dec 28, 2022

Neuron needs to re-sync indexer data when update from early to 0.106

Because after ckb node update to 0.106, the indexer service has merge into ckb-core. So we remove the indexer data path from Neuron at 0.106. But the ckb node will not create indexer data when migrating old data to new data. So the indexer data will sync from the beginning. It will cost about 30~50 minutes to re-sync indexer data.

On the other hand, we strongly recommended you to backup the old data before migrating, the ckb node data path can be found by clicking preference -> Data -> CKB Node Config & Storage. Because once the migration started, the data will be no longer compatible with all older versions of CKB.

Upgrade on macOS

Neuron for macOS has supported Apple silicon chips since v0.106.0, so there're two versions, x64 for intel chips and arm64 for apple silicon chips:

OS Arch Package SHA256 Checksum
macOS x64 zip 97ee83b8330515b77c53ac970181b942aea09b6664e913c02cd452cab0ec4635
macOS arm64 zip 5080518acdb733fbc0466cb8b7dba2d97d5d1fd1ab0022014c5d5b65de8279ec
macOS x64 DMG a27cb4546c57859c7e650b693920cda04cd64b274fd2d6419f1e535c7f864023
macOS arm64 DMG 25aac7745a49545593c7aa89ea0eecc82e8a132d7566baceac5031224ff35173

➡️ For some reason, upgrading inside Neuron will download a arch-mismatched version, and the application will be unavailable. In this case, please download the correct one on the release page(https://github.com/nervosnetwork/neuron/releases/tag/v0.106.0) and replace the mismatched one.

image
image

@yanguoyu yanguoyu added the t:doc label Dec 28, 2022
@yanguoyu yanguoyu self-assigned this Dec 28, 2022
@Keith-CY Keith-CY pinned this issue Dec 28, 2022
@Keith-CY Keith-CY changed the title Neuron needs to re-sync indexer data when update from early to 0.106 [v0.106.0] Neuron needs to re-sync indexer data when update from early to 0.106 Dec 28, 2022
@Keith-CY Keith-CY changed the title [v0.106.0] Neuron needs to re-sync indexer data when update from early to 0.106 [v0.106.0] Issues on upgrading to Neuron@v0.106.0 Dec 28, 2022
@wengby88
Copy link

我的钱包更新到 0.106 后,数据迁移了好几天,一直是正在数据迁移,正在链接节点,到底怎么了???

@yanguoyu
Copy link
Collaborator Author

@wengby88 迁移受硬件影响,可能时间会花费比较久,顺便可以导出日志看看我们看看是不是还在迁移,或者删除偏好设置-> 数据 -> 节点配置和数据文件夹,然后重新打开 Neuron 同步。
image

@CryptoGumby
Copy link

My migration has been ongoing for over 24hrs, It says migrating and connecting. After 12 hrs or so I did a restart. My balance disappeared and its still in migrating/connecting mode. From the Neuron Wallet I went to help tab to report an issue which led me here. It recommends doing a back up prior to migration but I did not as the message only alerts you after you encountered the problem. Please advise..

@Keith-CY
Copy link
Collaborator

My migration has been ongoing for over 24hrs, It says migrating and connecting. After 12 hrs or so I did a restart. My balance disappeared and its still in migrating/connecting mode. From the Neuron Wallet I went to help tab to report an issue which led me here. It recommends doing a back up prior to migration but I did not as the message only alerts you after you encountered the problem. Please advise..

Hi @CryptoGumby

A 24-hour-long migration is likely to fail. Besides, migration transformed data so it's incompatible with Neuronv0.103.0. Now the only solution is to synchronize from scratch by Menu -> Tools -> Clear all synchronized data

Sorry for missing the warning message before running the migration, reason was mentioned in #2448 (comment)

Due to our negligence in collaboration and the temporary absence of PM, point 1(notify users about the risk of migration) was mentioned(#2517 (comment)) but not delivered within the application. The caveat was included in Release note / #2557

@yanguoyu
Copy link
Collaborator Author

yanguoyu commented Apr 25, 2023

Some users encountered this problem messages.codes.SQLITE_MISUSE when downloading the arm64 0.106 version or upgrading to the arm64 0.106 version with Apple M1.

It may be the same as #2575. You can try to click Help -> Export debug information, if you can't export debug information and see messages.codes.SQLITE_MISUSE. I'm so sure that your problem is the same as #2575. You can try to download the x64 0.106 version to replace your arm64 application.

And we have fixed it by #2609 and will release it in the next version.

@Danie0918 Danie0918 added FAQ [Help documentation] Frequently Asked Questions Synchronization [FAQ] Synchronization related issues labels Jun 12, 2023
@github-actions
Copy link
Contributor

Mark this issue stale because no activity for 60 days

@github-actions github-actions bot added the stale label Aug 12, 2023
@github-actions
Copy link
Contributor

Close this issue because it's inactive since marked stale

@Keith-CY Keith-CY unpinned this issue Oct 16, 2023
@Danie0918 Danie0918 removed FAQ [Help documentation] Frequently Asked Questions Synchronization [FAQ] Synchronization related issues labels Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants