Re: [pcp] PostgreSQL PMDA --> EnterpriseDB

[Pieter Baele <pieter.baele@xxxxxxxxx>]

On Mon, Jul 6, 2015 at 11:37 PM, Ken McDonell <kenj@xxxxxxxxxxxxxxxx> wrote:

Â

This message comes from the pmda->set_user() call near the end of the Perl code. For reasons that escape me (I did not write this code) this is trying to set the O/S (Linux probably) user to "postgres" so the PMDA does not run with UID 0 (root). It is unfortunate and confusing that this is the same string as the default DB username.

Oh thanks, I looked only very briefly in the source code....

Unless there are some O/S level protections needed to connect to PostgreSQL (seems unlikely) you could replace 'postgres' here with any valid Linux user name, else you might consider the attached modified version of the PMDA that uses $os_user instead of 'postgres' which would allow you to change it via

$os_user = 'something else';

in one of the *.conf files mentioned in the man page. This version also includes some additional logging ahead of the set_user() call and the attempted DB connection.

I'll commit these changes once I receive some confirmation that this has improved the situation.

Â

It worked and patched correctly, 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