I've finally tracked down the obscure
No PMCD agent for domain of request
message that pollutes a number of QA failures after upgrade, but the
problem is not reproducible.
When we ship a new pmcd.conf and the installation tools encourage the
user to keep their existing one or install the new one, the common
choice is the latter (there is new syntactic sugar in there).
BUT in the process we may remove PMDAs from pmcd.conf and we DO NOT
clean up the PMNS, so for example the trace or logger PMDAs have metrics
in the PMNS, but no associated PMDA in pmcd.conf.
I think we need a one-trip after install check tool to make the PMNS
match pmcd.conf and warn about any metrics culled from the PMNS in the
process.
Thoughts?
|