On 1 Nov 2000, Alexander L. Belikoff wrote:
>
> Hello everybody -
>
> I'm just discovered PCP, so first of all, thanks SGI folks - the tool
> seems to be great and of all cluster management tools around, PCP
> seems to be the only one designed with scalability in mind. Thanks!
You're welcome ... scalability is one of the benefits of PCP over
competing infrastructures for capturing and transporting performance
data.
> Now, I'm trying to run PCP on a number of machines with logging on a
> special standalone node. I was able to start pmlogger for each of the
> collector nodes on that standalone machine, yet I have some problems
> disabling local pmlogger on the collector nodes. Commenting the
> LOCALHOST entry in the control file doesn't seem to help. The docs
> mention /etc/config/ files, yet they aren't present in the
> installation (I'm using pcp-2.1.10-8 on RedHat 6.2).
>
> So, how do I disable the local pmlogger?
This is a logic botch on our part ... it looks like the open source
version of /etc/rc.d/init.d/pcp has carried over some version bridging
logic from the IRIX version, but did not include the chkconfig controls.
We'll need to investigate the correct fix for this.
Pro tem, you have the following options.
0. ignore it ... the default pmlogger config means pmlogger spends most
of its time asleep.
1. don't run pmcd at all on the local machine (the remote pmloggers do
not need it), using chkconfig to turn pcp off, or
2. edit /etc/rc.d/init.d/pcp and remove or comment out the following
block in _start_pmlogger():
if grep '^LOCALHOSTNAME[ ]*y[ ]' $PMLOGCTRL >/dev/null
then
...
elif grep "^$LOCALHOSTNAME[ ]*y[ ]" $PMLOGCTRL >/dev/null
then
...
else
...
fi
3. edit /var/pcp/config/pmlogger/control and in the LOCALHOSTNAME
line change -c config.default to -c bogus ... this will make pmlogger
die immediately (but will send mail to root, so this is probably
the least attractive option).
|