Thanks Haosdent for your quick response. I added GLOG_v=1 to the master and agents.
1. The framework is registered. Marathon in this case. 2. I see messages 'Telling agent (...) to kill task (...)'. Why does this happen? I also see 'Sending explicit reconciliation state TASK_LOST for task fake-marathon-pacemaker-task-(...)'. 3. I searched for RunTaskMessage in the agent log but could not find it. Is this the exact text to search for or is this the name of the protobuf message? Are these logged on a higher log level? On Tue, Oct 4, 2016 at 11:22 AM, haosdent <[email protected]> wrote: > staging is the initialize status of the task. I think you may your logs via > these steps: > > 1. If your framework registered successfully in the master? > 2. If the master send resources offers to your framework and your framework > accept it? > 3. If your agents receive the RunTaskMessage from master to launch your > task? > > In additionally, use `export GLOG_v=1` before start masters and agents may > helpful for your troubleshooting. > > On Tue, Oct 4, 2016 at 4:58 PM, Frank Scholten <[email protected]> > wrote: >> >> Hi all, >> >> I am looking for some ways to troubleshoot or debug tasks that are >> stuck in the 'staging' state. Typically they have no logs in the >> sandbox. >> >> Are there are any endpoints or things to look for in logs to identify >> a root cause? >> >> Is there a troubleshooting guide for Mesos to solve problems like this? >> >> Cheers, >> >> Frank > > > > > -- > Best Regards, > Haosdent Huang
