influxd - InfluxDB service
API token hashing is enabled by default in InfluxDB OSS 2.9.0
Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.
For more information, see Token hashing.
The influxd daemon starts and runs all the processes necessary for InfluxDB to function.
Usage
influxd [flags]
influxd [command]For information about other available InfluxDB configuration methods, see InfluxDB configuration options.
Commands
| Command | Description |
|---|---|
| downgrade | Downgrade metadata schema to match an older release |
| help | Output help information for influxd |
| inspect | Inspect on-disk database data |
| print-config | (Deprecated) Print full influxd configuration for the current environment |
| recovery | Recover operator access to InfluxDB |
| run | Start the influxd server (default) |
| upgrade | Upgrade a 1.x version of InfluxDB to 2.9 |
| version | Output the current version of InfluxDB |
Flags
- --assets-path
- --bolt-path
- --e2e-testing
- --engine-path
- --feature-flags
- --flux-log-enabled
- --hardening-enabled
- -h, --help
- --http-bind-address
- --http-idle-timeout
- --http-read-header-timeout
- --http-read-timeout
- --http-write-timeout
- --influxql-max-select-buckets
- --influxql-max-select-point
- --influxql-max-select-series
- --instance-id
- --log-level
- --metrics-disabled
- --nats-max-payload-bytes - (deprecated in InfluxDB 2.2)
- --nats-port - (deprecated in InfluxDB 2.2)
- --no-tasks
- --overwrite-pid-file
- --pid-file
- --pprof-disabled
- --query-concurrency
- --query-initial-memory-bytes
- --query-max-memory-bytes
- --query-memory-bytes
- --query-queue-size
- --reporting-disabled
- --secret-store
- --session-length
- --session-renew-disabled
- --sqlite-path
- --storage-cache-max-memory-size
- --storage-cache-snapshot-memory-size
- --storage-cache-snapshot-write-cold-duration
- --storage-compact-full-write-cold-duration
- --storage-compact-throughput-burst
- --storage-max-concurrent-compactions
- --storage-max-index-log-file-size
- --storage-no-validate-field-size
- --storage-retention-check-interval
- --storage-series-file-max-concurrent-snapshot-compactions
- --storage-series-id-set-cache-size
- --storage-shard-precreator-advance-period
- --storage-shard-precreator-check-interval
- --storage-tsm-use-madv-willneed
- --storage-validate-keys
- --storage-wal-flush-on-shutdown
- --storage-wal-fsync-delay
- --storage-wal-max-concurrent-writes
- --storage-wal-max-write-delay
- --storage-write-timeout
- --store
- --strong-passwords
- --testing-always-allow-setup
- --tls-cert
- --tls-key
- --tls-min-version
- --tls-strict-ciphers
- --tracing-type
- --ui-disabled
- --use-hashed-tokens
- --vault-addr
- --vault-cacert
- --vault-capath
- --vault-client-cert
- --vault-client-key
- --vault-client-timeout
- --vault-max-retries
- --vault-skip-verify
- --vault-tls-server-name
- --vault-token
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB OSS v2 and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.