20.04.2012 03:21, Andrew Beekhof wrote:
> On Fri, Apr 20, 2012 at 7:41 AM, Vladislav Bogdanov
> wrote:
>> 19.04.2012 20:48, David Vossel wrote:
>>> - Original Message -
From: "Alan Robertson"
To: pacemaker@oss.clusterlabs.org, "Andrew Beekhof"
Cc: "Dejan Muhamedagic"
On Fri, Apr 20, 2012 at 3:09 AM, Andrew Beekhof wrote:
> On Thu, Apr 19, 2012 at 11:51 PM, Dan Frincu wrote:
>> Hi,
>>
>> On Thu, Apr 19, 2012 at 3:56 PM, Parshvi wrote:
>>> 1) What is the use of ssh without pass key between cluster nodes in
>>> pacemaker ?
>>> a. Use case:
>>> i. Two nodes
Hi,
is there an easy way to move the DC from one
node to another - without shutting down the current DC node ?
Karl
--
Karl RößmannTel. +49-711-689-1657
Max-Planck-Institut FKF Fax. +49-711-689-1632
Postfach 800 665
70506 Stuttgart
> Hi,
>
> is there an easy way to move the DC from one
> node to another - without shutting down the current DC node ?
>
> Karl
Why do you want to do this. Don't you like the computer where it is running
now? The location of the DC is completely irrelevant to the cluster.
--
Dr. Michael Schwa
On Fri, Apr 20, 2012 at 9:37 AM, Karl Rößmann wrote:
> Hi,
>
> is there an easy way to move the DC from one
> node to another - without shutting down the current DC node ?
Let's assume that you have a reason to do this. You can set maintenance-mode
to true, restart the corosync/heartbeat on the D
Quoting Michael Schwartzkopff :
Hi,
is there an easy way to move the DC from one
node to another - without shutting down the current DC node ?
Karl
Why do you want to do this. Don't you like the computer where it is running
now? The location of the DC is completely irrelevant to the cluster.
> Quoting Michael Schwartzkopff :
> >> Hi,
> >>
> >> is there an easy way to move the DC from one
> >> node to another - without shutting down the current DC node ?
> >>
> >> Karl
> >
> > Why do you want to do this. Don't you like the computer where it is
> > running now? The location of the DC
Hi,
On Fri, Apr 20, 2012 at 1:08 PM, Bensch, Kobus
wrote:
> Hi
>
> I have the following cluster setup:
>
> 2 physical Dell servers with RHEL6.2 with all the latest patches.
>
> Each server has 3 network connections that looks like this:
>
> BOND0 2 NIC's
>
> ETH4 for Corosync
> ETH6 for corosync
> Hi
>
> I have the following cluster setup:
(...)
> When the server crashes I get this in the log:
> Apr 20 10:54:17 corosync [TOTEM ] FAILED TO RECEIVE
Did you by chance not open the firewall for corosync communication?
--
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München
Tel: (0163) 1
On 04/20/2012 12:08 PM, Bensch, Kobus wrote:
> Hi
>
> I have the following cluster setup:
>
> 2 physical Dell servers with RHEL6.2 with all the latest patches.
>
> Each server has 3 network connections that looks like this:
>
> BOND02 NIC's
>
> ETH4 for Corosync
> ETH6 for corosync
>
> This i
Hi guys,
Got terrible error with monitoring DRBD active/passive cluster. This setup
had been working without issues for 1 year.
In logs:
...
WARN: unpack_rsc_op: Processing failed op P_DRBD:1_monitor_5000 on
server1.example.com : unknown exec error (-2)
...
Master/Slave Set: MS_DRBD
Apr 20 09:47
11 matches
Mail list logo