You can also see this error if the executor failed to launch the task for some reason. If the issues Stephan describes above are not the root cause, I'd recommend finding the task's directory (look at the mesos slave logs), and then look for the executor logs to see if anything is out of the ordinary there.
On Thu, Mar 17, 2016 at 3:42 AM, Erb, Stephan <[email protected]> wrote: > You commonly get this error, when: > > > * you are too quick clicking on the slave link after starting a task. > Refreshing after a couple of seconds should fix the issue. > > * your cluster is misconfigured so that your slave `--work_dir` path does > not align with the `--mesos-root` of the Thermos observer. Details in > https://github.com/apache/aurora/blob/31a538f190e356a4f82c767ce5c952cc62ba9778/docs/installing.md#configuration-1 > > > > > ------------------------------ > *From:* Krish <[email protected]> > *Sent:* Thursday, March 17, 2016 07:26 > *To:* [email protected] > *Subject:* Thermos Observer Error > > I am running an example job & trying to find what data does the thermos > observer collect about jobs. > However, when I click on the URL in Aurora UI, I see this: > > Error: 404 Not Found > Sorry, the requested URL ' > http://52.207.234.159:1338/task/1458194403029-root-devel-example_job-0-af5704f3-097e-4ff0-b133-3bcbd93e4855' > caused an error: > Failed to find task > 1458194403029-root-devel-example_job-0-af5704f3-097e-4ff0-b133-3bcbd93e4855. > Try again shortly. > > Thermos observer is running as a privileged container alongside > mesos-agent container on a slave. > Is there any special consideration for containers or some config I am > missing? > > > -- > κρισhναν >
