[
https://issues.apache.org/jira/browse/MESOS-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860915#comment-13860915
]
Vinod Kone commented on MESOS-625:
----------------------------------
A work around is to explicitly set the MESOS_BUILD_DIR environment variable,
but it would be nice if we dont require the users to do this.
[vinod@smfd-atr-11-sr1 build]$ MESOS_BUILD_DIR=/home/vinod/mesos/build
./src/long-lived-framework 127.0.0.1:5050
I0102 22:52:31.129765 60509 sched.cpp:218] No credentials provided. Attempting
to register without authentication
I0102 22:52:31.130317 60509 sched.cpp:230] Detecting new master
Registered!
.Starting task 0 on smfd-atr-11-sr1.devel.twitter.com
Task 0 is in state 1
.Starting task 1 on smfd-atr-11-sr1.devel.twitter.com
Task 1 is in state 1
Task 0 is in state 2
.Starting task 2 on smfd-atr-11-sr1.devel.twitter.com
Task 2 is in state 1
Task 2 is in state 2
> Long lived framework is broken in local runs
> --------------------------------------------
>
> Key: MESOS-625
> URL: https://issues.apache.org/jira/browse/MESOS-625
> Project: Mesos
> Issue Type: Bug
> Reporter: Vinod Kone
> Assignee: Vinod Kone
> Labels: twitter
> Fix For: 0.16.0
>
>
> When running both master and slave locally, the slave cannot launch the
> executor because it cannot find "libmesos.so".
> stderr of executor
> ---------------------------
> /home/vinod/mesos/build/src/.libs/long-lived-executor: error while loading
> shared libraries: libmesos-0.14.0.so: cannot open shared object file: No such
> file or directory
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
