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

[Bug]: Value log truncate required to run DB #1295

Open
lordrak007 opened this issue Oct 14, 2024 · 1 comment
Open

[Bug]: Value log truncate required to run DB #1295

lordrak007 opened this issue Oct 14, 2024 · 1 comment
Assignees
Labels
bug needs triage Waiting for discussion / prioritization by team

Comments

@lordrak007
Copy link

Steps to Reproduce

Download windows binary file:
Run step-ca without config. All another runs shows this error.
OR for example initialize step-ca using step.exe. During starting step-ca enter wrong password for CA or cancel startup. Every next start result in
badger 2024/10/14 14:16:12 INFO: All 1 tables opened in 1ms
badger 2024/10/14 14:16:12 INFO: Replaying file id: 0 at offset: 2923
badger 2024/10/14 14:16:12 WARNING: Truncate Needed. File C:\Users\marek.anyz.step\db\000000.vlog size: 2147483646 Endoffset: 3535
Error opening database of Type badgerv2: error opening Badger database: During db.vlog.open: Value log truncate required to run DB. This might result in data loss

Your Environment

  • OS -Windows server 2022
  • step CLI Version - Smallstep CLI/0.27.2 (windows/amd64)
    Release Date: 2024-07-18T18:15:09Z

Expected Behavior

Runc without error and have change to run truncate for badgerv2

Actual Behavior

step-ca does not start and prevent use step-ca

Additional Context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@lordrak007 lordrak007 added bug needs triage Waiting for discussion / prioritization by team labels Oct 14, 2024
@dopey dopey self-assigned this Oct 15, 2024
@dopey
Copy link
Contributor

dopey commented Nov 8, 2024

Hey, thanks for opening the issue!

It seems like the database is being corrupted by the early exit - it's possible it's not being closed properly on Windows. Unfortunately, our engineering team is compromised entirely of Mac and Linux users. We don't have folks readily available to debug Windows inter operability issues.

If theres a Windows user from the community who is able to reproduce the issue and would like to assist in debugging, please let us know.

cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs triage Waiting for discussion / prioritization by team
Projects
None yet
Development

No branches or pull requests

2 participants