Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Mon, Jun 7, 2010 at 10:18 PM, J. Adam Craig <acraig at pamplinpark.org>wrote:
> As an update, I managed to get DRBD starting up on boot by using
> update-rc.d. It is currently starting with the default priority (20), which
> is lower than corosync's, ocfs2's, etc. My presumption is that this means
> that DRBD should be starting before those services. Nevertheless, I
> continue to get the same corosync errors as before.
>
>
>
Probably better to be posted to pacemaker mailing list...
>
> I'm noticing that DRBD is not starting automatically on boot in my Ubuntu
> 8.04 LTS Server implementation. All was working fine with DRBD and
> Pacemaker / Corosync until I restarted the two nodes. DRBD did not startup
> on boot, and crm_mon is showing errors.
>
> I was wondering how (1) I could get DRBD to start on boot (should Pacemaker
> / Corosync do this, or do I need to do something with update-rc.d?) and (2)
> how these Corosync errors can be eliminated, if DRBD not starting on boot is
> not the cause of the trouble. I'm pasting the results of crm_mon below,
> along with my Corosync configuration below that.
>
> I do know that the drbd init file (ver 8.3.8) is stored as
> /usr/local/etc/init.d/drbd
>
> Thanks!
> - Adam
>
>
>
> *Corosync Configuration:*
>
pacemaker configuration actually....
>
> primitive Cluster-FS-DRBD ocf:linbit:drbd \
> params drbd_resource="cluster-ocfs" \
> operations $id="Cluster-FS-DRBD-ops" \
> op monitor interval="20" role="Master" timeout="20" \
> op monitor interval="30" role="Slave" timeout="20" \
> meta target-role="started"
>
>
>
If you use Pacemaker/corosync, you shouldn't configure at all drbd service
to start at boot or stop at shutdown.
On my rh el 5 based cluster
chkconfig --del drbd
Similar command or manual link removal to be done in Ubuntu.
Below some lines from howto (See complete document at
http://www.clusterlabs.org/wiki/DRBD_HowTo_1.0)
"You basically have two options to integrate DRBD with Pacemaker 1.0 (which
will be called just *Pacemaker* from now on in this document).
1. Use the legacy Heartbeat v1 style drbddisk resource agent to move the
Primary role. In this case, you *have to* let /etc/init.d/drbd load and
configure DRBD.
2. Use the DRBD OCF resource agent. In this case, you *must not* let init
load and configure DRBD, because this resource agent does that itself.
This document describes the *second* option."
And you are in option 2 too. See the remaining part of the doc and check.
My current config for the drbd resource
primitive nfsdrbd ocf:linbit:drbd \
params drbd_resource="nfsdata" \
op monitor interval="60s" \
op start interval="0" timeout="240" \
op stop interval="0" timeout="100"
Check also /var/log/messages
HIH,
Gianluca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20100608/4d536ce0/attachment.htm>