<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 05/22/2015 01:38 PM, Burlen Loring
wrote:<br>
</div>
<blockquote cite="mid:555F93D0.7060609@gmail.com" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Hi Jeff,<br>
<br>
It really sounds like you are unintentionally using X forwarding.
It could be baked into your ssh config or a bash alias.<br>
</blockquote>
<br>
After some digging, it appears X forwarding is configured on in our
ssh config. I got it to work by explicitly using ssh -x. Thanks for
your help.<br>
<br>
-jeff<br>
<blockquote cite="mid:555F93D0.7060609@gmail.com" type="cite">
<blockquote type="cite">I see the window with the gears</blockquote>
if you are really doing remote rendering, you won't see the
window.<br>
<br>
you may be able to confirm accidental X forward using ssh with -vv
option. there would be a bunch of X connection messages if it was
in use.<br>
<br>
also output of glxinfo may have some useful info. When I have
remote rendering setup I see<br>
<blockquote>name of display: :0.0<br>
display: :0 screen: 0<br>
direct rendering: Yes<br>
</blockquote>
with ssh -X<br>
<blockquote>name of display: localhost:10.0<br>
display: localhost:10 screen: 0<br>
direct rendering: No (If you want to find out why, try setting
LIBGL_DEBUG=verbose)<br>
</blockquote>
Burlen<br>
<br>
<div class="moz-cite-prefix">On 05/22/2015 12:10 PM, Jeff Becker
wrote:<br>
</div>
<blockquote cite="mid:555F7F22.5030702@nasa.gov" type="cite">On
05/22/2015 07:28 AM, Utkarsh Ayachit wrote: <br>
<blockquote type="cite">Jeff, <br>
<br>
Can you make sure the "Remote Render Threshold" is set to 0? <br>
</blockquote>
It is <br>
<blockquote type="cite"> <br>
Also, do you have an X server running (and accessible) on the
backend <br>
nodes? You're not using "ssh -X" to login to the backend
nodes, right? <br>
</blockquote>
<br>
I do start an X server on the backend (and I don't use ssh -X).
However, when I test the configuration using glxgears, <br>
I see the window with the gears but they don't turn even though
the app tells me how many frames <br>
it rendered every 5 seconds. <br>
<br>
My setup goes from my desktop (with GPU) through a front-end
node (without GPU) to the backend (with GPU). Maybe some
additional configuration is needed. <br>
<br>
It seems like I need to get glxgears working properly before I
try Paraview. What should I try? Thanks. <br>
<br>
-jeff <br>
<blockquote type="cite"> <br>
On Thu, May 21, 2015 at 4:54 PM, Jeff Becker <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:jeffrey.c.becker@nasa.gov"><jeffrey.c.becker@nasa.gov></a>
wrote: <br>
<blockquote type="cite">Hi. I created a VTK unstructured grid
(.vtu) file for a 500 by 500 by 500 <br>
point data set. In order to visualize it, I fire up 8
pvservers on my GPU <br>
multicore backend node using: <br>
<br>
mpirun -np 8 pvserver --client-host=XXX
--use-offscreen-rendering <br>
<br>
and connect to the root server from my ParaView client. I
then open my vtu <br>
file and hit apply, I can see the file gets read in, and
then nothing much <br>
else happens except X on my client grows to fill all of
memory, and my <br>
client system (my desktop) becomes unusable. I'm guessing
that the client is <br>
getting overwhelmed with X requests. <br>
<br>
What am I doing wrong, and how to fix? <br>
<br>
Thanks. <br>
<br>
-jeff <br>
_______________________________________________ <br>
Powered by <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="http://www.kitware.com">www.kitware.com</a> <br>
<br>
Visit other Kitware open-source projects at <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a>
<br>
<br>
Please keep messages on-topic and check the ParaView Wiki
at: <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://paraview.org/Wiki/ParaView">http://paraview.org/Wiki/ParaView</a>
<br>
<br>
Search the list archives at: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://markmail.org/search/?q=ParaView">http://markmail.org/search/?q=ParaView</a>
<br>
<br>
Follow this link to subscribe/unsubscribe: <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://public.kitware.com/mailman/listinfo/paraview">http://public.kitware.com/mailman/listinfo/paraview</a>
<br>
</blockquote>
</blockquote>
<br>
_______________________________________________ <br>
Powered by <a moz-do-not-send="true"
class="moz-txt-link-abbreviated" href="http://www.kitware.com">www.kitware.com</a>
<br>
<br>
Visit other Kitware open-source projects at <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a>
<br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://paraview.org/Wiki/ParaView">http://paraview.org/Wiki/ParaView</a>
<br>
<br>
Search the list archives at: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://markmail.org/search/?q=ParaView">http://markmail.org/search/?q=ParaView</a>
<br>
<br>
Follow this link to subscribe/unsubscribe: <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://public.kitware.com/mailman/listinfo/paraview">http://public.kitware.com/mailman/listinfo/paraview</a>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>