RE: Error running Application in Marathon

2017-01-11 Thread Joaquin Alzola
Thanks Guys

Recompile but this time as the instructions says …”under build directory” now 
it is working perfectly.


From: Tobias Pfeiffer [mailto:t...@preferred.jp]
Sent: 12 January 2017 00:22
To: user@mesos.apache.org
Subject: Re: Error running Application in Marathon

Hi,

On Wed, Jan 11, 2017 at 7:20 PM, Joaquin Alzola 
mailto:joaquin.alz...@lebara.com>> wrote:
#export 
MESOS_NATIVE_JAVA_LIBRARY=/usr/loca/lib/libmesos-1.1.0.so<http://libmesos-1.1.0.so>

You have a typo here, local is missing an l.

Tobias

This email is confidential and may be subject to privilege. If you are not the 
intended recipient, please do not copy or disclose its content but contact the 
sender immediately upon receipt.


Re: Error running Application in Marathon

2017-01-11 Thread Tobias Pfeiffer
Hi,

On Wed, Jan 11, 2017 at 7:20 PM, Joaquin Alzola 
wrote:
>
> #export MESOS_NATIVE_JAVA_LIBRARY=/usr/loca/lib/libmesos-1.1.0.so
>

You have a typo here, local is missing an l.

Tobias


RE: Error running Application in Marathon

2017-01-11 Thread Joaquin Alzola
Good point, will try that.

From: haosdent [mailto:haosd...@gmail.com]
Sent: 11 January 2017 10:25
To: user 
Subject: Re: Error running Application in Marathon

Have you try use `/usr/local/sbin/mesos-agent` instead of 
`./bin/mesos-agent.sh`?

On Wed, Jan 11, 2017 at 6:20 PM, Joaquin Alzola 
mailto:joaquin.alz...@lebara.com>> wrote:
Hi

I compiled mesos from source and then did ‘make install’
So my libmesos-1.1.0.so<http://libmesos-1.1.0.so> is under /usr/local/lib

I launch the mesos agents with the root user with the following command (it is 
a standalone node).

# ./bin/mesos-master.sh --ip=192.168.1.69 --work_dir=/var/lib/mesos 
–log_dir=/opt/mesos/logs –log_level=INFO –quiet
# ./bin/mesos-agent.sh --master=192.168.1.69:5050<http://192.168.1.69:5050> 
--work_dir=/var/lib/mesos –log_dir=/opt/mesos/logs –log_level=INFO –quiet

Marathon I launch it via:
#export 
MESOS_NATIVE_JAVA_LIBRARY=/usr/loca/lib/libmesos-1.1.0.so<http://libmesos-1.1.0.so>
#export MESOS_WORK_DIR=/tmp/mesos/local
# ./bin/start --master local

BR

Joaquin

From: haosdent [mailto:haosd...@gmail.com<mailto:haosd...@gmail.com>]
Sent: 11 January 2017 10:13
To: user mailto:user@mesos.apache.org>>
Subject: Re: Error running Application in Marathon

hi, @joaquin how you launch mesos agents. It looks like the library search path 
of your agents are incorrect.

On Wed, Jan 11, 2017 at 5:44 PM, Joaquin Alzola 
mailto:joaquin.alz...@lebara.com>> wrote:
Hi Guys

I have the following error running an application on Marathon.

I0110 22:16:29.048617 31888 containerizer.cpp:1489] Checkpointing container's 
forked pid 32028 to 
'/tmp/mesos/local/0/meta/slaves/2060e189-a0c7-42b6-aa07-95828d2065a4-S0/frameworks/2f3fb1d0-d990-4013-8f23-326de597e4e2-/executors/basic-joaquin.6f0026c2-d782-11e6-923d-ea09eed2770d/runs/dcd58aed-0717-4078-9919-b3993d088ef5/pids/forked.pid'
mesos-containerizer: error while loading shared libraries: 
libmesos-1.1.0.so<http://libmesos-1.1.0.so>: cannot open shared object file: No 
such file or directory
I0110 22:16:29.133458 31890 containerizer.cpp:2313] Container 
dcd58aed-0717-4078-9919-b3993d088ef5 has exited

