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

Error opening memory series storage: file missing" source="main.go:182 : Error message is not explicit #2888

Closed
akram opened this Issue Jun 30, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@akram
Copy link

akram commented Jun 30, 2017

What did you do?
We maybe have data corruption, we endup in this message which is not very helpful.

What did you expect to see?
Since the ErrMissingFiles struct has Fds []storage.FileDesc we want to have a list of the missing files so we can troubleshoot or restore missing files if relevant.

What did you see instead? Under which circumstances?
The simple error message: " file missing"

  • Prometheus version:

version=1.5.2, branch=master, revision=bd1182d29f462c39544f94cc822830e1c64cf55b

  • Logs:
revision=bd1182d29f462c39544f94cc822830e1c64cf55b)" source="main.go:75"
time="2017-06-29T09:50:51Z" level=info msg="Build context (go=go1.7.5, user=root@1a01c5f68840, date=20170210-16:23:28)" source="main.go:76"
time="2017-06-29T09:50:51Z" level=info msg="Loading configuration file /etc/prometheus/prometheus.yml" source="main.go:248"
time="2017-06-29T09:50:52Z" level=error msg="Error opening memory series storage: file missing" source="main.go:182"
@akram

This comment has been minimized.

Copy link
Author

akram commented Jun 30, 2017

fixed by #2889

@beorn7

This comment has been minimized.

Copy link
Member

beorn7 commented Jul 3, 2017

This is a LevelDB problem and needs to be fixed upstream.

The on-disk format of LevelDB is standardized, however, so you could shut down the Prometheus server and apply 3rd party LevelDB recovery and diagnostics tools on the LevelDB files.

@beorn7 beorn7 closed this Jul 3, 2017

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 23, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.