Documentation

Troubleshoot systemd errors

When running InfluxDB using systemd (Ubuntu, Debian, CentOS), you might encounter errors in the InfluxDB logs (via journalctl -u influxdb) like:

  • error msg="Unable to open series file"
  • run: open server: open tsdb store: mkdir /var/lib/influxdb/data/_internal/_series/00: permission denied

When InfluxDB is installed with systemd, an influxdb user and group is automatically created. If the user runs an influxd process directly from their login shell, it can generate new series files not accessible by the influxdb user. In this case, when systemd starts the InfluxDB service (via sudo systemctl start influxdb), the InfluxDB process will exit because it cannot access the leftover files owned by the root user.

To resolve this issue, set all files in the InfluxDB directories to be owned by the influxdb user and group. Run the following command:

sudo chown -R influxdb:influxdb /var/lib/influxdb/*

Alternatively, if the data is not important, reset the database by removing all files:

sudo rm -rf /var/lib/influxdb/

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2