[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] Clumembd heartbeat problem.



On Wed, 2004-08-11 at 15:14 +1200, Royce Brown wrote:
> I am not sure if this is the correct place to post this. If not
> and you know where I should, could you please tell me.

Better = taroon-list
Best = bugzilla!

> 	   Sending and receiving message (Correct behaviour)
> clumembd[2]: <debug> sending multicast message fd:5 ,nodeid:1
>             ,addr:225.0.0.11,token:0x0002881d4119638e
> clumembd[2]: <debug> update_seen new msg nodeid:1 token:0x0002881d4119638e
>          
> After a while you get. sinp = source address, nsp = expected address
>   
> clumembd[2]: <debug> sending multicast message fd:5 ,nodeid:1
>              ,addr:225.0.0.11,token:0x0002881d4119638e
> clumembd[2]: <debug> update_seen new msg nodeid:1 token:0x0002881d4119638e
> clumembd[2]: <debug> IP/NodeID mismatch: Probably another cluster on our
>              subnet... msg from nodeid:1 sinp:10.10.197.6 nsp:10.10.197.11

Hmm... this doesn't make a lot of sense; clumembd doesn't rebind
anything.  It's possible to work around it.

> Has anyone else noticed this sort of behaviour on sending multicast messages
> to a Ethernet device with multiple addresses. 

It's news; probably worthy of a bugzilla.

-- Lon


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]