[Paraview] Possible bug in client/server mode regarding file opening.

Andrew Maclean a.maclean at cas.edu.au
Fri May 13 02:17:35 EDT 2005 

The file opening problem seems to be fixed, thanks for that. 

With restpect to saving the animation, I have the client on the XP box (
pvclient -sh=linux_box ) and the server on a debian box ( pvserver
-ch=xp_box ).

I am saving a mp2 file 66s long with a resolution of around 717 by 619
pixels.  This saves OK producing an mp2 file of around 21Mb, but anything
larger resolution fails. It looks to be a memory allocation problem because
memory usage rises to around 1.8Gb on the XP machine and 1GB on the server.


Thanks

Andrew



-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Friday, 13 May 2005 07:50
To: Andrew Maclean
Cc: 'Amy Squillacote'; paraview at paraview.org
Subject: Re: [Paraview] Possible bug in client/server mode regarding file
opening.

The problem with opening a data file on the server has now been fixed 
(in CVS).

However, I was not able to reproduce the problem saving an animation. I 
had my client on a Win XP box and a server (run with mpirun -np 2) on a 
Debian box. ( I tried the opposite as well : server on Win XP and client 
on debian).

Can you verify if the animation saving problem has been fixed? If not 
could you please describe a reproducable scenario.

Thanks,
Utkarsh

