You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Luke Adolph <ke...@gmail.com> on 2016/12/20 06:23:55 UTC
how to debug when a task is killed
Hi all:
I have set up a mesos cluster with on mesos master and five mesos agents.
I use Marathon to depoy an app across mesos agents, which reads process
info from /proc.
About every 40 minuntes, my apps will be killed and Marathon restart them.
The stderr info in sandbox is:
I1220 05:05:12.014192 28736 exec.cpp:143] Version: 0.28.1
I1220 05:05:12.017397 28740 exec.cpp:217] Executor registered on slave
83e33a06-5794-4baa-a654-dd2ecfcd426d-S5
2016/12/20 05:05:12 status read fail.
2016/12/20 05:05:12 process id is: 8208
2016/12/20 05:05:12 open /proc/8208/status: no such file or directory
2016/12/20 05:06:16 status read fail.
2016/12/20 05:06:16 process id is: 8742
2016/12/20 05:06:16 open /proc/8742/status: no such file or directory
2016/12/20 05:07:16 status read fail.
2016/12/20 05:07:16 process id is: 9005
2016/12/20 05:07:16 open /proc/9005/status: no such file or directory
2016/12/20 05:25:50 status read fail.
2016/12/20 05:25:50 open /proc/17284/stat: no such file or directory
Killed
In addition to above stderr info, I have no meaningful info to provide or
debug.
May you share your experience on solving similar situation.
Thanks very much！
--
Thanks & Best Regards
卢文泉 | Adolph Lu
TEL：+86 15651006559
Linker Networks(http://www.linkernetworks.com/)
Re: how to debug when a task is killed
Posted by Luke Adolph <ke...@gmail.com>.
My app does not provide health check mechanism.
And I have got the reason: *Not enough memory*.
I should provide more memory for my app on Marathon.
Thanks all!
2016-12-20 15:17 GMT+08:00 haosdent <ha...@gmail.com>:
> Do you configure health check? If you configure health check and it could
> not pass, the task would be killed.
>
> On Tue, Dec 20, 2016 at 2:23 PM, Luke Adolph <ke...@gmail.com> wrote:
>
>> Hi all:
>>
>> I have set up a mesos cluster with on mesos master and five mesos agents.
>> I use Marathon to depoy an app across mesos agents, which reads process
>> info from /proc.
>> About every 40 minuntes, my apps will be killed and Marathon restart them.
>> The stderr info in sandbox is:
>>
>>
>> I1220 05:05:12.014192 28736 exec.cpp:143] Version: 0.28.1
>> I1220 05:05:12.017397 28740 exec.cpp:217] Executor registered on slave 83e33a06-5794-4baa-a654-dd2ecfcd426d-S5
>> 2016/12/20 05:05:12 status read fail.
>> 2016/12/20 05:05:12 process id is: 8208
>> 2016/12/20 05:05:12 open /proc/8208/status: no such file or directory
>> 2016/12/20 05:06:16 status read fail.
>> 2016/12/20 05:06:16 process id is: 8742
>> 2016/12/20 05:06:16 open /proc/8742/status: no such file or directory
>> 2016/12/20 05:07:16 status read fail.
>> 2016/12/20 05:07:16 process id is: 9005
>> 2016/12/20 05:07:16 open /proc/9005/status: no such file or directory
>> 2016/12/20 05:25:50 status read fail.
>> 2016/12/20 05:25:50 open /proc/17284/stat: no such file or directory
>> Killed
>>
>>
>>
>> In addition to above stderr info, I have no meaningful info to provide or
>> debug.
>> May you share your experience on solving similar situation.
>>
>> Thanks very much！
>>
>> --
>> Thanks & Best Regards
>> 卢文泉 | Adolph Lu
>> TEL：+86 15651006559 <+86%20156%205100%206559>
>> Linker Networks(http://www.linkernetworks.com/)
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>
--
Thanks & Best Regards
卢文泉 | Adolph Lu
TEL：+86 15651006559
Linker Networks(http://www.linkernetworks.com/)
Re: how to debug when a task is killed
Posted by haosdent <ha...@gmail.com>.
Do you configure health check? If you configure health check and it could
not pass, the task would be killed.
On Tue, Dec 20, 2016 at 2:23 PM, Luke Adolph <ke...@gmail.com> wrote:
> Hi all:
>
> I have set up a mesos cluster with on mesos master and five mesos agents.
> I use Marathon to depoy an app across mesos agents, which reads process
> info from /proc.
> About every 40 minuntes, my apps will be killed and Marathon restart them.
> The stderr info in sandbox is:
>
>
> I1220 05:05:12.014192 28736 exec.cpp:143] Version: 0.28.1
> I1220 05:05:12.017397 28740 exec.cpp:217] Executor registered on slave 83e33a06-5794-4baa-a654-dd2ecfcd426d-S5
> 2016/12/20 05:05:12 status read fail.
> 2016/12/20 05:05:12 process id is: 8208
> 2016/12/20 05:05:12 open /proc/8208/status: no such file or directory
> 2016/12/20 05:06:16 status read fail.
> 2016/12/20 05:06:16 process id is: 8742
> 2016/12/20 05:06:16 open /proc/8742/status: no such file or directory
> 2016/12/20 05:07:16 status read fail.
> 2016/12/20 05:07:16 process id is: 9005
> 2016/12/20 05:07:16 open /proc/9005/status: no such file or directory
> 2016/12/20 05:25:50 status read fail.
> 2016/12/20 05:25:50 open /proc/17284/stat: no such file or directory
> Killed
>
>
>
> In addition to above stderr info, I have no meaningful info to provide or
> debug.
> May you share your experience on solving similar situation.
>
> Thanks very much！
>
> --
> Thanks & Best Regards
> 卢文泉 | Adolph Lu
> TEL：+86 15651006559 <+86%20156%205100%206559>
> Linker Networks(http://www.linkernetworks.com/)
>
--
Best Regards,
Haosdent Huang