-
Notifications
You must be signed in to change notification settings - Fork 285
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
Missing file name in some "unable to verify file version: EOF" errors #1034
Comments
kozlovic
added a commit
that referenced
this issue
Apr 17, 2020
In some cases, the file name of the file unable to be recovered due to an error reading the first 4 bytes of the file (to check the file version) was not included in the error message, making it difficult to debug which file was impacted. Resolves #1034 Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
kozlovic
added a commit
that referenced
this issue
Apr 17, 2020
In some cases, the file name of the file unable to be recovered due to an error reading the first 4 bytes of the file (to check the file version) was not included in the error message, making it difficult to debug which file was impacted. Resolves #1034 Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
kozlovic
added a commit
that referenced
this issue
Apr 17, 2020
In some cases, the file name of the file unable to be recovered due to an error reading the first 4 bytes of the file (to check the file version) was not included in the error message, making it difficult to debug which file was impacted. Resolves #1034 Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
NATS Streaming files have a minimum header of 4 bytes that contain a version number. If during restart a file is found to have less than this size, the server will fail to start with "unable to verify file version: EOF" error. In some cases, it does not report which file caused that error.
Reported by @encee on Slack channel.
The text was updated successfully, but these errors were encountered: