InfluxDB no longer working on OS 17.0 (corrupt tsm file, too many open files)

Third party integrations
1

After ugrading to HA OS 17.0 InfluxDB no longer works. I have already restored old versions of the InfluxDB add-on, reinstalled it, and rebooted. Any help would be highly appreciated. Here the log file:

s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service base-addon-banner: starting

-----------------------------------------------------------

Add-on: InfluxDB

Scalable datastore for metrics, events, and real-time analytics

-----------------------------------------------------------

Add-on version: 5.0.2

You are running the latest version of this add-on.

System: Home Assistant OS 17.0 (aarch64 / odroid-n2)

Home Assistant Core: 2026.1.3

Home Assistant Supervisor: 2026.01.1

-----------------------------------------------------------

Please, share the above information when looking for help

or support in, e.g., GitHub, forums or the Discord chat.

-----------------------------------------------------------

s6-rc: info: service base-addon-banner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service base-addon-timezone: starting

s6-rc: info: service base-addon-log-level: starting

s6-rc: info: service fix-attrs successfully started

[07:42:09] INFO: Configuring timezone (Europe/Berlin)...

s6-rc: info: service base-addon-log-level successfully started

s6-rc: info: service base-addon-timezone successfully started

s6-rc: info: service legacy-cont-init: starting

cont-init: info: running /etc/cont-init.d/create-users.sh

cont-init: info: /etc/cont-init.d/create-users.sh exited 0

cont-init: info: running /etc/cont-init.d/influxdb.sh

cont-init: info: /etc/cont-init.d/influxdb.sh exited 0

cont-init: info: running /etc/cont-init.d/kapacitor.sh

cont-init: info: /etc/cont-init.d/kapacitor.sh exited 0

cont-init: info: running /etc/cont-init.d/nginx.sh

cont-init: info: /etc/cont-init.d/nginx.sh exited 0

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service legacy-services: starting

services-up: info: copying legacy longrun chronograf (no readiness notification)

services-up: info: copying legacy longrun influxdb (no readiness notification)

services-up: info: copying legacy longrun kapacitor (no readiness notification)

services-up: info: copying legacy longrun nginx (no readiness notification)

[07:42:11] INFO: Kapacitor is waiting until InfluxDB is available...

[07:42:11] INFO: Chronograf is waiting until InfluxDB is available...

s6-rc: info: service legacy-services successfully started

[07:42:11] INFO: Starting the InfluxDB...

ts=2026-01-27T06:44:39.882781Z lvl=error msg="Cannot read corrupt tsm file, renaming" log_id=10gYrSMW000 engine=tsm1 service=filestore path=/data/influxdb/data/_internal/monitor/962/000000346-000000002.tsm id=0 error="indirectIndex: not enough data for max time"

ts=2026-01-27T06:45:28.321175Z lvl=error msg="Cannot read corrupt tsm file, renaming" log_id=10gYrSMW000 engine=tsm1 service=filestore path=/data/influxdb/data/homeassistant/autogen/903/000000013-000000014.tsm id=0 error="init: read tombstones: open /data/influxdb/data/homeassistant/autogen/903/000000013-000000014.tombstone: too many open files"

ts=2026-01-27T06:45:28.321176Z lvl=error msg="Cannot read corrupt tsm file, renaming" log_id=10gYrSMW000 engine=tsm1 service=filestore path=/data/influxdb/data/homeassistant/autogen/92/000000002-000000016.tsm id=0 error="init: read tombstones: open /data/influxdb/data/homeassistant/autogen/92/000000002-000000016.tombstone: too many open files"

ts=2026-01-27T06:45:28.337057Z lvl=error msg="Cannot read corrupt tsm file, renaming" log_id=10gYrSMW000 engine=tsm1 service=filestore path=/data/influxdb/data/homeassistant/autogen/919/000000013-000000016.tsm id=0 error="init: read tombstones: open /data/influxdb/data/homeassistant/autogen/919/000000013-000000016.tombstone: too many open files"

ts=2026-01-27T06:45:28.314888Z lvl=error msg="Cannot read corrupt tsm file, renaming" log_id=10gYrSMW000 engine=tsm1 service=filestore path=/data/influxdb/data/homeassistant/autogen/911/000000013-000000015.tsm id=0 error="init: read tombstones: open /data/influxdb/data/homeassistant/autogen/911/000000013-000000015.tombstone: too many open files"

ts=2026-01-27T06:45:28.348453Z lvl=error msg="Cannot read corrupt tsm file, renaming" log_id=10gYrSMW000 engine=tsm1 service=filestore path=/data/influxdb/data/homeassistant/autogen/927/000000014-000000016.tsm id=0 error="init: read tombstones: open /data/influxdb/data/homeassistant/autogen/927/000000014-000000016.tombstone: too many open files"

