[Paraview] client/server display problem - on and on and on...

[Wylie, Brian]

Renato,
 
In your case (1 client) pvserver IS a data server. In fact it the best of both worlds, it's a data server until the polygonal data gets to big (passes the 10MB threshold) and then it becomes a render server, and you can dynamically change that threshold....or if for some bizarre reason you never want it to become a render server (not sure why.. but whatever) you can just turn compositing off and it will always be a data server.
 
In general the point I'm trying to make is that for 99% of the folks out there, splitting the server into a data server and a render server is a more complex, less effective solution, then just running pvserver and pvclient. If you are running pvdataserver and pvrenderserver you should have a REALLY good reason for doing so.
 
Okay have we beat this horse to death yet?  :)

Brian Wylie - Org 9227 
Sandia National Laboratories 
MS 0822 - Building 880/A1-J 
(505)844-2238 FAX(505)845-0833                       
     ____                  _    __ 
    / __ \____  _________ | |  / (_)__ _      __ 
   / /_/ / __ `/ ___/ __ `/ | / / / _ \ | /| / / 
  / ____/ /_/ / /  / /_/ /| |/ / /  __/ |/ |/ / 
 /_/    \__,_/_/   \__,_/ |___/_/\___/|__/|__/                                                   
                                    Unleash the Beast 

 


________________________________

	From: paraview-bounces+bnwylie=sandia.gov at paraview.org [mailto:paraview-bounces+bnwylie=sandia.gov at paraview.org] On Behalf Of Renato N. Elias
	Sent: Tuesday, May 16, 2006 2:19 PM
	To: 'Berk Geveci'
	Cc: paraview at paraview.org
	Subject: [Paraview] client/server display problem - Problem solved!
	
	
	problem solved :-)
	 
	my problem was solved after seeing the last posts. It was exactly due the DISPLAY enviroment variable which was set (wrongly) to localhost:10.
	 
	You know, as it was not necessary with PV 2.2.1 I got surprised after getting that error message in PV 2.4.3
	 
	Thanks a lot folks
	 
	obs.: Regarding the data server mode, for me, it is the most useful mode since I don't work with huge datasets and my client can perform all rendering work without having to download several pieces of files that were processed in parallel on the machine without rendering capability. I have a bunch of files on the processing machine that don't need to be rebuilt on the client's machine - for me, it's wonderful.
	 
	Renato N. Elias
	===============================================
	PhD student - http://www.nacad.ufrj.br/~rnelias
	High Performance Computing Center
	Federal University of Rio de Janeiro
	Rio de Janeiro, Brazil
	+55(21) 2562-8080 

________________________________

	De: Berk Geveci [mailto:berk.geveci at gmail.com] 
	Enviada em: terça-feira, 16 de maio de 2006 16:57
	Para: Renato N. Elias
	Cc: paraview at paraview.org
	Assunto: Re: [Paraview] client/server display problem
	
	
	So you are getting the same error when running pvserver and pvclient? Do me a favor, make sure that there is no DISPLAY enviromnent variable set when running in ParaView. You may have to unset it in .XXrc to override what ssh sets. I want to make sure that the reason the server is crashing is due to X not due to something else. Another way of finding out is to attach to one of the pvserver processes with a debugger. Also, does this happen when you run a 1 node server? 
	
	-Berk
	
	
	
	On 5/16/06, Renato N. Elias <rnelias at nacad.ufrj.br> wrote: 

		Berk: Well, mostly because this may not scale well. Polygonal data generated by 10 nodes might be too big to be handled by a single node. If you client can handle it, no problem
		 
		Renato: I see what you mean. My problem is that, unfortunately, we don't have render clusters here. Thus, we must try to work with the Altix as it was only a parallel data server connected to a Windows XP client machine performing all rendering work with its NVidia Quadro FX 4400 video card.
		 
		Berk: there is not pure data server in paraview
		 
		Renato: Ok. It's clear now. I guess I got confused after seeing what PV compilation produces. It builds different binaries (pvclient, pvrenderserver, pvserver and pvdataserver). Firstly I tried to connect the pvclient (on the Windows machine) with the pvserver (on the Altix system) but I got that error message (X connection to localhost:10.0 broken (explicit kill or server shutdown)). After that, I tried to connect pvclient with pvDATAserver and the problem persisted. I thought it strange since I was just repeating with PV 2.4.3 the same procedure I used to do with PV 2.2.1 (which has been running nicely in parallel, including with Ensight files which don't work fine with PV 2.4.3). 
		 
		Thanks Berk for the explanations 
		
		 
		Renato N. Elias
		===============================================
		PhD student - http://www.nacad.ufrj.br/~rnelias <http://www.nacad.ufrj.br/%7Ernelias> 
		High Performance Computing Center
		Federal University of Rio de Janeiro
		Rio de Janeiro, Brazil
		+55(21) 2562-8080 
		
		
________________________________

		De: Berk Geveci [mailto:berk.geveci at gmail.com] 
		Enviada em: terça-feira, 16 de maio de 2006 16:07
		Para: Renato N. Elias
		Cc: Wylie, Brian; paraview at paraview.org
		Assunto: Re: [Paraview] client/server display problem
		
		
		


		On 5/16/06, Renato N. Elias <rnelias at nacad.ufrj.br> wrote: 

			
			Sorry, but I'm still in doubt...
			
			Maybe my doubt is due the way I'm running the client/server mode. I should
			emphasize that I'm running in a client/DATA server mode using a SGI Altix
			which doesn't have any rendering capability. Thus, here goes my questions... 
			
			BRIAN: 1) Set up their server nodes so that they can open X windows (Sandia
			has done this on like 10 different clusters, it's not that hard, if you need
			instructions please email me).
			
			RENATO: Why? If I'm running in a client/data server scheme my data server 
			only need to load and dispatch my data to the client which should launch the
			PV GUI. I can't see why is it necessary to open X windows in this case.



		Well, mostly because this may not scale well. Polygonal data generated by 10 nodes might be too big to be handled by a single node. If you client can handle it, no problem. There is not client/data server scheme. You either have client/data server/render server or client/server modes. If you are running in client/server modes, the server is capable of both processing and rendering. If you don't want the server to render, disable compositing. At that point, there is no need for opengl or X display on the server. 
		


			BRIAN: 2) Compile the server with Mesa (note: the client should never be
			compiled with Mesa) 
			
			RENATO: The question remains. Is it really necessary to compile PV with Mesa
			support in a system without rendering capability?



		It is not necessary. It is optional. If you are not going to render anything on the server, compile with whatever opengl library you want. Unfortunately, there is not pure data server in paraview. All servers have to be linked against some opengl library, even if it is not used. 
		
		





-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/paraview/attachments/20060516/529cbdd8/attachment.htm