pcp
[Top] [All Lists]

Re: [pcp] PostgreSQL PMDA --> EnterpriseDB

To: Pieter Baele <pieter.baele@xxxxxxxxx>
Subject: Re: [pcp] PostgreSQL PMDA --> EnterpriseDB
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Tue, 07 Jul 2015 17:22:57 +1000
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <CADDXySrg7bgU_Cq9g54fSzPZQa75cX_+DcpuibyHn90wHGcuPw@xxxxxxxxxxxxxx>
References: <CADDXySqgr+X192n92WbxOpMywGBZ=+p1thzYiefkT4+1_J_1TA@xxxxxxxxxxxxxx> <559AF536.3060309@xxxxxxxxxxxxxxxx> <CADDXySrg7bgU_Cq9g54fSzPZQa75cX_+DcpuibyHn90wHGcuPw@xxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
On 07/07/15 17:12, Pieter Baele wrote:
...
It worked and patched correctly, ...

Good. I'll commit the change.

... however, on another host nothing
appears with pminfo -f.

I have seen this problem before ...
Check postgresql metrics have appeared ... 208 warnings, 208 metrics and
0 values

pminfo -f postgresql
postgresql: pmLookupName: No PMCD agent for domain of request

Note: RH is on version 3.9.5. They will rebase to 3.10 with RHEL 7.2

OK.  Now you're off in the land of PMDA debugging.

1. start with /var/log/pcp/pmcd/pmcd.log ... there you should see messages about the PMDA being installed (added to the config file) and then (I am guessing) the PMDA failed to respond to pmcd and exited.

2. next inspect /var/log/pcp/pmcd/postgresql.log (and possibly .../postgresql.log.prev if pmcd has tried to restart the PMDA).

If the answer is not obvious (I'd expect a DBI connect issue or more likely a permissions problem that prevents the user the PMDA is using from selecting from the stats tables), post the postgresql.log and pmcd.log files.

<Prev in Thread] Current Thread [Next in Thread>