Running the test-framework for java and python work perfectly, but failing for 
c++.

BR

Joaquin
This email is confidential and may be subject to privilege. If you are not the 
intended recipient, please do not copy or disclose its content but contact the 
sender immediately upon receipt.



--
Best Regards,
Haosdent Huang
This email is confidential and may be subject to privilege. If you are not the 
intended recipient, please do not copy or disclose its content but contact the 
sender immediately upon receipt.



--
Best Regards,
Haosdent Huang
This email is confidential and may be subject to privilege. If you are not the 
intended recipient, please do not copy or disclose its content but contact the 
sender immediately upon receipt.


Re: Error running Application in Marathon

2017-01-11 Thread haosdent
Have you try use `/usr/local/sbin/mesos-agent` instead of
`./bin/mesos-agent.sh`?

On Wed, Jan 11, 2017 at 6:20 PM, Joaquin Alzola 
wrote:

> Hi
>
>
>
> I compiled mesos from source and then did ‘make install’
>
> So my libmesos-1.1.0.so is under /usr/local/lib
>
>
>
> I launch the mesos agents with the root user with the following command
> (it is a standalone node).
>
>
>
> # ./bin/mesos-master.sh --ip=192.168.1.69 --work_dir=/var/lib/mesos
> –log_dir=/opt/mesos/logs –log_level=INFO –quiet
>
> # ./bin/mesos-agent.sh --master=192.168.1.69:5050
> --work_dir=/var/lib/mesos –log_dir=/opt/mesos/logs –log_level=INFO –quiet
>
>
>
> Marathon I launch it via:
>
> #export MESOS_NATIVE_JAVA_LIBRARY=/usr/loca/lib/libmesos-1.1.0.so
>
> #export MESOS_WORK_DIR=/tmp/mesos/local
>
> # ./bin/start --master local
>
>
>
> BR
>
>
>
> Joaquin
>
>
>
> *From:* haosdent [mailto:haosd...@gmail.com]
> *Sent:* 11 January 2017 10:13
> *To:* user 
> *Subject:* Re: Error running Application in Marathon
>
>
>
> hi, @joaquin how you launch mesos agents. It looks like the library search
> path of your agents are incorrect.
>
>
>
> On Wed, Jan 11, 2017 at 5:44 PM, Joaquin Alzola 
> wrote:
>
> Hi Guys
>
>
>
> I have the following error running an application on Marathon.
>
>
>
> I0110 22:16:29.048617 31888 containerizer.cpp:1489] Checkpointing
> container's forked pid 32028 to '/tmp/mesos/local/0/meta/
> slaves/2060e189-a0c7-42b6-aa07-95828d2065a4-S0/
> frameworks/2f3fb1d0-d990-4013-8f23-326de597e4e2-/
> executors/basic-joaquin.6f0026c2-d782-11e6-923d-
> ea09eed2770d/runs/dcd58aed-0717-4078-9919-b3993d088ef5/pids/forked.pid'
>
> mesos-containerizer: error while loading shared libraries:
> libmesos-1.1.0.so: cannot open shared object file: No such file or
> directory
>
> I0110 22:16:29.133458 31890 containerizer.cpp:2313] Container
> dcd58aed-0717-4078-9919-b3993d088ef5 has exited
>
>
>
> Running the test-framework for java and python work perfectly, but failing
> for c++.
>
>
>
> BR
>
>
>
> Joaquin
>
> This email is confidential and may be subject to privilege. If you are not
> the intended recipient, please do not copy or disclose its content but
> contact the sender immediately upon receipt.
>
>
>
>
>
> --
>
> Best Regards,
>
> Haosdent Huang
> This email is confidential and may be subject to privilege. If you are not
> the intended recipient, please do not copy or disclose its content but
> contact the sender immediately upon receipt.
>



-- 
Best Regards,
Haosdent Huang


RE: Error running Application in Marathon

2017-01-11 Thread Joaquin Alzola
Hi

