Thanks a lot Ben. The command seems to work. Where will I find the logs? Is there a way to dump the debug info onto the terminal for quick debugging?
Appreciate your help. Hopefully at some point, all the ovs cli commands will be uniform... :) vlog/set v/s vlog-set... similar to ovs-vsctl list-br and not ovs-vsctl list/br... :) On Mon, Dec 29, 2014 at 10:28 AM, Ben Pfaff <[email protected]> wrote: > On Fri, Dec 26, 2014 at 09:03:24PM -0800, Ashok Chippa wrote: > > After fixing the "ovs-vsctl set-controller..." command (with tcp: > > 127.0.0.1:6789 instead of just 127.0.0.1:6789), I can now get the > > openvswitch connecting to my controller... > > > > However, it seems (but I could be wrong) that the switch seems to be > > repeatedly connecting with the controller: > > ashok-vb$ python dispatcher.py > > _dispatcher_init() > > listening on socket: 127:0.0.1:6789 > > Connected with 127.0.0.1:39548 > > Connected with 127.0.0.1:39549 > > Connected with 127.0.0.1:39550 > > Connected with 127.0.0.1:39551 > > Connected with 127.0.0.1:39552 > > Connected with 127.0.0.1:39553 > > Connected with 127.0.0.1:39554 > > Connected with 127.0.0.1:39555 > > Connected with 127.0.0.1:39556 > > Connected with 127.0.0.1:39557 > > Connected with 127.0.0.1:39558 > > Connected with 127.0.0.1:39559 > > Connected with 127.0.0.1:39560 > > Connected with 127.0.0.1:39561 > > ... > > > > Any clues from openvswitch + socket experts out there as to why this may > be > > happening? Appreciate it. > > I'd look in the ovs-vswitchd log. If ovs-vswitchd is disconnecting, > it should tell you why. You might get more information if you turn up > appropriate logging levels: "ovs-appctl vlog/set vconn rconn" >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
