You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When adding ?ssl_mode=PREFERRED to a mysql DSN using the docker image, I get: MySQL client library does not support ssl_mode specification
Installation details
operating system: CentOS 7.9
query-exporter installation type:
docker image: docker
To Reproduce
If possible, please provide detailed steps to reproduce the behavior:
MySQL configured with SSL. Local connections work, yet get Access Denied with query_exporter. So attempted to set ssl_mode=PREFERRED
Config file content (redacted of secrets if needed) databasenamehere: dsn: mysql://user:pass@<host>/<database>?ssl_mode=PREFERRED
Ran query-exporter with the following command line ... docker run -p 9560:9560/tcp -v "/etc/query_exporter.yaml:/config.yaml" --rm -it adonato/query-exporter:latest
Got the error when ...
When attempting to do connections, see in the log: MySQL client library does not support ssl_mode specification
The text was updated successfully, but these errors were encountered:
Describe the bug
When adding ?ssl_mode=PREFERRED to a mysql DSN using the docker image, I get:
MySQL client library does not support ssl_mode specification
Installation details
To Reproduce
If possible, please provide detailed steps to reproduce the behavior:
MySQL configured with SSL. Local connections work, yet get Access Denied with query_exporter. So attempted to set ssl_mode=PREFERRED
Config file content (redacted of secrets if needed)
databasenamehere: dsn: mysql://user:pass@<host>/<database>?ssl_mode=PREFERRED
Ran query-exporter with the following command line ...
docker run -p 9560:9560/tcp -v "/etc/query_exporter.yaml:/config.yaml" --rm -it adonato/query-exporter:latest
Got the error when ...
When attempting to do connections, see in the log:
MySQL client library does not support ssl_mode specification
The text was updated successfully, but these errors were encountered: