[
https://issues.apache.org/jira/browse/MESOS-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431760#comment-15431760
]
Joseph Wu commented on MESOS-6055:
----------------------------------
Wasn't able to repro from my local build.
Agent launched from non-libtool'd binary:
{code}
sudo -E GLOG_v=1 LD_RUN_PATH=/mesos/build/src/.libs
LD_LIBRARY_PATH=/mesos/build/src/.libs src/.libs/mesos-agent
--work_dir=/tmp/agent --master=localhost:5050 --launcher_dir=/mesos/build/src
{code}
Master launched from wherever:
{code}
bin/mesos-master.sh --work_dir=/tmp/master
{code}
See if the fetcher does anything. The URI itself doesn't matter:
{code}
src/balloon-framework --master=localhost:5050 --task_memory=128MB
--task_memory_usage_limit=256MB
--executor_uri="http://dont/really/care/where/this/is";
{code}
Checked the task's stderr and it clearly showed a fetcher error, but not a
linking error.
> 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)
