Hi,
On Wed, Jan 23, 2013 at 5:21 AM, Brian J. Murrell br...@interlinx.bc.ca wrote:
OK. So you have a corosync cluster of nodes with pacemaker managing
resources on them, including (of course) STONITH.
What's the best/proper way to shut down a node, say, for maintenance
such that pacemaker
Hi,
We have a 2-node active/standby PGSQL/DRBD Cluster with STONITH and we put one
node in standby
Then shutdown pacemaker on this standby node (service pacemaker stop), wait
some sec, then doing the same
With corosync (service corosync stop), again wait some seconds and always have
a look at
I install drbd + lvm + postgresql + pacemaker on debian 6.
What's wrong with pg_lvm_start_0?
root@node1:/home/hj# crm_mon -1
Last updated: Wed Jan 23 16:36:34 2013
Stack: openais
Current DC: node1 - partition with quorum
Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b
2 Nodes
I've asked this before, you should be able to search the question.
Essentially if pacemaker is shut down gracefully the remaining nodes are
happy to leave it be.
Generally I standby the node and then stop openais ... I have been caught
out once bringing a node back online which was in standby.
root@node2:~# pvdisplay
--- Physical volume ---
PV Name /dev/drbd0
VG Name vgpg
PV Size 952.93 MiB / not usable 956.00 KiB
Allocatable yes
PE Size 4.00 MiB
Total PE 238
Free PE 13
Hello Everybody,
I've got a problem (but I am not quite sure if it is not a feature in
pacemaker ) that's why I decided to write on that mailing list.
It comes about migrate resource with collation in drbd resource.
I've got group including virtual IP and filesystem which is collated with
ms
On 2013-01-23 14:11, Dejan Muhamedagic wrote:
I fixed slapd startup problem by changing resource agent script:
--- slapd.orig 2013-01-22 17:23:42.266314000 +0400
+++ slapd 2013-01-22 17:23:12.094422000 +0400
@@ -299,6 +299,7 @@ slapd_start()
local reason
local result
local state
You must change the order
#order DRBD_BEF_FS inf: ms_drbd:promote IP-AND-FS:start
order DRBD_BEF_FS inf: IP-AND-FS:start ms_drbd:promote
//First start IP-AND-FS, only then promote ms_drbd
Regards,
Kashif Jawed Siddiqui
Ummm
Fist the IP-AND-FS? but what happen if the FS is on drbd?
Thanks
2013/1/23 Kashif Jawed Siddiqui kashi...@huawei.com
You must change the order
#order DRBD_BEF_FS inf: ms_drbd:promote IP-AND-FS:start
order DRBD_BEF_FS inf: IP-AND-FS:start ms_drbd:promote
//First start IP-AND-FS,
2013/1/23 emmanuel segura emi2f...@gmail.com
Ummm
Fist the IP-AND-FS? but what happen if the FS is on drbd?
Emmanuel, you are right, filesystem is on top of drbd device, so i cant run
that group before drbd promote.
I also noticed that, I can migrate it by force with use:
crm_resource -M
There is a Pacemaker bug which cannot be replaced due to legacy tracking and
backward compatibility
colocation FS_WITH_DRBD inf: IP-AND-FS ms_drbd:Master
order DRBD_BEF_FS inf: IP-AND-FS:start ms_drbd:promote
if colocation and order is specified between 2 Resources then it means the 2nd
one
Ohh.. I think it is wrongly interpreted by me. Apologies
Regards,
Kashif Jawed Siddiqui
***
This e-mail and attachments contain confidential information from HUAWEI, which
is intended only for the person or
- Original Message -
From: Raoul Bhatia [IPAX] r.bha...@ipax.at
To: Pacemaker list pacemaker@oss.clusterlabs.org
Sent: Wednesday, January 23, 2013 8:20:43 AM
Subject: Re: [Pacemaker] slapd RA does not start OpenLDAP server after reboot
On 2013-01-23 14:11, Dejan Muhamedagic wrote:
2013/1/23 Kashif Jawed Siddiqui kashi...@huawei.com
There is a Pacemaker bug which cannot be replaced due to legacy tracking
and backward compatibility
colocation FS_WITH_DRBD inf: IP-AND-FS ms_drbd:Master
order DRBD_BEF_FS inf: IP-AND-FS:start ms_drbd:promote
if colocation and order is
Hi,
I have recently upgraded Pacemaker on one of my clusters from
1.0.something to 1.1.8 and installed crmsh to manage it as I used to.
crmsh mostly works for me, until I try to change the configuration with
'crm configure'. Any, even trivial change shows verification errors and
fails to commit:
On 2013-01-23T16:31:20, Jacek Konieczny jaj...@jajcus.net wrote:
I have recently upgraded Pacemaker on one of my clusters from
1.0.something to 1.1.8 and installed crmsh to manage it as I used to.
It'd be helpful if you mentioned which crmsh version you installed. The
errors you get suggest
- Original Message -
From: Yan Gao y...@suse.com
To: pacemaker@oss.clusterlabs.org
Sent: Monday, January 21, 2013 11:28:40 PM
Subject: Re: [Pacemaker] Enable remote monitoring
Hi,
Here's the code for supporting nagios plugins in lrmd:
On Wed, 23 Jan 2013 16:44:45 +0100
Lars Marowsky-Bree l...@suse.com wrote:
On 2013-01-23T16:31:20, Jacek Konieczny jaj...@jajcus.net wrote:
I have recently upgraded Pacemaker on one of my clusters from
1.0.something to 1.1.8 and installed crmsh to manage it as I used
to.
It'd be
Hi,
On Wed, Jan 23, 2013 at 04:31:20PM +0100, Jacek Konieczny wrote:
Hi,
I have recently upgraded Pacemaker on one of my clusters from
1.0.something to 1.1.8 and installed crmsh to manage it as I used to.
crmsh mostly works for me, until I try to change the configuration with
'crm
On 13-01-23 03:32 AM, Dan Frincu wrote:
Hi,
Hi,
I usually put the node in standby, which means it can no longer run
any resources on it. Both Pacemaker and Corosync continue to run, node
provides quorum.
But a node in standby will still be STONITHed if it goes AWOL. I put a
node in standby
Indeed ... thats the correct behavior as it was still an active cluster
member, it just happens to not be running any resources as its in standby.
If you shutdown (gracefully) openais and its showing happily as 'offline'
on the remaining node(s) then all will be well.
On 24 January 2013 10:28,
21 matches
Mail list logo
