Service status showing unspecified

Description:

Hello team X Perconian, I need your help. I have a strange issue with PMM3. I tried to add a PostgreSQL service running in k8, but after adding it, the service is showing as unspecified in the service section of the inventory.

When I check the node section, it is showing down:

And strangely both services are running fine that i, the postgres exporter and quan, see below

I checked the connectivity and the required grants that are fine, I created a connection from inside the PMM container as well. And the pmm-manage logs show the connection successful, and it fetches the list of databases in response, which means pmm can connect to the target database.

I am not sure why it is showing unspecified, and I don’t see any data against such a service whose status is unspecified. Please check this and let me know if there are any areas where I can look.

Hi.

I was experiencing a similar problem, however in my case the Percona node has an undefined status.

I checked the agent’s status:

~ # pmm-admin status
Agent ID: 4ecdc597-1271-404d-9397-20f52b1b4c93
Node ID: ad825670-d34b-47b4-840d-bf344ea41e66
Node name: percona1.globaldomain

PMM Server:
       URL: https://pmm.globaldomain:443/
       Version: 3.6.0

PMMClient:
       Connected : true
       Time drift: -15h14m24.345098906s
       Latency: 1.938134937s
       Connection uptime: 100
       pmm-admin version: 3.6.0
       pmm-agent version: 3.6.0
Agents:
       1168e6eb-3f95-4142-ac9d-282b945f4d49 mysqld_exporter Running 42002
       6de14a59-8ef7-49ee-a7fb-5c467a3666d0 node_exporter Running 42000
       79ad32ea-fdc8-4483-afaf-1dbccd4b259d

I fix the time in pmm-server and it worked.

Also check the firewalld ports for pmm-server access to the agent. In my case I added:

firewall-cmd --permanent --add-port=42000-42001/tcp
firewall-cmd --reload