On 29/01/15 07:40, Martins Innus wrote:
...
OK, but you don't need to restart pmcd (that is expensive and disrupts
the data stream for the other PMDAs that you might be logging).
Sending pmcd a SIGHUP will restart the proc PMDA.
Thanks, I wasn't aware of that but it doesn't seem to work in my case.
Similar setup to my other email. No other pcp services running (
pmlogger, pmie, pmwebd, pmmgr all stopped).
I sent that mail from the time warp that is labelled "it is OK for all
PCP processes to run as root" ... later I realized that in the brave new
world where running as root has become less fashionable this won't work
if the PMDA needs root priveleges, because once pmcd is able to accept
the SIGHUP it has downgraded itself to user "pcp" ... so restarting
_pmcd_ (as root) is the only option in your case.
> ...
The following in pmcd.log
[Wed Jan 28 20:11:19] pmcd(494) Info: CleanupAgent ...
Cleanup "proc" agent (dom 3): protocol failure for fd=9, signal(15)
Configuration file '/etc/pcp/pmcd/pmcd.conf' unchanged
Restarting any deceased agents:
"proc" agent
pmcd: unexpected end-of-file at initial exchange with proc PMDA
I assume the cleanup agent is from the "killall -v pmdaproc" and expected?
CleanupAgent is expected in this scenario.
The "pmcd: unexpected ... proc PMDA" bit is probably because the proc
PMDA was restarted as user "pcp" and baulked ... it would be interesting
to see what's in /var/log/pcp/pmcd/proc.log (this should contain a
reason why the proc PMDA terminated at startup).
|