You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Damien Hardy <dh...@viadeoteam.com> on 2013/10/23 18:50:40 UTC
UI remote Task Sandbox displays error
Hello,
I suppose I'm doing wrong.
When running a task on a remote slave from master, clicking on sandbox link
on UI results in an error:
*Error browsing path:
/var/lib/mesos//slaves/201310211635-3951143104-5050-5534-2/frameworks/201310211635-3951143104-5050-5534-0002/executors/ct:1382546709043:0:test/runs/60a53a92-0e92-4f33-a0ac-9577fefa2dd7
*
/var/lib/mesos is the working dir for slave.
local dir (on master) is obviously empty, and path exists on distant slave.
(with stderr and stdout files as expected)
When task run locally with master it display well.
revision commit is b6405e20b1fc2163dada7072c4dd417518ce1efd
What did I miss ?
Regards,
--
Damien HARDY
Re: UI remote Task Sandbox displays error
Posted by Benjamin Mahler <be...@gmail.com>.
I would recommend inspecting what request the webui is making to the
/files/ endpoint on the slave, the response from this endpoint will be
insightful.
We should really be showing the response string when a non-successful
response is returned in the sandbox browsing ui:
https://issues.apache.org/jira/browse/MESOS-776
On Fri, Oct 25, 2013 at 9:15 AM, Damien Hardy <dh...@viadeoteam.com> wrote:
> Thank you Ben,
>
> For my case, guilty is here
>
> https://github.com/airbnb/chronos/blob/master/src/main/scala/com/airbnb/scheduler/jobs/TaskUtils.scala#L22:)
>
> maybe some base64 encoding for paths could be a way to do
>
> Best,
>
>
> 2013/10/23 Benjamin Mahler <be...@gmail.com>
>
>> There could be an issue related to using the ':' character in your
>> executor id (which ultimately gets mapped to a path). Awhile back I filed
>> this: https://issues.apache.org/jira/browse/MESOS-361
>>
>> That's all I have to go on with the given information, the slave log
>> might be more informative here, do you have it available?
>>
>>
>> On Wed, Oct 23, 2013 at 9:50 AM, Damien Hardy <dh...@viadeoteam.com>wrote:
>>
>>> Hello,
>>>
>>> I suppose I'm doing wrong.
>>>
>>> When running a task on a remote slave from master, clicking on sandbox
>>> link on UI results in an error:
>>>
>>> *Error browsing path:
>>> /var/lib/mesos//slaves/201310211635-3951143104-5050-5534-2/frameworks/201310211635-3951143104-5050-5534-0002/executors/ct:1382546709043:0:test/runs/60a53a92-0e92-4f33-a0ac-9577fefa2dd7
>>>
>>> *
>>> /var/lib/mesos is the working dir for slave.
>>>
>>> local dir (on master) is obviously empty, and path exists on distant
>>> slave. (with stderr and stdout files as expected)
>>>
>>> When task run locally with master it display well.
>>>
>>> revision commit is b6405e20b1fc2163dada7072c4dd417518ce1efd
>>>
>>> What did I miss ?
>>>
>>> Regards,
>>>
>>> --
>>> Damien HARDY
>>>
>>
>>
>
>
> --
> Damien HARDY
>
Re: UI remote Task Sandbox displays error
Posted by Damien Hardy <dh...@viadeoteam.com>.
Thank you Ben,
For my case, guilty is here
https://github.com/airbnb/chronos/blob/master/src/main/scala/com/airbnb/scheduler/jobs/TaskUtils.scala#L22:)
maybe some base64 encoding for paths could be a way to do
Best,
2013/10/23 Benjamin Mahler <be...@gmail.com>
> There could be an issue related to using the ':' character in your
> executor id (which ultimately gets mapped to a path). Awhile back I filed
> this: https://issues.apache.org/jira/browse/MESOS-361
>
> That's all I have to go on with the given information, the slave log might
> be more informative here, do you have it available?
>
>
> On Wed, Oct 23, 2013 at 9:50 AM, Damien Hardy <dh...@viadeoteam.com>wrote:
>
>> Hello,
>>
>> I suppose I'm doing wrong.
>>
>> When running a task on a remote slave from master, clicking on sandbox
>> link on UI results in an error:
>>
>> *Error browsing path:
>> /var/lib/mesos//slaves/201310211635-3951143104-5050-5534-2/frameworks/201310211635-3951143104-5050-5534-0002/executors/ct:1382546709043:0:test/runs/60a53a92-0e92-4f33-a0ac-9577fefa2dd7
>>
>> *
>> /var/lib/mesos is the working dir for slave.
>>
>> local dir (on master) is obviously empty, and path exists on distant
>> slave. (with stderr and stdout files as expected)
>>
>> When task run locally with master it display well.
>>
>> revision commit is b6405e20b1fc2163dada7072c4dd417518ce1efd
>>
>> What did I miss ?
>>
>> Regards,
>>
>> --
>> Damien HARDY
>>
>
>
--
Damien HARDY
Re: UI remote Task Sandbox displays error
Posted by Benjamin Mahler <be...@gmail.com>.
There could be an issue related to using the ':' character in your executor
id (which ultimately gets mapped to a path). Awhile back I filed this:
https://issues.apache.org/jira/browse/MESOS-361
That's all I have to go on with the given information, the slave log might
be more informative here, do you have it available?
On Wed, Oct 23, 2013 at 9:50 AM, Damien Hardy <dh...@viadeoteam.com> wrote:
> Hello,
>
> I suppose I'm doing wrong.
>
> When running a task on a remote slave from master, clicking on sandbox
> link on UI results in an error:
>
> *Error browsing path:
> /var/lib/mesos//slaves/201310211635-3951143104-5050-5534-2/frameworks/201310211635-3951143104-5050-5534-0002/executors/ct:1382546709043:0:test/runs/60a53a92-0e92-4f33-a0ac-9577fefa2dd7
>
> *
> /var/lib/mesos is the working dir for slave.
>
> local dir (on master) is obviously empty, and path exists on distant
> slave. (with stderr and stdout files as expected)
>
> When task run locally with master it display well.
>
> revision commit is b6405e20b1fc2163dada7072c4dd417518ce1efd
>
> What did I miss ?
>
> Regards,
>
> --
> Damien HARDY
>