[
https://issues.apache.org/jira/browse/MESOS-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431398#comment-15431398
]
Charles Allen commented on MESOS-6055:
--------------------------------------
Have mesos installed in a way where the main shared library isn't found. ex:
launching a slave should fail by default with errors about not able to
find/bind the mesos library.
Change the LD path via {{LD_LIBRARY_PATH}} such that the slave succeeds in
running.
Try and launch something with a URI to be fetched, it will fail in confusing
ways.
Try and launch something without a URI (like {{echo something}}). it will
print out {{something} as expected.
> 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)
