On Wed, Sep 1, 2010 at 3:05 PM, Rainer wrote:
> edit:
>
> Also found this in the Logs:
>
> stonith-ng: [18851]: ERROR: crm_abort: remote_op_done: Triggered assert at
> remote.c:134 : op->request != NULL
>
>
> Time for the Support Request i think...
Yes. Novell has a fix for this. It may even be
Andrew Beekhof writes:
> SLES11 ?
yes,
and now i also have my old vgdisplay hangs problem again :-) and i cannot reboot
the node, because the fencing mechanism is not working...
Funny thing about it, it's always the same volume group at the same time ( 22pm
) that fails...
Yesterday i put "on-
On Wed, Sep 1, 2010 at 3:05 PM, Rainer wrote:
> edit:
>
> Also found this in the Logs:
>
> stonith-ng: [18851]: ERROR: crm_abort: remote_op_done: Triggered assert at
> remote.c:134 : op->request != NULL
>
>
> Time for the Support Request i think...
SLES11 ?
>
> Kind regards,
>
> Rainer
>
>
>
>
>
edit:
Also found this in the Logs:
stonith-ng: [18851]: ERROR: crm_abort: remote_op_done: Triggered assert at
remote.c:134 : op->request != NULL
Time for the Support Request i think...
Kind regards,
Rainer
___
Pacemaker mailing list: Pacemaker@
Hi all,
i have a strange Error on one of my Clusters.
ERROR: tengine_stonith_callback: Stonith of saput1d1 failed (-7)... aborting
transition.
info: abort_transition_graph: tengine_stonith_callback:402 - Triggered
transition abort (complete=0) : Stonith failed
Due to that, the suriving node cou
