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 upreference sequence 0 out of range #4845
Comments
This comment has been minimized.
This comment has been minimized.
|
this is the docker-compose.yml used to start all the dockers:
|
This comment has been minimized.
This comment has been minimized.
There's been numerous problems reported due to NFS. The fact that the issue vanishes after restarting the machine seems to indicate that the data on disk isn't corrupted. |
simonpasquier
added
kind/question
component/local storage
labels
Nov 9, 2018
This comment has been minimized.
This comment has been minimized.
|
I forgot to mention, that data is stored correctly while the problem exists i.e. after I restart the machine, I can see data from the time period, where queries returned the "reference sequence 0 out of range" error. |
This comment has been minimized.
This comment has been minimized.
|
You can try to run |
This comment has been minimized.
This comment has been minimized.
|
Thanks for the tip with NFS. I have switched back from NFS 4 to NFS 3 for now (tried CIFS, but the permissions drove me crazy). |
This comment has been minimized.
This comment has been minimized.
|
@theRealAJR still facing any issues after switching? |
This comment has been minimized.
This comment has been minimized.
|
no - but I need to run it for a little longer to be sure. |
This comment has been minimized.
This comment has been minimized.
|
Closing for now. Note that using NFS for storing Prometheus data is inherently buggy. |
simonpasquier
closed this
Nov 30, 2018
This comment has been minimized.
This comment has been minimized.
troy256
commented
Mar 22, 2019
|
Running Prometheus and Grafana on top of Kubernetes and get the same issue periodically. I just checked and my NFS mounts are v4. Is falling back to v3 a viable workaround? |
This comment has been minimized.
This comment has been minimized.
|
Yes, I have no problems any more on NFS V3. |
This comment has been minimized.
This comment has been minimized.
troy256
commented
Mar 22, 2019
|
@theRealAJR Thanks, just made the switch. I will report back if any issues. |
theRealAJR commentedNov 8, 2018
What did you do?
I executed a query
What did you expect to see?
the result of the query
What did you see instead? Under which circumstances?
error message "reference sequence 0 out of range"
I have been running two Prometheus instances in Docker containers for about 2 years.
Since the end of August 2018 Prometheus starts to produce the error "reference sequence 0 out of range" frequently (on average once per week, sometimes it happens two days in a row, sometimes it happens after 10 days).
I have updated the OS from Ubuntu 16.04 to 18.04 not long before the problems started, but I have no real indication, that the OS upgrade is related (no other problems in the system or other Dockers).
After I get the error message for the first time, all queries fail with this error.
Once the problem has started, then there is nothing I can do to solve it, but restart the entire machine - restarting the Docker containers or even the Docker daemon has no effect.
I have two Prometheus instances, one for short term data and one for long term data with a big scrape interval. The configs are almost identical, the main differences are, that the short term instance has alert rules and the long term instance reads old data from a third Prometheus v1.8.2 instance (also in a Docker, but not scraping or accessed directly, just for access to the old data via the long term instance).
The problem usually happens on both instances simultaneously, but today I noticed for the first time, that the problem is only occurring on the long term instance.
The metrics are stored on a NAS which is accessed via NFS.
I thought that the NFS mount may be the problem and tried different configs for that, but none helped. Note that the NFS shares worked w/o any problem for over a year and the fact, that currently one instance works while the other has the problem, kind of rules out an NFS problem (the metrics for both instances are on the same NFS share).
Once the problem starts, it can be reproduced by entering any query in Prometheus' web interface: It will then always show the error message "Error executing query: reference sequence 0 out of range" in a red box.
I usually notice that the problem has started, when I access Grafana, which shows no data but an exclamation mark in an orange triangle, which shows the error message "reference sequence 0 out of range" when the mouse pointer touches it.
The log contains a line like
for each query that is made. All queries fail, once the problem has started.
Environment
Prometheus is running inside Docker, the image is currently:
I update the image frequently
Linux 4.15.0-38-generic x86_64
also earlier versions, since end of August 2018
This is for the long term instance, there are no rules in the configured directory.