mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alberto Rodriguez <>
Subject Native code error
Date Tue, 02 Jun 2015 09:37:02 GMT
Hi all,

I've got a bunch of tests that are checking whether my spark process is
able to connect to a mesos cluster. The "happy path" (mesos up & running)
is working fine the problem comes when I'm testing a connection with a
wrong mesos ip then I'm getting the following error:

WARNING: Logging before InitGoogleLogging() is written to STDERR
W0602 11:26:03.549504 13269 sched.cpp:1323]
Scheduler driver bound to loopback interface! Cannot communicate with
remote master(s). You might want to set 'LIBPROCESS_IP' environment
variable to use a routable IP address.
# A fatal error has been detected by the Java Runtime Environment:
#  SIGSEGV (0xb) at pc=0x00007fcdf32c5660, pid=13125, tid=140517706200832
# JRE version: Java(TM) SE Runtime Environment (7.0_75-b13) (build
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode
linux-amd64 compressed oops)
# Problematic frame:
# C  []  cfree+0x220
# Core dump written. Default location:
/home/arodriguez/dev/datavis-master/back/core or core.13125 (max size 50000
kB). To ensure a full core dump, try "ulimit -c unlimited" before starting
Java again
# An error report file with more information is saved as:
# /home/arodriguez/dev/datavis-master/back/hs_err_pid13125.log
# If you would like to submit a bug report, please visit:
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
/bin/sh: lĂ­nea 1: 13125 Abortado                (`core' generado)
-Xmx1024m -XX:MaxPermSize=256m
-Dlogback.configurationFile=conf/logger/develop.logger.xml$=conf/java.policy -XX:+HeapDumpOnOutOfMemoryError

Any ideas?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message