I compiled mesos from source and then did ‘make install’
So my libmesos-1.1.0.so is under /usr/local/lib

I launch the mesos agents with the root user with the following command (it is 
a standalone node).

# ./bin/mesos-master.sh --ip=192.168.1.69 --work_dir=/var/lib/mesos 
–log_dir=/opt/mesos/logs –log_level=INFO –quiet
# ./bin/mesos-agent.sh --master=192.168.1.69:5050 --work_dir=/var/lib/mesos 
–log_dir=/opt/mesos/logs –log_level=INFO –quiet

Marathon I launch it via:
#export MESOS_NATIVE_JAVA_LIBRARY=/usr/loca/lib/libmesos-1.1.0.so
#export MESOS_WORK_DIR=/tmp/mesos/local
# ./bin/start --master local

BR

Joaquin

From: haosdent [mailto:haosd...@gmail.com]
Sent: 11 January 2017 10:13
To: user 
Subject: Re: Error running Application in Marathon

hi, @joaquin how you launch mesos agents. It looks like the library search path 
of your agents are incorrect.

On Wed, Jan 11, 2017 at 5:44 PM, Joaquin Alzola 
mailto:joaquin.alz...@lebara.com>> wrote:
Hi Guys

I have the following error running an application on Marathon.

I0110 22:16:29.048617 31888 containerizer.cpp:1489] Checkpointing container's 
forked pid 32028 to 
'/tmp/mesos/local/0/meta/slaves/2060e189-a0c7-42b6-aa07-95828d2065a4-S0/frameworks/2f3fb1d0-d990-4013-8f23-326de597e4e2-/executors/basic-joaquin.6f0026c2-d782-11e6-923d-ea09eed2770d/runs/dcd58aed-0717-4078-9919-b3993d088ef5/pids/forked.pid'
mesos-containerizer: error while loading shared libraries: 
libmesos-1.1.0.so<http://libmesos-1.1.0.so>: cannot open shared object file: No 
such file or directory
I0110 22:16:29.133458 31890 containerizer.cpp:2313] Container 
dcd58aed-0717-4078-9919-b3993d088ef5 has exited

Running the test-framework for java and python work perfectly, but failing for 
c++.

BR

Joaquin
This email is confidential and may be subject to privilege. If you are not the 
intended recipient, please do not copy or disclose its content but contact the 
sender immediately upon receipt.



--
Best Regards,
Haosdent Huang
This email is confidential and may be subject to privilege. If you are not the 
intended recipient, please do not copy or disclose its content but contact the 
sender immediately upon receipt.


Re: Error running Application in Marathon

2017-01-11 Thread haosdent
hi, @joaquin how you launch mesos agents. It looks like the library search
path of your agents are incorrect.

On Wed, Jan 11, 2017 at 5:44 PM, Joaquin Alzola 
wrote:

> Hi Guys
>
>
>
> I have the following error running an application on Marathon.
>
>
>
> I0110 22:16:29.048617 31888 containerizer.cpp:1489] Checkpointing
> container's forked pid 32028 to '/tmp/mesos/local/0/meta/
> slaves/2060e189-a0c7-42b6-aa07-95828d2065a4-S0/
> frameworks/2f3fb1d0-d990-4013-8f23-326de597e4e2-/
> executors/basic-joaquin.6f0026c2-d782-11e6-923d-
> ea09eed2770d/runs/dcd58aed-0717-4078-9919-b3993d088ef5/pids/forked.pid'
>
> mesos-containerizer: error while loading shared libraries:
> libmesos-1.1.0.so: cannot open shared object file: No such file or
> directory
>
> I0110 22:16:29.133458 31890 containerizer.cpp:2313] Container
> dcd58aed-0717-4078-9919-b3993d088ef5 has exited
>
>
>
> Running the test-framework for java and python work perfectly, but failing
> for c++.
>
>
>
> BR
>
>
>
> Joaquin
> This email is confidential and may be subject to privilege. If you are not
> the intended recipient, please do not copy or disclose its content but
> contact the sender immediately upon receipt.
>



-- 
Best Regards,
Haosdent Huang