oh, sorry.. I misunderstood your problem..<br><br>You're saying that your backend nodes have no external visibility? (eg, they can't see the client). We have that same situation here. There's a few options that I know of, other folks here may know more:
<br>1) Make sure that Process 0 of your pvserver is running on the Head-Node. Only Process-0 needs to communicate with the client.<br>2) Talk to your admins & get NAT setup on the cluster.<br><br>In short, you need to be able to get traffic between Process 0 and your client.. If you can't access the nodes, and they can't access you, then you're hosed.
<br><br><br><div><span class="gmail_quote">On 10/19/06, <b class="gmail_sendername">Weiguang Guan</b> <<a href="mailto:guanw@rhpcs.mcmaster.ca">guanw@rhpcs.mcmaster.ca</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I already built ParaView with mesa and did off-screen rendering so "no X"<br>is not an issue in my case. The problem lies on pvclient/pvserver<br>connection. And I already made it work by running pvserver only on the
<br>login node. But I really want to run ParaView in parallel.<br><br>Weiguang<br><br>--<br>========================================================<br>Weiguang Guan, Research Engineer<br>RHPCS, McMaster University<br>========================================================
<br><br>On Thu, 19 Oct 2006, Randall Hand wrote:<br><br>> Well, it wants an X server on each node for the Rendering/Compositing<br>> functions...<br>><br>> If you /really/ want to run it without X, then either compile paraview with
<br>> MangledMesa, or use pvdataserver instead of pvserver.<br>><br>> On 10/19/06, Weiguang Guan <<a href="mailto:guanw@rhpcs.mcmaster.ca">guanw@rhpcs.mcmaster.ca</a>> wrote:<br>>><br>>> Hello,<br>
>><br>>> I attempted to run ParaView on a Linux cluster. The cluster has one<br>>> special node, which user can log on and submit jobs. All the other<br>>> nodes are not accessable from outside.<br>
>><br>>> As the cluster doesn't have X on any node I was trying to run ParaView in<br>>> the client/server mode. The problem is that processes running on internal<br>>> nodes couldn't get connected with pvclient running on a desktop outside
<br>>> the cluster via port 11111 (other ports, no matter priviledged or not, are<br>>> blocked too). Did anyone encounter this situation? And what's the<br>>> solution?<br>>><br>>> I tried ssh -R to forward port 11111 of the login node of the cluster
<br>>> to that of my desktop, and start pvserver with -ch="login_node", but it<br>>> didn't work.<br>>><br>>> I would very much appreciate it if you could give me<br>>> solution/suggestion...
<br>>><br>>> Weiguang<br>>><br>>> --<br>>> ========================================================<br>>> Weiguang Guan, Research Engineer<br>>> RHPCS, McMaster University<br>>> ========================================================
<br>>> _______________________________________________<br>>> ParaView mailing list<br>>> <a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br>>> <a href="http://www.paraview.org/mailman/listinfo/paraview">
http://www.paraview.org/mailman/listinfo/paraview</a><br>>><br>><br>><br>><br>><br></blockquote></div><br><br clear="all"><br>-- <br>----------------------------------------<br>Randall Hand<br>Visualization Scientist
<br>ERDC MSRC-ITL