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@mmnc-1:/usr/local/sbin# ulimit -c 0 On Tue, Oct 20, 2015 at 1:11 PM, Joe Stringer <[email protected]> wrote: > On 17 October 2015 at 12:46, Murali R <[email protected]> wrote: > > On Fri, Oct 16, 2015 at 7:45 PM, Ben Pfaff <[email protected]> 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/. >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
