On 2013-11-26T12:09:41, Ulrich Windl wrote:
> I saw that I don't have an SBD device any more (it's stopped). Unfortunately I
> could not start it (crm resource start prm_stonith_sbd).
> I guess it's due to the fact that the cluster won't start resources until the
> UNCLEAN node has been fenced. T
Hi!
I think it's only fair to update you on this issue:
As it turned out the SP3-Upgdate did not update all software that was installed
on the node.
The reason for that seems to be: The RPM database did not contain all installed
software
The reason for that seems to be: The kernel, ext3 filesyst
Hi!
Some updates:
I've completed upgrading 4 of 5 nodes to SP3; the remaining node won't boot
due to a hardware problem.
I saw that I don't have an SBD device any more (it's stopped). Unfortunately I
could not start it (crm resource start prm_stonith_sbd).
I guess it's due to the fact that the c
On 2013-11-26T09:32:50, Ulrich Windl wrote:
> Anotherthing I've notivced: One of out nodes has defective hardware and is
> down. It was OK all the time with SLES11 SP2, but SP3 now tried to fence the
> node and got a fencing timeout:
Hmmm.
> Isn't the logic that after a fencing operation timeou
>>> Lars Marowsky-Bree schrieb am 25.11.2013 um 18:20 in
Nachricht
<20131125172059.gw10...@suse.de>:
> On 2013-11-25T17:48:25, Ulrich Windl
wrote:
>
> Hi Ulrich,
>
>> Probably reason:
>> cib: [12226]: ERROR: cib_perform_op: Discarding update with feature set
> '3.0.7' greater than our own '3.0
