pcp
[Top] [All Lists]

Re: pcp updates - slow start PMDAs

To: Martins Innus <minnus@xxxxxxxxxxx>, pcp@xxxxxxxxxxx
Subject: Re: pcp updates - slow start PMDAs
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Wed, 09 Apr 2014 06:37:41 +1000
Cc: "Eigler, Frank" <fche@xxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <53445377.50301@xxxxxxxxxxx>
References: <5341E094.5090304@xxxxxxxxxxxxxxxx> <53445377.50301@xxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
On 09/04/14 05:52, Martins Innus wrote:
> ...
> Based on some initial testing, my slow start case in perl appears to be 
> fixed with this change, thanks very much for fixing this!  I'm not sure 
> yet if I will hit the other problem you mention.  I will have to do some 
> more testing.

Thanks Martins.

This may help any diagnosis you're trying.

Slow startup failure is reported in pmcd.log like this ...

[Mon Apr  7 06:55:09] pmcd(5065) Warning: pduread: timeout (after 3.000 sec) 
while attempting to read 12 bytes out of 12 in HDR on fd=38
pmcd: error at initial PDU exchange with slow PMDA: Timeout waiting for a 
response from PMCD

but a PMDA that does not respond to a subsequent request from pmcd in time 
produces this failure report in pmcd.log ...

[Wed Apr  9 06:32:34] pmcd(4426) Warning: pduread: timeout (after 5.000 sec) 
while attempting to read 12 bytes out of 12 in HDR on fd=28
[Wed Apr  9 06:32:34] pmcd(4426) Info: CleanupAgent ...
Cleanup "slow" agent (dom 243): protocol failure for fd=28

The pduread diagnostic is similar (although the 3.000 sec vs 5.000 sec is 
significant, assuming you've not changed pmcd's default timeout parameters via 
pmcd.options), but the next line shows the different signatures.

<Prev in Thread] Current Thread [Next in Thread>