Hello,
I check my openvswitch log :
2019-02-04T22:28:19.137Z|1|vlog|INFO|opened log file
/var/log/openvswitch/ovvsdb-server.log
2019-02-04T22:28:19.160Z|2|ovsdb_server|INFO|ovsdb-server (Open vSwitch)
2.99.2
2019-02-04T22:28:19.358Z|3|jsonrpc|WARN|unix#2: receive error: Connection
I have worked past this issue for now. I think the most common reason
that ovs-vsctl hangs is because ovs-vswitchd is not actually running.
The systemd mechanism (service openvswitch-swith start|stop|status) can
get confused by openvswitch because it is likely that ovsdb-server is
running even if
Has this ever been resolved? I am having a similar problem where I
followed the instructions and ended up in a condition where ovs-vsctl
hangs on every command.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for openvswitch (Ubuntu) because there has been no activity for
60 days.]
** Changed in: openvswitch (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
One more thing, I noticed two times. When I restart the machine, it crashes
completely.
Error in the screen in the last part:
[FAILED ]Failed to start Getty on tty1
See 'systemctl status getty@tty1.service' for details.
Thanks
Best regards
Sothy
--
You received this bug
Hello,
I did the following to configuraton. I am using three VMXNET3
interfaces. Two are binded to DPDK.
echo "NR_2M_PAGES=4096" >> /etc/dpdk/dpdk.conf
"DPDK_OPTS='--dpdk -c 0x3 -n 4 -m 1024' in /etc/default/openvswitch-
switch.
After that I am running to create ovs bridge. It worked. Then I
Also setting to openvswitch as so far the issue is not dpdk specific
(although it likely is the vswitch crashing on initialzation due to dpdk
errors, but we will have to see that first)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
"ovs-vsctl show" can display only the DB config entries - so that show works is
no guarantee that it is actually running. In case it is not running the
described behavior occurs.
If you just want to go on configuring (without actually starting the
vswitch) you can add --no-wait to the
If the logs aren't helping you right away please share them and I'll try to
have a look.
If it works I'd also be happy to get a short update.
Setting to incomplete for now until further Detail is provided.
** Changed in: openvswitch (Ubuntu)
Status: New => Incomplete
--
You received
