Hi , I'm having a pretty bad issue with OVN controller on the hypervisors being unable to connect to the OVS SB DB ,
2023-05-01T19:13:33.969Z|00541|reconnect|ERR|tcp:10.193.1.2:6642: no response to inactivity probe after 5 seconds, disconnecting 2023-05-01T19:13:33.969Z|00542|reconnect|INFO|tcp:10.193.1.2:6642: connection dropped 2023-05-01T19:13:43.043Z|00543|reconnect|INFO|tcp:10.193.1.2:6642: connected 2023-05-01T19:13:56.115Z|00544|reconnect|ERR|tcp:10.193.1.2:6642: no response to inactivity probe after 5 seconds, disconnecting 2023-05-01T19:13:56.115Z|00545|reconnect|INFO|tcp:10.193.1.2:6642: connection dropped 2023-05-01T19:14:36.177Z|00546|reconnect|INFO|tcp:10.193.1.2:6642: connected 2023-05-01T19:14:44.996Z|00547|jsonrpc|WARN|tcp:10.193.1.2:6642: receive error: Connection reset by peer 2023-05-01T19:14:44.996Z|00548|reconnect|WARN|tcp:10.193.1.2:6642: connection dropped (Connection reset by peer) 2023-05-01T19:15:44.131Z|00549|reconnect|INFO|tcp:10.193.1.2:6642: connected 2023-05-01T19:15:54.137Z|00550|reconnect|ERR|tcp:10.193.1.2:6642: no response to inactivity probe after 5 seconds, disconnecting 2023-05-01T19:15:54.137Z|00551|reconnect|INFO|tcp:10.193.1.2:6642: connection dropped 2023-05-01T19:16:02.184Z|00552|reconnect|INFO|tcp:10.193.1.2:6642: connected 2023-05-01T19:16:14.488Z|00553|reconnect|ERR|tcp:10.193.1.2:6642: no response to inactivity probe after 5 seconds, disconnecting 2023-05-01T19:16:14.488Z|00554|reconnect|INFO|tcp:10.193.1.2:6642: connection dropped This happened after pushing a configuration to north db for around 250 logical switch ports. Once I turn on the VM's everything goes bad very quickly, 2023-05-01T04:27:09.294Z|01947|poll_loop|INFO|wakeup due to [POLLOUT] on fd 66 (10.193.200.6:6642<->10.193.0.102:48794) at ../lib/stream-fd.c:153 (100% CPU usage) Can anyone provide any guidance how to run down an issue like this ?
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
