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

fix: v1.3.1-beta cannot start with --pruneancient=true #1986

Merged
merged 1 commit into from
Nov 14, 2023

Conversation

weiihann
Copy link
Contributor

Description

Fix the node unable to start issue if --pruneancient=true by creating a non-read-only database.

Refer to #1984 and #1982.

Rationale

When initializing a readonly database, it will attempt to open a freezer file for read only (refer to code here). Since ancient files are pruned and no longer exist, the read file operation will fail and return error.

Example

Refer to #1984 and #1982.

Changes

Create a non-read-only database if --pruneancient=true.

@tangzhiwei429
Copy link

i got this issue also

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 this pull request may close these issues.

None yet

5 participants