Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

telegraf 1.33.0 does not start with a valid certificate in inputs.influxdb_listener #16306

Open
wargamez opened this issue Dec 14, 2024 · 2 comments
Assignees
Labels
bug unexpected problem or unintended behavior

Comments

@wargamez
Copy link

wargamez commented Dec 14, 2024

Relevant telegraf.conf

[[inputs.influxdb_listener]]
#   ## Address and port to host InfluxDB listener on
  service_address = ":8186"
#
#   ## maximum duration before timing out read of the request
  read_timeout = "10s"
#   ## maximum duration before timing out write of the response
  write_timeout = "10s"
#
#   ## Maximum allowed HTTP request body size in bytes.
#   ## 0 means to use the default of 32MiB.
#   max_body_size = "32MiB"
#
#   ## Optional tag name used to store the database.
#   ## If the write has a database in the query string then it will be kept in this tag name.
#   ## This tag can be used in downstream outputs.
#   ## The default value of nothing means it will be off and the database will not be recorded.
#   # database_tag = ""
#
#   ## If set the retention policy specified in the write query will be added as
#   ## the value of this tag name.
#   # retention_policy_tag = ""
#
#   ## Set one or more allowed client CA certificate file names to
#   ## enable mutually authenticated TLS connections
#   tls_allowed_cacerts = ["/etc/telegraf/clientca.pem"]
#
#   ## Add service certificate and key
  tls_cert = "/etc/nginx/ssl/server.crt"
  tls_key = "/etc/nginx/ssl/private.key"

Logs from Telegraf

N/A

System info

telegraf 1.33.0

Docker

No response

Steps to reproduce

...

Expected behavior

I expect it to start

Actual behavior

It does not start. However downgrading to 1.32.3 makes it work again...

Additional info

No response

@wargamez wargamez added the bug unexpected problem or unintended behavior label Dec 14, 2024
@wargamez
Copy link
Author

Commenting out the tls_xxx sections also makes it start, but that is unfortunate.

@DStrand1
Copy link
Member

DStrand1 commented Dec 16, 2024

Thanks for the issue!

Are there any log messages, if so could you send them?
Is this a self-signed certificate? Either way, how did you generate it?

@DStrand1 DStrand1 self-assigned this Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

2 participants