-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
failed to store statistics: timeout 1.2.0 #8036
Comments
Any information you could need feel free to ask. |
We need more information in order to diagnose what is going on. Can you update the issue description with the instructions listed in our issue template? Profile data when the timeouts occur would be useful. |
Ok, I have just installed on new vm influxdb and this is the info: System info:
Steps to reproduce:
Expected behavior: Actual behavior:
Additional info: 1 _internal monitor 1 2017-02-21T00:00:00Z 2017-02-22T00:00:00Z 2017-03-01T00:00:00Z stgats: https://gist.github.com/claubrz/6cb969b66a32955614a68ab1091fce62 I hope this helps. Regards, |
+1 keep getting this as well |
+1 same for 1.2.2 |
I'm also getting this error occasionally, and after a few days, no more data is written to InfluxDB. If I restart InfluxDB it works again for a few days and then stops receiving data until I restart it again. |
+1 same for 1.2.4 |
I'm also seeing this since
Disabling |
Same here. All writes end up in a timeout after a few hours of operation. No workaround seems to help. Restarting helps but then it gets stuck again.
|
I get this for Influx 1.3.7 as well.
|
I get this also sometimes (every 2-3 days ) at midnight
|
I am also getting this but very infrequently (and without a pattern).
|
+1. |
I have the same problem with influx. I use a raspi 3 with the latest influx InfluxDB v1.7.2 When the issues started, I saw that some of the files at /var/lib/influxdb/ where at once belonging to root and influx could not write to it. As consequence, influx started to make the systen in-responsive and used >90% of CPU (usually it is at 0.3%) This is the last message before influx crashed:
|
@cbarzu what is your settings for wal-fsync-delay in influxdb.conf ? |
+1
|
@dracula92107 |
Thank @conet , |
the fix for #13010 is in the 1.7 branch if you are building from source and our plan is to have a 1.7.6 tagged and built next week. Also useful to review the best practices related to monitoring Influx itself. http://docs.influxdata.com/platform/monitoring/influxdata-platform It was noted earlier in the thread that turning off |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions. |
I'm running V1.8.3 on a virtual server and ran into the error message. Using influxdb to store temperature data (one set per 5min, so small database, low load) und visualize the data via grafana installed on the same server. Server runs Ubuntu 18.04. influxd is running, telegraf is running to ship influxd data to a seperate server that is used for monitoring the main server. During grafana queries the "failed to store statistics" messages appeared repeatedly, at the end, influxd was killed by the kernel. The influxd started again and went down during startup a second time. After another restart, influxd survided and is still running and serving queries as speak. During the problem yesterday, grafana couldn' get the data for 30+mins. Complete logfiles are available when needed. Seems that fixes done so far didn't completely solve the problem. Any advise/fix to avoid such an incident in the future is highly appreciated! Thanks in advance. Logfile excerpts: Main server: influxd.log: Main server: syslog: |
I have version 1.8.6 running on RPi4. Got the same timeouts: It helped me to reconfigure the default values in /etc/influxdb/influxdb.conf:
The timeouts disappear when write-timeout is longer than wal-fsync-delay, eg:
Hope this helps someone in the future. |
Hi guys,
I saw there are some tickets with this error but without a solution. Because this still happens on influx 1.2.0 I create another one.
System info: [Include InfluxDB version, operating system name, and other relevant details]
systemctl start influxd
Wait some minutes
Actual behavior:
2017-02-21T16:37:50Z failed to store statistics: timeout service=monitor
Querys and writes works correctly, although some writes timeouts.
Thank you,
Claudiu
The text was updated successfully, but these errors were encountered: