On Mon, Oct 30, 2017 at 2:49 PM, Michael Vorburger <[email protected]> wrote:
> Hi Sam, > > On Mon, Oct 30, 2017 at 7:45 PM, Sam Hague <[email protected]> wrote: > >> Stephen, Michael, Tom, >> >> do you have any ways to collect debugs when ODL crashes in CSIT? >> > > JVMs (almost) never "just crash" without a word... either some code > does java.lang.System.exit(), which you may remember we do in the CDS/Akka > code somewhere, or there's a bug in the JVM implementation - in which case > there should be a one of those JVM crash logs type things - a file named > something like hs_err_pid22607.log in the "current working" directory. > Where would that be on these CSIT runs, and are the CSIT JJB jobs set up to > preserve such JVM crash log files and copy them over to > logs.opendaylight.org ? > Akka will do System.exit() if it encounters an error serious for that. But it doesn't do it silently. However I believe we disabled the automatic exiting in akka. > > Tx, > M. > -- > Michael Vorburger, Red Hat > [email protected] | IRC: vorburger @freenode | ~ = http://vorburger.ch > > > >> >> We have a number of jobs [1] that have recently started to crash. ODL >> just goes away in the middle of the job. No warnings or exceptions. This >> seems to only happen with ntirogen and oxygen so it leads me to believe it >> is a recent patch in something core. >> >> Thanks, Sam >> >> [1] https://logs.opendaylight.org/releng/jenkins092/netvirt- >> csit-1node-openstack-ocata-upstream-stateful-nitrogen/319/od >> l1_karaf.log.gz >> > >
_______________________________________________ controller-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/controller-dev
