[
https://issues.apache.org/jira/browse/MESOS-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14123612#comment-14123612
]
Iain Mckay commented on MESOS-1769:
-----------------------------------
[~jieyu] as you suggested in IRC I recompiled the slave from the latest master.
This in itself cured my segfault, I didn't need to apply the patch.
The slave starts up and registers with the master now but no tasks are launched
on the slave (with and without the patch applied) but I think that's more an
issue with deimos and outside the scope of this issue.
Thanks
> Segfault when using external containerizer
> ------------------------------------------
>
> Key: MESOS-1769
> URL: https://issues.apache.org/jira/browse/MESOS-1769
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Affects Versions: 0.20.0
> Environment: Ubuntu Trusty 64bit, Vagrant 1.6.3, 4GB RAM, 2 CPU's.
> Reporter: Iain Mckay
>
> I've been attemping to get the 0.4.2 release of Deimos running with Mesos
> 0.20.0. On launch with the following arguments, the system segfaults:
> bq. mesos-slave --master=zk://33.33.32.1:2181/mesos --ip=33.33.32.10
> --containerizer_path=/usr/local/bin/deimos --containerizers=external
> You can find the core-dump
> [here|https://drive.google.com/file/d/0B8zUJw_2eBVYUFlYYTd0YWlLOFU/edit?usp=sharing]
> and I've extracted the stacktrace
> [here|https://gist.github.com/iainmckay/579fac480b9a89fb57ef].
> I can provide more information and I'm available for further debugging if
> required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
