pcp
[Top] [All Lists]

Re: [pcp] pmcd gets stuck with pmda kill

To: Martins Innus <minnus@xxxxxxxxxxx>
Subject: Re: [pcp] pmcd gets stuck with pmda kill
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 5 Mar 2015 02:11:13 -0500 (EST)
Cc: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>, pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <54CA900E.5000702@xxxxxxxxxxx>
References: <54C7FF66.5090503@xxxxxxxxxxx> <1902595642.1770600.1422398645794.JavaMail.zimbra@xxxxxxxxxx> <54C9441E.4060302@xxxxxxxxxxxxxxxx> <54C946A7.3080002@xxxxxxxxxxx> <54C95A00.2060006@xxxxxxxxxxxxxxxx> <54CA900E.5000702@xxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: Jbx+natvZI9IX/rvU8XoNqawSM75sA==
Thread-topic: pmcd gets stuck with pmda kill
Hi Martins,

----- Original Message -----
> [...]
> Yes, this would be my example posted that showed a backtrace with a
> problem in AgentsAttributes:
> [...]
> 
>  >killall -v pmdaproc
>      Killed pmdaproc(23682) with signal 15
> 
>  >pmval pmcd.agent.status
>      pmval: pmLookupDesc: IPC protocol failure
> 
>  >pmval hinv.ncpu
>      pmval: pmLookupDesc: IPC protocol failure
> 
>  >pminfo hinv.ncpu
>      Error: hinv.ncpu: Broken pipe
> 
> The only thing that brings it back to life is a "pminfo", "pminfo proc",
> or if a pmlogger instance is logging a proc metric.
> 

I've just pushed the fix for this into the dev branch, could you
give it a whirl and double check it for me?

Also, let me know if you're still interested in hacking on that
restarting-privileged-PMDAs aspect.  Its not on my TODO list yet
and quite a few other things precede that, unfortunately.  :(

cheers.

--
Nathan

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