Hi Alan,

> > blue04 IPaddr2::192.168.5.5/24/eth1:1
> >
> > This works just fine in release 2.0.3-9, but after having recently
> > upgraded to 2.0.5-1, I noticed that a nasty error message is now
printed
> > every time the resource is checked (every 5 seconds in this case):
> 
> I can understand how that might be annoying ;-).
> 
> BUT, you should also understand that I think the code doesn't pay any
> attention to that parameter.  Unless I'm mistaken, you got that
virtual
> interface more by luck than anything else...
> 
> You might consider using IPaddr2 instead.  By default it doesn't
assign
> any name to the interface.  Since it doesn't try and find a free
> interface number, it allows you to specify it instead as parameter.

That's just it - I've been using IPaddr2 this whole time, in the
following format: IPaddr2::192.168.5.5/24/eth1:1
As you said, it normally does not assign a virtual interface, unless I
explicitly specify it, as above. This is why I was surprised by the
recurring error message. 

eth1 normally has only one IP Address bound to it, and there are no
other virtual interfaces associated with eth1. If a virtual interface
number was specified, the proper virtual interface seems to get grabbed
every time, but it keeps printing the error message.

> I see the bug :-(.
> 
> I'll file a bugzilla...
> 
> http://www.osdl.org/developer_bugzilla/show_bug.cgi?id=1259
> [Of course, I could be wrong ;-)]

Doubt that, I've got megabytes upon megabytes of logs with that error
message  :)
Regardless of the resolution to the virtual interface support issue,
we've decided to stop depending on the presence of a virtual interface.
Instead, we'll be parsing the results of 'ip addr show', which is the
approach that we should've taken in the first place, in my opinion.

Big Thanks for looking into it, Alan and David!

Thanks,
--John
 

_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Reply via email to