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

Cannot start new bor client v0.3.0 with datadir.ancient flag #605

Closed
keksa905 opened this issue Nov 29, 2022 · 4 comments · Fixed by #614
Closed

Cannot start new bor client v0.3.0 with datadir.ancient flag #605

keksa905 opened this issue Nov 29, 2022 · 4 comments · Fixed by #614

Comments

@keksa905
Copy link

System information

Bor client version: v0.3.0

Heimdall client version: v0.3.0

OS & Version: Linux

It seems that new version of Bor client is not supporting flag for changing default directory for ancient db (-datadir.ancient), but in my setting it is in the different directory. But it cannot be started without this flag neither. See screenshots with error messages below.
polygon-ancient
polygon_ancient2

@pratikspatil024
Copy link
Member

Hi @keksa905, could you please share the steps that lead to this error?
I believe that you are using start.sh for running bor. It would be great if you could share that file as well.

@pratikspatil024 pratikspatil024 linked a pull request Dec 4, 2022 that will close this issue
2 tasks
@keksa905
Copy link
Author

keksa905 commented Dec 5, 2022

Hi @keksa905, could you please share the steps that lead to this error? I believe that you are using start.sh for running bor. It would be great if you could share that file as well.

I am running full node, but lately it started to fall behind most recent data so i wanted to update Bor and Heimdall to the latest version. So i stopped nodes, updated clients and starting scripts according to the changelog. But in my setting, ancient DB is separated from the rest. And these errors occurred when i wanted to restart Bor node with this setting. And yes I am using start.sh and I am attaching it here.
start_new.txt

@pratikspatil024
Copy link
Member

Thanks, @keksa905.
Closing in favour of #614.

@keksa905
Copy link
Author

keksa905 commented Dec 6, 2022

Thanks @pratikpatil024. It is working now :).

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

Successfully merging a pull request may close this issue.

2 participants