Do this: Kill the daemons that you manually started.
Go to the directory where you did your 'make install' and do: ./configure make uninstall Now, do: ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc --enable-ssl make -j3 make install cp debian/openvswitch-switch.init /etc/init.d/openvswitch-switch /etc/init.d/openvswitch-switch start On 9 September 2016 at 08:07, Ashish Kurian <ashish...@gmail.com> wrote: > Dear Guru, > > After reboot, If I try to give command ovs-vsctl add-br br0, I get the > following error. > > ovs-vsctl: unix:/usr/local/var/run/openvswitch/db.sock: database > connection failed (No such file or directory). > > So what I do then is that I give the following commands(from install.md) > > sudo ovsdb-server --remote=punix:/usr/local/var/run/openvswitch/db.sock > --remote=db:Open_vSwitch,Open_vSwitch,manager_options > --private-key=db:Open_vSwitch,SSL,private_key > --certificate=db:Open_vSwitch,SSL,certificate > --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert > --pidfile --detach > sudo ovs-vsctl --no-wait init > sudo ovs-vswitchd --pidfile --detach > > Then I will be able to view result of ovs-vsctl add-br br0 but then I get > the error as mentioned previously when I try to add a bridge. > > I did not update the database schema and do not know how to do that. I am > doing everything manually. > > Please advice me on the procedure to do this properly. > > > Best Regards, > Ashish Kurian > > On Fri, Sep 9, 2016 at 4:58 PM, Guru Shetty <g...@ovn.org> wrote: > >> >> >> On 9 September 2016 at 07:48, Ashish Kurian <ashish...@gmail.com> wrote: >> >>> Dear Team, >>> >>> I installed the ovs successfully and tested the ovs-vsctl add-br br0 >>> command and it was successful. But after I reboot my machine and try the >>> command again, I get the error as in the subject. >>> >>> When I looked into the log this is my output. >>> >>> 2016-09-09T12:08:03.251Z|00001|vlog|INFO|opened log file >>> /var/log/openvswitch/ovs-vswitchd.log >>> 2016-09-09T12:08:03.258Z|00002|ovs_numa|INFO|Discovered 1 CPU cores on >>> NUMA node 0 >>> 2016-09-09T12:08:03.258Z|00003|ovs_numa|INFO|Discovered 1 NUMA nodes >>> and 1 CPU cores >>> 2016-09-09T12:08:03.258Z|00004|reconnect|INFO|unix:/var/run/openvswitch/db.sock: >>> connecting... >>> 2016-09-09T12:08:03.258Z|00005|reconnect|INFO|unix:/var/run/openvswitch/db.sock: >>> connected >>> 2016-09-09T12:08:03.260Z|00006|ovsdb_idl|WARN|Interface table in >>> Open_vSwitch database lacks mtu_request column (database needs upgrade?) >>> >> >> The above indicates to me that you likely did not upgrade the database >> schema? If you are using a startup script to start OVS, then it should have >> done this automatically for you. You likely are doing everything manually? >> >> >> >>> 2016-09-09T12:08:03.260Z|00007|ovsdb_idl|WARN|Mirror table in >>> Open_vSwitch database lacks snaplen column (database needs upgrade?) >>> 2016-09-09T12:08:03.260Z|00008|bridge|INFO|ovs-vswitchd (Open vSwitch) >>> 2.6.90 >>> 2016-09-09T12:08:16.790Z|00009|memory|INFO|8928 kB peak resident set >>> size after 13.5 seconds >>> 2016-09-09T12:46:31.613Z|00002|daemon_unix(monitor)|INFO|pid 1452 died, >>> killed (Terminated), exiting >>> >>> >>> Do you know what can be done to fix this error. >>> >>> Best Regards, >>> Ashish Kurian >>> >>> _______________________________________________ >>> discuss mailing list >>> discuss@openvswitch.org >>> http://openvswitch.org/mailman/listinfo/discuss >>> >>> >> >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
