[ovs-discuss] error inserting brcompat

Mon Nov 19 17:37:50 UTC 2012

Those aren't the relevant messages, I'm talking about what gets logged
to the console at bootup.  It might be in some system log file too, not
sure on Ubuntu.

Any hits for "zgrep 'not removing bridge module' /var/log/*"?

It would be better to upgrade to v1.4.3 if you can.

On Mon, Nov 19, 2012 at 11:35:10AM -0600, Brad Hedlund wrote:
> Hi Ben,
> 
> Here are the OVS relevant messages in *dmesg | tail* with an unmodified
> /etc/init.d/openvswitch-switch file.
> 
> [   13.511615] openvswitch_mod: Open vSwitch switching datapath 1.4.0,
> built Nov  9 2012 19:01:58
> [   13.513072] brcompat_mod: exports duplicate symbol br_should_route_hook
> (owned by bridge)
> [   13.706462] brcompat_mod: exports duplicate symbol br_should_route_hook
> (owned by bridge)
> 
> It would appear my initscript is not running *rmmod bridge* by default.
> 
> As you can see above, I am running OVS 1.4.0  -- as this is the version
> installed by default when installing OVS with *apt-get install* on Ubuntu
> Server 12.04.1
> 
> Cheers,
> Brad
> 
> 
> On Mon, Nov 19, 2012 at 11:03 AM, Ben Pfaff <blp at nicira.com> wrote:
> 
> > I don't understand why this makes a difference, because
> > /etc/init.d/openvswitch-switch should already rmmod the bridge module,
> > unless bridges have already been created.
> >
> > Do either of you see the message "not removing bridge module because
> > bridges exist" on failed start?  That's the only reason why the
> > initscript should not rmmod bridge.
> >
> > What version of OVS are each of you using?
> >
> > On Mon, Nov 19, 2012 at 10:21:36AM -0600, Brad Hedlund wrote:
> > > I had a similar problem.  OVS loads perfectly along with brcompat after a
> > > fresh install on Ubuntu 12.04.  But when the machine reboots your bridge
> > > kernel module is back and causes conflict when OVS tries to start/load.
> > >  This is because bridge-utils is still installed on the machine as
> > Ubunutu
> > > views it as a dependency for KVM.  I tried 'rmmod bridge' as suggested
> > > below, and that allows me to then manually load OVS with no problem.  But
> > > that's not a permanent fix -- reloading the machine again brings us back
> > to
> > > square one.  So here is what I did...
> > >
> > > This may not be the perfect solution but here is what seems to have
> > worked
> > > for me.
> > > Edit */etc/init.d/openvswitch-switch*
> > > Prepend the file with this line: *rmmod bridge*
> > > *
> > > *
> > > Your OVS install will persist happily across reboots.
> > >
> > > The only less than perfect thing I have observed so far from doing this
> > is
> > > that when you run *service openvswitch-switch status* -- you will see an
> > > error message:  *ERROR: Module bridge does not exist in /proc/modules*
> > >
> > > I think that's just because the *rmmod bridge* statement you added in
> > > /etc/init.d/openvswitch-switch runs again.  So that "ERROR" message
> > > is innocuous and can be ignored.
> > >
> > > But perhaps there is a better way than this band-aid...
> > >
> > > Cheers,
> > > Brad
> > >
> > > On Sun, Nov 18, 2012 at 11:57 AM, Ben Pfaff <blp at nicira.com> wrote:
> > >
> > > > On Sun, Nov 18, 2012 at 10:55:52PM +0700, hasan mustafa wrote:
> > > > > i'm succesfully install Open vSwitch on Ubuntu 12.04. however i get
> > some
> > > > > problem, when i reboot my machine, and i try to start open vswitch
> > > > service,
> > > > > i get some error
> > > > >
> > > > >  /etc/init.d/openvswitch-switch start
> > > > > FATAL: Error inserting brcompat_mod
> > > > > (/lib/modules/3.2.0-33-generic-pae/kernel/brcompat_mod.ko): Invalid
> > > > module
> > > > > format
> > > > >  * Inserting brcompat module
> > > > > Module has probably not been built for this kernel.
> > > > > For instructions, read
> > > > > /usr/share/doc/openvswitch-datapath-source/README.Debian
> > > > > FATAL: Error inserting brcompat_mod
> > > > > (/lib/modules/3.2.0-33-generic-pae/kernel/brcompat_mod.ko): Invalid
> > > > module
> > > > > format
> > > > >  * Inserting brcompat module
> > > >
> > > > Here's the advice from INSTALL:
> > > >
> > > > 6. If you built kernel modules, you may load them with "insmod", e.g.:
> > > >
> > > >       % insmod datapath/linux/openvswitch.ko
> > > >
> > > >    You may need to specify a full path to insmod, e.g. /sbin/insmod.
> > > >    To verify that the modules have been loaded, run "/sbin/lsmod" and
> > > >    check that openvswitch is listed.
> > > >
> > > >    If the "insmod" operation fails, look at the last few kernel log
> > > >    messages (e.g. with "dmesg | tail"):
> > > >
> > > >       - The message "openvswitch: exports duplicate symbol
> > > >         br_should_route_hook (owned by bridge)" means that the bridge
> > > >         module is loaded.  Run "/sbin/rmmod bridge" to remove it.
> > > >
> > > >         If "/sbin/rmmod bridge" fails with "ERROR: Module bridge does
> > > >         not exist in /proc/modules", then the bridge is compiled into
> > > >         the kernel, rather than as a module.  Open vSwitch does not
> > > >         support this configuration (see "Build Requirements", above).
> > > >
> > > >       - The message "openvswitch: exports duplicate symbol
> > > >         dp_ioctl_hook (owned by ofdatapath)" means that the ofdatapath
> > > >         module from the OpenFlow reference implementation is loaded.
> > > >         Run "/sbin/rmmod ofdatapath" to remove it.  (You might have to
> > > >         delete any existing datapaths beforehand, using the "dpctl"
> > > >         program included with the OpenFlow reference implementation.
> > > >         "ovs-dpctl" will not work.)
> > > >
> > > >       - Otherwise, the most likely problem is that Open vSwitch was
> > > >         built for a kernel different from the one into which you are
> > > >         trying to load it.  Run "modinfo" on openvswitch.ko and on
> > > >         a module built for the running kernel, e.g.:
> > > >
> > > >            % /sbin/modinfo openvswitch.ko
> > > >            % /sbin/modinfo /lib/modules/`uname
> > > > -r`/kernel/net/bridge/bridge.ko
> > > >
> > > >         Compare the "vermagic" lines output by the two commands.  If
> > > >         they differ, then Open vSwitch was built for the wrong kernel.
> > > >
> > > >       - If you decide to report a bug or ask a question related to
> > > >         module loading, please include the output from the "dmesg" and
> > > >         "modinfo" commands mentioned above.
> > > > _______________________________________________
> > > > discuss mailing list
> > > > discuss at openvswitch.org
> > > > http://openvswitch.org/mailman/listinfo/discuss
> > > >
> >