Dejan, Thanks for the reply. I realize I should have replied to my own question to let everyone know I was able to resolve my issue. The core issue was that I had modified the Zimbra init.d script from some earlier troubleshooting. That modification rendered the script non-lsb compliant and so Corosync couldn't start the resource. I changed back to as packaged and everything is now working great. Thanks, Todd
On Fri, Jun 24, 2011 at 2:44 AM, Dejan Muhamedagic <[email protected]>wrote: > Hi, > > On Sun, May 22, 2011 at 01:02:03PM -0600, Todd Munson wrote: > > Hi, > > I've got the bulk of my cluster configured but am running into an > > issue with the order of resources starting. Framework of this cluster > > is Coryosync, DRBD and heartbeat and the purpose is to run Zimbra > > (email application). > > The main issue is that corosync is starting my lsb application > > (Zimbra) prior to the DRBD disk resource being up. The Zimbra > > installation is on the DRBD resource so it can't be started without > > the DRBD resource being mounted. > > > > Can anyone help me with getting the zimbrad resource to start after my > > fs_zimbra resource? Do I need to setup a group or two within > > Corosync? > > Your configuration looks OK. Are you really sure that zimbrad > is ordered to start before the filesystem got mounted? What does > it look like in the logs? > > Thanks, > > Dejan > > > Here is my Corosync configuration, the output of my crm configure show. > > > > node granite \ > > attributes standby="off" > > node slate \ > > attributes standby="off" > > primitive ClusterIP ocf:heartbeat:IPaddr2 \ > > params ip="10.10.1.103" cidr_netmask="32" \ > > op monitor interval="30s" > > primitive Zimbra ocf:linbit:drbd \ > > params drbd_resource="zimbradisk" \ > > op start interval="0" timeout="240" \ > > op stop interval="0" timeout="100" \ > > op monitor interval="10s" > > primitive fs_zimbra ocf:heartbeat:Filesystem \ > > params device="/dev/drbd1" directory="/opt/zimbra" fstype="ext3" > \ > > op start interval="0" timeout="100" \ > > op stop interval="0" timeout="100" \ > > meta target-role="Started" > > primitive zimbrad lsb:zimbra \ > > op start interval="0" timeout="720s" \ > > op stop interval="0" timeout="720s" \ > > meta target-role="Started" is-managed="true" > > ms Zimbraclone Zimbra \ > > meta master-max="1" master-node-max="1" clone-max="2" > > clone-node-max="1" notify="true" > > colocation fs_on_drbd inf: fs_zimbra Zimbraclone:Master > > colocation zimbrad-with-fs_zimbra inf: zimbrad fs_zimbra > > colocation zimbrad-with-ip inf: zimbrad ClusterIP > > order fs_zimbra-after-Zimbra inf: Zimbraclone:promote fs_zimbra:start > > order zimbra-after-ip inf: ClusterIP zimbrad > > order zimbrad-after-fs_zimbra inf: fs_zimbra zimbrad > > 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" \ > > last-lrm-refresh="1305934568" > > rsc_defaults $id="rsc-options" \ > > resource-stickiness="100" > > > > Thanks! > > _______________________________________________ > > Linux-HA mailing list > > [email protected] > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
