----- Original Message -----
> >> [...]
> >> and pmDestroyContext paths though. Any details in pmcd.log after this
> >> test runs? (not failing here)
> >
> > Attached.
The client select loop failures are particularly interesting; scanning on
some of my hosts here, I'm also seeing this intermittently... need to get
to the bottom of that, methinks, to solve this issue.
> just noticed the attachment shows the root PMDA is installed as a daemon but
> the Linux PMDA is still a DSO. Does that matter?
It doesn't matter. Some container functionality will not be present,
but it should definitely not cause this class of failure.
> (and if so, we need a DSO->daemon migration mechanism for upgrades).
Either are valid configurations though.
> I play Mary-the-average sysadmin all the time ... get new packages and
> install 'em. If upgrade magic is needed I assume that *will* be part of
> the packaging scripts.
FWLIW, *some* level of intervention has happened here - the pmcd.conf has
been modified to include pmdaroot (as per a fresh install, but that would
not have been done automatically on upgrade). Maybe QA is to blame there?
Hmm, qa/761 does appear to put pmcd.conf back as it found it though.
cheers.
--
Nathan
|