ts=2026-01-27T06:45:28.388117Z lvl=error msg="Cannot read corrupt tsm file, renaming" log_id=10gYrSMW000 engine=tsm1 service=filestore path=/data/influxdb/data/homeassistant/autogen/975/000000013-000000016.tsm id=0 error="init: read tombstones: open /data/influxdb/data/homeassistant/autogen/975/000000013-000000016.tombstone: too many open files"

ts=2026-01-27T06:45:28.407274Z lvl=error msg="Cannot read corrupt tsm file, renaming" log_id=10gYrSMW000 engine=tsm1 service=filestore path=/data/influxdb/data/homeassistant/autogen/951/000000013-000000015.tsm id=0 error="init: read tombstones: open /data/influxdb/data/homeassistant/autogen/951/000000013-000000015.tombstone: too many open files"

ts=2026-01-27T06:45:28.416613Z lvl=error msg="Cannot read corrupt tsm file, renaming" log_id=10gYrSMW000 engine=tsm1 service=filestore path=/data/influxdb/data/homeassistant/autogen/967/000000013-000000015.tsm id=0 error="init: read tombstones: open /data/influxdb/data/homeassistant/autogen/967/000000013-000000015.tombstone: too many open files"

ts=2026-01-27T06:45:28.432269Z lvl=error msg="Cannot read corrupt tsm file, renaming" log_id=10gYrSMW000 engine=tsm1 service=filestore path=/data/influxdb/data/homeassistant/autogen/991/000000013-000000016.tsm id=0 error="init: read tombstones: open /data/influxdb/data/homeassistant/autogen/991/000000013-000000016.tombstone: too many open files"

2026/01/27 06:45:34 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 5ms

2026/01/27 06:45:34 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 10ms

2026/01/27 06:45:34 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 20ms

2026/01/27 06:45:34 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 40ms

2026/01/27 06:45:34 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 80ms

2026/01/27 06:45:34 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 160ms

2026/01/27 06:45:34 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 320ms

2026/01/27 06:45:34 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 640ms

2026/01/27 06:45:35 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s

2026/01/27 06:45:36 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s

2026/01/27 06:45:37 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s

2026/01/27 06:45:38 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s

2026/01/27 06:45:39 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s

2026/01/27 06:45:40 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s

2026/01/27 06:45:41 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s

2026/01/27 06:45:42 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s

2026/01/27 06:45:43 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s

2026/01/27 06:45:44 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s

2026/01/27 06:45:45 http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s

s6-rc: info: service legacy-services: stopping

[tcp] 2026/01/27 06:45:46 tcp.Mux: Listener at 127.0.0.1:8088 failed failed to accept a connection, closing all listeners - accept tcp 127.0.0.1:8088: use of closed network connection

[07:45:46] INFO: NGINX stopped, restarting...

[07:45:46] INFO: Kapacitor stopped, restarting...

[07:45:46] INFO: Chronograf stopped, restarting...

[07:45:46] INFO: InfluxDB stopped, restarting...

s6-rc: info: service legacy-services successfully stopped

s6-rc: info: service legacy-cont-init: stopping

s6-rc: info: service legacy-cont-init successfully stopped

s6-rc: info: service fix-attrs: stopping

s6-rc: info: service base-addon-timezone: stopping

s6-rc: info: service base-addon-log-level: stopping

s6-rc: info: service fix-attrs successfully stopped

s6-rc: info: service base-addon-timezone successfully stopped

s6-rc: info: service base-addon-log-level successfully stopped

s6-rc: info: service base-addon-banner: stopping

s6-rc: info: service base-addon-banner successfully stopped

s6-rc: info: service s6rc-oneshot-runner: stopping

s6-rc: info: service s6rc-oneshot-runner successfully stopped
2

Is filestor path your issue? Corrupt database? Corrupt backups? Incomplete backups? Incomplete restores?

3

I don’t believe there is something wrong with the path, because when the problem startet I still had some very slow access to the database. I also don’t believe it is a backup/restore problem, as the issue started right after the OS 17.0 upgrade and afterwards I tried to restore different Influx DB add-on backups without solving the issue.

4

I have exactly the same problem since upgrade to HA OS 17:

 Add-on: InfluxDB
 Scalable datastore for metrics, events, and real-time analytics
