On Fri, Jul 8, 2011 at 7:46 PM, Andreas Kurz wrote:
> On 2011-07-08 06:52, Andrew Beekhof wrote:
> ...snip...
>>>
>>> Probably the cluster should not have tried to shut down the node as a
>>> substitute for lack of stonith.
>>>
>>
>> Correction, I just checked the code and it does not try to do th
On 2011-07-08 06:52, Andrew Beekhof wrote:
...snip...
>>
>> Probably the cluster should not have tried to shut down the node as a
>> substitute for lack of stonith.
>>
>
> Correction, I just checked the code and it does not try to do this.
> So some part of your sequence of events is off - someone
On 2011-07-08 06:43, Andrew Beekhof wrote:
> On Wed, Jul 6, 2011 at 10:26 PM, Andreas Kurz wrote:
>> On 2011-07-05 00:24, Andrew Beekhof wrote:
>>> On Fri, Jul 1, 2011 at 9:23 PM, Andreas Kurz
>>> wrote:
Hello,
In a cluster without stonith enabled (yes I know ) the monitor
>>>
On Fri, Jul 8, 2011 at 2:43 PM, Andrew Beekhof wrote:
> On Wed, Jul 6, 2011 at 10:26 PM, Andreas Kurz wrote:
>> On 2011-07-05 00:24, Andrew Beekhof wrote:
>>> On Fri, Jul 1, 2011 at 9:23 PM, Andreas Kurz
>>> wrote:
Hello,
In a cluster without stonith enabled (yes I know ) the
On Wed, Jul 6, 2011 at 10:26 PM, Andreas Kurz wrote:
> On 2011-07-05 00:24, Andrew Beekhof wrote:
>> On Fri, Jul 1, 2011 at 9:23 PM, Andreas Kurz wrote:
>>> Hello,
>>>
>>> In a cluster without stonith enabled (yes I know ) the monitor
>>> failure of one resource followed by the stop failure o
On 2011-07-05 00:24, Andrew Beekhof wrote:
> On Fri, Jul 1, 2011 at 9:23 PM, Andreas Kurz wrote:
>> Hello,
>>
>> In a cluster without stonith enabled (yes I know ) the monitor
>> failure of one resource followed by the stop failure of a dependent
>> resource lead to a cascade of errors especia
On Fri, Jul 1, 2011 at 9:23 PM, Andreas Kurz wrote:
> Hello,
>
> In a cluster without stonith enabled (yes I know ) the monitor
> failure of one resource followed by the stop failure of a dependent
> resource lead to a cascade of errors especially because the cluster did
> not stop the shutdow
Hello,
In a cluster without stonith enabled (yes I know ) the monitor
failure of one resource followed by the stop failure of a dependent
resource lead to a cascade of errors especially because the cluster did
not stop the shutdown sequence on stop (timeout) failures:
WARN: should_dump_input: