Hi Ulrich,
When you think the problem is relative to a specified vendor, you'd better
file a report as Lars said.
For see sles11 sp3, you can report here: https://bugzilla.suse.com/index.cgi
>>>
Lars Marowsky-Bree schrieb am 17.07.2015 um 09:50 in Nachricht
> <20150717075045.gu6...@suse.de>
hi Victor.
yeah sure will try it out.
On 27 Jul 2015 20:11, "Victor José Acosta Domínguez"
wrote:
> Can you try "pcs resource defaults on-fail=restart"
>
> then
>
> "pcs resource cleanup "
>
> Victor Acosta
>
>
> 2015-07-27 3:26 GMT-04:00 Digimer :
>
>> On 27/07/15 02:17 AM, Vijay Partha wrote:
Can you try "pcs resource defaults on-fail=restart"
then
"pcs resource cleanup "
Victor Acosta
2015-07-27 3:26 GMT-04:00 Digimer :
> On 27/07/15 02:17 AM, Vijay Partha wrote:
> > This is my messages log.
>
> OK, lets me very precise;
>
> First; Tell us what OS/version you are using and the ve
On 27/07/15 02:17 AM, Vijay Partha wrote:
> This is my messages log.
OK, lets me very precise;
First; Tell us what OS/version you are using and the versions of
corosync and pacemaker (1.1.11 I think).
Second,
1. Get your services running.
2. Log into each node, open a terminal and run 'tail -f
Stonith, in short, puts a node that has entered an unknown state (or a
service is it running enters a unknown state) into a known state,
usually by force-rebooting the node. How this is actually done depends
on what hardware (or hypervisor) your nodes are using.
So for me to offer any additional a