Andrew Maclean wrote:
> It is the development version. When I attempt to open a file on the server
(
> A Debian Linux box) I get the following message on the client ( XP ):
> ----------------------
> There was a VTK Error in file:  vtk ParaView Servers ServerManager
> vtkSMIntVectorProperty.cxx (283)
>  No default value is specified for property: ActiveFileIsDirectory. This
> might lead to stability problems
> There was a VTK Error in file:  vtk ParaView Servers ServerManager
> vtkSMIntVectorProperty.cxx (283)
>  No default value is specified for property: ActiveFileIsReadable. This
> might lead to stability problems
> ----------------------
> 
> If I quit and restart, then there are no error messages and everything
seems
> to be OK. Hoerver ... after a while ... if you are saving an animation to
> disk I get this error message:
> --------------------------
> There was a VTK Error in file:  vtk ParaView Gui Client
vtkPVApplication.cxx
> (1686)
>  TclTk error: Uncaught exception: bad allocation
> --------------------------
> 
> Something has recently changed because the program used to just crash.
> 
> 
> Regards
>    Andrew
> 
> -----Original Message-----
> From: Amy Squillacote [mailto:amy.squillacote at kitware.com] 
> Sent: Wednesday, 11 May 2005 22:31
> To: Andrew Maclean
> Cc: paraview at paraview.org
> Subject: RE: [Paraview] Possible bug in client/server mode regarding file
> opening.
> 
> Hi Andrew,
> 
> I'm posting this back to the ParaView users' list.  This way other people 
> have the benefit of seeing the whole thread.
> 
> When you were having problem connecting an XP client to a linux server,
was 
> it in the development version or in 2.0?
> 
> - Amy
> 
> At 07:11 PM 5/10/2005, Andrew Maclean wrote:
> 
>>Thanks Amy,
>>  It is certainly fixed in the development version.
>>
>>   I haven't had a chance to look further but at one stage I experimented
>>connecting a client on XP to a Linux box. If I remember correctly opening
>>sources like spheres worked Ok but opening files failed. I think it should
>>be possible to do this. I am running a samba server on the linux box and I
>>have no trouble opening/editing files at all either XP->Linux or
Linus->XP.
>>If you get a chance please try it out. I'll probably have a chance
sometime
>>on the weekend to try it again.
>>
>>
>>Have a great day
>>   Andrew
>>
>>
>>-----Original Message-----
>>From: Amy Squillacote [mailto:amy.squillacote at kitware.com]
>>Sent: Wednesday, 11 May 2005 03:01
>>To: joseph insley; Utkarsh Ayachit
>>Cc: Andrew Maclean; paraview-anl at mcs.anl.gov; paraview at paraview.org
>>Subject: Re: [Paraview] Possible bug in client/server mode regarding file
>>opening.
>>
>>Hi Joe,
>>
>>According to Utkarsh, this bug was introduced into ParaView after ParaView
>>2.0 was released, so this should not be an issue in ParaView 2.0.1.
>>
>>- Amy
>>
>>At 11:43 AM 5/10/2005, joseph insley wrote:
>>
>>
>>>I saw that a fix for this bug was committed to CVS, but was wondering
>>>when we can expect to see a release which contains the fix.
>>>
>>>Also, is this a failure that happens every time ParaView 2.0.1 is run
>>>in client/server mode?  Or was there some rare condition that was met
>>>that most users will not run into?  We are deploying ParaView in a
>>>production environment, and are trying to decide whether we should go
>>>with 2.0.1, or wait for the next release.
>>>
>>>Thanks,
>>>joe.
>>>
>>>
>>>On Apr 23, 2005, at 7:33 PM, Utkarsh Ayachit wrote:
>>>
>>>
>>>>That's a bug. Thanks.
>>>>I will commit a fix to the CVS tomorrow morning.
>>>>
>>>>Utkarsh
>>>>
>>>>Andrew Maclean wrote:
>>>>
>>>>>I don't know whether this is a bug or something wrong that I am doing
>>>>>as I
>>>>>am not very experienced with ParaView.
>>>>>Assume that I have machine A as the client and machine B as the
>>>>>server.
>>>>>So on B I type:
>>>>>pvserver -ch=A
>>>>>On A I type:
>>>>>pvclient -sh=B
>>>>>Everything works OK if I use one of the existing sources like the
>>>>>sphere
>>>>>source. Rendering seems to go OK and there seem to be no problems.
>>>>>However if I try to open a file the server crashes with the following
>>>>>message:
>>>>>----------------------------------------------------------------------
>>
>>----
>>
>>>>>pvserver -ch=a
>>>>>Listen on port: 11111
>>>>>Waiting for client...
>>>>>connected to port 11111
>>>>>Client connected.
>>>>>ERROR: In
>>>>>/usr/local/src/vtk/ParaView/Servers/Common/vtkProcessModule.cxx,
>>>>>line540
>>>>>vtkPVClientServerModule (0x9a7a420): Object type:
>>>>>vtkPVServerFileListing,
>>>>>couldnot find requested method: "GetActiveFileIsDirectory"
>>>>>or the method was called with incorrect arguments.
>>>>>while processing
>>>>>Message 0 = Invoke
>>>>>  Argument 0 = id_value {677}
>>>>>  Argument 1 = string_value {GetActiveFileIsDirectory}
>>>>>ERROR: In
>>>>>/usr/local/src/vtk/ParaView/Servers/Common/vtkProcessModule.cxx,
>>>>>line542
>>>>>vtkPVClientServerModule (0x9a7a420): Aborting execution for debugging
>>>>>purposes.
>>>>>Aborted
>>>>>----------------------------------------------------------------------
>>
>>----
>>
>>>>>I can open directories on the remote machine and read/write to files
>>>>>OK. So
>>>>>is it something that I am doing wrong? It seems to me that paraview is
>>>>>unable to open a directory on the remote machine for some reason.
>>>>>Thanks for any help
>>>>>Andrew
>>>>>_______________________________________________
>>>>>ParaView mailing list
>>>>>ParaView at paraview.org
>>>>>http://www.paraview.org/mailman/listinfo/paraview
>>>>
>>>>_______________________________________________
>>>>ParaView mailing list
>>>>ParaView at paraview.org
>>>>http://www.paraview.org/mailman/listinfo/paraview
>>>>
>>>
>>>===================================================
>>>joseph a. insley
>>>insley at mcs.anl.gov
>>>mathematics & computer science division      (630) 252-5649
>>>argonne national laboratory                              (630) 252-5986
>>>(fax)
>>>
>>>_______________________________________________
>>>ParaView mailing list
>>>ParaView at paraview.org
>>>http://www.paraview.org/mailman/listinfo/paraview
> 
> 
> 
> 
> 
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>

More information about the ParaView mailing list