On 2008-07-15T08:13:25, Paul Walsh <[EMAIL PROTECTED]> wrote: > I have the following resource group defined: > > Resource Group: Moodle > web_dev (heartbeat:drbddisk): Started mercury > mysql_dev (heartbeat:drbddisk): Started mercury > weblog_dev (heartbeat:drbddisk): Started mercury > web_fs (heartbeat::ocf:Filesystem): Started mercury > mysql_fs (heartbeat::ocf:Filesystem): Started mercury > weblog_fs (heartbeat::ocf:Filesystem): Started mercury > fs_Alert (heartbeat::ocf:MailTo): Started mercury > ClusterIP (heartbeat::ocf:IPaddr2): Started mercury > monitor (heartbeat::ocf:ClusterMon): Started mercury > mysql (heartbeat:MySQL): Started mercury > Apache (BCU::ocf:apache2): Started mercury > appsAlert (heartbeat::ocf:MailTo): Started mercury
(Stopping Apache would at least imply also stopping appsAlert, btw, as the group has linear dependencies.) > If I want to stop/start *just* Apache, is the best way to simply run > > /usr/lib/ocf/resource.d/BCU/apache2 stop > /usr/lib/ocf/resource.d/BCU/apache2 start No, not if you're doing monitoring; the cluster will find out and restart the group. > http://www.linux-ha.org/v2/AdminTools/crm_resource seems to imply > crm_resource can be used to stop/start resources so I tried > > crm_resource -r Apache -p target_role -v stopped > > but nothing happened. Is this because its a member of a group and that > crm_resource would only be used to stop/start the entire group? That will work, unless you have several target_roles defined, possibly as meta_attributes? Newer versions will warn about that, but it's impossible to say without seeing your configuration. Regards, Lars -- Teamlead Kernel, SuSE Labs, Research and Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
