Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Thu, 18 Aug 2016 01:11:20 +0000 (UTC)
From: "Charles Allen (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12998079.1471482639000.338837.1471482680446@Atlassian.JIRA>
In-Reply-To: <JIRA.12998079.1471482639000@Atlassian.JIRA>
References: <JIRA.12998079.1471482639000@Atlassian.JIRA> <JIRA.12998079.1471482639484@arcas>
Subject: [jira] [Updated] (MESOS-6055) Mesos libs in LD_LIBRARY_PATH cause
 fetcher to fail and not report errors
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 18 Aug 2016 01:11:22 -0000


     [ https://issues.apache.org/jira/browse/MESOS-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Charles Allen updated MESOS-6055:
---------------------------------
    Summary: Mesos libs in LD_LIBRARY_PATH cause fetcher to fail and not report errors  (was: Mesos libs in LD_LIBRARY_PATH cause fetcher to fail)

> Mesos libs in LD_LIBRARY_PATH cause fetcher to fail and not report errors
> -------------------------------------------------------------------------
>
>                 Key: MESOS-6055
>                 URL: https://issues.apache.org/jira/browse/MESOS-6055
>             Project: Mesos
>          Issue Type: Bug
>          Components: fetcher
>            Reporter: Charles Allen
>
> in 1.0.0, if the agent is launched such that the mesos libraries can only be found under {{LD_LIBRARY_PATH}}, the fetcher will fail and simply exit with no output. The log will not show linker errors. I'm not sure where they are swallowed. If the task is launched with LD_LIBRARY_PATH set to include where the mesos libs can be found, the fetcher functions as expected.
> The problem is that the errors in the fetcher linking are not obvious as no logs are produced from the fetcher sub process.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)