Sorry, re-reading that I can see what you mean now. I'll try the patched
packages listed in a bit.
Gordan
On Thu, 12 Mar 2009 16:20:34 +, Gordan Bobic wrote:
> I saw that, but they still seem to be for cman-2.0.98, which I've tried
> from the latest 5.3 package, and it's still broken. The bu
I saw that, but they still seem to be for cman-2.0.98, which I've tried
from the latest 5.3 package, and it's still broken. The bug page Chrissie
pointed at still doesn't list any resolution.
On Thu, 12 Mar 2009 17:11:32 +0100, Gianluca Cecchi
wrote:
> On Thu, 12 Mar 2009 11:04:16 + Gordan
On Thu, 12 Mar 2009 11:04:16 + Gordan Bobic wrote:
>>Marc Grimme wrote:
>> Hi Gordan,
>> more information can be found in this bug (at least you can get the
>> information how far this bug goes back).
>> https://bugzilla.redhat.com/show_bug.cgi?id=485026
> Yeah, I saw that bug entry. The l
The new parameter is -m. Sorry for the confusion.
-Mark
> A new parameter (-w) has been added to the fence_tool utility in RHEL5.3.
> In the latest open-sharedroot preview packages the -w option is used. If
> your fence_tool version does not support -w, the join command will fail.
> The rpm chang
On Thursday 12 March 2009 12:04:16 Gordan Bobic wrote:
> On Thu, 12 Mar 2009 11:52:32 +0100, Mark Hlawatschek
>
> wrote:
> > Hi Gordon,
> >
> >> Yeah, I saw that bug entry. The listing says 5.2 and 5.3 are both
> >> affected (cman 2.0.84 and 2.0.98). I tried 2.0.73 from RHEL 5.1, but
> >> that mak
On Thu, 12 Mar 2009 11:52:32 +0100, Mark Hlawatschek
wrote:
> Hi Gordon,
>
>> Yeah, I saw that bug entry. The listing says 5.2 and 5.3 are both
>> affected (cman 2.0.84 and 2.0.98). I tried 2.0.73 from RHEL 5.1, but
>> that makes my OSR startup fail while joining the fencing domain. :-(
>
> This
Hi Gordon,
> Yeah, I saw that bug entry. The listing says 5.2 and 5.3 are both
> affected (cman 2.0.84 and 2.0.98). I tried 2.0.73 from RHEL 5.1, but
> that makes my OSR startup fail while joining the fencing domain. :-(
This is because the supported parameters in fence_tool have been changed.
Yo
Marc Grimme wrote:
Hi Gordan,
more information can be found in this bug (at least you can get the
information how far this bug goes back).
https://bugzilla.redhat.com/show_bug.cgi?id=485026
Yeah, I saw that bug entry. The listing says 5.2 and 5.3 are both
affected (cman 2.0.84 and 2.0.98). I
Hi Gordan,
more information can be found in this bug (at least you can get the
information how far this bug goes back).
https://bugzilla.redhat.com/show_bug.cgi?id=485026
--
Gruss / Regards,
Marc Grimme
http://www.atix.de/ http://www.open-sharedroot.org/
--
Linux-cluster mailing
Chrissie Caulfield wrote:
Gordan Bobic wrote:
I have a two-node cluster and ever since I updated the kernel and
cluster components I cannot get more than one node running with GFS.
Here are the package versions I have:
kernel-2.6.18-92.1.22.el5
cman-2.0.98-1
kmod-gfs-0.1.23-5.el5_2.4
gfs-utils-
Gordan Bobic wrote:
> I have a two-node cluster and ever since I updated the kernel and
> cluster components I cannot get more than one node running with GFS.
>
> Here are the package versions I have:
> kernel-2.6.18-92.1.22.el5
> cman-2.0.98-1
> kmod-gfs-0.1.23-5.el5_2.4
> gfs-utils-0.1.17-1.el5
I have a two-node cluster and ever since I updated the kernel and
cluster components I cannot get more than one node running with GFS.
Here are the package versions I have:
kernel-2.6.18-92.1.22.el5
cman-2.0.98-1
kmod-gfs-0.1.23-5.el5_2.4
gfs-utils-0.1.17-1.el5
gfs2-utils-0.1.53-1.1
Node 2 star
12 matches
Mail list logo
