Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

`pmm-agent` reports "Malformed DSN" error when adding PostgreSQL instance with a PMM user password containing `=` (equals sign)

Description

Password format for the instance on which the issue was discovered was something like this: 
JK87Exs_=kUYE5Si

Passing the password with quotes, without quotes doesn't have have any impact, it still errors out on PMM-agent log, Dashboards show no data, only QAN works. 

impact on user: Dashboards don't show any data, exporter status is running, QAN works
 

Steps to Recreate:

1) setup PostgreSQL 12.x with a dedicated pmm_user something like this: 

2) Setup pmm-agent `dev-latest` or `2.9.0`

3) Make sure connection to postgresql works with the user created in step 1

3) add postgresql instance for monitoring: 

4) check pmm-agent logs: 

5) try removing and connecting the same instance for monitoring using single and double quotes on the password field with pmm-admin add command, still the same error. 

6) pmm-agent status returns "Running" status while postgresql dashboards have "N/A"  for this service. 

7) QAN shows data for this instance, even though we have error in pmm-agent log. 

Issue from Reporter: 

I encounter an issue with posgresql servers v12, pmm agent complains about a malformed dsn :

I can establish a connection by using the connection URI from logs. But i cant check the password effectively sent as it appears as PASSWORD_REMOVED in the logs.

 

How to test

None

How to document

None

Attachments

3

Smart Checklist

Activity

Show:

Former user February 9, 2021 at 3:06 PM

Roma Novikov January 28, 2021 at 10:26 PM

please consider implementation of   together or before this fix

Jira Bot July 17, 2020 at 8:56 AM

To: Former user
CC:

Hi, I'm jira-bot, Percona's Jira automation tool. I've detected that someone from
Percona has made an edit to the Summary field of an issue that you reported.

I'm not sentient (yet) so I'm not sure whether the person fixed a typo, changed
a few words, or completely rewrote the text. In any case, it is Percona Engineering's
intention to make the Summary and Description of an issue as accurate as possible
so that we're fixing the actual problem you're encountering, and to avoid
misunderstandings about symptoms and causes.

If the current Summary does not accurately reflect the problem you are reporting,
or if you feel the change was otherwise inappropriate in some way, please add a
new comment explaining things and we'll address it as soon as we can.

This message will be added only once per issue, regardless of how many times
the Summary is edited.

message-code:summary-edited

Lalit Choudhary May 6, 2020 at 7:58 AM

Debug output

Lalit Choudhary May 6, 2020 at 7:34 AM
Edited

Hi

Thank you for the test.

I'm able to reproduce same issue when using the above password for PostgreSQL user. 

Reproduciable Test case:

Postgresql User with a specific password, example: JK87Exs_=kUYE5Si

Expected Behaviour: pmm-agent should not have an error for the password , and it should allow using given password (eg: JK87Exs_=kUYE5Si)
 

Done

Details

Assignee

Reporter

Priority

Components

Labels

Needs QA

Yes

Fix versions

Sprint

Affects versions

Reviewer

Smart Checklist

Created April 27, 2020 at 1:41 PM
Updated March 6, 2024 at 4:32 AM
Resolved February 9, 2021 at 6:36 PM
Configure