A gentle ping. Ben, is it possible to have a look at this patch set - https://patchwork.ozlabs.org/project/openvswitch/list/?series=12481.
Thanks Numan On Wed, Nov 8, 2017 at 2:30 PM, Numan Siddique <nusid...@redhat.com> wrote: > > > On Wed, Nov 8, 2017 at 9:36 AM, Numan Siddique <nusid...@redhat.com> > wrote: > >> >> >> On Wed, Nov 8, 2017 at 9:25 AM, Ben Pfaff <b...@ovn.org> wrote: >> >>> On Wed, Nov 08, 2017 at 08:57:38AM +0530, Numan Siddique wrote: >>> > On Wed, Nov 8, 2017 at 8:36 AM, Ben Pfaff <b...@ovn.org> wrote: >>> > >>> > > On Tue, Nov 07, 2017 at 09:01:06PM +0530, nusid...@redhat.com wrote: >>> > > > From: Numan Siddique <nusid...@redhat.com> >>> > > > >>> > > > In the RHEL environment, when OVN db servers are started using >>> ovn-ctl, >>> > > > log files are empty. Adding "-vfile:info" option to ovsdb-server is >>> > > > resolving this issue. Running 'ovs-apptctl -t .. vlog/reopen" >>> results in >>> > > the >>> > > > logs appearing in the log files. This issue is seen with 2.7.2. >>> > > > >>> > > > "-vfile:info" option is passed to ovn-northd and ovn-controller >>> when >>> > > starting. >>> > > > There is no harm in adding this to OVN db servers. >>> > > > >>> > > > Signed-off-by: Numan Siddique <nusid...@redhat.com> >>> > > >>> > > This should be harmless, since "info" is the default log level, but I >>> > > don't understand why it makes a difference. Is there an underlying >>> bug >>> > > that should be fixed? (Is the --log-file option being passed in? >>> That >>> > > is the documented way to enable logging to a file.) >>> > > >>> > >>> > Yes. --log-file option is passed. I only see this issue with RHEL and >>> not >>> > with centos. >>> > And if I restart the DB servers later, the log file gets generated >>> > properly. It is seen >>> > only for the first time durng tripleo deployment in RHEL environment. I >>> > couldn't figure out the underlying >>> > cause. Since "vlog:info" is passed for ovn-northd and ovn-controller, I >>> > thought of taking this approach. >>> > But I agree there seems to be underlying issue and this patch might >>> hide >>> > it. >>> >>> Have you spent a little time trying to track down the root cause? If >>> you have already done that, and still did not figure it out, then I'm >>> happy to apply this patch. Let me know. >>> >> >> Thanks Ben. I did try. I am trying again with a fresh deployment to see >> if I can find anything. >> I will come back to you with the results. >> >> > Hi Ben, > > I couldn't find the root cause. I submitted v2 of the patch series. > > Thanks > Numan > > >> Thanks >> Numan >> >> >> > _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev