On Fri, 30 Jan 2009 14:56:53 +0100 Gunther Schlegel wrote:
> Rolling back to openais-0.80.3-15.el5 worked for me as well.
Hello,
with the same strategy I was only able to partially solve the problem.
Two nodes with this in cluster.conf
and
after updating to U3
Rolling back to openais-0.80.3-15.el5 worked for me as well.
Though, this is an 5.3 update blocker, as it prevents rolling upgrades
-- and that is why you run a cluster, ins't it?
I also have no clue whether a native "nativwe" 5.3 /
openais-0.80.3-22el5 system will work. Can anyone confirm th
Confirmed. Same here. Seems like a bug to me still though. I would hope
we have to ability to do rolling upgrades on openais in our RHEL clusters.
2009/1/28 Alan A
> Rolling back to previous openais package allowed me to restart cman. From
> openais-0.80.3-22el5 to
> openais-0.80.3-15.el5.
>
Rolling back to previous openais package allowed me to restart cman. From
openais-0.80.3-22el5 to
openais-0.80.3-15.el5.
2009/1/28 Dave Costakos
> Like you, I've run into this same issue. I have 2 clusters that I'm trying
> to update in our lab. On one, I only updated the cman and rgmanager
>
Like you, I've run into this same issue. I have 2 clusters that I'm trying
to update in our lab. On one, I only updated the cman and rgmanager
packages: this update was successful. On another I did a full update to 5.3
and ran into what appears to be this same problem. II've noticed that
manual
I just opened RHEL case number 1890184 regarding the same issue. First
Kernel would not start due to the HP ILO driver conflict, but at the same
time CMAN broke, and fencing fails. I rolled back cman rpm to the previous
version but problem persists. Something else changed to affect CMAN not
startin
Hello,
I updated one node from 5.2 to 5.3 using yum update and now cman does
not start up anymore -- looks like ccsd has some problems:
[r...@motel6 /]# /sbin/ccsd -4 -n
Starting ccsd 2.0.98:
Built: Dec 3 2008 16:32:30
Copyright (C) Red Hat, Inc. 2004 All rights reserved.
IP Protocol::
