@Stefan, thanks for the reply. It seems my information was not that
clear. Here some more so it is more clear what my problem was.
The problem is with the pacemaker drbd agent:
/usr/lib/ocf/resource.d/linbit/drbd
Here a snippet of this agent:
-
drbd_start() {
local rc
Ah yes, that helps a lot. So somehow (not sure this is because I am
using the Linux Cluster Management Console for setting up my test
environment or because timing is just in my favour) I seem to avoid this
because the drbd init script already loads the module. So by the time
the pacemaker agent
@Stefan, thanks for the reply. It seems my information was not that
clear. Here some more so it is more clear what my problem was.
The problem is with the pacemaker drbd agent:
/usr/lib/ocf/resource.d/linbit/drbd
Here a snippet of this agent:
-
drbd_start() {
local rc
Ah yes, that helps a lot. So somehow (not sure this is because I am
using the Linux Cluster Management Console for setting up my test
environment or because timing is just in my favour) I seem to avoid this
because the drbd init script already loads the module. So by the time
the pacemaker agent
@Jacob, sorry for the long delay. I tried to confirm your report but
could not see any problem (drbd8 version 2:8.4.3-0ubuntu0.12.04.2). Not
sure whether you refer to eval $(drbdadm --version ...) in
/etc/init.d/drbd. That could indeed be wrong on start. Though the values
are actually only
@Jacob, sorry for the long delay. I tried to confirm your report but
could not see any problem (drbd8 version 2:8.4.3-0ubuntu0.12.04.2). Not
sure whether you refer to eval $(drbdadm --version ...) in
/etc/init.d/drbd. That could indeed be wrong on start. Though the values
are actually only
I had the same problem and found out that there is a different behaviour
of the drbd agent between just stop and start the drbd resource or
rebooting the system. When you stop drbd, the drbd module stay loaded so
when you start drbd again, the validity check of the agent correctly
detects an 8.3
I had the same problem and found out that there is a different behaviour
of the drbd agent between just stop and start the drbd resource or
rebooting the system. When you stop drbd, the drbd module stay loaded so
when you start drbd again, the validity check of the agent correctly
detects an 8.3
Hi,
I had same problem during a regular update. The package from
http://people.canonical.com/~smb/lp1185756/ works for me in individual
DRBD config and Pacemaker/Heartbeat env. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Hi,
I had same problem during a regular update. The package from
http://people.canonical.com/~smb/lp1185756/ works for me in individual
DRBD config and Pacemaker/Heartbeat env. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can confirm that solution in #97 (i.e. #71) worked for me as well
(also Pacemaker/Heartbeat).
# uname -a
Linux server 3.5.0-49-generic #74~precise1-Ubuntu SMP Fri May 2 21:32:31 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
# drbdadm --version : identical
# echo drbd8-utils hold | dpkg
I can confirm that solution in #97 (i.e. #71) worked for me as well
(also Pacemaker/Heartbeat).
# uname -a
Linux server 3.5.0-49-generic #74~precise1-Ubuntu SMP Fri May 2 21:32:31 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
# drbdadm --version : identical
# echo drbd8-utils hold | dpkg
I was able to fix this by downgrading drbd8-utils as explained in #71,
Pacemaker/heartbeat.
CRM is again UP!
# uname -a
Linux flexfive 3.5.0-48-generic #72~precise1-Ubuntu SMP Tue Mar 11 20:09:08 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
# drbdadm --version
DRBD module version: 8.3.13
I was able to fix this by downgrading drbd8-utils as explained in #71,
Pacemaker/heartbeat.
CRM is again UP!
# uname -a
Linux flexfive 3.5.0-48-generic #72~precise1-Ubuntu SMP Tue Mar 11 20:09:08 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
# drbdadm --version
DRBD module version: 8.3.13
FTR, my reported bug was triggered by the environment variable
DRBD_DONT_WARN_ON_VERSION_MISMATCH, which was set on my systems.
To work around this bug:
unset DRBD_DONT_WARN_ON_VERSION_MISMATCH
restart pacemaker
(do this before installing drbd8-utils 8.4.3-0ubuntu0.12.04.x)
See also:
FTR, my reported bug was triggered by the environment variable
DRBD_DONT_WARN_ON_VERSION_MISMATCH, which was set on my systems.
To work around this bug:
unset DRBD_DONT_WARN_ON_VERSION_MISMATCH
restart pacemaker
(do this before installing drbd8-utils 8.4.3-0ubuntu0.12.04.x)
See also:
I hope if I can get someone to sponsor the upload. Of course every
positive feedback about the last version helps me in my argument. :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
I still have problems after upgrading to drbd8-utils
2:8.4.3-0ubuntu0.12.04.2~rc4.
Especially the pacemaker drbd agent does not work
(/usr/lib/ocf/resource.d/linbit/drbd). For example, there is a line
do_drbdadm $DRBD_TO_PEER -v adjust $DRBD_RESOURCE which translates to
drbdadm -c /etc/drbd.conf
I can confirm that drbd8-utils 2:8.4.3-0ubuntu0.12.04.2~rc4 works fine,
at least for me.
I put one node to standby, installed drbd8-utils
2:8.4.3-0ubuntu0.12.04.2~rc4, did not change drbd.conf, brought node up
again and migrated all resources to that node. Everything is working as
expected:
@Thilo,
this is odd. Locally I see the same adjust command but it will get
translated into a drbdadm-83 call which works. Would it be possible for
you to create '/tmp/drbd.ocf.ra.debug', set it to chmod 700 for root and
touch /tmp/drbd.ocf.ra.debug/log as root. Then service corosync
restart will
Thilo, I looked at the debug data you sent me and somehow it seems that
using hearbeat runs a different resource agent. So drbd itself ships a
resource agent in /usr/lib/ocf/resource.d/linbit/drbd but hearbeat uses
another one (.../resource.d/heartbeat/drbd) that comes with a different
package
Must admit the two scripts as they are installed on my test system
differ more. Weirdly in your output there was a version check of
++ DRBDADM_VERSION_CODE=0x08030b
++ DRBDADM_VERSION=8.3.11
+ (( 0x08030b = 0x080302 ))
and that check I cannot find in the heartbeat/drbd script. And the
That really depends on the Pacemaker configuration. If the primitive
DRBD resource uses ocf::heartbeat::drbd, it's the resource agent from
resource-agents, /usr/lib/ocf/resource.d/heartbeat/drbd, which is
ancient and shouldn't be used.
If the primitive, however, uses ocf::linbit::drbd, it's the
Thanks, Martin, fot the clarification. The ocf::linbit::drbd agent is
(and was) configured, so that's not the source of the problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
Right, thanks Martin. So Thilo, the mysterious question is what is
actually executed. If you manually unpack the rc4 deb:
dpkg -x drbd8-utils_8.4.3-0ubuntu0.12.04.2~rc4_amd64.deb unpack
and compare unpack/usr/lib/ocf/resource.d/linbit/drbd with what is in
/usr/lib/... they should be the same.
regression is tracked under bug 1314289
** Description changed:
Request for SRU:
[Impact]
DRBD will not work (hang) on fresh install using Ubuntu 12.04.3 media, and
will stop working on sites where the Raring Enablement Stacks is manually
installed as the API between older and newer drbd
I hope if I can get someone to sponsor the upload. Of course every
positive feedback about the last version helps me in my argument. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
I still have problems after upgrading to drbd8-utils
2:8.4.3-0ubuntu0.12.04.2~rc4.
Especially the pacemaker drbd agent does not work
(/usr/lib/ocf/resource.d/linbit/drbd). For example, there is a line
do_drbdadm $DRBD_TO_PEER -v adjust $DRBD_RESOURCE which translates to
drbdadm -c /etc/drbd.conf
I can confirm that drbd8-utils 2:8.4.3-0ubuntu0.12.04.2~rc4 works fine,
at least for me.
I put one node to standby, installed drbd8-utils
2:8.4.3-0ubuntu0.12.04.2~rc4, did not change drbd.conf, brought node up
again and migrated all resources to that node. Everything is working as
expected:
@Thilo,
this is odd. Locally I see the same adjust command but it will get
translated into a drbdadm-83 call which works. Would it be possible for
you to create '/tmp/drbd.ocf.ra.debug', set it to chmod 700 for root and
touch /tmp/drbd.ocf.ra.debug/log as root. Then service corosync
restart will
Thilo, I looked at the debug data you sent me and somehow it seems that
using hearbeat runs a different resource agent. So drbd itself ships a
resource agent in /usr/lib/ocf/resource.d/linbit/drbd but hearbeat uses
another one (.../resource.d/heartbeat/drbd) that comes with a different
package
Must admit the two scripts as they are installed on my test system
differ more. Weirdly in your output there was a version check of
++ DRBDADM_VERSION_CODE=0x08030b
++ DRBDADM_VERSION=8.3.11
+ (( 0x08030b = 0x080302 ))
and that check I cannot find in the heartbeat/drbd script. And the
That really depends on the Pacemaker configuration. If the primitive
DRBD resource uses ocf::heartbeat::drbd, it's the resource agent from
resource-agents, /usr/lib/ocf/resource.d/heartbeat/drbd, which is
ancient and shouldn't be used.
If the primitive, however, uses ocf::linbit::drbd, it's the
Thanks, Martin, fot the clarification. The ocf::linbit::drbd agent is
(and was) configured, so that's not the source of the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
Right, thanks Martin. So Thilo, the mysterious question is what is
actually executed. If you manually unpack the rc4 deb:
dpkg -x drbd8-utils_8.4.3-0ubuntu0.12.04.2~rc4_amd64.deb unpack
and compare unpack/usr/lib/ocf/resource.d/linbit/drbd with what is in
/usr/lib/... they should be the same.
regression is tracked under bug 1314289
** Description changed:
Request for SRU:
[Impact]
DRBD will not work (hang) on fresh install using Ubuntu 12.04.3 media, and
will stop working on sites where the Raring Enablement Stacks is manually
installed as the API between older and newer drbd
Stefan, thank you for the fixes! Will your version find its way to the
update-repo for 12.04lts?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not
Stefan, thank you for the fixes! Will your version find its way to the
update-repo for 12.04lts?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with
I tried the fixed package in comment 60. Unfortunately, the fix did not
completely resolve the problems I had with my Corosync/Pacemaker
cluster.
I also noticed, that I had problems with the new global_common.conf parameters,
that is being installed with drbd-utils 8.4.3:
# service drbd start
*
Well yes, there are already plenty of hints in this thread. The problem is that
while having a config option to enable those compat binaries, those do not seem
to be very well tested. I am working on it but its a bit of a mess. I think I
got the ra script in a state now where it seems to work
Updated http://people.canonical.com/~smb/lp1185756/ with packages that
seem to fix normal corosync startup at least. Still not perfect. Migrate
through the LCMC gui might still be a problem. I need to look into that
next. Also if someone knows from the top of their head what the LCMC gui
does to
** Patch added: Debdiff for rc2 level.
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+attachment/4096314/+files/drbdsetup-fix.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
Finally figured out the problem with LCMC which maybe also improves
other drbdsetup oddness. The problem is that unlike drbdadm, drbdsetup
did not use the kernel drbd module version to decide whether it should
run the legacy binary. Instead it waited for some socket connection to
fail. But that
*sigh* Final update, at least this week. With rc4 my code actually does
the right thing. Updated the kernel on one side to a 3.11 one and then
the other side to the new package (keeping the 3.2 kernel there). From
what I can tell, the cluster seems happy with that.
** Patch added: Debdiff for rc4
Stefan, your rc4 update seems to have nailed it! My cluster running the
3.2 kernel is now happy. The new fix you used also pleases Ganeti.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
I tried the fixed package in comment 60. Unfortunately, the fix did not
completely resolve the problems I had with my Corosync/Pacemaker
cluster.
I also noticed, that I had problems with the new global_common.conf parameters,
that is being installed with drbd-utils 8.4.3:
# service drbd start
*
Well yes, there are already plenty of hints in this thread. The problem is that
while having a config option to enable those compat binaries, those do not seem
to be very well tested. I am working on it but its a bit of a mess. I think I
got the ra script in a state now where it seems to work
** Patch added: Debdiff for rc2 level.
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+attachment/4096314/+files/drbdsetup-fix.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Updated http://people.canonical.com/~smb/lp1185756/ with packages that
seem to fix normal corosync startup at least. Still not perfect. Migrate
through the LCMC gui might still be a problem. I need to look into that
next. Also if someone knows from the top of their head what the LCMC gui
does to
Finally figured out the problem with LCMC which maybe also improves
other drbdsetup oddness. The problem is that unlike drbdadm, drbdsetup
did not use the kernel drbd module version to decide whether it should
run the legacy binary. Instead it waited for some socket connection to
fail. But that
*sigh* Final update, at least this week. With rc4 my code actually does
the right thing. Updated the kernel on one side to a 3.11 one and then
the other side to the new package (keeping the 3.2 kernel there). From
what I can tell, the cluster seems happy with that.
** Patch added: Debdiff for rc4
Stefan, your rc4 update seems to have nailed it! My cluster running the
3.2 kernel is now happy. The new fix you used also pleases Ganeti.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
I also had a problem starting DRBD with my Corosync/Pacemaker cluster
after upgrading drbd8-utils to 8.4.3.
This is a line from the log file where it is failing:
Apr 24 08:21:02 www6a lrmd: [1183]: info: RA output: (p_drbd_r0:0:start:stderr)
Could not connect to 'drbd' generic netlink family
@Rocco, the problem is that there did not seem to be any sane way to do
a separate package and dependencies. You cannot depend on it in the lts
kernel package because drbd is not a required package. In don't know of
any way in Debian packaging to declare complex relationships like if
package a
@Andreas, that particular error is fixed by the test packages (see
comment #60). There could be one in conjunction with pacemaker which
reports an error about drbdadm syncer not being a valid command.
Unfortunately I don't think anyone who is running a pacemaker cluster
really can afford to help
Hello,
the Linux Cluster Management Console (LCMC) makes it quite easy to setup a
DRBD/Pacemaker cluster.
http://lcmc.sourceforge.net/
Christoph
- Ursprüngliche Mail -
Von: Stefan Bader stefan.ba...@canonical.com
An: cmita...@thomas-krenn.com
Gesendet: Donnerstag, 24. April 2014
My clusters are configured to use Linbit:drbd which is:
/usr/lib/ocf/resource.d/linbit/drbd
and that file is in drbd8-utils
On Thu, Apr 24, 2014 at 10:45 AM, Christoph Mitasch
cmita...@thomas-krenn.com wrote:
Hello,
the Linux Cluster Management Console (LCMC) makes it quite easy to setup
I'm not sure if anyone has mentioned it yet, but the command syntax to
the drbdsetup command has changed totally between drbd8-utils 8.3 and
8.4
e.g. if you are using drbd-utils 8.3 then the command is
drbdsetup /dev/drbd0 show
if you are using drbd-utils 8.4 then the command is
drbdsetup show
Hmm, just to clarify: when using the drbd8-utils 8.4 package and the
kernel module 8.3, then drbdsetup execs the drbdsetup-83 compatibility
module which implements the old syntax, and will also if necessary swap
the first two arguments for forward compatibility
However there are some commands
I also had a problem starting DRBD with my Corosync/Pacemaker cluster
after upgrading drbd8-utils to 8.4.3.
This is a line from the log file where it is failing:
Apr 24 08:21:02 www6a lrmd: [1183]: info: RA output: (p_drbd_r0:0:start:stderr)
Could not connect to 'drbd' generic netlink family
@Rocco, the problem is that there did not seem to be any sane way to do
a separate package and dependencies. You cannot depend on it in the lts
kernel package because drbd is not a required package. In don't know of
any way in Debian packaging to declare complex relationships like if
package a
@Andreas, that particular error is fixed by the test packages (see
comment #60). There could be one in conjunction with pacemaker which
reports an error about drbdadm syncer not being a valid command.
Unfortunately I don't think anyone who is running a pacemaker cluster
really can afford to help
Hello,
the Linux Cluster Management Console (LCMC) makes it quite easy to setup a
DRBD/Pacemaker cluster.
http://lcmc.sourceforge.net/
Christoph
- Ursprüngliche Mail -
Von: Stefan Bader stefan.ba...@canonical.com
An: cmita...@thomas-krenn.com
Gesendet: Donnerstag, 24. April 2014
My clusters are configured to use Linbit:drbd which is:
/usr/lib/ocf/resource.d/linbit/drbd
and that file is in drbd8-utils
On Thu, Apr 24, 2014 at 10:45 AM, Christoph Mitasch
cmita...@thomas-krenn.com wrote:
Hello,
the Linux Cluster Management Console (LCMC) makes it quite easy to setup
I'm not sure if anyone has mentioned it yet, but the command syntax to
the drbdsetup command has changed totally between drbd8-utils 8.3 and
8.4
e.g. if you are using drbd-utils 8.3 then the command is
drbdsetup /dev/drbd0 show
if you are using drbd-utils 8.4 then the command is
drbdsetup show
Hmm, just to clarify: when using the drbd8-utils 8.4 package and the
kernel module 8.3, then drbdsetup execs the drbdsetup-83 compatibility
module which implements the old syntax, and will also if necessary swap
the first two arguments for forward compatibility
However there are some commands
It is a bit odd. Ok, some warnings seems to be coming from pacemaker commands.
Like the
WARN: decode_transition_key: Bad UUID (crm-resource-3048) in sscanf result (3)
for 0:0:crm-resource-3048
I guess the problem is this:
Apr 22 21:55:43 storage0 lrmd: [1242]: info: RA output:
On a side note, I'm not sure why a new package where released for the
raring stack? Is there a really brilliant reason for not having two
different packages?
On 23 Apr 2014 12:06, Stefan Bader stefan.ba...@canonical.com wrote:
It is a bit odd. Ok, some warnings seems to be coming from pacemaker
This was done because later point releases of 12.04 come with newer
kernels and the drbd module in later kernels needed the newer userspace.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
@Rocco, that said (and not remembering), could it be that that server
uses a kernel version 3.2.x? What does /proc/drbd say?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
~# cat /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
srcversion: 93CE421BB73A731BDC72D8E
~# uname -a
Linux zed1 3.2.0-60-generic #91-Ubuntu
@smb I mean like it states in the header:
But since the new Plans for the LTS-Enablement Stack [1] there should be a
package like drbd8-utils-lts-raring.
It is a bit odd. Ok, some warnings seems to be coming from pacemaker commands.
Like the
WARN: decode_transition_key: Bad UUID (crm-resource-3048) in sscanf result (3)
for 0:0:crm-resource-3048
I guess the problem is this:
Apr 22 21:55:43 storage0 lrmd: [1242]: info: RA output:
On a side note, I'm not sure why a new package where released for the
raring stack? Is there a really brilliant reason for not having two
different packages?
On 23 Apr 2014 12:06, Stefan Bader stefan.ba...@canonical.com wrote:
It is a bit odd. Ok, some warnings seems to be coming from pacemaker
This was done because later point releases of 12.04 come with newer
kernels and the drbd module in later kernels needed the newer userspace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
@Rocco, that said (and not remembering), could it be that that server
uses a kernel version 3.2.x? What does /proc/drbd say?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils
~# cat /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
srcversion: 93CE421BB73A731BDC72D8E
~# uname -a
Linux zed1 3.2.0-60-generic #91-Ubuntu
@smb I mean like it states in the header:
But since the new Plans for the LTS-Enablement Stack [1] there should be a
package like drbd8-utils-lts-raring.
@Thomas, Simon, can you reveal whether there are maybe special options enabled
in the global config or for the resource configs? Both other sides are running
12.04 (Precise) and have not been upgraded, right?
The difference is that Simon did not reboot the upgraded machine but Thomas did
and
I have the same symptoms on my kernel 3.2 cluster indeed:
drbdsetup show all
Could not connect to 'drbd' generic netlink family
I'm sorry I didn't notice this in my tests - I never use drbdsetup which
is supposed to be a low-level tool.
--
You received this bug notification because you are a
Hm, ok. So we where only using drbdadm in testing? In theory there is
also a compat version of drbdsetup there and like for drbdadm the
fallback should be drbdsetup-83 (in /lib/drbd) ...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Looks very much like drbdsetup does not fall back to the 8.3 version, even
though it should according to this commit:
http://git.drbd.org/gitweb.cgi?p=drbd-8.4.git;a=commit;h=b5ef99654f8008a7b6632261f39fc908b4e84210
Anyway, executing /lib/drbd/drbdsetup-83 instead of /sbin/drbdsetup seems
i see no uncommon options in my configs, i built the cluster basically of
linbits dox.
i run a standard pp with no extra repos and did not upgrade to 8.4 whatsoever.
(the updated) node storage0:
root@storage1:~# ssh storage0 cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
thx stefan lionel, will try your suggestions ASAP.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
To
As a workaround verified at my end, you may simply symlink the 8.3 tools
somewhere in the path, so that drbdsetup will find them:
ln -s /lib/drbd/drbdsetup-83 /sbin
Alternatively, you may revert drbd-utils to the 8.3 bersion which is still
available from the release repository and freeze it
I can confirm the problem with the netlink error.
Apr 20 11:54:59 node1 lrmd: [3636]: info: RA output:
(res_drbd_1:0:monitor:stderr) Could not connect to 'drbd' generic
netlink family
I'm using 12.04 with 3.2 kernel (3.2.0-60-generic).
The Pacemaker resource agent is also shipped in a new
From my (quick) reading of the source code, drbdadmin works because it adds
/lib/drbd to the path using add_lib_drbd_to_path(), and drbdsetup seems not to.
One reason for this could be that the driver calls drbdsetup with an abolute
path and the source says in case drbdsetup is called with an
I would rather fix drbdsetup in the same way drbdadm works (so add the
libpath). That way the compat binaries are not exposed in the normal
search path. Which I believe is intentional as from the user perspective
there should be only one command. I am working on a patch and some test
binaries
Also lost my slave on prod system today, pacemaker,crm cluster with
drbd.
lrmd: [1952]: info: RA output: (res_drbd_1:1:monitor:stderr) Could not
connect to 'drbd' generic netlink family
My resources are marked as Unconfigured on slave, but still Primary on
master.
Have not rebooted.
What is
Anyone seeing the error message, try the proposed package on the
upgraded server. Those are for Precise (12.04) and you will need only
the one matching your installation (64bit or 32bit).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Proposing to fix this by adding the patch in drbdsetup, too. See attached
debdiff. Test packages can be found at
http://people.canonical.com/~smb/lp1185756/
** Patch added: Debdiff of proposed fix.
@Stefan, your proposed fix (http://people.canonical.com/~smb/lp1185756/)
worked for me on Precise 64bit with kernel 3.2. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Linking the /lib/drbd/drbdsetup-8.3 to /sbin did NOT solve the problem
for me. Had to revert to to old packages then everyting worked after
cluster restart.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
The proposed package fixes the issue at my end too.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
To
@Rocco, could you try whether the proposed packages from comment #59
would work? The error message only in the drbdsetup code when it fails
to find the compat binary. So I hope that you will not loose the
connection again. I know it really would suck if not but it would give
higher confidence in
@smb I'm afraid I can't. The problem with the upgrade of drbd8-utils
cause downtime on your main (production) DB-cluster today.
I can look though the logs tomorrow, but it was the drbd ocf
master/slave in pacemaker that was failing, causing drbd to get
unconfigured on both nodes.
--
You
got a maintainance-window today and tried
drbd8-utils_8.4.3-0ubuntu0.12.04.2~rc1_amd64.deb which doesnt help the cluster
cause.
attached a cleanup result of one of the drbd resources.
service drbd start still works.
** Attachment added: error_cluster_drbd.log
@Thomas, Simon, can you reveal whether there are maybe special options enabled
in the global config or for the resource configs? Both other sides are running
12.04 (Precise) and have not been upgraded, right?
The difference is that Simon did not reboot the upgraded machine but Thomas did
and
I have the same symptoms on my kernel 3.2 cluster indeed:
drbdsetup show all
Could not connect to 'drbd' generic netlink family
I'm sorry I didn't notice this in my tests - I never use drbdsetup which
is supposed to be a low-level tool.
--
You received this bug notification because you are a
Hm, ok. So we where only using drbdadm in testing? In theory there is
also a compat version of drbdsetup there and like for drbdadm the
fallback should be drbdsetup-83 (in /lib/drbd) ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks very much like drbdsetup does not fall back to the 8.3 version, even
though it should according to this commit:
http://git.drbd.org/gitweb.cgi?p=drbd-8.4.git;a=commit;h=b5ef99654f8008a7b6632261f39fc908b4e84210
Anyway, executing /lib/drbd/drbdsetup-83 instead of /sbin/drbdsetup seems
i see no uncommon options in my configs, i built the cluster basically of
linbits dox.
i run a standard pp with no extra repos and did not upgrade to 8.4 whatsoever.
(the updated) node storage0:
root@storage1:~# ssh storage0 cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
1 - 100 of 214 matches
Mail list logo
