Jean-Baptiste created MESOS-8011:
------------------------------------
Summary: Enabling Port mapping generate segfault
Key: MESOS-8011
URL: https://issues.apache.org/jira/browse/MESOS-8011
Project: Mesos
Issue Type: Bug
Components: agent, network
Affects Versions: 1.4.0, 1.3.1, 1.3.0
Reporter: Jean-Baptiste
h2. Overview
After a succesful build of Mesos in the different versions (1.3.0 / 1.3.1 /
1.4.0 / 1.5.0), I still get stuck with the following segfault when starting the
`Mesos` agent:
h2. Environment
* Debian Linux `8.7` (Jessie)
* Kernel `4.12` (also tried with 3.16 and 4.9)
* Mesos `1.3.0` (also tried with 1.3.1, 1.4.0 and 1.5.0)
* Libnl `3.2.27-2`
h2. Stack trace
{code}
Sep 25 12:41:46 ip-10-43-20-218 systemd[1]: Starting Mesos Slave...
Sep 25 12:41:46 ip-10-43-20-218 systemd[1]: Started Mesos Slave.
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: WARNING: Logging before
InitGoogleLogging() is written to STDERR
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: W0925 12:41:46.510066 2717
parse.hpp:97] Specifying an absolute filename to read a command line option out
of without using 'file:// is deprecated and will be removed in a future
release. Simply adding 'file://' to the beginning of the path should eliminate
this warning.
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: I0925 12:41:46.510259 2717
main.cpp:322] Build: 2017-09-04 19:29:27 by pbuilder
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: I0925 12:41:46.510275 2717
main.cpp:323] Version: 1.3.1
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: I0925 12:41:46.511230 2717
logging.cpp:194] INFO level logging started!
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: I0925 12:41:46.517127 2717
systemd.cpp:238] systemd version `215` detected
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: W0925 12:41:46.517174 2717
systemd.cpp:246] Required functionality `Delegate` was introduced in Version
`218`. Your system may not function properly; however since some distributions
have patched systemd packages, your system may still be functional. This is why
we keep running. See MESOS-3352 for more information
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: I0925 12:41:46.517293 2717
main.cpp:432] Inializing systemd state
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: I0925 12:41:46.520074 2717
systemd.cpp:326] Started systemd slice `mesos_executors.slice`
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: W0925 12:41:46.611994 2717
containerizer.cpp:189] 'posix/disk' has been renamed as 'disk/du', please
update your --isolation flag to use 'disk/du'
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: I0925 12:41:46.612027 2717
containerizer.cpp:221] Using isolation:
cgroups/cpu,posix/mem,posix/disk,network/port_mapping,filesystem/posix
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: I0925 12:41:46.615073 2717
linux_launcher.cpp:150] Using /sys/fs/cgroup/freezer as the freezer hierarchy
for the Linux launcher
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: I0925 12:41:46.615413 2717
provisioner.cpp:249] Using default backend 'overlay'
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: mesos-slave:
../3rdparty/boost-1.53.0/boost/icl/concept/interval.hpp:586: typename
boost::enable_if<boost::icl::is_asymmetric_interval<Type>, bool>::type
boost::icl::non_empty::exclusive_less(const Type&, const Type&) [with Type =
Interval<short unsigned int>; typename
boost::enable_if<boost::icl::is_asymmetric_interval<Type>, bool>::type = bool]:
Assertion `!(icl::is_empty(left) || icl::is_empty(right))' failed.
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: *** Aborted at 1506343306
(unix time) try "date -d @1506343306" if you are using GNU date ***
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: PC: @ 0x7f27069d1067
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: *** SIGABRT (@0xa9d)
received by PID 2717 (TID 0x7f270a0a2800) from PID 2717; stack trace: ***
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x7f2706d56890
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x7f27069d1067
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x7f27069d2448
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x7f27069ca266
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x7f27069ca312
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x7f2708d124c3
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x7f2708d126a7
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x7f2708d4d0dc
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x7f2708d38dc2
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x7f27089dbe2c
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x7f27089cf201
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x7f2708944198
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x557ff33c4e7a
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x7f27069bdb45
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x557ff33c62db
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 mesos-slave[2754]: @ 0x0
(unknown)
Sep 25 12:41:46 ip-10-43-20-218 systemd[1]: mesos-slave.service: main process
exited, code=killed, status=6/ABRT
Sep 25 12:41:46 ip-10-43-20-218 systemd[1]: Unit mesos-slave.service entered
failed state.
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
