[Linux-HA] lsb resource not starting during bootup
pavlos.parissis at gmail.com
Sat Dec 11 08:48:41 MST 2010
On 9 December 2010 09:44, Linux Cook <linuxcook at gmail.com> wrote:
> I have a lsb resource not running during bootup but successfully runs after
> issueing command:
Any application that is under cluster control should start only by the
cluster and not by the system via init process
> crm resource start <resourcename>
> Here's my config:
> primitive nuxeoctl lsb:nuxeoctl \
> op monitor interval="30s" timeout="300" depth="0" \
> op start interval="0" timeout="300s" \
> op stop interval="0" timeout="300s"
> primitive data_fs ocf:heartbeat:Filesystem \
> params device="/dev/mapper/data" directory="/var/lib/data"
> clone datafsClone data_fs
how is it possible to mount the same FS on both systems? Do you have
dual primary DRBD or other cluster FS deployed?
> clone nuxeoClone nuxeoctl
> colocation colNuxeowithDataFS inf: nuxeoClone datafsClone
you don't need that because the cloned primitives will run on all
> order ordNuxeoafterDataFS inf: datafsClone nuxeoClone
you better set the start action on nuceoClone, so it should be
order ordNuxeoafterDataFS inf: datafsClone nuxeoClone:start
> Anything I missed out? By the way, the lsb resource is an application based
> on jboss AS.
You didn't say what is the problem but I assumed your problem is that
pacemaker doesn't start your clones, right?
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> See also: http://linux-ha.org/ReportingProblems
More information about the Linux-HA