Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of bigo@uber.com designates
 209.85.192.46 as permitted sender)
MIME-Version: 1.0
From: Oliver Nicholas <bigo@uber.com>
Date: Fri, 6 Feb 2015 18:09:49 -0800
Message-ID: 
 <CABTw1kVRcnpbCrcGfrmBQB6xxnpzjfojar77P7=AkBa-TbmGPA@mail.gmail.com>
Subject: Issues with Aurora Hello World
To: dev@aurora.incubator.apache.org
Content-Type: multipart/mixed; boundary=001a11c1efb86a7fa3050e760981

--001a11c1efb86a7fa3050e760981
Content-Type: multipart/alternative; boundary=001a11c1efb86a7f9e050e76097f

--001a11c1efb86a7f9e050e76097f
Content-Type: text/plain; charset=UTF-8

Hello folks,

I was working with wfarner in the IRC channel and he had to run; he asked
me to send an email to this list (which I think wins the awards for deepest
subdomain chain in an email address since the late eighties :).

So, first off real quick, the Hello World docs specify the commands as eg/
"aurora create devcluster/www-data/devel/hello_world
/vagrant/hello_world.aurora", when the command appears to now be "aurora
job create" (rather than just "aurora create").  Something to update.

Second, the real issue - I'm working through the Hello World stuff with
vagrant/VirtualBox on OS X.  I've got the hello_world.py job running just
fine, doing nothing more or less than the instructions, and it shows up in
the scheduler web UI (the one running on port 8081). But when I click
through to look at the task details - the link that jumps to the thermos
observer (sorry, I'm new to this, not sure about nomenclature) running on
port 1338, I get a 404.  And if I look at the base URL for the observer (
http://192.168.33.7:1338/) I get some empty tables titled like "active
tasks 0...-1 of 0".

Now...I'm definitely only running one VM right now.  The task is running -
the scheduler says so and I can see the process.  I've attached the various
upstart logs that wfarner asked for - as you can see, it appears that the
observer is...not observing much.

I've also attached an strace of the observer process idling and with me
hitting it over the web iterface (to be clear, the one with the proctitle
"python2.7 /home/vagrant/aurora/dist/thermos_observer.pex
--root=/var/run/thermos --port=1338 --log_to_disk=NONE
--log_to_stderr=google:INFO").  The only thing of note I see is that it's
trying to hit these files under the /var/run/thermos tree (the --root
parameter on the command line), but there is no 'thermos' in /var/run.
Come to think of it, that seems significant.

Halp?

Cheers,
bigo

--001a11c1efb86a7f9e050e76097f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello folks,<div><br></div><div>I was working with wfarner=
 in the IRC channel and he had to run; he asked me to send an email to this=
 list (which I think wins the awards for deepest subdomain chain in an emai=
l address since the late eighties :).</div><div><br></div><div>So, first of=
f real quick, the Hello World docs specify the commands as eg/ &quot;aurora=
 create devcluster/www-data/devel/hello_world /vagrant/hello_world.aurora&q=
uot;, when the command appears to now be &quot;aurora job create&quot; (rat=
her than just &quot;aurora create&quot;).=C2=A0 Something to update.</div><=
div><br></div><div>Second, the real issue - I&#39;m working through the Hel=
lo World stuff with vagrant/VirtualBox on OS X.=C2=A0 I&#39;ve got the hell=
o_world.py job running just fine, doing nothing more or less than the instr=
uctions, and it shows up in the scheduler web UI (the one running on port 8=
081). But when I click through to look at the task details - the link that =
jumps to the thermos observer (sorry, I&#39;m new to this, not sure about n=
omenclature) running on port 1338, I get a 404.=C2=A0 And if I look at the =
base URL for the observer (<a href=3D"http://192.168.33.7:1338/">http://192=
.168.33.7:1338/</a>) I get some empty tables titled like &quot;active tasks=
 0...-1 of 0&quot;.</div><div><br></div><div>Now...I&#39;m definitely only =
running one VM right now.=C2=A0 The task is running - the scheduler says so=
 and I can see the process.=C2=A0 I&#39;ve attached the various upstart log=
s that wfarner asked for - as you can see, it appears that the observer is.=
..not observing much.</div><div><br></div><div>I&#39;ve also attached an st=
race of the observer process idling and with me hitting it over the web ite=
rface (to be clear, the one with the proctitle &quot;python2.7 /home/vagran=
t/aurora/dist/thermos_observer.pex --root=3D/var/run/thermos --port=3D1338 =
--log_to_disk=3DNONE --log_to_stderr=3Dgoogle:INFO&quot;).=C2=A0 The only t=
hing of note I see is that it&#39;s trying to hit these files under the /va=
r/run/thermos tree (the --root parameter on the command line), but there is=
 no &#39;thermos&#39; in /var/run.=C2=A0 Come to think of it, that seems si=
gnificant.</div><div><br></div><div>Halp?</div><div><br></div><div>Cheers,<=
/div><div>bigo</div></div>

--001a11c1efb86a7f9e050e76097f--

--001a11c1efb86a7fa3050e760981--