influxdata / influxdata/influxdb

collectd.security-level defaults to empty string, which is invalid

Open
#15,285 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1.x
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

I'm trying to receive collectd inputs to influxdb, but when i try to restart the service i get the following message:

influxdb0 influxd[24391]: run: invalid collectd config: Invalid security level. To generate a valid configuration file run influxd config > influxdb.generated.conf

My influx.conf is exactly like the documentation:

[[collectd]]
enabled = true
bind-address = ":25826"
database = "collectd"
retention-policy = ""
batch-size = 5000
batch-pending = 10
batch-timeout = "10s"
read-buffer = 0
typesdb = "/usr/share/collectd/types.db"
security-level = "none"
parse-multivalue-plugin = "split"

Worth mentioning that my security-level is defined as none, both in my influx.conf and in my collectd.conf (wich is running perfectly):

      LoadPlugin network
      
      <Plugin "network">
        <Server "my_influxdb_server" "25826">
          SecurityLevel "None"
        </Server>
        ReportStats true
      </Plugin>

So, in theory, there would be no reason to display this message.

  • System info: Linux 4.15.0-1040-gcp x86_64
  • InfluxDB version: InfluxDB v1.7.7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the collectd configuration path invoked by influxd config and compare its security-level default with the documented influx.conf and the reported collectd.conf. Reproduce the invalid empty-string configuration on InfluxDB v1.7.7, then verify that generated and loaded configurations use a valid security level and no longer emit the startup error.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.