[Openais] firewire

Dan Frincu df.cluster at gmail.com
Tue Mar 8 02:45:00 PST 2011


On Tue, Mar 8, 2011 at 2:07 AM, ray klassen
<julius_ahenobarbus at yahoo.co.uk>wrote:

> well I have the 1.3.0 version of corosync seemingly happy with udpu and
> firewire. The logs report connection back and forth between the two boxes.
> But
> now crm_mon never connects. Does pacemaker not support udpu yet?
>

Pacemaker is the Cluster Resource Manager, so it doesn't really care about
the underlying method that the Messaging and Membership layer uses to
connect between nodes.

I've had this issue (crm_mon not connecting) when I performed an upgrade
from openais-0.80 to corosync-1.3.0 with udpu, I solved it by eventually
rebooting the servers. In your case I doubt it's an upgrade between versions
of software, since you've reinstalled.

My 2 cents.


>
> pacemaker-1.1.4-5.fc14.i686
> (I switched to fedora from debian to get the latest version of corosync)
>
>
>
>
> ----- Original Message ----
> From: Steven Dake <sdake at redhat.com>
> To: ray klassen <julius_ahenobarbus at yahoo.co.uk>
> Cc: openais at lists.linux-foundation.org
> Sent: Thu, 3 March, 2011 16:56:21
> Subject: Re: [Openais] firewire
>
> On 03/03/2011 05:45 PM, ray klassen wrote:
> > Has anyone had any success running corosync with the firewire-net module?
> I
> >want
> >
> > to set up a two node router cluster with a dedicated link between the
> routers.
>
> > Only problem is, I've run out of ethernet ports so I've got ip configured
> on
> >the
> >
> > firewire ports. pinging's no problem between the addresses.. funny thing
> is, on
> >
> > one of them (and they're really identical) corosync starts up no problem
> at all
> >
> > and stays up. on the other one corosync fails with  "ERROR: ais_dispatch:
> > Receiving message body failed: (2) Library error: Resource temporarily
> > unavailable (11)."
> >
> >
> > Reading up on the firewire-net mailing outstanding issues turned up that
> > multicast wasn't fully implemented so my corosync.conf files both say
> >broadcast:
> >
> > yes. instead of mcast-addr
> >
> > Firewire-net was emitting fwnet_write_complete: failed: 10  errors so I
> pulled
>
> > down the latest vanilla kernel 2.6.37.2 and am running that. with far
> fewer of
>
> > that error..
> >
> > otherwise versions are
> > Debian Squeeze
> > Corosync Version: 1.2.1-4
> > Pacemaker 1.0.9.1+hg15626-1
> >
> > Is this a hopeless case? I've a got a debug log from corosync that
> doesn't seem
> >
> > that helpful. If you want I can post that as well
> >
> > Thanks
> >
>
> I'm hesitant to suggest using firewire as a transport as your the first
> person that has ever tried it.  If multicast is broken on your hardware,
> you might try the "udpu" transport which uses UDP only (udp is the basis
> for all network communication).
>
> Regards
> -steve
>
> >
> >
> > _______________________________________________
> > Openais mailing list
> > Openais at lists.linux-foundation.org
> > https://lists.linux-foundation.org/mailman/listinfo/openais
>
>
>
> _______________________________________________
> Openais mailing list
> Openais at lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/openais
>



-- 
Dan Frincu
CCNA, RHCE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linux-foundation.org/pipermail/openais/attachments/20110308/8590e276/attachment.htm 


More information about the Openais mailing list