Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upPrometheus does not start: Opening storage failed invalid block sequence #4324
Comments
This comment has been minimized.
This comment has been minimized.
|
Can you share the steps to reproduce this? The logs before this happened would be useful. as a workaround I have attached a tool I have been working on which should allow you to delete the overlapping blocks and allow a normal startup |
This comment has been minimized.
This comment has been minimized.
|
Looks like #4302 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
it is still WIP, but here is the code |
This comment has been minimized.
This comment has been minimized.
|
if you can it will be even better to compile from that PR as it includes more recent code. |
This comment has been minimized.
This comment has been minimized.
|
Fabian did few changes in the tsdb that should prevent this so I would say it is safe to close and will revisit if it happens again in the next release which is coming soon. |
krasi-georgiev
closed this
Jul 5, 2018
This comment has been minimized.
This comment has been minimized.
Hashfyre
commented
Feb 4, 2019
|
Running into this issue again
using: kube-prometheus/jsonnet
|
This comment has been minimized.
This comment has been minimized.
|
@Hashfyre please open a new issue with more details. |
This comment has been minimized.
This comment has been minimized.
Hashfyre
commented
Feb 4, 2019
•
|
|
This comment has been minimized.
This comment has been minimized.
|
This could be due to many reasons - large WAL file could be one of them(it could take few minutes to read a large WAL file.). |
This comment has been minimized.
This comment has been minimized.
Hashfyre
commented
Feb 4, 2019
|
@krasi-georgiev our issue seems to mimick #4003 |
This comment has been minimized.
This comment has been minimized.
|
unless you spend the time to open a new issue including all relevant details don't think anyone would spend the time for a proper troubleshooting. |

apsega commentedJun 29, 2018
•
edited
Bug Report
After restarting Prometheus, it couldn't manage to startup (that's quite sad with 1.5TB local data). It has been running on 2.3 version for a week now, and upgrade to 2.3.1 didn't help.
We have HA Prometheus setup and the other instance (
v2.1.0) is running just perfectly fine.Environment
Prometheus is running in Docker (
Docker version 1.13.0, build 49bf474) on CentOS (7.4.1708).Is there a way to start Prometheus by skipping broken blocks?