It's claiming you have more than one instance of ovs-vswitchd running. Make
sure you're only one instance and that your paths are all correct. ovs-ofctl
will look in the run path configured during build time for a unix domain socket
representing the bridge. Your ovs-ofctl man page will show you where it will
look for that socket. For example, from my local repo:
bridge This is short for unix://var/run/openvswitch/bridge.mgmt, as
long as bridge does not contain a colon.
--Justin
On Nov 30, 2013, at 3:27 PM, navaz <[email protected]> wrote:
> Looks like ERR when running this.
>
> root@ovs1:~# ovs-vswitchd
> 2013-11-30T23:22:36Z|00001|worker(worker)|INFO|worker process started
> 2013-11-30T23:22:36Z|00001|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
> connecting...
> 2013-11-30T23:22:36Z|00002|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
> connected
> 2013-11-30T23:22:36Z|00003|bridge|ERR|another ovs-vswitchd process is
> running, disabling this process until it goes away
> 2013-11-30T23:22:51Z|00004|memory|INFO|3428 kB peak resident set size after
> 14.2 seconds
> 2013-11-30T23:22:51Z|00005|memory|INFO|
> 2013-11-30T23:23:41Z|00006|bridge|ERR|Dropped 12 log messages in last 60
> seconds (most recently, 5 seconds ago) due to excessive rate
> 2013-11-30T23:23:41Z|00007|bridge|ERR|another ovs-vswitchd process is
> running, disabling this process until it goes away
>
>
>
> On Sat, Nov 30, 2013 at 5:18 PM, Justin Pettit <[email protected]> wrote:
> Is ovs-vswitchd running?
>
> --Justin
>
>
> On Nov 30, 2013, at 12:26 PM, navaz <[email protected]> wrote:
>
> > Thanks Ben and Nick.
> >
> > Now I have loaded disk image you have mentioned after selecting silver
> > type: emulab-xen.
> >
> > It is the output.
> > vm:~% sudo bash
> > root@vm:~# ovs-vsctl show
> > 378b2a4d-481e-4f4c-b97b-eb8b6c0ea5f1
> > ovs_version: "1.9.3"
> > root@vm:~#
> > root@vm:~# ovs-vsctl add-br br0
> > root@vm:~# ovs-ofctl show br0
> > ovs-ofctl: br0 is not a bridge or a socket
> > root@vm:~# ovs-vsctl show
> > 378b2a4d-481e-4f4c-b97b-eb8b6c0ea5f1
> > Bridge "br0"
> > Port "br0"
> > Interface "br0"
> > type: internal
> > ovs_version: "1.9.3"
> > root@vm:~#
> >
> > why I am getting the above error message?
> >
> > Thanks
> > Navaz
> >
> >
> >
> >
> >
> > On Fri, Nov 29, 2013 at 3:56 PM, Nicholas Bastin <[email protected]>
> > wrote:
> > On Thu, Nov 28, 2013 at 2:36 PM, navaz <[email protected]> wrote:
> > I am trying to install OVS on XENVM from intsageniracks. I followed the
> > steps mentioned here.
> >
> > http://groups.geni.net/geni/wiki/HowTo/InstallOVSInProtoGENI
> >
> > Those steps unfortunately don't work anymore (and the ubuntu repos no
> > longer have the kernel headers for 3.2.46, and you can't replace their
> > kernel due to the way their PV booting works). There is a disk image that
> > you can use that already has OVS built and installed:
> >
> > "url":
> > "https://www.utahddc.geniracks.net/image_metadata.php?uuid=468c846d-5395-11e3-880c-000000000000";,
> > "urn":
> > "urn:publicid:IDN+utahddc.geniracks.net+image+ch-geni-net:OVSUbuntu1204LTS"
> >
> > You should be able to reference this in your rspecs using:
> >
> > <sliver_type name="emulab-xen">
> > <disk_image
> > name="urn:publicid:IDN+utahddc.geniracks.net+image+ch-geni-net:OVSUbuntu1204LTS"/>
> > </sliver_type>
> >
> > You can use that at any rack - the AM will copy it from the source if it
> > doesn't already exist at that site.
> >
> > --
> > Nick
> >
> >
> >
> > --
> > Abdul Navaz
> > Masters in Network Communications
> > University of Houston
> > Houston, TX - 77204-4020
> > Ph - 281-685-0388
> > [email protected]
> >
> > _______________________________________________
> > discuss mailing list
> > [email protected]
> > http://openvswitch.org/mailman/listinfo/discuss
>
>
>
>
> --
> Abdul Navaz
> Masters in Network Communications
> University of Houston
> Houston, TX - 77204-4020
> Ph - 281-685-0388
> [email protected]
>
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
