This is what I have: “ovs-vswitchd –pidfile –log-file” And, I changed vlog/set as well.
Thanks, Monica From: Guru Shetty [mailto:g...@ovn.org] Sent: Monday, March 21, 2016 12:13 PM To: Rajasekaran, Monica <monica.rajaseka...@us.fujitsu.com> Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] Debugging through OVS On 20 March 2016 at 18:24, Rajasekaran, Monica <monica.rajaseka...@us.fujitsu.com<mailto:monica.rajaseka...@us.fujitsu.com>> wrote: Hi Guru, Thanks for your input. It is specified that “—log-file” is used when “Regardless of the log levels set for file, logging to a FILE will not take place unless ovs-vswitchd was invoked with the --log-file option”. But, I am only trying to log to the console and not to a file. “—detach” seems to be an option which (as a side effect) disables logging to the console. I still do not understand why my ovs does not log to the console though I have enabled DBG level logging for all modules. Please let me know if I am missing something here. Paste your ovs-vswitchd arguments. Does it have -vconsole set? Thanks, Monica From: Guru Shetty [mailto:g...@ovn.org<mailto:g...@ovn.org>] Sent: Friday, March 18, 2016 5:03 PM To: Rajasekaran, Monica <monica.rajaseka...@us.fujitsu.com<mailto:monica.rajaseka...@us.fujitsu.com>> Cc: discuss@openvswitch.org<mailto:discuss@openvswitch.org> Subject: Re: [ovs-discuss] Debugging through OVS Please read about the following options in 'man ovs-vswitchd' 1. --log-file 2. "Logging Options" 3. --detach And then follow it by the section on "LOGGING COMMANDS" in 'man ovs-appctl' On 18 March 2016 at 14:54, Rajasekaran, Monica <monica.rajaseka...@us.fujitsu.com<mailto:monica.rajaseka...@us.fujitsu.com>> wrote: Hi guys, While trying to understand parts of the code, I would like to print stuff to the terminal so that I know how the flow works. But I tried printf, even vlog/set to DBG. Nothing gets printed though my OVS is working perfectly! Am I missing something ? *Side Note: I even tried with a print inside vport-internal_dev.c --> internal_dev_xmit(). That’s not the first function to be called when a packet enters ovs but it is pretty initial. That’s the one that calls ovs_vport_receive(). Any help is greatly appreciated! Thanks. _______________________________________________ discuss mailing list discuss@openvswitch.org<mailto:discuss@openvswitch.org> http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
