pcp
[Top] [All Lists]

[Bug 1376856] pmlogger pmcd-restart persistence breaks pmmgr assumptions

To: pcp@xxxxxxxxxxx
Subject: [Bug 1376856] pmlogger pmcd-restart persistence breaks pmmgr assumptions
From: bugzilla@xxxxxxxxxx
Date: Fri, 16 Sep 2016 20:33:05 +0000
Auto-submitted: auto-generated
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <bug-1376856-355098@xxxxxxxxxxxxxxxxxxx>
References: <bug-1376856-355098@xxxxxxxxxxxxxxxxxxx>
https://bugzilla.redhat.com/show_bug.cgi?id=1376856



--- Comment #2 from Frank Ch. Eigler <fche@xxxxxxxxxx> ---
(In reply to Nathan Scott from comment #1)
> | target pmcd dying
> [...]
> | the remote pmcd came back because new PMDAs were installed
> 
> PMDA installation often doesn't cause a pmcd restart (just sighup) - and
> increasingly will happen less and less as $force_restart gets slowly removed
> from the code base, so this line of argument is flawed.

Whatever shape the argument, the underlying issue is real.  If pmlogconf is the
premier way of autoconfiguring loggers, changes such as pmdas coming and going
must be reflected in pmlogconf getting run.  Whether this is done by pmmgr
(predictably), or by pmlogger_check (unpredictably), it is worse than the new
status quo (not at all).


> The same problem also affects pmmgr's use of pmie,

No.  PMIE is hardly configured at all - pmieconf is perfunctory.  And
multi-host pmie rules are simply outside pmmgr's host-focused definition.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=P4T8BPXuvh&a=cc_unsubscribe
<Prev in Thread] Current Thread [Next in Thread>