On 08/11/2016 07:04 PM, Nathan Scott wrote:
Hi Jeff,
----- Original Message -----
[...]
after a while pmdacluster crashes, then the pmval only give (as expected):
pmval: pmFetch: No PMCD agent for domain of request
pmval: pmFetch: No PMCD agent for domain of request
pmval: pmFetch: No PMCD agent for domain of request
pmval: pmFetch: No PMCD agent for domain of request
On a similar sized system I have yet to reproduce. Assuming at some
point I can what would be good debugging tools for a sigpipe in a pmda?
Or general pmda debugging tools?
I tend to use a combination of dbpmda(1) and gdb if that helps. You
may have some initial luck with setting a breakpoint in _exit if the
PMDA is choosing to exit itself, to get an initial backtrace.
Actually it's not pmdacluster that crashes but pmcd.
pmcd log
pmcd: PID = 19253, PDU version = 2
pmcd request port(s):
sts fd port family address
=== ==== ===== ====== =======
ok 4 unix /var/run/pcp/pmcd.socket
ok 0 44321 inet INADDR_ANY
ok 3 44321 ipv6 INADDR_ANY
[Tue Aug 16 13:14:56] pmcd(19253) Warning: pduread: timeout (after 5.000 sec)
while attempting to read 12 bytes out of 12 in HDR on fd=19
[Tue Aug 16 13:14:56] pmcd(19253) Info: CleanupAgent ...
Cleanup "cluster" agent (dom 65): protocol failure for fd=19
I have an strace of the pmcd process which doesn't (yet) show me anything
interesting. So new general question - pmcd debugging hints?
--
-----------------------------------------------------------------------
Jeff Hanson - jhanson@xxxxxxx - Senior Technical Support Engineer
You can choose a ready guide in some celestial voice.
If you choose not to decide, you still have made a choice.
You can choose from phantom fears and kindness that can kill;
I will choose a path that's clear
I will choose freewill. - Peart
|