[Paraview] Visualizing a Cone with PVW - Connection can't be established

[Sebastien Jourdain]

Everything should be explained here:
http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04

But for that you need to have apache 2.4.6+ and make sure the launcher
configuration and apache one match.

Launcher side:

"sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect
to apache)/proxy?sessionId=${id}",

"proxy_file": "/data/proxy.txt"

Apache side

RewriteMap  session-to-port  txt:/data/proxy.txt

Then when a session start you can check the content of that /data/proxy.txt
and that should one line by running session with {sessionId} localhost:yyyyy

On the other hand you forgot that line in the config of your cone app:
"ready_line" : "Starting factory"

You can check is any pvpython process is running, on which port, see if
that match in the proxy file (/data/proxy.txt) and also looking at the log
directory with the output of the pvpython process.

A common error could also be that the apache does not have the right to
read the /data/proxy.txt file or that the launcher is not able to write it.

Good luck,

Seb


On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <duplyakin at uchicago.edu>
wrote:

> Hi all,
>
> My name is Dmitry Duplyakin. I am a PhD student helping to build a
> ParaViewWeb system at University of Chicago.
>
> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2 Ubuntu 12.04
> instances.
>
> We have verified that PV builds without errors and that PVW launcher is
> functioning (new entries are added to the proxy file, vis sessions are
> created and are listening to ports in the specified range, etc.)
>
> We are trying to visualize a simple cone:
> (added app in launch.json)
> "cone": {"cmd": ["${python_exec}",
> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
> "${port}"]}},
>
> We have verified that vtk_web_cone.py actually gets called. In order to
> test it, we used /pv/www/apps/TestApp/index.html as a template and created
> /pv/www/apps/Cone/index.html where we have:
> ...
>   var config = {
>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>     application: "cone"
>   };
> ...
>
> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
> we either get a timeout or "connection can't be established" message.
>
> In the apache error log we see:
> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] proxy: Error
> reading from remote server returned by /paraview/, referer:
> http://54.211.22.94/apps/Cone/
> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] File does not
> exist: /pv/www/ws
>
> It appears that it has do to with Apache configuration, where we have:
> ProxyPass        /paraview http://localhost:8080/paraview
> ProxyPassReverse /paraview http://localhost:8080/paraview
> RewriteEngine On
> RewriteMap session-to-port txt:/pv/conf/proxy.conf
> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>
> Do these Rewrite commands look right? How can their actions be logged and
> verified?
>
> Do we actually need ProxyPassReverse here?
>
> Is it possible that we are missing a module or some additional
> configuration in Apache?
> # apachectl -t -D DUMP_MODULES
> ...
>  proxy_module (shared)
>  proxy_http_module (shared)
>  proxy_wstunnel_module (shared)
>  rewrite_module (shared)
> ...
> Syntax OK
>
> Any debugging advice?
>
> Your help will be much appreciated and will allow to move forward with our
> isntallation.
>
>
> -------------------------------------------------------------------------------
>
> Dmitry Duplyakin
> PhD student, CS at University of Colorado - Boulder
>
>
> _______________________________________________
> 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
>
> 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/20140720/4d7db56c/attachment.html>