[
https://issues.apache.org/jira/browse/MESOS-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631199#comment-14631199
]
Mike Michel commented on MESOS-2035:
------------------------------------
It would be very helpfull if the information would be written to the sandbox
too. The stderr log is already used to write mesos info to the box when a
container was started
I0717 12:30:01.219111 54012 exec.cpp:132] Version: 0.22.1
Starting task mike-website_frontend_apache.bd016cba-2c6e-11e5-bc1c-02016fccc167
I0717 12:30:01.226969 54028 exec.cpp:206] Executor registered on slave
20150626-195146-1694738624-5050-2
Is it possible to extend this with the information for a failed start? The
slave already has this info in it's own logfile
failed to start: Failed to 'docker pull mikemichel/notexist': exit status =
exited with status 1 stderr = time="2015-07-15T01:48:57+02:00" level=fatal
msg="Error pulling image (latest) from mikemichel/notexist, HTTP code 400"
This way you have the info availabe in the mesos ui.
> Add reason to containerizer proto Termination
> ---------------------------------------------
>
> Key: MESOS-2035
> URL: https://issues.apache.org/jira/browse/MESOS-2035
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Affects Versions: 0.21.0
> Reporter: Dominic Hamon
> Assignee: Joerg Schad
> Labels: mesosphere
>
> When an isolator kills a task, the reason is unknown. As part of MESOS-1830,
> the reason is set to a general one but ideally we would have the termination
> reason to pass through to the status update.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
