You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Iain Mckay (JIRA)" <ji...@apache.org> on 2014/09/05 23:31:33 UTC

[jira] [Issue Comment Deleted] (MESOS-1769) Segfault when using external containerizer

     [ https://issues.apache.org/jira/browse/MESOS-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Iain Mckay updated MESOS-1769:
------------------------------
    Comment: was deleted

(was: This problem disapears in 0.21.0 compiled from master.)

> 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
>             Fix For: 0.21.0
>
>
> 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)