[
https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946393#comment-14946393
]
Erhan Kesken commented on MESOS-3136:
-------------------------------------
I tested mesos 0.24.1 with marathon 0.11.0, I'm using puppet module
https://github.com/deric/puppet-mesos to install mesos package, I needed to add
--launch-dir=/usr/libexec/mesos parameter to mesos-slave process, but that was
not enough I also needed to put "MESOS_LAUNCHER_DIR": "/usr/libexec/mesos" line
into env dict of my marathon config as well, otherwise launchhealthcheck
command can not find place of mesos-health-check command. Is there a more
proper solution for this problem?
> COMMAND health checks with Marathon 0.10.0 are broken
> -----------------------------------------------------
>
> Key: MESOS-3136
> URL: https://issues.apache.org/jira/browse/MESOS-3136
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Dr. Stefan Schimanski
> Assignee: haosdent
> Priority: Critical
> Fix For: 0.23.1, 0.24.1, 0.25.0
>
> Attachments: MESOS-3136_0_23_0.patch, MESOS-3136_0_24_0.patch
>
>
> When deploying Mesos 0.23rc4 with latest Marathon 0.10.0 RC3 command health
> check stop working. Rolling back to Mesos 0.22.1 fixes the problem.
> Containerizer is Docker.
> All packages are from official Mesosphere Ubuntu 14.04 sources.
> The issue must be analyzed further.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
