[Paraview] ParaviewWeb on EC2

[Sebastien Jourdain]

If you just want to run it on your desktop, just download a ParaView binary
and you will be all set.

The only thing with Ubuntu 16, is that the documentation explaining how to
make services and configure apache might be slightly off.
Also the ansible provisioning script won't work, but everything can be done
by hand without too much issue.

Seb

On Wed, Aug 9, 2017 at 12:19 PM, Evans, Llion <Llion.Evans at ukaea.uk> wrote:

> Ok, thanks. I guess to get it to work on the free tier I’d need to rebuild
> with mesa. I’d rather not go down that path as I’m not knowledgeable enough.
>
>
>
> That means I need to go back to trying to install on my local machine, but
> I was having difficulty getting Visualizer to start properly on Ubuntu 16.
>
>
>
> I notice you mentioned a compatibility issue with 16. Will this work on a
> VM? If so, I could try copying some of the file structure from the AMI to a
> fresh Ubuntu 14 VM install?
>
>
>
> Llion
>
>
>
> *From:* Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com]
> *Sent:* 09 August 2017 17:07
>
> *To:* Evans, Llion
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] ParaviewWeb on EC2
>
>
>
> Yes, you need a g2
>
>
>
> On Wed, Aug 9, 2017 at 10:10 AM, Evans, Llion <Llion.Evans at ukaea.uk>
> wrote:
>
> I found the error below (there was a new entry for each time I refreshed
> the page on the browser).
>
>
>
> ERROR: In /home/kitware/Dashboards/buildbot/paraview-debian4dash-
> linux-shared-release_qt4_superbuild/source-paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx,
> line 333
>
> vtkXOpenGLRenderWindow (0x64982b0): bad X server connection. DISPLAY=:0.0.
> Aborting.
>
>
>
> I assume that this is due to my choice of machine (i.e. using the aws free
> tier which doesn’t have a gpu).
>
>
>
> Llion
>
>
>
> *From:* Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com]
> *Sent:* 09 August 2017 14:48
> *To:* Evans, Llion
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] ParaviewWeb on EC2
>
>
>
> Did you look at the logs on the server to see if you could have some hints
> on what could be the issue?
>
>
>
> On Wed, Aug 9, 2017 at 8:32 AM, Evans, Llion <Llion.Evans at ukaea.uk> wrote:
>
> Hi Seb/Claude,
>
> Hopefully this should be an easy answer.
>
> I’ve been trying to get Visualizer up and running on aws. I used the ami
> mentioned below (ami-34f3f65e) and can load the page in a browser which
> brings up the 'ParaViewWeb' logo and a spinning cog. After a short while I
> get an error message 'Session did not start before timeout expired. Check
> session logs.'
>
> Other than installing a local browser I've not changed much of anything on
> the AMI. What am I doing wrong? I assume it's something simple that I'm
> missing, like do I need to drop in a dataset somewhere before it'll even
> load the page?
>
> Kind regards,
> Llion
> _______________________________________________
> 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/20170809/a3678490/attachment.html>