[Pacemaker] Resources won't start

[Phil Hunt]

>>Did it start?

No, here is the output, all resources kind of went away.  Thats what I've been fighting all day......

============
Last updated: Tue Apr 19 13:52:18 2011
Stack: openais
Current DC: CentClus2 - partition with quorum
Version: 1.0.10-da7075976b5ff0bee71074385f8fd02f296ec8a3
2 Nodes configured, 2 expected votes
1 Resources configured.
============

Online: [ CentClus1 CentClus2 ]




Thats it!

Config:
node CentClus1
node CentClus2
primitive FS_disk ocf:heartbeat:Filesystem \
        params device="/dev/VolGroup01/Shared1" directory="/data" fstype="gfs"
primitive ClusterIP ocf:heartbeat:IPaddr2 \
        params ip="192.168.1.90" cidr_netmask="32" \
        op monitor interval="30s"
primitive ISCSI_disk ocf:heartbeat:iscsi \
        params portal="192.168.1.79:3260" \
target="iqn.1991-05.com.microsoft:wss-w2xxxvr-wss-target3-target" \
        op start interval="0" timeout="120s" \
        op stop interval="0" timeout="120s" \
        op monitor interval="120s" timeout="30s"
primitive VG_disk ocf:heartbeat:LVM \
        params volgrpname="VolGroup01" exclusive="yes" \
        op monitor interval="10" timeout="30" on-fail="restart" depth="0" \
        op start interval="0" timeout="30" \
        op stop interval="0" timeout="30"
primitive IP_ping ocf:heartbeat:IPaddr2 \
        params ip="192.168.1.90" cidr_netmask="32" \
        op monitor interval="30s"
primitive PM_ping ocf:pacemaker:ping \
        params name="p_ping" host_list="192.168.1.91 192.168.1.92 192.168.1.1 " \
        op monitor interval="15s" timeout="30s"
property $id="cib-bootstrap-options" \
        dc-version="1.0.10-da7075976b5ff0bee71074385f8fd02f296ec8a3" \
        cluster-infrastructure="openais" \
        expected-quorum-votes="2" \
        stonith-enabled="false" \
        no-quorum-policy="ignore"
group CL_group ClusterIP ISCSI_disk VG_disk FS_disk PM_ping IP_ping
location Loc_ping CL_group \
        rule $id="loc_ping-rule" -inf: not_defined PM_ping or PM_ping lte 0
rsc_defaults $id="rsc-options" \
        resource-stickiness="1000"









	
	

PHIL HUNT AMS Consultant 
phil.hunt at orionhealth.com 
P: +1 857 488 4749 
M: +1 508 654 7371 
S: philhu0724 
www.orionhealth.com 

----- Original Message -----
From: "mark - pacemaker list" <m+pacemaker at nerdish.us>
To: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
Sent: Tuesday, April 19, 2011 5:05:16 PM GMT -05:00 US/Canada Eastern
Subject: Re: [Pacemaker] Resources won't start

Hi Phil,

On Tue, Apr 19, 2011 at 3:36 PM, Phil Hunt <Phil.Hunt at orionhealth.com> wrote:
> Hi
> I have iscsid running, no iscsi.

Good.   You don't want the system to auto-connect the iSCSI disks on
boot, pacemaker will do that for you.

>
>
>
> Here is the crm status:
> ============
> Last updated: Tue Apr 19 12:39:03 2011
> Stack: openais
> Current DC: CentClus2 - partition with quorum
> Version: 1.0.10-da7075976b5ff0bee71074385f8fd02f296ec8a3
> 2 Nodes configured, 2 expected votes
> 1 Resources configured.
> ============
>
> Online: [ CentClus1 CentClus2 ]
>
>  Resource Group: CL_group
>     ClusterIP  (ocf::heartbeat:IPaddr2):       Started CentClus2
>     FS_disk    (ocf::heartbeat:Filesystem):    Stopped
>     ISCSI_disk (ocf::heartbeat:iscsi): Stopped
>     VG_disk    (ocf::heartbeat:LVM):   Stopped
>     PM_ping    (ocf::pacemaker:ping):  Stopped
>     IP_ping    (ocf::heartbeat:IPaddr2):       Stopped
>
>

The resources are listed in top-down start order.  So you're starting
ClusterIP, but then try to start the filesystem when you still haven't
connected to the iSCSI disk or started the volume group.

>
> Here is the crm config:
> node CentClus1
....
> group CL_group ClusterIP FS_disk ISCSI_disk VG_disk PM_ping IP_ping
....
> order ISCSI_startup inf: ISCSI_disk VG_disk FS_disk

You have conflicting orders, there.  A resource group defines an
order, so the other order statement seems unnecessary.  If you remove
that order constraint, and change your group line so that things start
in the correct order, does it come up?

group CL_group ClusterIP ISCSI_disk VG_disk FS_disk PM_ping

I left off IP_ping, because it's exactly the same as ClusterIP.  Was
it meant to be something else?

Regards,
Mark

_______________________________________________
Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker