Re: [pcp] PostgreSQL PMDA --> EnterpriseDB

[Pieter Baele <pieter.baele@xxxxxxxxx>]

On Tue, Jul 7, 2015 at 9:22 AM, Ken McDonell <kenj@xxxxxxxxxxxxxxxx> wrote:

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

Needed debugging already for PAPI (which is impressive..., I only need to configure pmmgr to have some more data centrally on the collector)

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.

Indeed.

But a service pcp restart brought some data, until a pminfo -f is used,

 ok 1025 44321 ipv6 INADDR_ANY
[Tue Jul 7 09:26:13] pmcd(16292) Info: CleanupAgent ...
Cleanup "postgresql" agent (dom 110): protocol failure for fd=26, signal(11)

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.

Correct. I've the feeling it's a weak point, as I had the same problem on the community version (no postgresql PMDA data once I used a pminfo -f)
ex. postgresql.stat.all_tables.last_analyze: pmLookupName: No PMCD agent for domain of request

But also
[Tue Jul 7 09:48:03] pmdapostgresql(8911) Info: Skipping table pg_stat_database_conflicts, not supported on EnterpriseDB 9.4.1.4 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11), 64-bit

As our DB's are maintained by a separate DBA team, I'll ask them what I need to query pg_stat*

Thanks a lot!