Hi Ben, do we have any update on this issue ? ~Saurabh.
On 24/08/21, 11:21 AM, "Saurabh Deokate" <[email protected]> wrote: Hi Ben, can you please help us understand why are we seeing these retrying even after setting inactivity_probe to 0. Are we missing on some configuration ? ~Saurabh. On 18/08/21, 11:50 AM, "Saurabh Deokate" <[email protected]> wrote: Hi Ben, I tested with latest OVS 2.16, which has your fix, even after setting inactivity_probe to 0, we are still seeing ovs retrying after every 5 sec. Can you please help us with this ? Here are the details - root@ip-10-192-20-160:/home/ubuntu# ovs-vsctl --version ovs-vsctl (Open vSwitch) 2.16.0 DB Schema 8.3.0 root@ip-10-192-20-160:/home/ubuntu# ovs-vsctl list controller _uuid : e2947bdf-3695-42d0-a8fc-5efc7c1a7a01 connection_mode : [] controller_burst_limit: [] controller_queue_size: [] controller_rate_limit: [] enable_async_messages: [] external_ids : {} inactivity_probe : 0 is_connected : true local_gateway : [] local_ip : [] local_netmask : [] max_backoff : [] other_config : {} role : other status : {last_error="Connection timed out", sec_since_connect="7", sec_since_disconnect="9", state=IDLE} target : "tcp:127.0.0.1:10000" type : [] LOGS - /var/log//openvswitch/ovs-vswitchd.log 2021-08-18T06:06:06.874Z|00830|rconn|ERR|br0<->tcp:127.0.0.1:10000: no response to inactivity probe after 5 seconds, disconnecting 2021-08-18T06:06:07.884Z|00831|rconn|INFO|br0<->tcp:127.0.0.1:10000: connecting... 2021-08-18T06:06:07.889Z|00832|rconn|INFO|br0<->tcp:127.0.0.1:10000: connected 2021-08-18T06:06:17.890Z|00833|rconn|ERR|br0<->tcp:127.0.0.1:10000: no response to inactivity probe after 5 seconds, disconnecting 2021-08-18T06:06:18.903Z|00834|rconn|INFO|br0<->tcp:127.0.0.1:10000: connecting... 2021-08-18T06:06:19.404Z|00835|rconn|INFO|br0<->tcp:127.0.0.1:10000: connected 2021-08-18T06:06:20.405Z|00836|fail_open|INFO|Still in fail-open mode after 184 seconds disconnected from controller 2021-08-18T06:06:29.405Z|00837|rconn|ERR|br0<->tcp:127.0.0.1:10000: no response to inactivity probe after 5 seconds, disconnecting 2021-08-18T06:06:30.419Z|00838|rconn|INFO|br0<->tcp:127.0.0.1:10000: connecting... 2021-08-18T06:06:30.884Z|00839|rconn|INFO|br0<->tcp:127.0.0.1:10000: connected 2021-08-18T06:06:40.884Z|00840|rconn|ERR|br0<->tcp:127.0.0.1:10000: no response to inactivity probe after 5 seconds, disconnecting 2021-08-18T06:06:41.884Z|00841|rconn|INFO|br0<->tcp:127.0.0.1:10000: connecting... 2021-08-18T06:06:41.935Z|00842|rconn|INFO|br0<->tcp:127.0.0.1:10000: connected On 02/07/21, 11:40 PM, "Ben Pfaff" <[email protected]> wrote: I just pushed the fixes to the repo, so it'll be released as part of the next regular OVS release. Building from a patch isn't any different from building any other way. On Thu, Jul 01, 2021 at 06:19:08AM +0000, Saurabh Deokate wrote: > Hi Ben, > > I have two questions, > 1. When is this patch going to be released ? > 2. Do we have any documentation for building modules from patch? > > On 28/06/21, 10:25 PM, "Ben Pfaff" <[email protected]> wrote: > > I recommend trying the patches that I posted: > https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_pipermail_ovs-2Ddev_2021-2DJune_383783.html&d=DwIDaQ&c=s883GpUCOChKOHiocYtGcg&r=jK9phexdherJTNL6qWfkjyz7vNK2P5VYFIeRp9Vdy5s&m=0Y5dlQZ6-TXyNkmMDUiCUN6JaZJeIf_W69zr7CdJ_3A&s=7gXiz2Z8l7MPXHoqsyHwzyX4sozNLZM5RFJam3PSMRA&e= > https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_pipermail_ovs-2Ddev_2021-2DJune_383784.html&d=DwIDaQ&c=s883GpUCOChKOHiocYtGcg&r=jK9phexdherJTNL6qWfkjyz7vNK2P5VYFIeRp9Vdy5s&m=0Y5dlQZ6-TXyNkmMDUiCUN6JaZJeIf_W69zr7CdJ_3A&s=GZqZu8jql-ra0ik1wyfKSM4p6uNSvycyhJnMkTtIJTc&e= > > On Tue, Jun 15, 2021 at 07:24:06AM +0000, Saurabh Deokate wrote: > > Hi Ben, > > > > Here is the output for ovs-vsctl list controller > > > > [root@172-31-64-26-aws-eu-central-1c ~]# ovs-vsctl list controller > > _uuid : eb56176a-ad32-4eb0-9cd8-7ab3bd448a68 > > connection_mode : out-of-band > > controller_burst_limit: [] > > controller_queue_size: [] > > controller_rate_limit: [] > > enable_async_messages: [] > > external_ids : {} > > inactivity_probe : 0 > > is_connected : true > > local_gateway : [] > > local_ip : [] > > local_netmask : [] > > max_backoff : [] > > other_config : {} > > role : other > > status : {last_error="Connection refused", sec_since_connect="42606", sec_since_disconnect="42614", state=ACTIVE} > > target : "tcp:127.0.0.1:6653" > > type : [] > > > > Let me know if you need any other details. > > > > ~Saurabh. > > > > On 11/06/21, 4:03 AM, "Ben Pfaff" <[email protected]> wrote: > > > > On Mon, Jun 07, 2021 at 02:51:58PM +0000, Saurabh Deokate wrote: > > > Hi Team, > > > > > > We are seeing an issue in OVS 2.14.0 after moving from 2.8.0. We first set the controller on the bridge and then set inactivity probe for our controller to 0 to disable new connection attempts by ovs. After this we start our controller to serve request. But in the new version of OVS somehow we still see inactivity probe kicking in after every 5s and trying to reconnect. This issue is triggered when we are in the middle of handling a packet in our controller (i.e. OFController) which is blocked for almost 40s. > > > > > > > > > Kernel version: CentOS Linux release 7.9.2009 > > > Output of ovs-vsctl list controller command shows inactivity_probe: 0 > > > > > > Below is the snippet from ovs-vswitchd.log > > > > > > 021-05-11T22:32:55.378Z|00608|rconn|INFO|br0.uvms<->tcp:127.0.0.1:6653: connected > > > 2021-05-11T22:33:05.382Z|00609|connmgr|INFO|br0.uvms<->tcp:127.0.0.1:6653: 44 flow_mods 10 s ago (44 adds) > > > 2021-05-11T22:33:05.386Z|00610|rconn|ERR|br0.uvms<->tcp:127.0.0.1:6653: no response to inactivity probe after 5 seconds, disconnecting > > > 2021-05-11T22:33:06.406Z|00611|rconn|INFO|br0.uvms<->tcp:127.0.0.1:6653: connecting... > > > 2021-05-11T22:33:06.438Z|00612|rconn|INFO|br0.uvms<->tcp:127.0.0.1:6653: connected > > > 2021-05-11T22:33:16.438Z|00613|rconn|ERR|br0.uvms<->tcp:127.0.0.1:6653: no response to inactivity probe after 5 seconds, disconnecting > > > 2021-05-11T22:33:17.921Z|00614|rconn|INFO|br0.uvms<->tcp:127.0.0.1:6653: connecting... > > > 2021-05-11T22:33:18.108Z|00615|rconn|INFO|br0.uvms<->tcp:127.0.0.1:6653: connected > > > 2021-05-11T22:33:28.110Z|00616|rconn|ERR|br0.uvms<->tcp:127.0.0.1:6653: no response to inactivity probe after 5 seconds, disconnecting > > > 2021-05-11T22:33:29.433Z|00617|rconn|INFO|br0.uvms<->tcp:127.0.0.1:6653: connecting... > > > 2021-05-11T22:33:29.933Z|00618|rconn|INFO|br0.uvms<->tcp:127.0.0.1:6653: connected > > > > > > > > > Can you please help us find out what could be wrong with this configuration and what is the expected behaviour from ovs switch when the receiver on the controller is blocked for long. > > > > Hmm, I can't reproduce this with current OVS. I do see a problem with > > the fail-open implementation; I'll see a patch for that. > > > > Can you show the output of "ovs-vsctl list controller"? > > > _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
