I used GDB to get more information about the connection reset and
seems after dispatch(), it closes connection. Am I missing some steps
in invoking nox_core? ./nox_core -v -i ptcp:6633
Here is the output from GDB, I am running new NOX on ubuntu 12.04LTS.
Your help is appreciated!
=========================================
Breakpoint 2,
vigil::Stream_connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp,
boost::asio::stream_socket_service<boost::asio::ip::tcp> >
>::~Stream_connection (this=0x7ffff0000bf0, __in_chrg=<optimized out>)
at ../../../src/lib/connection.cc:117
117 VLOG_DBG(lg, "flushed (tx: %zu, rx: %zu)", tx_bytes, rx_bytes);
(gdb) bt
#0
vigil::Stream_connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp,
boost::asio::stream_socket_service<boost::asio::ip::tcp> >
>::~Stream_connection (this=0x7ffff0000bf0, __in_chrg=<optimized out>)
at ../../../src/lib/connection.cc:117
#1 0x00007ffff7b96361 in
vigil::Stream_connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp,
boost::asio::stream_socket_service<boost::asio::ip::tcp> >
>::~Stream_connection (this=0x7ffff0000bf0, __in_chrg=<optimized out>)
at ../../../src/lib/connection.cc:118
#2 0x000000000047d401 in release (this=0x7ffff00009f0)
at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:145
#3 boost::detail::shared_count::~shared_count (this=<optimized out>,
__in_chrg=<optimized out>)
#4 0x00000000004a2dd4 in ~shared_ptr (this=0x7ffff4f8fa50,
__in_chrg=<optimized out>)
at /usr/include/boost/smart_ptr/shared_ptr.hpp:168
#5
vigil::Connection_manager::handle_connect<boost::asio::basic_stream_socket<boost::asio::ip::tcp,
boost::asio::stream_socket_service<boost::asio::ip::tcp> >
>(boost::shared_ptr<boost::asio::basic_stream_socket<boost::asio::ip::tcp,
boost::asio::stream_socket_service<boost::asio::ip::tcp> > >,
boost::function<void ()>, boost::system::error_code const&)
(this=0x731b40, socket=..., cb=...,
ec=...) at ../../src/builtin/connection-manager.cc:227
#6 0x00000000004a96cf in operator() (a3=...,
a2=<error reading variable: access outside bounds of object
referenced via synthetic pointer>,
---Type <return> to continue, or q <return> to quit---
a1=<error reading variable: access outside bounds of object
referenced via synthetic pointer>, p=0x731b40, this=0x7ffff4f8fc10)
at /usr/include/boost/bind/mem_fn_template.hpp:393
#7 boost::_bi::list4<boost::_bi::value<vigil::Connection_manager*>,
boost::_bi::value<boost::shared_ptr<boost::asio::basic_stream_socket<boost::asio::ip::tcp,
boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >,
boost::_bi::value<boost::function<void ()> >, boost::arg<1>
>::operator()<boost::_mfi::mf3<void, vigil::Connection_manager,
boost::shared_ptr<boost::asio::basic_stream_socket<boost::asio::ip::tcp,
boost::asio::stream_socket_service<boost::asio::ip::tcp> > >,
boost::function<void ()>, boost::system::error_code const&>,
boost::_bi::list1<boost::system::error_code const&>
>(boost::_bi::type<void>, boost::_mfi::mf3<void,
vigil::Connection_manager,
boost::shared_ptr<boost::asio::basic_stream_socket<boost::asio::ip::tcp,
boost::asio::stream_socket_service<boost::asio::ip::tcp> > >,
boost::function<void ()>, boost::system::error_code const&>&,
boost::_bi::list1<boost::system::error_code const&>&, int)
(this=<optimized out>, f=...,
a=...) at /usr/include/boost/bind/bind.hpp:457
#8 0x00000000004a98ed in operator()<boost::system::error_code> (a1=...,
this=0x7ffff4f8fc10) at /usr/include/boost/bind/bind_template.hpp:47
#9 operator() (this=0x7ffff4f8fc10)
at /usr/include/boost/asio/detail/bind_handler.hpp:40
#10 asio_handler_invoke<boost::asio::detail::binder1<boost::_bi::bind_t<void,
boost::_mfi::mf3<void, vigil::Connection_manager,
boost::shared_ptr<boost::asio::basic_stream_socket<boost::asio::ip::tcp>
>, boost::function<void()>, const boost::system::error_code&>,
boost::_bi::list4<boost::_bi::value<vigil::Connection_manager*>,
boost::_bi::value<boost::shared_ptr<boost::asio::basic_stream_socket<bo---Type
<return> to continue, or q <return> to quit---
ost::asio::ip::tcp> > >, boost::_bi::value<boost::function<void()> >,
boost::arg<1> > >, boost::system::error_code> > (
function=<error reading variable: access outside bounds of object
referenced via synthetic pointer>) at
/usr/include/boost/asio/handler_invoke_hook.hpp:64
#11 invoke<boost::asio::detail::binder1<boost::_bi::bind_t<void,
boost::_mfi::mf3<void, vigil::Connection_manager,
boost::shared_ptr<boost::asio::basic_stream_socket<boost::asio::ip::tcp>
>, boost::function<void()>, const boost::system::error_code&>,
boost::_bi::list4<boost::_bi::value<vigil::Connection_manager*>,
boost::_bi::value<boost::shared_ptr<boost::asio::basic_stream_socket<boost::asio::ip::tcp>
> >, boost::_bi::value<boost::function<void()> >, boost::arg<1> > >,
boost::system::error_code>, boost::_bi::bind_t<void,
boost::_mfi::mf3<void, vigil::Connection_manager,
boost::shared_ptr<boost::asio::basic_stream_socket<boost::asio::ip::tcp>
>, boost::function<void()>, const boost::system::error_code&>,
boost::_bi::list4<boost::_bi::value<vigil::Connection_manager*>,
boost::_bi::value<boost::shared_ptr<boost::asio::basic_stream_socket<boost::asio::ip::tcp>
> >, boost::_bi::value<boost::function<void()> >, boost::arg<1> > > >
(function=...,
context=...)
at /usr/include/boost/asio/detail/handler_invoke_helpers.hpp:39
#12
boost::asio::detail::reactive_socket_accept_op<boost::asio::basic_socket<boost::asio::ip::tcp,
boost::asio::stream_socket_service<boost::asio::ip::tcp> >,
boost::asio::ip::tcp, boost::_bi::bind_t<void, boost::_mfi::mf3<void,
vigil::Connection_manager,
boost::shared_ptr<boost::asio::basic_stream_socket<boost::asio::ip::tcp,
boost::asio::stream_socket_service<boost::asio::ip::tcp> > >,
boost::function<void ()>, boost::system::error_code const&>,
boost::_bi::list4<boost::_bi::value<vigil::Connection_manager*>,
boost::_bi::value<boost::shared_ptr<boost::---Type <return> to
continue, or q <return> to quit---
#12
boost::asio::detail::reactive_socket_accept_op<boost::asio::basic_socket<boost::asio::ip::tcp,
boost::asio::stream_socket_service<boost::asio::ip::tcp> >,
boost::asio::ip::tcp, boost::_bi::bind_t<void, boost::_mfi::mf3<void,
vigil::Connection_manager,
boost::shared_ptr<boost::asio::basic_stream_socket<boost::asio::ip::tcp,
boost::asio::stream_socket_service<boost::asio::ip::tcp> > >,
boost::function<void ()>, boost::system::error_code const&>,
boost::_bi::list4<boost::_bi::value<vigil::Connection_manager*>,
boost::_bi::value<boost::shared_ptr<boost::---Type <return> to
continue, or q <return> to quit---
asio::basic_stream_socket<boost::asio::ip::tcp,
boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >,
boost::_bi::value<boost::function<void ()> >, boost::arg<1> > >
>::do_complete(boost::asio::detail::task_io_service*,
boost::asio::detail::task_io_service_operation*,
boost::system::error_code, unsigned long) (owner=0x72fc10,
base=<optimized out>)
at /usr/include/boost/asio/detail/reactive_socket_accept_op.hpp:119
#13 0x00000000004bcb13 in complete (owner=..., this=0x7ffff0001e30)
at /usr/include/boost/asio/detail/task_io_service_operation.hpp:35
#14 boost::asio::detail::task_io_service::do_one (this=0x72fc10, lock=...,
this_idle_thread=0x7ffff4f8fdd0)
at /usr/include/boost/asio/detail/impl/task_io_service.ipp:278
#15 0x00000000004bd340 in boost::asio::detail::task_io_service::run (
this=0x72fc10, ec=...)
at /usr/include/boost/asio/detail/impl/task_io_service.ipp:130
#16 0x00000000004bd459 in boost::asio::io_service::run (this=0x72f9c8)
at /usr/include/boost/asio/impl/io_service.ipp:57
#17 0x00007ffff7950ce9 in thread_proxy ()
from /usr/lib/libboost_thread.so.1.46.1
#18 0x00007ffff5f11e9a in start_thread ()
from /lib/x86_64-linux-gnu/libpthread.so.0
#19 0x00007ffff62194bd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#20 0x0000000000000000 in ?? ()
(gdb)
On Thu, Jul 5, 2012 at 9:47 AM, YIMIN CHEN <[email protected]> wrote:
> Hi Amin,
>
> Thank you for your reply!
>
> I do have both NOX classic and new NOX installed and OVS 1.4.2 works
> with NOX classic but not new NOX.
>
> Today I did a fresh install of both NOX classic (pulled using git
> clone git://noxrepo.org/nox) and new NOX(pulled using git clone
> http://www.github.com/noxrepo/nox), and tried again, same issue.
>
> So this is the output from OVS, and you can see it worked with NOX
> classic and not new NOX. I have NOX classic running on 172.16.1.99,
> and OVS and new NOX running on 172.16.1.34.
>
> ymchen@ymchen-lnx:~/openvswitch-1.4.2$ sudo ovs-vswitchd --pidfile
> <========== this is how I started OVS
> Jul 05
> 09:36:11|00001|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
> connecting...
> Jul 05
> 09:36:11|00002|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
> connected
> Jul 05 09:36:11|00003|bridge|INFO|created port eth0 on bridge br0
> Jul 05 09:36:11|00004|bridge|INFO|created port br0 on bridge br0
> Jul 05 09:36:11|00005|ofproto|INFO|using datapath ID 0000002320ec2323
> Jul 05 09:36:11|00006|ofproto|INFO|datapath ID changed to 00000021cc6f7831
> Jul 05 09:36:11|00007|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
> <============================ new NOX
> Jul 05 09:36:11|00008|rconn|WARN|br0<->tcp:127.0.0.1: connection
> failed (Connection refused)
> Jul 05 09:36:11|00009|rconn|INFO|br0<->tcp:127.0.0.1: waiting 1
> seconds before reconnect
> Jul 05 09:36:12|00010|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
> Jul 05 09:36:12|00011|rconn|WARN|br0<->tcp:127.0.0.1: connection
> failed (Connection refused)
> Jul 05 09:36:12|00012|rconn|INFO|br0<->tcp:127.0.0.1: waiting 2
> seconds before reconnect
> Jul 05 09:36:14|00013|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
> Jul 05 09:36:14|00014|rconn|WARN|br0<->tcp:127.0.0.1: connection
> failed (Connection refused)
> Jul 05 09:36:14|00015|rconn|INFO|br0<->tcp:127.0.0.1: waiting 4
> seconds before reconnect
> Jul 05 09:36:18|00016|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
> Jul 05 09:36:18|00017|rconn|WARN|br0<->tcp:127.0.0.1: connection
> failed (Connection refused)
> Jul 05 09:36:18|00018|rconn|INFO|br0<->tcp:127.0.0.1: continuing to
> retry connections in the background but suppressing further logging
> Jul 05 09:36:26|00019|rconn|WARN|br0<->tcp:127.0.0.1: connection
> failed (Connection refused)
> Jul 05 09:36:26|00020|fail_open|WARN|Could not connect to controller
> (or switch failed controller's post-connection admission control
> policy) for 15 seconds, failing open
> Jul 05 09:36:28|00021|rconn|INFO|br0<->tcp:172.168.1.99: connecting...
> <==================== NOX classic
> Jul 05 09:36:29|00022|rconn|INFO|br0<->tcp:172.168.1.99: connection timed out
> Jul 05 09:36:29|00023|rconn|INFO|br0<->tcp:172.168.1.99: waiting 1
> seconds before reconnect
> Jul 05 09:36:30|00024|rconn|INFO|br0<->tcp:172.168.1.99: connecting...
> Jul 05 09:36:30|00025|rconn|INFO|br0<->tcp:172.168.1.99: connected
> Jul 05 09:36:30|00026|ofp_util|WARN|received Nicira extension message
> of unknown type 8
> Jul 05 09:36:30|00027|ofp_util|WARN|received Nicira extension message
> of unknown type 8
> Jul 05 09:36:30|00028|connmgr|INFO|br0<->tcp:172.168.1.99: sending
> type OFPET_BAD_REQUEST, code OFPBRC_BAD_SUBTYPE error reply to invalid
> message
> Jul 05 09:36:30|00029|fail_open|WARN|No longer in fail-open mode
> Jul 05 09:37:20|00030|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
> <=============================== new NOX again
> Jul 05 09:37:20|00031|rconn|INFO|br0<->tcp:127.0.0.1: connection
> failed (Connection reset by peer)
> Jul 05 09:37:21|00032|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
> Jul 05 09:37:21|00033|rconn|INFO|br0<->tcp:127.0.0.1: connection
> failed (Connection reset by peer)
> Jul 05 09:37:21|00034|rconn|INFO|br0<->tcp:127.0.0.1: waiting 2
> seconds before reconnect
> Jul 05 09:37:23|00035|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
> Jul 05 09:37:23|00036|rconn|INFO|br0<->tcp:127.0.0.1: connection
> failed (Connection reset by peer)
> Jul 05 09:37:23|00037|rconn|INFO|br0<->tcp:127.0.0.1: waiting 4
> seconds before reconnect
> Jul 05 09:37:27|00038|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
> Jul 05 09:37:27|00039|rconn|INFO|br0<->tcp:127.0.0.1: connection
> failed (Connection reset by peer)
> Jul 05 09:37:27|00040|rconn|INFO|br0<->tcp:127.0.0.1: continuing to
> retry connections in the background but suppressing further logging
> Jul 05 09:37:35|00041|fail_open|WARN|Could not connect to controller
> (or switch failed controller's post-connection admission control
> policy) for 15 seconds, failing open
> Jul 05 09:38:36|00042|fail_open|INFO|Still in fail-open mode after 76
> seconds disconnected from controller
>
>
>
> This is how I started new NOX. Could you please have a look to see if
> there is any step I made some mistake? new NOX does not seem to
> process message at all, just flushing and resetting connection.
>
>
> ymchen@ymchen-lnx:~/upgrade/nox/build/src$ ./nox_core -v -i ptcp:6633
> 00001|main|INFO:Starting nox_core
> (/home/ymchen/upgrade/nox/build/src/.libs/lt-nox_core)
> 00002|event-dispatcher|DBG:Registering event 'New_connection_event'.
> 00003|event-dispatcher|DBG:Registering event 'Shutdown_event'.
> 00004|event-dispatcher|DBG:Registering handler for Shutdown_event, order 9999
> 00005|event-dispatcher|DBG:creating thread 1
> 00006|dso-deployer|DBG:Component 'openflow-manager' scanned.
> 00007|dso-deployer|DBG:Component 'switch' scanned.
> 00008|connection_manager|DBG:listening on ptcp:0.0.0.0:6633:::
> <=========== Is this correct to listen on 0.0.0.0, meaning all
> interfaces?
> 00009|main|DBG:Application installation report:
> 00010|main|DBG:connection-manager:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00011|main|DBG:dso-deployer:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00012|main|DBG:event-dispatcher:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00013|main|INFO:nox bootstrap complete
> 00014|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:56146
> 00015|connection|DBG:flushed (tx: 0, rx: 0)
> 00016|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:56147
> 00017|connection|DBG:flushed (tx: 0, rx: 0)
> 00018|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:56148
> 00019|connection|DBG:flushed (tx: 0, rx: 0)
> 00020|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:56150
> 00021|connection|DBG:flushed (tx: 0, rx: 0)
> 00022|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:56151
> 00023|connection|DBG:flushed (tx: 0, rx: 0)
> 00024|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:56152
> 00025|connection|DBG:flushed (tx: 0, rx: 0)
> 00026|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:56155
> 00027|connection|DBG:flushed (tx: 0, rx: 0)
> 00028|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:56156
> 00029|connection|DBG:flushed (tx: 0, rx: 0)
> 00030|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:56157
> 00031|connection|DBG:flushed (tx: 0, rx: 0)
>
> Thanks!
> Yimin
>
>
> On Wed, Jul 4, 2012 at 12:17 AM, Amin Tootoonchian <[email protected]>
> wrote:
>> I personally have been using OVS for testing and it should be fine.
>> Here is what you could do:
>>
>> * Try OVS with another controller (e.g., POX or NOX Zaku) to see if it
>> works fine.
>>
>> * Make sure that you are running the latest NOX (run "git pull" and
>> recompile). In verbose mode, NOX should report the messages it
>> receives, but the output you sent shows no ofp_hello message received.
>>
>> Cheers,
>> Amin
>>
>> On Mon, Jul 2, 2012 at 9:31 PM, YIMIN CHEN <[email protected]> wrote:
>>> Sorry, NOX output from my previous email was for earlier connections
>>> from another OVS 1.4.2. Here is the matching NOX output. Now NOX and
>>> OVS are running on the same machine.
>>> =============
>>> new NOX
>>> =============
>>> 00024|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:51118
>>> 00025|connection|DBG:flushed (tx: 0, rx: 0)
>>> 00026|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:51119
>>> 00027|connection|DBG:flushed (tx: 0, rx: 0)
>>> 00028|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:51120
>>> 00029|connection|DBG:flushed (tx: 0, rx: 0)
>>> 00030|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:51121
>>> 00031|connection|DBG:flushed (tx: 0, rx: 0)
>>> 00032|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:51122
>>> 00033|connection|DBG:flushed (tx: 0, rx: 0)
>>> 00034|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:51123
>>> 00035|connection|DBG:flushed (tx: 0, rx: 0)
>>> 00036|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:51124
>>> 00037|connection|DBG:flushed (tx: 0, rx: 0)
>>> 00038|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:51125
>>> 00039|connection|DBG:flushed (tx: 0, rx: 0)
>>> 00040|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:51127
>>> 00041|connection|DBG:flushed (tx: 0, rx: 0)
>>> 00042|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:51128
>>> 00043|connection|DBG:flushed (tx: 0, rx: 0)
>>> 00044|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:51129
>>> 00045|connection|DBG:flushed (tx: 0, rx: 0)
>>>
>>>
>>> ===============
>>> OVS 1.4.2
>>> ===============
>>> ymchen@ymchen-lnx:~/openvswitch-1.4.2$ vi INSTALL.Linux
>>> ymchen@ymchen-lnx:~/openvswitch-1.4.2$ sudo ovs-vswitchd --pidfile
>>> [sudo] password for ymchen:
>>> Jul 03
>>> 09:25:17|00001|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
>>> connecting...
>>> Jul 03
>>> 09:25:17|00002|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
>>> connected
>>> Jul 03 09:25:17|00003|bridge|INFO|created port eth0 on bridge br0
>>> Jul 03 09:25:17|00004|bridge|INFO|created port br0 on bridge br0
>>> Jul 03 09:25:17|00005|ofproto|INFO|using datapath ID 0000002320d349df
>>> Jul 03 09:25:17|00006|ofproto|INFO|datapath ID changed to 00000021cc6f7831
>>> Jul 03 09:25:17|00007|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
>>> Jul 03 09:25:18|00008|rconn|INFO|br0<->tcp:127.0.0.1: connection
>>> failed (Connection reset by peer)
>>> Jul 03 09:25:18|00009|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
>>> Jul 03 09:25:18|00010|rconn|INFO|br0<->tcp:127.0.0.1: connection
>>> failed (Connection reset by peer)
>>> Jul 03 09:25:18|00011|rconn|INFO|br0<->tcp:127.0.0.1: waiting 2
>>> seconds before reconnect
>>> Jul 03 09:25:20|00012|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
>>> Jul 03 09:25:20|00013|rconn|INFO|br0<->tcp:127.0.0.1: connection
>>> failed (Connection reset by peer)
>>> Jul 03 09:25:20|00014|rconn|INFO|br0<->tcp:127.0.0.1: waiting 4
>>> seconds before reconnect
>>> Jul 03 09:25:24|00015|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
>>> Jul 03 09:25:24|00016|rconn|INFO|br0<->tcp:127.0.0.1: connection
>>> failed (Connection reset by peer)
>>> Jul 03 09:25:24|00017|rconn|INFO|br0<->tcp:127.0.0.1: continuing to
>>> retry connections in the background but suppressing further logging
>>>
>>>
>>>
>>> Thanks!
>>> Yimin
>>>
>>> On Tue, Jul 3, 2012 at 9:28 AM, YIMIN CHEN <[email protected]> wrote:
>>>> Hi Murphy,
>>>>
>>>> Here is the output from both:
>>>>
>>>> ===========
>>>> new NOX
>>>> ===========
>>>> ymchen@ymchen-lnx:~/noxrepo-nox-61d3f51/build/src$ ./nox_core -v -i
>>>> ptcp:6633
>>>> 00001|main|INFO:Starting nox_core
>>>> (/home/ymchen/noxrepo-nox-61d3f51/build/src/.libs/lt-nox_core)
>>>> 00002|event-dispatcher|DBG:Registering event 'New_connection_event'.
>>>> 00003|event-dispatcher|DBG:Registering event 'Shutdown_event'.
>>>> 00004|event-dispatcher|DBG:Registering handler for Shutdown_event, order
>>>> 9999
>>>> 00005|event-dispatcher|DBG:creating thread 1
>>>> 00006|dso-deployer|DBG:Component 'openflow-manager' scanned.
>>>> 00007|dso-deployer|DBG:Component 'switch' scanned.
>>>> 00008|connection_manager|DBG:listening on ptcp:0.0.0.0:6633:::
>>>> 00009|main|DBG:Application installation report:
>>>> 00010|main|DBG:connection-manager:
>>>> Current state: INSTALLED
>>>> Required state: INSTALLED
>>>> Dependencies:
>>>>
>>>> 00011|main|DBG:dso-deployer:
>>>> Current state: INSTALLED
>>>> Required state: INSTALLED
>>>> Dependencies:
>>>>
>>>> 00012|main|DBG:event-dispatcher:
>>>> Current state: INSTALLED
>>>> Required state: INSTALLED
>>>> Dependencies:
>>>>
>>>> 00013|main|INFO:nox bootstrap complete
>>>> 00014|connection_manager|WARN:connected: 172.16.1.4:6633<->172.16.1.2:37886
>>>> 00015|connection|DBG:flushed (tx: 0, rx: 0)
>>>> 00016|connection_manager|WARN:connected: 172.16.1.4:6633<->172.16.1.2:37887
>>>> 00017|connection|DBG:flushed (tx: 0, rx: 0)
>>>> 00018|connection_manager|WARN:connected: 172.16.1.4:6633<->172.16.1.2:37888
>>>> 00019|connection|DBG:flushed (tx: 0, rx: 0)
>>>>
>>>> ==================
>>>> openvswitch 1.4.2
>>>> ==================
>>>> ymchen@ymchen-lnx:~/openvswitch-1.4.2$ sudo ovs-vswitchd --pidfile
>>>> [sudo] password for ymchen:
>>>> Jul 03
>>>> 09:25:17|00001|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
>>>> connecting...
>>>> Jul 03
>>>> 09:25:17|00002|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
>>>> connected
>>>> Jul 03 09:25:17|00003|bridge|INFO|created port eth0 on bridge br0
>>>> Jul 03 09:25:17|00004|bridge|INFO|created port br0 on bridge br0
>>>> Jul 03 09:25:17|00005|ofproto|INFO|using datapath ID 0000002320d349df
>>>> Jul 03 09:25:17|00006|ofproto|INFO|datapath ID changed to 00000021cc6f7831
>>>> Jul 03 09:25:17|00007|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
>>>> Jul 03 09:25:18|00008|rconn|INFO|br0<->tcp:127.0.0.1: connection
>>>> failed (Connection reset by peer)
>>>> Jul 03 09:25:18|00009|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
>>>> Jul 03 09:25:18|00010|rconn|INFO|br0<->tcp:127.0.0.1: connection
>>>> failed (Connection reset by peer)
>>>> Jul 03 09:25:18|00011|rconn|INFO|br0<->tcp:127.0.0.1: waiting 2
>>>> seconds before reconnect
>>>> Jul 03 09:25:20|00012|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
>>>> Jul 03 09:25:20|00013|rconn|INFO|br0<->tcp:127.0.0.1: connection
>>>> failed (Connection reset by peer)
>>>> Jul 03 09:25:20|00014|rconn|INFO|br0<->tcp:127.0.0.1: waiting 4
>>>> seconds before reconnect
>>>> Jul 03 09:25:24|00015|rconn|INFO|br0<->tcp:127.0.0.1: connecting...
>>>> Jul 03 09:25:24|00016|rconn|INFO|br0<->tcp:127.0.0.1: connection
>>>> failed (Connection reset by peer)
>>>> Jul 03 09:25:24|00017|rconn|INFO|br0<->tcp:127.0.0.1: continuing to
>>>> retry connections in the background but suppressing further logging
>>>> Jul 03 09:25:32|00018|fail_open|WARN|Could not connect to controller
>>>> (or switch failed controller's post-connection admission control
>>>> policy) for 15 seconds, failing open
>>>>
>>>> Am I missing some steps?
>>>>
>>>> Thanks!
>>>> Yimin
>>>>
>>>> On Mon, Jul 2, 2012 at 4:19 PM, Murphy McCauley
>>>> <[email protected]> wrote:
>>>>> Can you post Open vSwitch's log from the same time period?
>>>>>
>>>>> -- Murphy
>>>>>
>>>>> On Jul 1, 2012, at 12:44 AM, YIMIN CHEN wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I installed NOX tarball from NOXrepo verify, and seeing the following
>>>>>> when openvswitch 1.4.2 tries to connect to NOX controller:
>>>>>>
>>>>>>
>>>>>> 00013|main|INFO:nox bootstrap complete
>>>>>> 00014|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:41689
>>>>>> 00015|connection|DBG:flushed (tx: 0, rx: 0)
>>>>>> 00016|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:41690
>>>>>> 00017|connection|DBG:flushed (tx: 0, rx: 0)
>>>>>> 00018|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:41691
>>>>>> 00019|connection|DBG:flushed (tx: 0, rx: 0)
>>>>>> 00020|connection_manager|WARN:connected: 127.0.0.1:6633<->127.0.0.1:41692
>>>>>> 00021|connection|DBG:flushed (tx: 0, rx: 0)
>>>>>>
>>>>>>
>>>>>> When I use this openvswitch version connect to NOX classic, it
>>>>>> connects fine. Has anyone successfully connect openvswitch to new NOX?
>>>>>>
>>>>>>
>>>>>> Thanks!
>>>>>> Yimin
>>>>>
