[Expired for ocfs2-tools (Ubuntu) because there has been no activity for
60 days.]
** Changed in: ocfs2-tools (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ocfs2-tools in Ubuntu.
[Expired for ocfs2-tools (Ubuntu) because there has been no activity for
60 days.]
** Changed in: ocfs2-tools (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Jacob,
you were right. Of course the leftover from the Master/Slave setup up was
utterly wrong and I removed that.
Other than that I changed the following Pacemaker objects:
- Object that defines the multi state resource:
- ms msDrbd2 resDrbd2 meta resource-stickiness=100 master-max=2
Henning
You are probably right that this isn't the right place to continue with
non-bug questions though Andres or others could answer that more
acurately.
I would recommend drbd-users mailing list as there are many experts
there for config and troubleshooting. Also the pacemaker mailing lists
Hi Jacob,
You have your split brain handling configured like this still?:
after-sb-0pri disconnect;
after-sb-1pri consensus;
after-sb-2pri disconnect;
Yes, I stil have this configuration active. I'll try your suggestions.
No, I have not configured STONIT properly yet.
I hope all of
Henning
You are probably right that this isn't the right place to continue with
non-bug questions though Andres or others could answer that more
acurately.
I would recommend drbd-users mailing list as there are many experts
there for config and troubleshooting. Also the pacemaker mailing lists
Hi Jacob,
You have your split brain handling configured like this still?:
after-sb-0pri disconnect;
after-sb-1pri consensus;
after-sb-2pri disconnect;
Yes, I stil have this configuration active. I'll try your suggestions.
No, I have not configured STONIT properly yet.
I hope all of
Hello Jacob,
you were right. Of course the leftover from the Master/Slave setup up was
utterly wrong and I removed that.
Other than that I changed the following Pacemaker objects:
- Object that defines the multi state resource:
- ms msDrbd2 resDrbd2 meta resource-stickiness=100 master-max=2
Hello Jacob,
thank you for your reply. I'm not sure whether the Pacemaker resource
definitions are the real problem as I keep getting the following message
Jul 13 16:18:01 node2 ocfs2_controld[29698]: Unable to open checkpoint
ocfs2:controld: Object does not exist
Jul 13 16:18:53 node2
I know how it might not look like a Pacemaker problem but I believe it
is. Pacemaker is in charge of everything. As I put in the comment
before I believe this line disallows Drbd2 to be master on node 2:
location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1
Since everything else
Hello Jacob,
thank you for your reply. I'm not sure whether the Pacemaker resource
definitions are the real problem as I keep getting the following message
Jul 13 16:18:01 node2 ocfs2_controld[29698]: Unable to open checkpoint
ocfs2:controld: Object does not exist
Jul 13 16:18:53 node2
I know how it might not look like a Pacemaker problem but I believe it
is. Pacemaker is in charge of everything. As I put in the comment
before I believe this line disallows Drbd2 to be master on node 2:
location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1
Since everything else
Hi there,
sorry for getting back that late to the issue but I had to work on
somehting else for the past few days.
I did revert both virtual machines again and here's the exact sequence
of commands I've use to attempt to get the Pacemaker integrated dual
master setup to work:
- apt-get install
The requested corosync configuration file
** Attachment added: corosync.conf
https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+attachment/2195103/+files/corosync.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
The full Pacemaker configuration
** Attachment added: PacemakerConfiguration.txt
https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+attachment/2195104/+files/PacemakerConfiguration.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team,
You have a location constraint for msDrbd2 that requires it to be master
on node 1 only. I would assume it's leftover from your master/slave
setup:
location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1
I would remove that and see what happens. Also a few other things:
In
Whoops! I put them backwards too!
In this ordering statement I think you meant to put before not after...
:-)
order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm
I meant it should be after not before!
--
You received this bug notification because you are a member of Ubuntu
Hi there,
sorry for getting back that late to the issue but I had to work on
somehting else for the past few days.
I did revert both virtual machines again and here's the exact sequence
of commands I've use to attempt to get the Pacemaker integrated dual
master setup to work:
- apt-get install
The requested corosync configuration file
** Attachment added: corosync.conf
https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+attachment/2195103/+files/corosync.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The full Pacemaker configuration
** Attachment added: PacemakerConfiguration.txt
https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+attachment/2195104/+files/PacemakerConfiguration.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You have a location constraint for msDrbd2 that requires it to be master
on node 1 only. I would assume it's leftover from your master/slave
setup:
location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1
I would remove that and see what happens. Also a few other things:
In
Whoops! I put them backwards too!
In this ordering statement I think you meant to put before not after...
:-)
order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm
I meant it should be after not before!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
U Čet, 23. 06. 2011., u 07:13 +, HenningMalzahn je napisao/la:
3. When you dpkg-reconfigure ocfs2-tools package, and after the output has
finished showing, did you disable o2cb as showed in the HowTo? sudo
update-rc.d o2cb disable
- Yes, did that. Enabled the services to be loaded at
Hello Andres,
I have to apologize having files this as a bug. It definitely was a simple
configuration issue on my side. The problem
was not having installed the package openais.
1. Where did you install the tools from? From the Ubuntu Archive or from the
PPA given at the HowTo? (Tools in the
Hi there,
one more question:
Even though everything seems to work fine I get the following message on
the second node
Jun 23 11:21:22 node2 ocfs2_controld[3986]: Unable to open checkpoint
ocfs2:controld: Object does not exist
Jun 23 11:21:22 node2 ocfs2_controld[3986]: last message repeated 17
Hello again,
after a while the setup stopped working completely. Even though the
status (cat /proc/drbd) showed that everything was ok on both nodes the
following message was issued when trying to mount the device on the
first node
root@node1:[/tmp] # mount -t ocfs2 /dev/drbd2 /var/www/
Hello Andres,
I have to apologize having files this as a bug. It definitely was a simple
configuration issue on my side. The problem
was not having installed the package openais.
1. Where did you install the tools from? From the Ubuntu Archive or from the
PPA given at the HowTo? (Tools in the
Hi there,
one more question:
Even though everything seems to work fine I get the following message on
the second node
Jun 23 11:21:22 node2 ocfs2_controld[3986]: Unable to open checkpoint
ocfs2:controld: Object does not exist
Jun 23 11:21:22 node2 ocfs2_controld[3986]: last message repeated 17
Hello again,
after a while the setup stopped working completely. Even though the
status (cat /proc/drbd) showed that everything was ok on both nodes the
following message was issued when trying to mount the device on the
first node
root@node1:[/tmp] # mount -t ocfs2 /dev/drbd2 /var/www/
Hi There!
Thank you for taking the time to report bugs and trying to make Ubuntu
better.
Now, I have a few questions and suggestions that will help determine
your issue:
1. Where did you install the tools from? From the Ubuntu Archive or from the
PPA given at the HowTo? (Tools in the Ubuntu
Hi There!
Thank you for taking the time to report bugs and trying to make Ubuntu
better.
Now, I have a few questions and suggestions that will help determine
your issue:
1. Where did you install the tools from? From the Ubuntu Archive or from the
PPA given at the HowTo? (Tools in the Ubuntu
31 matches
Mail list logo