On Tue, Mar 23, 2010 at 2:11 AM, Michael, Benjamin P.
(GSFC-690.0)[CATHOLIC UNIV OF AMERICA]
wrote:
>
> Am somewhat confused with the requirements for Pacemaker. This is what I
> think I understand on the current state. If I have the following right would
> appreciate an affirmative.
>
> 1. T
On Sat, Mar 27, 2010 at 8:36 PM, Stefan Kelemen wrote:
> Hello,
> i have here testsetup with 2 Servers.
>
> Pacemaker does no Failover. when one side is down the takes not teh services
> over.
Please attach the result of 'cibadmin -Ql' when the cluster is in this state.
> After the downed Server
On Sat, Mar 27, 2010 at 6:04 PM, Ray Kiddy wrote:
>
> I hope this is not an aggressively obnoxious first post, but I did look for
> archives
I figured I was the only one doing this :-)
I usually just use the same prefix as used by the ports system...
For glue I use:
./configure --prefix /
Hello,
i have here testsetup with 2 Servers.
Pacemaker does no Failover. when one side is down the takes not teh services
over.
After the downed Server comes up again there is takes all services. Both Nodes
are aktiv.
Pacemaker and heartbeat are the newest stable Versions.
Migration works fine.
I hope this is not an aggressively obnoxious first post, but I did look for
archives
I followed the (very concise) instructions on
http://clusterlabs.org/wiki/install#Darwin.2FMacOS_X and got:
sh-3.2# pwd
/Users/ray/Projects/Clustering/Reusable-Cluster-Components-f46f8eb768
Hi all,
How can I define a resource to configure an active/passive postfix instance? I
have executed "crm ra list ocf heartbeat" and doesn't appears postfix resource.
Which do I need to use??
Thanks.
--
CL Martinez
carlopmart {at} gmail {d0t} com
___
Am somewhat confused with the requirements for Pacemaker. This is what I think
I understand on the current state. If I have the following right would
appreciate an affirmative.
1. The opensuse repo is no longer supported and the clusterlabs repo is the
current officially supported one.
2.
I noticed iSCSILogicalUnit resource agent having faulty behavior with CentOS
5.4 that causes it to fail in monitor operation.
Every monitor cycle it executes the following command:
tgtadm --lld iscsi --op show --mode target
and tries to figure out if there is the volume we're looking for w
Lon Hohberger wrote:
On Fri, 2010-03-26 at 20:05 +0100, carlopmart wrote:
Thanks Lon but I am using fence_xvm from CentOS/RHEL cman package ... Fence-virt
comes from Fedora, correct?? Can I use fence-virt under Centos/Rhel??
You'd have to rebuild it for RHEL/CentOS as it is not currently in R
Resuming normal operation.
If you're having trouble posting, please contact me directly.
-- Andrew
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
On Sat, Mar 27, 2010 at 8:52 AM, Andrew Beekhof wrote:
> Normal operation should resume shortly ;-)
If you can see this, then everything is working again.
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listi
Normal operation should resume shortly ;-)
-- Andrew
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
12 matches
Mail list logo