如何从App Creation Command获取Mesos Marathon Stdout?

时间:2016-02-10 17:25:51

标签: docker mesos marathon

如果我使用带有错误命令的Marathon UI创建一个新的应用程序,例如“badcommand”没有与任务关联的stdout / stderr(在Marathon UI或Mesos UI中)。如何获得stdout / stderr?

我在下面列出了Marathon日志,但它只是说任务(test2)失败了。使用Docker容器,stdout对我来说很好。我确实在docs中看到了一些信息,但没有解决这个问题。

对于我的实际用例,我正在尝试运行bash脚本来创建一些数据库表。显然我可以创建一个扩展现有的Dockerfile,但是从Marathon运行脚本会更容易,因为如果我创建自己的Dockerfile,其敏感信息比我必须为私有托管付费而不是使用免费的Docker Hub服务。

I0210 17:07:12.341120     9 slave.cpp:4999] Launching executor test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 with resources cpus(*):0.1; mem(*):32 in work directory '/tmp/mesos/slaves/379ed26c-465f-4b0f-90f9-d058ad6d028b-S0/frameworks/379ed26c-465f-4b0f-90f9-d058ad6d028b-0000/executors/test2.ba02dba1-d018-11e5-87cd-02420a013102/runs/ef4db108-dce3-45f6-b273-11db38289e24'
I0210 17:07:12.341696     8 docker.cpp:735] No container info found, skipping launch
I0210 17:07:12.341958     9 slave.cpp:1628] Queuing task 'test2.ba02dba1-d018-11e5-87cd-02420a013102' for executor 'test2.ba02dba1-d018-11e5-87cd-02420a013102' of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000
E0210 17:07:12.342250     9 slave.cpp:3466] Container 'ef4db108-dce3-45f6-b273-11db38289e24' for executor 'test2.ba02dba1-d018-11e5-87cd-02420a013102' of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 failed to start: None of the enabled containerizers (docker) could create a container for the provided TaskInfo/ExecutorInfo message
E0210 17:07:12.343215     9 slave.cpp:3537] Termination of executor 'test2.ba02dba1-d018-11e5-87cd-02420a013102' of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 failed: Unknown container: ef4db108-dce3-45f6-b273-11db38289e24
I0210 17:07:12.343487     9 slave.cpp:2762] Handling status update TASK_FAILED (UUID: 02327ed1-3b62-47ae-860a-29a055df99a6) for task test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 from @0.0.0.0:0
W0210 17:07:12.343763    11 docker.cpp:998] Ignoring updating unknown container: ef4db108-dce3-45f6-b273-11db38289e24
I0210 17:07:12.344077    10 status_update_manager.cpp:322] Received status update TASK_FAILED (UUID: 02327ed1-3b62-47ae-860a-29a055df99a6) for task test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000
I0210 17:07:12.344272    10 status_update_manager.cpp:826] Checkpointing UPDATE for status update TASK_FAILED (UUID: 02327ed1-3b62-47ae-860a-29a055df99a6) for task test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000
I0210 17:07:12.369632    10 slave.cpp:3087] Forwarding the update TASK_FAILED (UUID: 02327ed1-3b62-47ae-860a-29a055df99a6) for task test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000 to master@192.168.8.101:5050
I0210 17:07:12.382553     8 status_update_manager.cpp:394] Received status update acknowledgement (UUID: 02327ed1-3b62-47ae-860a-29a055df99a6) for task test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000
I0210 17:07:12.382820     8 status_update_manager.cpp:826] Checkpointing ACK for status update TASK_FAILED (UUID: 02327ed1-3b62-47ae-860a-29a055df99a6) for task test2.ba02dba1-d018-11e5-87cd-02420a013102 of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000
I0210 17:07:12.414659     8 slave.cpp:3657] Cleaning up executor 'test2.ba02dba1-d018-11e5-87cd-02420a013102' of framework 379ed26c-465f-4b0f-90f9-d058ad6d028b-0000

0 个答案:

没有答案