On Mon, 14 Apr 2014 14:40:43 +1000
Andrew Beekhof wrote:
>
> On 11 Apr 2014, at 10:54 pm, Marco Felettigh wrote:
>
> > On Fri, 11 Apr 2014 17:17:57 +1000
> > Andrew Beekhof wrote:
> >
> >>
> >> On 8 Apr 2014, at 8:37 pm, ma...@nucleus.it wrote:
> >>
> >>> On Tue, 8 Apr 2014 10:49:16 +1000
On 11 Apr 2014, at 10:54 pm, Marco Felettigh wrote:
> On Fri, 11 Apr 2014 17:17:57 +1000
> Andrew Beekhof wrote:
>
>>
>> On 8 Apr 2014, at 8:37 pm, ma...@nucleus.it wrote:
>>
>>> On Tue, 8 Apr 2014 10:49:16 +1000
>>> Andrew Beekhof wrote:
>>>
On 7 Apr 2014, at 8:46 pm, ma...@nuc
On Fri, 11 Apr 2014 17:17:57 +1000
Andrew Beekhof wrote:
>
> On 8 Apr 2014, at 8:37 pm, ma...@nucleus.it wrote:
>
> > On Tue, 8 Apr 2014 10:49:16 +1000
> > Andrew Beekhof wrote:
> >
> >>
> >> On 7 Apr 2014, at 8:46 pm, ma...@nucleus.it wrote:
> >>
> >>> Hi,
> >>> in a production environment
On 8 Apr 2014, at 8:37 pm, ma...@nucleus.it wrote:
> On Tue, 8 Apr 2014 10:49:16 +1000
> Andrew Beekhof wrote:
>
>>
>> On 7 Apr 2014, at 8:46 pm, ma...@nucleus.it wrote:
>>
>>> Hi,
>>> in a production environment with 2 nodes ( nodeA , nodeB ) we had an
>>> hardware failure so we restart the
On 7 Apr 2014, at 8:46 pm, ma...@nucleus.it wrote:
> Hi,
> in a production environment with 2 nodes ( nodeA , nodeB ) we had an
> hardware failure so we restart the nodeB.
> After the restarted nodeB came up we restart corosync/pacemaker on it
> but for 2 days till now che corosync/pacemaker stuf
Hi,
in a production environment with 2 nodes ( nodeA , nodeB ) we had an
hardware failure so we restart the nodeB.
After the restarted nodeB came up we restart corosync/pacemaker on it
but for 2 days till now che corosync/pacemaker stuff is looping.
crm_mon NodeA:
Stack: openais
Current DC: nodeA
