[Paraview] ParaviewWeb on EC2

[Sebastien Jourdain]

Hi Claude,

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.

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.

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 DNS_NAME or something else. But from what I understand, you've done
exactly what I would have done myself.

I'm wondering if when you edited your launcher config you managed to
produce an invalid JSON file. (You can paste it here http://jsonlint.com/
to be sure)

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.

Seb


On Thu, Jan 19, 2017 at 5:01 PM, claude <claude at theweak.link> wrote:

> Hello!
>
> Following up one of the previous thread on setting up
> ParaviewWeb+Visualizer, I am trying to get it going on AWS EC2 with
> paraview-5.2. Maybe someone already went through it and know how to
> solve this little problem?
>
> * I launched the public AMI (ami-34f3f65e) on Ubuntu-14 with paraviewweb
> 4.4 which seemed like a good starting point.
> * I tested the visualizer on paraviewweb-4.4 and works perfectly.
> * I downloaded paraviewweb-5.2 and updated the 'pv' and 'www' symlinks
> under /data folder (see 'aws_data_dir' snapshot attached).
> * I also updated the paths in the start.sh, apache-TEMPLATE.conf and
> launcher-TEMPLATE.json files so that they reflect the correct path for
> paraview-5.2 (which are bit different than paraview-4.4). By the way,
> having start.sh running as a service at startup configuring properly the
> TEMPLATE files with the proper DNS name is admirable (each time I look
> at the doc, config files or code, I am amazed by the quality of it,
> thumb up!).
> * when I navigate to the EC2 DNS, the Visualizer comes up and I can
> browse for data files. The files seem to successfully load but nothing
> show up in the camera (see snapshot 'aws_ec2_visu'). Looking at the logs
> on the machine, they don't report any error (and look similar to what I
> can get locally on my machine). There is a couple of errors showing up
> in the web console though (in the snapshot attached).
>
> It looks like I am very close to make it work, I am probably missing
> something obvious.
> I tried the following to solve it by using my configuration on my local
> machine:
> 1. update the apache-TEMPLATE.conf with the following rules:
> RewriteCond %{QUERY_STRING} ^sessionId=(.*)&path=(.*)$ [NC]
> RewriteRule ^/proxy.*$ ws://${session-to-port:%1}/%2 [P]
>
> 2. update the launcher-TEMPLATE.json with the following line:
> "sessionURL" : "ws://DNS_NAME/proxy?sessionId=${id}&path=ws",
>
> 3. reboot (so that the files get updated)
>
> but this time the UI doesn't even load, meaning I made it worse.
>
> It seems just like a websocket connection issue, right?
>
> Thanks in advance for any ideas to try.
> cheers
> claude
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170119/b35acd18/attachment-0001.html>