[Paraview] Setting up Paraview Web on a headless Fedora server with GPU
Jiří Vyskočil
jiri.vyskocil at fjfi.cvut.cz
Fri May 6 11:49:30 EDT 2016
Ha! I got it - I had apache configured as SSL-only. That is: http at port 80 was hard redirected to
https at port 443. I changed the config to only use http, and now it works. For now that's not
critical - this is an experimental server accessible only from our internal network, I can try to
fix this later.
Now I'll start playing with the visualizer app. So far it seems to work pretty well - I just need to
make it use all available resources (it just runs sigle-core).
Thank you for your help, Sebastien!
For the record, this was the apache config that didn't work:
NameVirtualHost *:80
<VirtualHost *:80>
ServerName vbl-sim.eli-beams.eu
Redirect permanent / https://vbl-sim.eli-beams.eu/
</VirtualHost>
NameVirtualHost *:443
<VirtualHost *:443>
ServerName vbl-sim.eli-beams.eu
ServerAdmin jiri.vyskocil at eli-beams.eu
DocumentRoot /usr/local/share/paraview-5.0/www/
ErrorLog "logs/pv-error_log"
CustomLog "logs/pv-access_log" common
<Location /usr/local/share/paraview-5.0/www/>
SSLRequireSSL On
SSLVerifyClient optional
SSLVerifyDepth 1
SSLOptions +StdEnvVars +StrictRequire
</Location>
ProxyPass /paraview http://localhost:9000/paraview
RewriteEngine On
RewriteMap session-to-port txt:/etc/httpd/paraview-mapping/proxy.txt
RewriteCond %{QUERY_STRING} ^sessionId=(.*)$ [NC]
RewriteRule ^/proxy.*$ ws://${session-to-port:%1}/ws [P]
SSLEngine on
SSLCertificateFile /etc/pki/tls/certs/vblpar.crt
SSLCertificateKeyFile /etc/pki/tls/private/vblpar.key
<Directory /usr/local/share/paraview-5.0/www/>
Options Indexes FollowSymLinks
Order allow,deny
Allow from all
AllowOverride None
Require all granted
</Directory>
</VirtualHost>
On 06/05/16 16:54, Sebastien Jourdain wrote:
> You are getting really close...
>
> Basically you have the ParaView process that properly started at the request of the client and
> waits to it to connect, which never happen.
>
> Usually that mean, you have a mistake either in your Apache config and/or in your launcher.
>
> Could you share your Apache virtual host with your launcher config along with the URL the web
> client connects to?
>
> Seb
>
> On Fri, May 6, 2016 at 5:47 AM, Jiří Vyskočil <jiri.vyskocil at fjfi.cvut.cz
> <mailto:jiri.vyskocil at fjfi.cvut.cz>> wrote:
>
> One more step closer to the goal it seems - if run:
>
>
> export XAUTHORITY=/var/run/slim/slim.auth
> DISPLAY=:0 xhost +
>
>
> as root, I can get the launcher to start, and not die with an X-related error (cumbersome
> workaround, but I guess I can find a better way later).
>
>
> [paraview at vbl-sim ~] $ cat /etc/httpd/paraview-mapping/proxy.txt
> be12802a-137f-11e6-b12c-002590e6af35 vbl-sim.eli-beams.eu:9003 <http://vbl-sim.eli-beams.eu:9003>
>
> [paraview at vbl-sim ~] $ ps aux | grep pvpython
> paraview 1792 1.2 0.1 1393740 144956 pts/1 S+ 13:42 0:02
> /usr/local/lib/paraview-5.0/pvpython
> /usr/local/lib/paraview-5.0/site-packages/vtk/web/launcher.py
> /etc/httpd/paraview-launcher.config -d
> paraview 1887 1.6 0.1 1519164 237520 pts/1 Sl+ 13:43 0:02
> /usr/local/lib/paraview-5.0/pvpython -dr
> /usr/local/lib/paraview-5.0/site-packages/paraview/web/pv_web_visualizer.py --port 9003
> --data-dir /var/paraview/data -f --authKey 3ZXwyWwTz7aPjT9p
>
>
> Now when I try to open an app from the browser, it still doesn't work (waits forever to load
> some part, etc.), and I see thist in the paraview log:
>
>
> [strazce at vbl-sim ~] $ cat /var/log/paraview-viz-logs/be12802a-137f-11e6-b12c-002590e6af35.txt
> 2016-05-06 13:43:27+0200 [-] Log opened.
> 2016-05-06 13:43:27+0200 [-] Site starting on 9003
> 2016-05-06 13:43:27+0200 [-] Starting factory <twisted.web.server.Site instance at 0x7fd34014f3b0>
> 2016-05-06 13:43:27+0200 [-]
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2016-05-06 13:43:27+0200 [-]
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> and a lot of lines which contain just the repeating plus signs.
>
>
>
>
>
>
>
> On 05/05/16 16:23, Sebastien Jourdain wrote:
>> You were on the right track with DISPLAY=:0 but I'm wondering if you setup a "virtual"
>> monitor or if your "paraview" user is auto logged in a X session or if it stuck at the
>> "login" panel?
>>
>> You can find some information about the virtual screen here: (Search for "Screen")
>>
>> http://kitware.github.io/paraviewweb/docs/guides/graphics_on_ec2_g2.html
>>
>> And for the autologin if it is needed. (Note on EC2 the user start X hence no need to login...)
>>
>> https://github.com/Kitware/paraviewweb/blob/master/tools/ansible/roles/paraview/tasks/Ubuntu.yml
>>
>> Seb
>>
>> On Thu, May 5, 2016 at 6:58 AM, Jiří Vyskočil <jiri.vyskocil at fjfi.cvut.cz
>> <mailto:jiri.vyskocil at fjfi.cvut.cz>> wrote:
>>
>> Hello,
>>
>>
>> I'm trying to set up a Paraview Web server on a Fedora 23 machine. The serves is not
>> connected to a monitor or a keyboard (I only have access through ssh), but it has a
>> nvidia GPU which I want to use for paraview.
>>
>>
>> I have installed xdm to run the X server, and verified that it is in fact running with
>> the correct nvidia drivers (by checking the Xorg.0.log file). The problem is I don't know
>> how to run the paraview webserver on the X display when there's no one physically logged
>> in - I can only get to the server via ssh. When I log in, and switch to the paraview
>> user, the DISPLAY and XAUTHORITY variables are empty.
>>
>>
>> The webserver itself is running (apache + the python launcher), but when I try to open
>> any of the example applications, I get an error like this:
>>
>>
>> $ ./launch-paraview.sh
>> 2016-05-05 14:54:17,528:INFO:twisted:Site starting on 9000
>> 2016-05-05 14:54:17,528:INFO:twisted:Starting factory <twisted.web.server.Site instance
>> at 0x7fe20da6a998>
>> 2016-05-05 14:55:09,655:INFO:twisted:"127.0.0.1" - - [05/May/2016:12:55:09 +0000] "POST
>> /paraview/ HTTP/1.1" 503 78 "https://vbl-sim.eli-beams.eu/apps/Visualizer/" "Mozilla/5.0
>> (X11; Fedora; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
>>
>>
>> $ cat 965318f2-12c0-11e6-a3cb-002590e6af35.txt
>> 2016-05-05 14:55:06+0200 [-] Log opened.
>> ERROR: In
>> /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx,
>> line 333
>> vtkXOpenGLRenderWindow (0x3f00be0): bad X server connection. DISPLAY=
>>
>>
>> Specifying DISPLAY=:0 when running the launcher gives this error:
>>
>> $ cat e73921bc-12c0-11e6-b002-002590e6af35.txt
>> 2016-05-05 14:57:22+0200 [-] Log opened.
>> No protocol specified
>> No protocol specified
>> No protocol specified
>> ERROR: In
>> /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx,
>> line 333
>> vtkXOpenGLRenderWindow (0x4127c10): bad X server connection. DISPLAY=:0. Aborting.
>>
>>
>>
>> Thanks for any hints,
>>
>> Jiri
>>
>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com <http://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
>>
>>
>
>
> _______________________________________________
> Powered by www.kitware.com <http://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/20160506/4b7cabf2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3733 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/4b7cabf2/attachment.bin>
More information about the ParaView
mailing list