influxdb: failed to store statistics: timeout 1.2.0

I have version 1.8.6 running on RPi4. Got the same timeouts: Jul 7 12:37:40 srv-rpi4 influxd[1607]: ts=2021-07-07T10:37:40.085034Z lvl=info msg="failed to store statistics" log_id=0VBNlMQ0000 service=monitor error=timeout

It helped me to reconfigure the default values in /etc/influxdb/influxdb.conf:

[data]
  wal-fsync-delay = "10s"
[coordinator]
  write-timeout = "10s"

The timeouts disappear when write-timeout is longer than wal-fsync-delay, eg:

[data]
  wal-fsync-delay = "10s"
[coordinator]
  write-timeout = "30s"

Hope this helps someone in the future. It would be beneficial to change the default values in influxdb.conf to something more reasonable.

+1 keep getting this as well

@dracula92107 1.7.5 is broken, either use 1.7.4 or wait for 1.7.6, see #13010.

+1 I have the same issue on version 1.7.5 (docker latest version)

2019-04-04T03:24:00.958588Z error [500] - "timeout" {"log_id": "0Ea_2oP0000", "service": "httpd"} [httpd] 172.17.0.1 - admin [04/Apr/2019:03:24:00 +0000] "POST /write?db=waf_log&rp=autogen&precision=n&consistency=one HTTP/1.1" 500 20 "-" "okhttp/3.11.0" 171a2d77-5689-11e9-83dd-0242ac110002 10000297 2019-04-04T03:24:10.961376Z error [500] - "timeout" {"log_id": "0Ea_2oP0000", "service": "httpd"} [httpd] 172.17.0.1 - admin [04/Apr/2019:03:24:10 +0000] "POST /write?db=waf_log&rp=autogen&precision=n&consistency=one HTTP/1.1" 500 20 "-" "okhttp/3.11.0" 1d10694b-5689-11e9-83de-0242ac110002 10000663

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 monitor.store-enabled in the config addressed some of the issues prior to 1.7 where timeout errors were being thrown. Turning this off eliminates some resource contention, but eliminates the ability for you to gather stats within the database itself. But, if you are working on a constrained environment/resources to begin with this turning this off will help.

+1. I happened to get this on version: 1.6.0 One thing I noticed was that, I was running another process which involved writing to disk (postgres writes) when influxdb started throwing these errors. Not sure if that has any relation to this, but just throwing it out there in case someone else also has similar correlation.

Ok, I have just installed on new vm influxdb and this is the info:

System info:

$ uname -a
Linux influx 3.10.0-327.10.1.el7.x86_64 #1 SMP Sat Jan 23 04:54:55 EST 2016 x86_64 x86_64 x86_64 GNU/Linu

$ cat /etc/*release
NAME="Red Hat Enterprise Linux Server"
VERSION="7.2 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="7.2"
PRETTY_NAME="Red Hat Enterprise Linux"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.2:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.2
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.2"
Red Hat Enterprise Linux Server release 7.2 (Maipo)
Red Hat Enterprise Linux Server release 7.2 (Maipo)

$ influxd version
InfluxDB v1.2.0 (git: master b7bb7e8359642b6e071735b50ae41f5eb343fd42)

$ df -h  #this is a ssd disk
/dev/mapper/vg_influx-influx_data   49G   63M   46G   1% /var/lib/influxdb

Steps to reproduce:

1. wget https://dl.influxdata.com/influxdb/releases/influxdb-1.2.0.x86_64.rpm
2. sudo yum localinstall influxdb-1.2.0.x86_64.rpm
3. sudo systemctl start influxdb

Expected behavior: service=monitor shouldn’t timeout

Actual behavior:

 2017-02-21T19:58:48Z retention policy shard deletion check commencing service=retention
feb 21 21:03:10 influx[1078]: [I] 2017-02-21T20:03:10Z failed to store statistics: timeout service=monitor
feb 21 21:03:20 influx[1078]: [I] 2017-02-21T20:03:20Z failed to store statistics: timeout service=monitor

Additional info: There is no custom configuration, just install and run. I’m not writing or reading anything from influxdb. logs: https://gist.github.com/claubrz/02b973e8d4c6ab198d5689a09ff8943d block: https://gist.github.com/claubrz/1411ca3c371f6e24cb2a64d6cf05a691 goroutine: https://gist.github.com/claubrz/a737d399596c161ef6356bbe188cc538 heap: https://gist.github.com/claubrz/338153a34a9288336c3c9484ce8607e4 vars: https://gist.github.com/claubrz/5a5f0420c3d9e4bdc442a1bb7fa1b283 iostat: https://gist.github.com/claubrz/9668562d7fdc1a277d159c4d9962599c shards: name: _internal id database retention_policy shard_group start_time end_time expiry_time owners

---

1 _internal monitor 1 2017-02-21T00:00:00Z 2017-02-22T00:00:00Z 2017-03-01T00:00:00Z 2 _internal monitor 2 2017-02-22T00:00:00Z 2017-02-23T00:00:00Z 2017-03-02T00:00:00Z

stgats: https://gist.github.com/claubrz/6cb969b66a32955614a68ab1091fce62 diagonostics: https://gist.github.com/claubrz/eded534953d006754dd989c4052a76c0

I hope this helps.

Regards, Claudiu