Troubleshooting InfluxDB

Error Messages

This page documents errors, their descriptions, and, where applicable, common resolutions. Disclaimer: This document does not contain an exhaustive list of all possible InfluxDB errors. error: database name required The database name required error occurs when certain SHOW queries do not specify a database. Specify a database with an ON clause in the SHOW query, with USE <database_name> in the CLI, or with the db query string parameter in the HTTP API request.

Frequently Asked Questions

This page addresses frequent sources of confusion and places where InfluxDB behaves in an unexpected way relative to other database systems. Where applicable, it links to outstanding issues on GitHub. Administration How do I include a single quote in a password? How can I identify my version of InfluxDB? Where can I find InfluxDB logs? What is the relationship between shard group durations and retention policies? Why aren’t data dropped after I’ve altered a retention policy?

Query Management

With InfluxDB’s query management features, users are able to identify currently-running queries, kill queries that are overloading their system, and prevent and halt the execution of inefficient queries with several configuration settings. SHOW QUERIES KILL QUERY Configuration Settings List currently-running queries with SHOW QUERIES SHOW QUERIES lists the query ID, query text, relevant database, and duration of all currently-running queries on your InfluxDB instance. For InfluxDB Enterprise clusters, the SHOW QUERIES output also includes the TCP host.

Server Monitoring

InfluxDB can display statistical and diagnostic information about each node. This information can be very useful for troubleshooting and performance monitoring. SHOW STATS To see node stats execute the command SHOW STATS. The statistics returned by SHOW STATS are stored in memory only, and are reset to zero when the node is restarted. SHOW DIAGNOSTICS To see node diagnostics execute the command SHOW DIAGNOSTICS. This returns information such as build information, uptime, hostname, server configuration, memory usage, and Go runtime diagnostics.