Thank you, I will try it next week (since today is Friday) and update this
thread if it has fixed my issues. We are indeed using the latest RDO Pike, so
ovsdbapp 0.4.3.1 .
Jean-Philippe Méthot
Openstack system administrator
Administrateur système Openstack
PlanetHoster inc.
> Le 28 sept.
Hi,
What version of Neutron and ovsdbapp You are using? IIRC there was such issue
somewhere around Pike version, we saw it in functional tests quite often. But
later with new ovsdbapp version I think that this problem was somehow solved.
Maybe try newer version of ovsdbapp and check if it will
I got some answers from the openvswitch mailing list, essentially indicating
the issue is in the connection between neutron-openvswitch-agent and ovs.
Here’s an output of ovs-vsctl list controller:
_uuid : ff2dca74-9628-43c8-b89c-8d2f1242dd3f
connection_mode : out-of-band
Yes, I notice that every time that message appears, at least a few packets get
dropped and some of our instances pop up in nagios, even though they are
reachable 1 or 2 seconds after. It’s really causing us some issues as we can’t
ensure proper network quality for our customers. Have you
Jean-Philippe Méthot writes:
> This particular message makes it sound as if openvswitch is getting
> overloaded.
> Sep 23 03:54:08 network1 ovsdb-server:
> ovs|01253|reconnect|ERR|tcp:127.0.0.1:50814: no response to inactivity probe
> after 5.01 seconds, disconnecting
We get these as well :-(
This particular message makes it sound as if openvswitch is getting overloaded.
Sep 23 03:54:08 network1 ovsdb-server:
ovs|01253|reconnect|ERR|tcp:127.0.0.1:50814: no response to inactivity probe
after 5.01 seconds, disconnecting
A lot of those keep appear, and openvswitch always reconnects
Ate you getting any particular log messages that lead you to conclude your
issue lies with OVS? I've hit lots of kernel limits under those conditions
before OVS itself ever noticed. Anything in dmesg, journal or neutron logs
of interest?
On Tue, Sep 25, 2018, 7:27 PM Jean-Philippe Méthot <
Hi,
Are there some recommendations regarding kernel settings configuration for
openvswitch? We’ve just been hit by what we believe may be an attack of some
kind we have never seen before and we’re wondering if there’s a way to optimize
our network nodes kernel for openvswitch operation and
