[Pacemaker] Node crash when 'ifdown eth0'

[Oscar Remí­rez de Ganuza Satrústegui]

Hi,

Just an update on my experience:

After upgrading to newer versions the problem no longer exists:
pacemaker 1.0.6, corosync 1.1.2, openais 1.1.0 (as found on 
http://www.clusterlabs.org/rpm/epel-5/x86_64/)

No process crashes when I put down the interface (ifdown eth0), and 
everything goes back to normal when I put it up again (ifup eth0)

Lars Marowsky-Bree escribió:
> On 2009-11-30T20:59:13, Steven Dake <sdake at redhat.com> wrote:
>
>   
>> ifconfig eth0 down is a totally different then testing if there is a
>> node disconnection.  When corosync detects eth0 being taken down, it
>> binds to the interface 127.0.0.1.  This is probably not what you had in
>> mind when you wanted to test split brain.  Keep in mind an interface
>> taken out of service is different then an interface failing from a posix
>> api perspective.
>>     
>
> It'd still be nice if it didn't just crash, but if there was some way to
> recover from it at run-time. Think "hotplug network cards (in a telco
> environment)".
>
>
> Regards,
>     Lars
>
>   

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4422 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20091210/45d0b135/attachment-0003.bin>