Thank you for reporting bugs and trying to make Ubuntu better!
Given that Ubuntu Jaunty 9.04 has hit it's End of Life (EOL), I'm
closing this bug report. For more information about the EOL please refer
to [1].
[1]: https://wiki.ubuntu.com/Releases
** Changed in: heartbeat (Ubuntu)
Status:
OK, here is a recipe to see this problem. I hope all the
steps are here!
(0) Install drbd8-utils and heartbeat.
(1) Create a fake disk
dd if=/dev/zero of=drbd_disk count=1M bs=1
losetup /dev/loop0 ./drbd_disk
(2) Create /etc/drbd.conf. I used:
global {
usage-count yes;
}
common {
protocol C
Hi, I am now trying to come up with a simple recipe that
will enable you to reproduce the problem. However, let
me just point out that the current jaunty heartbeat sources
has
./resources/OCF/drbd: DRBD_STATE=$(do_drbdadm state $RESOURCE)
which results in the mentioned problematic output using
Hi Andres,
> So you are setting up MySQL with DRBD.
the service I'm starting is not mysql, but otherwise it is essentially
the same. Since the drbd disk isn't even considered for mounting, due
to error output from drdbadm, it probably doesn't matter what service
is started.
> I'll try to reprod
So you are setting up MySQL with DRBD. I'll try to reproduce this.
However, I've used this setup, and worked ok. Would you mind modying it
so it looks similar? I think you'll only need to add the
tag:
--
heartbe
This is V2 (crm) style, set up following http://www.drbd.org/docs/about (Part
IV, “DRBD-enabled applications”,
section "Using DRBD in Heartbeat CRM-enabled clusters"). It's one drbd disk,
and heartbeat simply mounts it.
--
heartbeat incompatible with drbd8-utils in jaunty
https://bugs.launchpa
Hello there. Are you using Heartbeat V1 or V2 config style? Would you
mind providing and step by step to reproduce this bug please?
** Changed in: heartbeat (Ubuntu)
Status: New => Incomplete
** Changed in: heartbeat (Ubuntu)
Assignee: (unassigned) => Ubuntu High Availability Team (ub
