It looks like ndb is listening (netstat shows this), but not receiving anything (log is empty). This looks like a connectivity issue. Can the provider host ping the ovn host? Is firewalld/iptables disabled on both hosts? Let's make sure that OVN is working fine. I attach a short python script that checks the connection from the localhost. Please check if it can connect to ovn from localhost (just execute this on the host with ovn: "python tcp_connection_test.py" ). It should connect and print out all the OVN networks. Does this work? On Mon, Apr 24, 2017 at 11:23 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com
wrote:
On Mon, Apr 24, 2017 at 10:03 PM, Marcin Mirecki <mmirecki@redhat.com> wrote:
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?
Actually yes... it seems that the switch "-t" with the "-p" doesn't catch the 6641 and 6642 "LISTEN" lines, while if I use "-a" instead of "-t" I get them too...
with "-a" root@ovmgr1 ~]# netstat -apn | grep 664 tcp 0 0 0.0.0.0:6641 0.0.0.0:* LISTEN 6691/ovsdb-server tcp 0 0 0.0.0.0:6642 0.0.0.0:* LISTEN 6699/ovsdb-server 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 10.4.192.43:6642 10.4.168.74:59176 ESTABLISHED 6699/ovsdb-server unix 3 [ ] STREAM CONNECTED 14119 664/vmtoolsd
with "-t" [root@ovmgr1 ~]# netstat -tpn | grep 664 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 10.4.192.43:6642 10.4.168.74:59176 ESTABLISHED 6699/ovsdb-server
-- MARCIN mIRECKI Red Hat <https://www.redhat.com> <https://red.ht/sig>