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

can not sync #404

Open
jie35752321 opened this issue Jul 11, 2024 · 5 comments
Open

can not sync #404

jie35752321 opened this issue Jul 11, 2024 · 5 comments

Comments

@jie35752321
Copy link

jie35752321 commented Jul 11, 2024

the node get syncing at 3170766 and the it stopped syncing. but nothing error in logs
what can I do.fellows?

@ccHarvestasya
Copy link

This repository is currently not maintained.
Please use the repository forked by the Symbol core team.

https://github.com/symbol/symbol-bootstrap

@jie35752321
Copy link
Author

This repository is currently not maintained. Please use the repository forked by the Symbol core team.

https://github.com/symbol/symbol-bootstrap

Sorry to bother you. I have a look at this new release, but I don't see any difference between it and the original one.
And I looked at the way it's built, and it doesn't seem to have anything to do with release, what do you think?

@ccHarvestasya
Copy link

This is bootstrap; it's just an environment; the Symbol node itself is downloaded and run as a docker image.
The version in this repository downloads Symbol server (Catapult Client) v.1.0.3.6. This version cannot synchronize certain blocks.

So you need to use the Symbol core team bootstrap which uses v.1.0.3.7.

@jie35752321
Copy link
Author

This is bootstrap; it's just an environment; the Symbol node itself is downloaded and run as a docker image. The version in this repository downloads Symbol server (Catapult Client) v.1.0.3.6. This version cannot synchronize certain blocks.

So you need to use the Symbol core team bootstrap which uses v.1.0.3.7.

I started the node according to the readme, and then checked the version of Node, but it will generate a directory called target, by checking the docker-compose.yml file in the target/docker/ directory, It was found that the symbolplatform/symbol-server version used was still 1.0.3.6, and after manually changing it to 1.0.3.7, the broker container and node container would not start. The error data is recovered.

Any suggestions for installation

@ccHarvestasya
Copy link

ccHarvestasya commented Jul 14, 2024

Since symbol-bootstrap is a tool to generate a group of execution servers for Symbol nodes, it will not work just by changing the version of Symbol Server. It is also necessary to change the configuration file. (You will get a better idea of this by doing a manual installation... it is very tedious)

I think you should install symbol-bootstrap v1.1.11.
Another option is shoestring, but it still lacks some features.

symbol-bootstrap v1.1.11 installation
(vague recollection...)

git clone https://github.com/symbol/symbol-bootstrap.git
cd symbol-bootstrap
npm i
npm run build
sudo npm install -g .
symbol-bootstrap -v

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants