Looks like the south db works properly. The north db uses the same mechanism, just a different schema and port. Looking at the netstat output it looks like ovn north db is not even listening, or is there anything for 6641? On Mon, Apr 24, 2017 at 10:37 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com
wrote:
On Sun, Apr 23, 2017 at 11:32 PM, Marcin Mirecki <mmirecki@redhat.com> wrote:
Hello Gianluca,
Can you please check the ovn north db log. This is placed in /var/log/openvswitch/ovsdb-server-nb.log Please check if the logs has any new entries when you try to connect and when you issue the 'ovn-nbctl set-connection ptcp:6641' command. If the connection attempt is getting through, pvs db should print an error to the log.
Please also try restarting the ovn-northd service.
Do the ovn-controllers connect to the south-db? You can verify this by looking at /var/log/openvswitch/ovn-controller.log on the ovn-controller host (please look for entries saying "... <north ip>:6642 connected")
Marcin
The ovirt nb log contains: 2017-04-24T07:46:51.541Z|00001|vlog|INFO|opened log file /var/log/openvswitch/ovsdb-server-nb.log 2017-04-24T07:46:51.550Z|00002|ovsdb_server|INFO|ovsdb-server (Open vSwitch) 2.7.0 2017-04-24T07:47:01.560Z|00003|memory|INFO|2268 kB peak resident set size after 10.0 seconds 2017-04-24T07:47:01.560Z|00004|memory|INFO|cells:100 json-caches:1 monitors:1 ses
In my ovn-controller.log of my 3 hosts I have this, when I run the 2 commands below on the provider host
ovn-sbctl set-connection ptcp:6642 ovn-nbctl set-connection ptcp:6641
2017-04-24T07:56:23.178Z|00247|reconnect|INFO|tcp:10.4.192.43:6642: connecting... 2017-04-24T07:56:23.178Z|00248|reconnect|INFO|tcp:10.4.192.43:6642: connection attempt failed (Connection refused) 2017-04-24T07:56:23.178Z|00249|reconnect|INFO|tcp:10.4.192.43:6642: waiting 8 seconds before reconnect 2017-04-24T07:56:31.187Z|00250|reconnect|INFO|tcp:10.4.192.43:6642: connecting... 2017-04-24T07:56:31.188Z|00251|reconnect|INFO|tcp:10.4.192.43:6642: connected 2017-04-24T07:56:31.193Z|00252|ofctrl|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting to switch 2017-04-24T07:56:31.193Z|00253|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting... 2017-04-24T07:56:31.201Z|00254|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connected 2017-04-24T07:56:31.201Z|00255|pinctrl|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting to switch 2017-04-24T07:56:31.201Z|00256|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting... 2017-04-24T07:56:31.201Z|00257|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connected 2017-04-24T07:56:31.202Z|00258|binding|INFO|Releasing lport 0a2a47bc-ea0d-4f1d-8f49-ec903e519983 from this chassis.
On my provider I see then the 3 oVirt hosts connected: [root@ovmgr1 openvswitch]# netstat -tpn|grep 66 tcp 0 0 10.4.192.43:6642 10.4.168.76:38882 ESTABLISHED 6699/ovsdb-server tcp 0 0 10.4.192.43:6642 10.4.168.75:45486 ESTABLISHED 6699/ovsdb-server tcp 0 0 127.0.0.1:5432 127.0.0.1:37074 ESTABLISHED 16696/postgres: eng tcp 0 0 10.4.192.43:6642 10.4.168.74:59176 ESTABLISHED 6699/ovsdb-server [root@ovmgr1 openvswitch]#
But it seems that the "set" command above is not persistent across reboot of the provider host.... that in my case is the oVirt engine server
-- MARCIN mIRECKI Red Hat <https://www.redhat.com> <https://red.ht/sig>