[ovs-discuss] [ovn] vswitchd seg fault

Murali R muralirdev at gmail.com
Tue Oct 20 22:06:18 UTC 2015


Thanks Joe. Looks like it was ulimit -c. These are VMs I spin up in the
cloud, so was not set. Will add this to the list of things to set in future
on a new vm.

root at mmnc-1:/usr/local/sbin# ulimit -c
0



On Tue, Oct 20, 2015 at 1:11 PM, Joe Stringer <joestringer at nicira.com>
wrote:

> On 17 October 2015 at 12:46, Murali R <muralirdev at gmail.com> wrote:
> > On Fri, Oct 16, 2015 at 7:45 PM, Ben Pfaff <blp at nicira.com> wrote:
> >>
> >> On Fri, Oct 16, 2015 at 06:51:41PM -0700, Murali R wrote:
> >> > This is a neutron/ovn setup. I was just doing regular query
> >> > commands following some forced set command. And now it is not
> >> > restarting.
> >> > What did I do wrong?
> >>
> >> To debug this, we need either a backtrace or instructions for
> >> reproduction.
> >
> > I don't see it generated a core file. Should I look anywhere else?
> Looked in
> > most obvious places
> > /usr/local/sbin/ovs-vswitchd
> > /usr/local/var/run/openvswitch
> > /opt/stack/ovs/vswitchd/
>
> For what it's worth, you may need to set the core file size in 'ulimit
> -c' to nonzero in the shell that you run OVN/OVS (I use 'unlimited').
> Another potential path is /var/crash/.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20151020/d6c0abfb/attachment-0002.html>


More information about the discuss mailing list