On 29/01/15 06:43, Martins Innus wrote:
...
The main issue I'm trying to solve is that for us, when a system gets
heavily loaded (seems to correlate to high I/O) and we have pmlogger
grabbing metrics from the proc pmda at regular intervals, we get the
following in the pmcd.log:
[Thu Jan 15 10:29:25] pmcd(15873) Warning: pduread: timeout (after 5.000
sec) while attempting to read 12 bytes out of 12 in HDR on fd=11
[Thu Jan 15 10:29:25] pmcd(15873) Info: CleanupAgent ...
Cleanup "proc" agent (dom 3): protocol failure for fd=11
I'd like to not increase the timeout since then we are reporting
incorrect timestamps for collected data, so I was going to use pmie to
restart pmcd when the pmda dies.
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.
|