Hi,
On 2016-03-01 05:51, Nathan Scott wrote:
> ----- Original Message -----
>> [...] I'd expect them both getting killed. Is this a feature or a
>> bug or something that should be handled in the Remove script?
>
> Not seeing this here - can you share the Install & Remove scripts
> you're using there too? Thanks.
>
> After the Remove script is run, there should definitely be no trace
> of the PMDA or any children anymore (has pmcd.conf not been updated
> somehow? maybe check the "iam=xxx" setting in Remove script?).
Install/Remove are just like everywhere else, PMDA installed as
collector, tried enabling/disabling daemon_opt/forced_restart to no avail:
Install:
. $PCP_DIR/etc/pcp.env
. $PCP_SHARE_DIR/lib/pmdaproc.sh
iam=test
perl_opt=true
daemon_opt=false
forced_restart=true
pmdaSetup
pmdaInstall
exit 0
Remove:
. $PCP_DIR/etc/pcp.env
. $PCP_SHARE_DIR/lib/pmdaproc.sh
iam=test
pmdaSetup
pmdaRemove
exit 0
pmcd.conf hasn't been updated, this happens also on a freshly booted
machine when doing the test more or less as the first thing. Log for the
test PMDA show it stopped logging when it was removed
...
[Tue Mar 1 14:55:53] pmdatest(11628) Info: Incoming data:DATA:
[Tue Mar 1 14:55:58] pmdatest(11628) Info: Incoming data:DATA:
Log finished Tue Mar 1 14:55:59 2016
But in pmcd.log I see:
pmcd RESTARTED at Tue Mar 1 14:55:59 2016
...
[Tue Mar 1 14:55:59] pmcd(11617) Info: CleanupAgent ...
Cleanup "test" agent (dom 497): unconfigured, exit(0)
...
[Tue Mar 1 14:56:00] pmcd(11617) Info: PMNS file "DEFAULT" is unchanged
...
If I stop and start pmcd with systemctl stop/start pmcd then the test
PMDA is gone as expected. So I wonder what is this cleanup agent? Should
the domain be configured somewhere else than in Install, too? Or perhaps
the QA tests I've run on this system have left some scars behind?
Thanks,
--
Marko Myllynen
|