[ovs-discuss] ovs goes down after making connection

[Ben Pfaff]

You should probably enable core dump and then get a backtrace.

On Sun, Jul 13, 2014 at 03:49:23AM +0530, thasleem palara wrote:
> Ben,
> 
> Here is the log. Also I didnt see any core dump .. After this daemon no
> more running
> 
> 1970-01-16T16:42:47.682Z|00204|rconn|INFO|br<->tcp:192.168.1.10:6633:
> connected
> 1970-01-16T16:42:47.686Z|00205|fail_open|WARN|No longer in fail-open mode
> 1970-01-16T16:42:47.687Z|00206|pktbuf|WARN|attempt to reuse buffer 00000000
> 1970-01-16T16:42:47.688Z|00207|connmgr|INFO|br<->tcp:192.168.1.10:6633:
> sending  OFPBRC_BUFFER_EMPTY error reply to OFPT_FLOW_MOD message
> 
> Thanks,
> Thas
> 
> 
> On Sun, Jul 13, 2014 at 1:37 AM, Ben Pfaff <blp at nicira.com> wrote:
> 
> > OK, what's in the log?  Is there a core dump?
> >
> > On Sat, Jul 12, 2014 at 12:15 AM, thasleem palara <thasleemp at gmail.com>
> > wrote:
> > > OVS daemon  is no more running ..
> > >
> > >
> > > On Fri, Jul 11, 2014 at 10:39 PM, Ben Pfaff <blp at nicira.com> wrote:
> > >>
> > >> On Fri, Jul 11, 2014 at 09:17:42PM +0530, thasleem palara wrote:
> > >> > After the connection established  to nox-controller OVS demon goes
> > down.
> > >> > Logs are given below.
> > >> > Version : openvswitch-2.1.2
> > >> >
> > >> >
> > >> > 1970-01-16T16:42:47.682Z|00204|rconn|INFO|br<->tcp:192.168.1.10:6633:
> > >> > connected
> > >> > 1970-01-16T16:42:47.686Z|00205|fail_open|WARN|No longer in fail-open
> > >> > mode
> > >> > 1970-01-16T16:42:47.687Z|00206|pktbuf|WARN|attempt to reuse buffer
> > >> > 00000000
> > >> > 1970-01-16T16:42:47.688Z|00207|connmgr|INFO|br<->tcp:
> > 192.168.1.10:6633:
> > >> > sending  OFPBRC_BUFFER_EMPTY error reply to OFPT_FLOW_MOD message
> > >>
> > >> When you say it goes down, what do you mean?
> > >
> > >
> >
> >
> >
> > --
> > "I don't normally do acked-by's.  I think it's my way of avoiding
> > getting blamed when it all blows up."               Andrew Morton
> >