-----------------------------------------------------------
 Add-on version: 5.0.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 17.0  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2026.1.3
 Home Assistant Supervisor: 2026.01.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[20:03:06] INFO: Configuring timezone (Europe/Berlin)...
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/create-users.sh
cont-init: info: /etc/cont-init.d/create-users.sh exited 0
cont-init: info: running /etc/cont-init.d/influxdb.sh
cont-init: info: /etc/cont-init.d/influxdb.sh exited 0
cont-init: info: running /etc/cont-init.d/kapacitor.sh
cont-init: info: /etc/cont-init.d/kapacitor.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun chronograf (no readiness notification)
services-up: info: copying legacy longrun influxdb (no readiness notification)
services-up: info: copying legacy longrun kapacitor (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
s6-rc: info: service legacy-services successfully started
[20:03:10] INFO: Kapacitor is waiting until InfluxDB is available...
[20:03:10] INFO: Chronograf is waiting until InfluxDB is available...
[20:03:11] INFO: Starting the InfluxDB...
ts=2026-02-03T19:05:59.206869Z lvl=error msg="Cannot read corrupt tsm file, renaming" log_id=10qE27xl000 engine=tsm1 service=filestore path=/data/influxdb/data/_internal/monitor/960/000000509-000000002.tsm id=0 error="init: read tombstones: open /data/influxdb/data/_internal/monitor/960/000000509-000000002.tombstone: too many open files"
ts=2026-02-03T19:05:59.471707Z lvl=error msg="Cannot read corrupt tsm file, renaming" log_id=10qE27xl000 engine=tsm1 service=filestore path=/data/influxdb/data/_internal/monitor/995/000000541-000000002.tsm id=0 error="init: read tombstones: open /data/influxdb/data/_internal/monitor/995/000000541-000000002.tombstone: too many open files"
2026/02/03 19:06:00 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 5ms
2026/02/03 19:06:00 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 10ms
2026/02/03 19:06:00 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 20ms
2026/02/03 19:06:00 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 40ms
2026/02/03 19:06:00 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 80ms
2026/02/03 19:06:00 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 160ms
2026/02/03 19:06:00 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 320ms
2026/02/03 19:06:00 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 640ms
2026/02/03 19:06:01 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:02 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:03 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:04 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:05 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:07 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:08 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:09 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:10 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:11 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:12 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
[20:06:13] INFO: Starting Chronograf...
[20:06:13] INFO: Starting the Kapacitor
'##:::'##::::'###::::'########:::::'###:::::'######::'####:'########::'#######::'########::
 ##::'##::::'## ##::: ##.... ##:::'## ##:::'##... ##:. ##::... ##..::'##.... ##: ##.... ##:
 ##:'##::::'##:. ##:: ##:::: ##::'##:. ##:: ##:::..::: ##::::: ##:::: ##:::: ##: ##:::: ##:
 #####::::'##:::. ##: ########::'##:::. ##: ##:::::::: ##::::: ##:::: ##:::: ##: ########::
 ##. ##::: #########: ##.....::: #########: ##:::::::: ##::::: ##:::: ##:::: ##: ##.. ##:::
 ##:. ##:: ##.... ##: ##:::::::: ##.... ##: ##::: ##:: ##::::: ##:::: ##:::: ##: ##::. ##::
 ##::. ##: ##:::: ##: ##:::::::: ##:::: ##:. ######::'####:::: ##::::. #######:: ##:::. ##:
..::::..::..:::::..::..:::::::::..:::::..:::......:::....:::::..::::::.......:::..:::::..::
2026/02/03 20:06:14 Using configuration at: /etc/kapacitor/kapacitor.conf
2026/02/03 19:06:14 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 5ms
2026/02/03 19:06:14 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 10ms
2026/02/03 19:06:14 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 20ms
2026/02/03 19:06:14 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 40ms
2026/02/03 19:06:14 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 80ms
2026/02/03 19:06:15 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 160ms
2026/02/03 19:06:15 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 320ms
2026/02/03 19:06:15 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 640ms
2026/02/03 19:06:16 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:17 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:18 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:19 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:20 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:21 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:22 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:23 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:24 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 1s
2026/02/03 19:06:26 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 5ms
2026/02/03 19:06:26 http: Accept error: accept tcp 0.0.0.0:8086: accept4: too many open files; retrying in 10ms

Before the update no problem at all…

5

I have exactly the same problem after updating to v17.0. I rolled back to v15.2 and now Influx runs flawlessly. I hope this will be sorted in the near future

6

I am also experiencing this problem when upgrading to 17.0 (corrupt tsm file followed by too many open files). I am running 16.3 with no problems.

I read in other reports this might be a ulimit problem, and one suggestion that didn’t work for me was to modify the influxDB configuration file to add in a parameter “INFLUXDB_MONITOR_STORE_ENABLED” with a false value.