[ 
https://issues.apache.org/jira/browse/MESOS-8800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810573#comment-16810573
 ] 

Pavel commented on MESOS-8800:
------------------------------

Nearly the same error on 1.7.2, build with ./configure 
--ENABLE_NETWORK_PORTS_ISOLATOR
 --isolation=filesystem/linux,docker/runtime,posix/rlimits,network/port_mapping
{noformat}
mesos-slave: ../3rdparty/boost-1.65.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.
mesos-slave[24391]: *** Aborted at 1554415003 (unix time) try "date -d 
@1554415003" if you are using GNU date ***
mesos-slave[24391]: PC: @     0x7f81feba21f7 __GI_raise
mesos-slave[24391]: *** SIGABRT (@0x5ef4) received by PID 24308 (TID 
0x7f8203b8ba00) from PID 24308; stack trace: ***
mesos-slave[24391]:     @     0x7f81ff45d5e0 (unknown)
mesos-slave[24391]:     @     0x7f81feba21f7 __GI_raise
mesos-slave[24391]:     @     0x7f81feba38e8 __GI_abort
mesos-slave[24391]:     @     0x7f81feb9b266 __assert_fail_base
mesos-slave[24391]:     @     0x7f81feb9b312 __GI___assert_fail
mesos-slave[24391]:     @     0x7f8201d5c711 std::_Rb_tree<>::_M_lower_bound()
mesos-slave[24391]:     @     0x7f8201d96cfc std::_Rb_tree<>::find()
mesos-slave[24391]:     @     0x7f8201d7e19d 
mesos::internal::slave::PortMappingIsolatorProcess::create()
mesos-slave[24391]:     @     0x7f8201b47f8c 
std::_Function_handler<>::_M_invoke()
mesos-slave[24391]:     @     0x7f8201b36ab2 
mesos::internal::slave::MesosContainerizer::create()
mesos-slave[24391]:     @     0x7f8201aac1b6 
mesos::internal::slave::Containerizer::create()
mesos-slave[24391]:     @     0x55a31557011d main
mesos-slave[24391]:     @     0x7f81feb8ec05 __libc_start_main
mesos-slave[24391]:     @     0x55a315572c2c (unknown)
{noformat}
Sometimes it is preferred using network=host for container with port mapping 
isolation, because apps need host IP, and port range as a resource.

Could it probably be a configuratin error issue?

> start failed after add "network/port_mapping" to isolation
> ----------------------------------------------------------
>
>                 Key: MESOS-8800
>                 URL: https://issues.apache.org/jira/browse/MESOS-8800
>             Project: Mesos
>          Issue Type: Task
>    Affects Versions: 1.5.0
>            Reporter: stevenlee
>            Priority: Major
>
> when i add 
> "cgroups/cpu,cgroups/mem,disk/du,filesystem/linux,docker/runtime,network/port_mapping"
>  to islotion and add 
> "cpus:24;mem:128000;ports:[31000-32000];disk:100000;ephemeral_ports:[32768-57344]"
>  to resources,then i systemctl start mesos-slave,report this:
> Log file created at: 2018/04/18 15:15:56
> Running on machine: test.machine.net
> Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
> I0418 15:15:56.583765 21945 logging.cpp:201] INFO level logging started!
> I0418 15:15:56.584277 21945 main.cpp:365] Build: 2018-04-14 13:33:38 by root
> I0418 15:15:56.584306 21945 main.cpp:366] Version: 1.5.0
> I0418 15:15:56.615106 21945 systemd.cpp:240] systemd version `219` detected
> I0418 15:15:56.615202 21945 main.cpp:468] Initializing systemd state
> I0418 15:15:56.623399 21945 systemd.cpp:328] Started systemd slice 
> `mesos_executors.slice`
> I0418 15:15:56.626150 21945 resolver.cpp:69] Creating default secret resolver
> I0418 15:15:56.713505 21945 containerizer.cpp:304] Using isolation \{ 
> environment_secret, volume/image, volume/host_path, cgroups/cpu, cgroups/mem, 
> docker/runtime, volume/sandbox_path, disk/du, filesystem/linux, 
> network/port_mapping }
> I0418 15:15:56.725468 21945 linux_launcher.cpp:146] Using 
> /sys/fs/cgroup/freezer as the freezer hierarchy for the Linux launcher
> I0418 15:15:56.812513 21945 fetcher.cpp:69] Skipping URI fetcher plugin 
> 'hadoop' as it could not be created: Failed to create HDFS client: Hadoop 
> client is not available, exit status: 32512
> I0418 15:15:56.818392 21945 provisioner.cpp:299] Using default backend 'copy'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to