Ya, just confirmed, when I set --work_dir="anything" (anything being even the default /tmp/mesos/slave/ ) there are no sandbox logs, yet, when I leave it off on the slave, then it shows the sandbox. Anything thoughts? Anyone able to reproduce?
On Thu, Sep 4, 2014 at 7:23 PM, John Omernik <[email protected]> wrote: > No firewalls. When I changed the slave work Dir it fixed ...I wonder if > its a permissions thing? > On Sep 4, 2014 5:38 PM, "Dick Davies" <[email protected]> wrote: > >> I don't think that's the issue - i have a custom work_dir too and can >> see the logs fine. >> >> Don't they still get served up from the slaves themselves (port 5051)? >> Maybe you've got >> a firewall blocking that from where you're viewing the mesos ui? >> >> On 4 September 2014 23:58, John Omernik <[email protected]> wrote: >> > Thanks Tim. Some testing showed that when I moved to 0.20, I setup the >> > slaves to use a specific log directory rather than just default to /tmp. >> > Basically, if you specify a customer work_dir for the slave, the master >> > doesn't know (I am guessing?) where to find to logs? This seems like >> > something that should work (if you change the work_dir, it should >> update the >> > master with where to look for logs in the gui). Thoughts? >> > >> > >> > On Thu, Sep 4, 2014 at 5:34 PM, Tim Chen <[email protected]> wrote: >> >> >> >> Hi John, >> >> >> >> Take a look at the slave log and see if your task failed, what was the >> >> failure message that was part of your task failure. >> >> >> >> Tim >> >> >> >> >> >> On Thu, Sep 4, 2014 at 3:24 PM, John Omernik <[email protected]> wrote: >> >>> >> >>> Hey all, I upgraded to 0.20 and when I click on sandbox, the link is >> >>> good, but there are not futher links for logs (i.e. standard err, out >> etc) >> >>> like there was in 0.19. I have changed my log location, but it should >> still >> >>> work... Curious on what I can look at to troubleshoot. >> >>> >> >>> Thanks! >> >>> >> >>> John >> >> >> >> >> > >> >
