PostgreSQL exporter throws "queryNamespaceMappings returned N errors"
Description
How to test
How to document
AFFECTED CS IDs
relates to
Activity
Nurlan Moldomurov February 22, 2024 at 10:30 AM
@Aaditya Dubey that’s not supposed to disappear, it’s supposed to provide more information, and that’s why we are waiting for feedback from MS team.
Aaditya Dubey February 22, 2024 at 10:11 AM
Hi @Roma Novikov
During testing of other bugs i found this error still exists in latest PMM 2.41.1:
time="2024-02-22T10:01:21.584+00:00" level=error msg="ts=2024-02-22T10:01:21.584Z caller=postgres_exporter.go:713 level=error err=\"queryNamespaceMappings returned 1 errors\"" agentID=/agent_id/390ba939-e05b-45c2-9540-6dc56ded5703 component=agent-process type=postgres_exporter
time="2024-02-22T10:01:23.013+00:00" level=error msg="ts=2024-02-22T10:01:23.013Z caller=collector.go:202 level=error msg=\"collector failed\" name=replication duration_seconds=0.007212079 err=\"pq: Function pg_last_xlog_receive_location() is currently not supported for Aurora\"" agentID=/agent_id/390ba939-e05b-45c2-9540-6dc56ded5703 component=agent-process type=postgres_exporter
Roma Novikov February 1, 2024 at 10:45 AM
Considering https://perconadev.atlassian.net/browse/PMM-12486 - we should have el7 imaged for the latest pmm versions. Can we retest and update if it’s ok.
PMM will produce el7 images for pmm v2
Jiří Čtvrtka September 11, 2023 at 9:49 AM
@C W @Max Bubenick Could someone verify if 2.39 is already available for Managed services? Thank you.
shivam.dhapatkar September 11, 2023 at 4:50 AM
Hello Team,
Is PMM 2.39 available for Managed services?
We tried to upgrade PMM from 2.37.1 to 2.39.0, but it is not getting upgraded.
We can see the 2.37.1 version on the link https://github.com/percona/remote-dba-ansible/blob/master/playbooks/roles/pmm/vars/main.yml
Could you please confirm the latest available PMM version for Managed Services ??
Thanks.
One of the recently onboarded MS PG customer reported an issue that PostgreSQL exporter throws an error:
Feb 17 03:27:50 gmsql11-p2lg pmm-agent: #033[31mERRO#033[0m[2023-02-17T03:27:50.502+00:00] ts=2023-02-17T03:27:50.502Z caller=postgres_exporter.go:742 level=error err="queryNamespaceMappings returned 1 errors" #033[31magentID#033[0m=/agent_id/7cf7ec5b-b499-4871-961f-cb9aafb6c6f4 #033[31mcomponent#033[0m=agent-process #033[31mtype#033[0m=postgres_exporter
I was able to reproduce the issue on 2.29.1 with RDS PostgreSQL 13.7, but not on 2.34.0.
Customer's setup:
PMM Server version: 2.34.0
PMM Client version: 2.34.0
PostgreSQL version: PostgreSQL 12.3 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39), 64-bit
Additional info from customer:
PostgreSQL running on a Physical server
PostgreSQL service was added using platform automation script
There are total 6 DB Instance having 3 different environments (master-replica set up) - out of which 2 instances of single environment have this issue
Link to Slack thread: https://perconacorp.slack.com/archives/C03FB1CAZH9/p1676264835439279