[Paraview] connectivity errors

[Burlen Loring]

Hi Rich,

Did you get it to work? You should be using the same version on both
sides. If you are setting this up for multiple people it's simpler to
use the official releases, and do version check in your server side
scripts, print a nice error message when someone connects with an
unsupported version. The scripts
<https://github.com/burlen/pvserver-configs> I wrote for NERSC Edison
have this check.

Burlen

On 07/09/2014 06:15 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US)
wrote:
> I forgot to include that I get the same behavior on both an OSX and Linux
> ParaView client - so I don’t think that it’s a client-side software issue.
>   But, what I don’t understand is what could happen on the server side to
> crash the client?
>
> I think that my cmake/build command is pretty straight forward an
> essentially identical to the cmake command I’ve used on other Cray systems:
>
> cmake \
> -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \
> -DCMAKE_BUILD_TYPE=Release \
> -DParaView_FROM_GIT=ON \
> -DENABLE_boost=ON \
> -DENABLE_cgns=OFF \
> -DENABLE_ffmpeg=ON \
> -DENABLE_fontconfig=ON \
> -DENABLE_freetype=ON \
> -DENABLE_hdf5=ON \
> -DENABLE_libxml2=ON \
> -DENABLE_matplotlib=OFF \
> -DENABLE_mesa=OFF \
> -DENABLE_mpi=ON \
> -DENABLE_numpy=ON \
> -DENABLE_osmesa=ON \
> -DENABLE_paraview=ON \
> -DENABLE_png=ON \
> -DENABLE_python=ON \
> -DENABLE_qhull=ON \
> -DENABLE_qt=OFF \
> -DENABLE_silo=ON \
> -DENABLE_szip=ON \
> -DENABLE_visitbridge=ON \
> -DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmp
> ichcxx.so" \
> -DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpic
> h.so" \
> -DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpichc
> xx.so" \
> -DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/includ
> e/" \
> -DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/include/
> " \
> -DUSE_SYSTEM_mpi=ON \
> -DUSE_SYSTEM_python=ON \
> -DUSE_SYSTEM_zlib=ON \
> ../Source
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> On 7/9/14, 9:02 AM, "Angelini, Richard C (Rick) CIV USARMY ARL (US)"
> <richard.c.angelini.civ at mail.mil> wrote:
>
>> I¹m setting up Paraview client/server  on a new Cray XC30 system.   I have
>> a totally clean build on Paraview on the Cray side, but I can¹t get the
>> client-server connection to work, and I¹m seeing a strange error.   It
>> looks like the client-server connection is being established, and then the
>> client crashes with this error:
>>
>> Accepting connection(s): my-client-host:53484
>> ERROR: In 
>> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release
>> /
>> paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxyDef
>> i
>> nitionManager.cxx, line 565
>> vtkSIProxyDefinitionManager (0x113fe5fc0): No proxy that matches:
>> group=misc and proxy=StrictLoadBalancing were found.
>>
>>
>> Segmentation fault
>>
>>
>>
>> On the server side,  I¹m getting a more standard connectivity error:
>>
>> Client connected.
>> ERROR: In 
>> /p/home/angelini/PV/Build_4.1.0_osmesa/paraview/src/paraview/VTK/Parallel/
>> C
>> ore/vtkSocketCommunicator.cxx, line 812
>> vtkSocketCommunicator (0xe2b930): Could not receive tag. 1
>>
>>
>> I know that the communication path from the compute nodes to the client
>> workstation is valid because VisIt and Ensight both work on this system.
>>
>> Any ideas?
>>
>>
>>
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
> _______________________________________________
> Powered by 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
>
> 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/20140710/a029f027/attachment-0001.html>