Ok, thanks for the tip!
Made some progress. Now this is what I get :
stderr on the slave:
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0818 19:06:55.03369922 fetcher.cpp:73] Fetching URI
'http://downloads.mesosphere.io/storm/storm-mesos-0.9.tgz'
I0818 19:06:55.033994
Hi,
I compiled my executor with the following command
g++ executor.cpp -Lmesos-0.18.1/src/.libs/ -lmesos -I/usr/local/include
-Imesos-0.18.1/src/
-Imesos-0.18.1/3rdparty/libprocess/3rdparty/protobuf-2.5.0/src/
-Imesos-0.18.1/3rdparty/libprocess/3rdparty/stout/include/
Yes
On Monday, August 18, 2014, Vinod Kone vinodk...@gmail.com wrote:
On Sat, Aug 16, 2014 at 4:26 AM, John Omernik j...@omernik.com
javascript:_e(%7B%7D,'cvml','j...@omernik.com'); wrote:
I've confirmed on the package I am using that when I untar it using tar
zxf as root, that the
What version of the storm on mesos code are you running? i.e., what is the
git sha?
On Mon, Aug 18, 2014 at 11:53 PM, Yaron Rosenbaum yaron.rosenb...@gmail.com
wrote:
Ok, thanks for the tip!
Made some progress. Now this is what I get :
stderr on the slave:
WARNING: Logging before
Hi everyone,
I've just released a project that might be of interest to some of you.
It can be used to automatically reload HAProxy configurations when
something in Marathon changes so that traffic is proxied to the right ports
on the right hosts as soon as tasks are started and stopped.
It
Can you do me a favor? on one of your running tasks, or recently completed
tasks, in the Mesos task, click on it, go to the logs (it shows the stderr
and stdout) and then drill into the extracted hadoop package to
/hadoop-version/bin/Linux-amd64-64/bin and let me know what the
owner/permissions of
what is the error?
On Mon, Aug 18, 2014 at 11:54 PM, Sai Sagar jsaisa...@gmail.com wrote:
Hi,
I compiled my executor with the following command
g++ executor.cpp -Lmesos-0.18.1/src/.libs/ -lmesos -I/usr/local/include
-Imesos-0.18.1/src/
Is this repeatable? If yes, mind filing a ticket at
https://issues.apache.org/jira/browse/MESOS?
On Mon, Aug 18, 2014 at 11:47 PM, Giovanni Colapinto
gcolapi...@innovazionedigitale.it wrote:
Hello.
I've compiled mesos from source. All fine with make, but make check gives
me this error:
On Tue, Aug 19, 2014 at 12:06 PM, mohit soni mohitsoni1...@gmail.com
wrote:
If slave doesn't directly use task id or executor id, and instead use
the random UUID for cgroup, then my assumption is that it maintains a
mapping from this UUID to either task or executor id, internally.
that's
+1
make check on
Ubuntu 14.04 gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) and
Mac OS X clang-503.0.40
Looking so much forward to this release!
Niklas
On 19 August 2014 11:28, Ian Downes idow...@twitter.com.invalid wrote:
+1
make check passes on CentOS 5.5 with 3.4 kernel. Docker tests were
./bootstrap ./configure make check
'+1 make check' on clean el7 is green
However on machines that already have deps installed, my F20 machine: I've seen
'[ FAILED ] ExamplesTest.PythonFramework' for a while.
Digging I find:
Traceback (most recent call last):
File
Tim, I demangled the symbol:
google::FlagRegisterer::FlagRegisterer(char const*, char const*, char
const*, char const*, void*, void*)
Doesn't seem to be from mesos.
- Jie
On Tue, Aug 19, 2014 at 6:44 PM, Tim St Clair tstcl...@redhat.com wrote:
./bootstrap ./configure make check
'+1 make
Hi,
In the logs, I am getting the following message:
I0820 11:10:53.440304 9713 launcher.cpp:120] Forked child with pid '11499'
for container 'afcf561f-99ec-4af7-bddd-9ba015926192'
I0820 11:10:53.441041 9712 slave.cpp:2001] Monitoring executor 'default'
of framework
13 matches
Mail list logo
