<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I'm definitely up for the challenge. Thanks for referring the
current issues that will help. I am not familiar with Ansible, I'll
definitely give it a try then.<br>
<br>
I'll try the following:<br>
* make a public AMI for Ubuntu 16.04 - paraview-5.2<br>
* port the Ansible book to Ubuntu 16.04<br>
<br>
I'll keep you posted.<br>
Thank you Sebastien!<br>
claude<br>
<br>
<br>
<div class="moz-cite-prefix">On 01/20/2017 09:46 AM, Sebastien
Jourdain wrote:<br>
</div>
<blockquote
cite="mid:CABObKxc5XLt9o+ZQs4gPny+4KqRBSu=YL16oQd+UZxAFeka_4g@mail.gmail.com"
type="cite">
<div dir="ltr">Thanks Claude for your feedback and I'm happy to
ear that's working.
<div><br>
</div>
<div>We haven't moved to Ubuntu 16.04 so far due to the lack of
time and the fact that services management is different.</div>
<div><br>
</div>
<div>For Ubuntu 14.04, you can use our ansible provisioning
script here: <a moz-do-not-send="true"
href="http://kitware.github.io/paraviewweb/docs/ansible.html">http://kitware.github.io/paraviewweb/docs/ansible.html</a></div>
<div>But as I said, it won't fully work on 16.04, but if you are
up for it, you can always fix it for 16.04 and contribute
back.</div>
<div><br>
</div>
<div>Moreover, we still have some manual step for the driver as
the user should pick the right driver.</div>
<div><br>
</div>
<div>You might also find some useful information here too: <a
moz-do-not-send="true"
href="https://github.com/Kitware/paraviewweb/issues/319"><a class="moz-txt-link-freetext" href="https://github.com/Kitware/paraviewweb/issues/319">https://github.com/Kitware/paraviewweb/issues/319</a></a></div>
<div><br>
</div>
<div>Good luck,</div>
<div><br>
</div>
<div>Seb</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Jan 20, 2017 at 8:33 AM, claude
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:claude@theweak.link" target="_blank">claude@theweak.link</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hi Sebastien,<br>
<br>
sorry to make you dig into old memories :S<br>
so far I have been able to achieve the goals thanks to the
documentation and help. Last thing I tried was to connect
the visualizer to pv server in parallel. The help contents
(--help) of bin/pvserver and the pvw-visualizer.py helped
me to figure it out (all I had to do is use "reverse
connection" and have pvserver connect to paraviewweb).<br>
<br>
I don't think it's possible to document every single
possibility and that's where the code quality+comment and
built-in help are very useful and complete. I will let you
know if I find anything but so far so amazingly good.<br>
<br>
<br>
Regarding the EC2 at startup (pvw-start service running
/data/start.sh), only DNS_NAME (<a moz-do-not-send="true"
href="http://ec2-xxxx-compute1-amazonaws.com"
target="_blank">ec2-xxxx-compute1-amazonaws.<wbr>com</a>)
is fetched and replaced in the
{apache/launcher}-TEMPLATE.{<wbr>conf/json} files. I
didn't see any other variable in there. <br>
<br>
After checking with JSONLint, the launcher JSON file is
indeed valid.<br>
<br>
Paying more attention to the network requests, I don't see
the failed GET and WS switching protocol requests anymore.
Even more strange, when I move the camera, I can see the
stack of black/blank frames being send by the server (axis
are not visible either).<br>
<br>
By the way I used this config:<br>
* apache.conf<span class=""><br>
RewriteCond %{QUERY_STRING}
^sessionId=(.*)&path=(.*)$ [NC]<br>
RewriteRule ^/proxy.*$ <a moz-do-not-send="true"
class="m_-1814509315359930843moz-txt-link-freetext">ws://$</a>{session-to-port:%1}/%2
[P]<br>
<br>
</span> * launcher.json<span class=""><br>
"sessionURL" : <a moz-do-not-send="true"
class="m_-1814509315359930843moz-txt-link-rfc2396E">"ws://DNS_NAME/proxy?<wbr>sessionId=${id}&path=ws"</a>,<br>
<br>
</span> As I am writing this, I just restarted the
instance (terminate+launch) instead of reboot and it is
now working... I went back to see the logs of failed
remote viewing and I can now see this at the very end
(after proper launching and everything):<br>
<font size="-1" face="Courier New, Courier, monospace">XIO:
fatal IO error 0 (Success) on X server ":0.0"</font><br>
<br>
So here is what I am guessing:<br>
- I messed up something in the config files yesterday as I
didn't get to that point<br>
- rebooting the instance doesn't start X properly, which
fails to render the 3D view and explains why the frames
are blank but everything else is fine. <br>
- somehow re-launching the instance starts X properly.<br>
<br>
I am puzzled but also happy that it seems to be working :)<br>
Do you know what would be the reasons for this issue with
X? Since I started from the pv AMI, I didn't have to
install any drivers nor configure the display. Maybe I'll
try a fresh AMI with ubuntu-16 and install the drivers
nvidia-367 to see if I encounter similar issues with X.<br>
<br>
Thanks for the pointers Sebastien.<br>
<br>
cheers,<br>
Claude
<div>
<div class="h5"><br>
<br>
<div class="m_-1814509315359930843moz-cite-prefix">On
01/19/2017 06:19 PM, Sebastien Jourdain wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi Claude,
<div><br>
</div>
<div>I'm glad you like our doc and code. If you
feel we are missing something that is not
obvious, please report it so we can fix it.</div>
<div><br>
</div>
<div>Regarding your issue, you had a good reflex
in fixing apache and the launcher config, as
with PV5.2 we use a second ws connection for
streaming the images in binary format. But it
has been forever since I setup that ami, I have
very little memory of what was setup.</div>
<div><br>
</div>
<div>I do know that we use 'sed' to dynamically
replace some string so the proper HOST for
apache and the launcher get used, but I don't
remember if it was <span
style="font-size:12.8px">DNS_NAME or something
else</span>. But from what I understand,
you've done exactly what I would have done
myself.</div>
<div><br>
</div>
<div>I'm wondering if when you edited your
launcher config you managed to produce an
invalid JSON file. (You can paste it here <a
moz-do-not-send="true"
href="http://jsonlint.com/" target="_blank"><a class="moz-txt-link-freetext" href="http://jsonlint.com/">http://jsonlint.com/</a></a>
to be sure)</div>
<div><br>
</div>
<div>Moreover, seeing the network calls of the web
page that don't even load might be useful. I'd
be curious to see the response of the POST on
/paraview.</div>
<div><br>
</div>
<div>Seb</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jan 19, 2017 at
5:01 PM, claude <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:claude@theweak.link"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:claude@theweak.link">claude@theweak.link</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">Hello!<br>
<br>
Following up one of the previous thread on
setting up<br>
ParaviewWeb+Visualizer, I am trying to get it
going on AWS EC2 with<br>
paraview-5.2. Maybe someone already went
through it and know how to<br>
solve this little problem?<br>
<br>
* I launched the public AMI (ami-34f3f65e) on
Ubuntu-14 with paraviewweb<br>
4.4 which seemed like a good starting point.<br>
* I tested the visualizer on paraviewweb-4.4
and works perfectly.<br>
* I downloaded paraviewweb-5.2 and updated the
'pv' and 'www' symlinks<br>
under /data folder (see 'aws_data_dir'
snapshot attached).<br>
* I also updated the paths in the start.sh,
apache-TEMPLATE.conf and<br>
launcher-TEMPLATE.json files so that they
reflect the correct path for<br>
paraview-5.2 (which are bit different than
paraview-4.4). By the way,<br>
having start.sh running as a service at
startup configuring properly the<br>
TEMPLATE files with the proper DNS name is
admirable (each time I look<br>
at the doc, config files or code, I am amazed
by the quality of it,<br>
thumb up!).<br>
* when I navigate to the EC2 DNS, the
Visualizer comes up and I can<br>
browse for data files. The files seem to
successfully load but nothing<br>
show up in the camera (see snapshot
'aws_ec2_visu'). Looking at the logs<br>
on the machine, they don't report any error
(and look similar to what I<br>
can get locally on my machine). There is a
couple of errors showing up<br>
in the web console though (in the snapshot
attached).<br>
<br>
It looks like I am very close to make it work,
I am probably missing<br>
something obvious.<br>
I tried the following to solve it by using my
configuration on my local<br>
machine:<br>
1. update the apache-TEMPLATE.conf with the
following rules:<br>
RewriteCond %{QUERY_STRING}
^sessionId=(.*)&path=(.*)$ [NC]<br>
RewriteRule ^/proxy.*$ <a
moz-do-not-send="true"
class="m_-1814509315359930843moz-txt-link-freetext"><a class="moz-txt-link-freetext" href="ws://$">ws://$</a></a>{session-to-port:%1}/%2
[P]<br>
<br>
2. update the launcher-TEMPLATE.json with the
following line:<br>
"sessionURL" : "<a moz-do-not-send="true"
class="m_-1814509315359930843moz-txt-link-freetext">ws://DNS_NAME/proxy</a>?sessionId<wbr>=${id}&path=ws",<br>
<br>
3. reboot (so that the files get updated)<br>
<br>
but this time the UI doesn't even load,
meaning I made it worse.<br>
<br>
It seems just like a websocket connection
issue, right?<br>
<br>
Thanks in advance for any ideas to try.<br>
cheers<br>
<span class="m_-1814509315359930843HOEnZb"><font
color="#888888">claude<br>
</font></span><br>
______________________________<wbr>_________________<br>
Powered by <a moz-do-not-send="true"
href="http://www.kitware.com"
rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a
moz-do-not-send="true"
class="m_-1814509315359930843moz-txt-link-freetext"
href="http://www.kitware.com/"
target="_blank"><a class="moz-txt-link-freetext" href="http://www.kitware.com/">http://www.kitware.com/</a></a>opensou<wbr>rce/opensource.html<br>
<br>
Please keep messages on-topic and check the
ParaView Wiki at: <a moz-do-not-send="true"
href="http://paraview.org/Wiki/ParaView"
rel="noreferrer" target="_blank">http://paraview.org/Wiki/ParaV<wbr>iew</a><br>
<br>
Search the list archives at: <a
moz-do-not-send="true"
href="http://markmail.org/search/?q=ParaView"
rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="http://markmail.org/search/?q=">http://markmail.org/search/?q=</a><wbr>ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a moz-do-not-send="true"
href="http://public.kitware.com/mailman/listinfo/paraview"
rel="noreferrer" target="_blank">http://public.kitware.com/mail<wbr>man/listinfo/paraview</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>