Hi,
On 30.05.2014 13:20, Robert Dahlem wrote:
>> run crm_report for the period covered by these commands and attach the
>> result:
>>
>> # crm node standby korfwf01 ; sleep 10
>> # crm node standby korfwf02 ; sleep 10
>> # crm node online korfwf02 ; sleep 10
>> # crm node online korfwf01 ; sleep
Hi,
On 23.05.2014 02:40, Andrew Beekhof wrote:
> run crm_report for the period covered by these commands and attach the result:
>
> # crm node standby korfwf01 ; sleep 10
> # crm node standby korfwf02 ; sleep 10
> # crm node online korfwf02 ; sleep 10
> # crm node online korfwf01 ; sleep 10
> #
Hi
I wonder if anyone on the list can help me - I’m new to Pacemaker so apologies
if I’m posting in the wrong place.
I have a four-node cluster running Pacemaker 1.1.10 with Corosync 1.4.1 on
CentOS 6.4. Resource-wise I have eight Lustre storage targets on an iSCSI SAN
- two each colocated wi
On 30 May 2014, at 7:15 pm, Robert Dahlem wrote:
> Hi,
>
> On 23.05.2014 02:40, Andrew Beekhof wrote:
>
>> run crm_report for the period covered by these commands and attach the
>> result:
>>
>> # crm node standby korfwf01 ; sleep 10
>> # crm node standby korfwf02 ; sleep 10
>> # crm node on
Hello there, people!
I am new to this list, so please excuse me if i'm posting to the wrong
place.
I've got a pacemaker cluster with such a configuration:
http://pastebin.com/1SbWWh4n.
Output of "crm status":
Last updated: Fri May 30 11:22:59 2014
Last change: Thu May 29 03:22:38 201
