[Pacemaker] Antwort: !!!!!!!!!!!!!!!!!!!!!!!!!!WG: clvm cluster failover problem

Patrik.Rapposch at knapp.com Patrik.Rapposch at knapp.com
Wed Feb 9 08:17:48 UTC 2011


the solution was to change the ressource constraint to a single ressource 
in the group and not have the constraint between dlm-clvm-clone and the 
group itself. - this doesn't work.

kr patrik

Mit freundlichen Grüßen / Best Regards

Patrik Rapposch, BSc
System Administration

KNAPP Systemintegration GmbH
Waltenbachstraße 9
8700 Leoben, Austria 
Phone: +43 3842 805-915
Fax: +43 3842 82930-500
patrik.rapposch at knapp.com 
www.KNAPP.com 

Commercial register number: FN 138870x
Commercial register court: Leoben

The information in this e-mail (including any attachment) is confidential 
and intended to be for the use of the addressee(s) only. If you have 
received the e-mail by mistake, any disclosure, copy, distribution or use 
of the contents of the e-mail is prohibited, and you must delete the 
e-mail from your system. As e-mail can be changed electronically KNAPP 
assumes no responsibility for any alteration to this e-mail or its 
attachments. KNAPP has taken every reasonable precaution to ensure that 
any attachment to this e-mail has been swept for virus. However, KNAPP 
does not accept any liability for damage sustained as a result of such 
attachment being virus infected and strongly recommend that you carry out 
your own virus check before opening any attachment.



Patrik.Rapposch at knapp.com 
31.01.2011 06:49
Bitte antworten an
The Pacemaker cluster resource manager  <pacemaker at oss.clusterlabs.org>


An
pacemaker at oss.clusterlabs.org
Kopie

Thema
[Pacemaker] !!!!!!!!!!!!!!!!!!!!!!!!!!WG: clvm cluster failover problem






doesn noone have an idea?
would need that realy urgent.
thx,
kr
 
 

Patrik.Rapposch at knapp.com
29.01.2011 03:42Bitte antworten anThe Pacemaker cluster resource manager

An   pacemaker at oss.clusterlabs.org
Kopie   
Blindkopie   
Thema   [Pacemaker] clvm cluster failover problem
 

hy,

a problem with the clvm cluster solution. Everything works fine, except 
the
rejoin of a failed node. when the node comes back, the ressources get
stopped and started again on the node where they reside when the node 
comes
back and I don't realy know the reason for this.

I use the newest approved novell versions for sles 11.1:
pacemaker-1.1.2-0.7.1
pacemaker-mgmt-client-2.0.0-0.3.10
libpacemaker3-1.1.2-0.7.1
pacemaker-mgmt-2.0.0-0.3.10
libpacemaker-devel-1.1.2-0.7.1
drbd-pacemaker-8.3.7-0.4.15
pacemaker-mgmt-devel-2.0.0-0.3.10
libcorosync4-1.2.6-0.2.2
corosync-1.2.6-0.2.2
libcorosync-devel-1.2.6-0.2.2
libopenais3-1.1.3-0.2.3
libopenais-devel-1.1.3-0.2.3
openais-1.1.3-0.2.3
yast2-cluster-2.15.0-8.8.9
cluster-glue-1.0.6-0.3.7
cluster-network-kmp-default-1.4_2.6.32.24_0.2-2.3.22

Attached you can find my main configuration. I would appreciate any ideas
on that problem. Services which are managed by the cluster are off.

many thx in advance.

kr patrik
_______________________________________________
Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: 
http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
_______________________________________________
Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: 
http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110209/d6ed3788/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cib.xml
Type: application/octet-stream
Size: 11520 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110209/d6ed3788/attachment-0003.obj>


More information about the Pacemaker mailing list