[ovs-discuss] CentOS 6.4 warning: "RTNETLINK answers: File exists" while network restart.

[Denis Iskandarov]

I'm trying.
It's not error of OVS but as well not problem of system only.
RTNETLINK is like bridge between kernel and userspace which notifies and
controls network aspects of systems.
http://www.linuxjournal.com/article/8498
System giving warning because scripts on which ovs depends ifup-ovs
ifdown-ovs creating bridge twice.
Alexey I. Froloff, creator of this scripts, gave me some introduction and
explanation of this warning.
I'm not guru of scripting and many linux aspects by myself.

P.S.: BTW. I realized you are Ben who created OpenFlow.
Respect for this!
Z only future of networking!(and future of my ISP in couple months ;) )
(but controllers still crappy, without failover.)




On Wed, Mar 13, 2013 at 9:51 PM, Ben Pfaff <blp at nicira.com> wrote:

> On Wed, Mar 13, 2013 at 09:29:52PM +0400, Denis Iskandarov wrote:
> > I've tried your suggestion and renamed ovs0 to br0.
> > But still same.
> > I knew that it's not problem but anyways tried. Anything could happen.
> > I knew because it's giving this warning not on bridge creation but on
> both
> > ethernets i added to this bridge.
> > Here is output of "service network restart" with bridge which contains 2
> > interfaces.
> >
> > # service network restart
> > > Shutting down interface br0:                               [  OK  ]
> > > Shutting down interface eth0:                              [  OK  ]
> > > Shutting down interface eth1:                              [  OK  ]
> > > Shutting down loopback interface:                          [  OK  ]
> > > Bringing up loopback interface:                            [  OK  ]
> > > Bringing up interface br0:                                 [  OK  ]
> > > Bringing up interface eth0:  RTNETLINK answers: File exists [  OK  ]
> > > Bringing up interface eth1:  RTNETLINK answers: File exists [  OK  ]
> >
> >
> > Another my suggestion: while i have renamed ovs0 to br0, and renamed
> bridge
> > of interfaces in network script files only and restarted service networ
> > i've got error that can't add interfaces becouse they are slaves of ovs0
> > which i thought i have removed by only changing names in network scripts.
> > So i have checked ovs-vsctl and whole old configuration was still in
> place.
> > i had to remove it and then next network restart assigned this interfaces
> > to br0.
> > So final thought: while system service destroys interfaces and then
> trying
> > to add it again it seeing that those already are part of bridge in system
> > and nothing to do here.
> >
> > What do you think about that, Ben?
>
> I think that I already told you what you need to do in a previous
> email.  Here it is again, in case you did not read it.
>
> The warning does not come from Open vSwitch, which never produces
> error messages of this form.  It comes from some tool that the CentOS
> network scripts run.  I do not see any such calls in the sh -vx
> output.  You need to look closer, at the programs that run inside that
> output.  One of them is calling such a tool.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20130313/6f6532c1/attachment-0001.html>