[Paraview] Error when connecting to pvserver (pv 4.3.1)
Utkarsh Ayachit
utkarsh.ayachit at kitware.com
Sun Apr 12 14:29:05 EDT 2015
Are the client and server created using the similar build flags? One
guess would be that you don't have MPI enabled on the server, but you
do have it enabled on the client build. Is that correct?
Utkarsh
On Sat, Apr 11, 2015 at 12:45 PM, Schlottke, Michael
<M.Schlottke at aia.rwth-aachen.de> wrote:
> Hi,
>
> I just installed PV 4.3.1 from source as I need to compile some custom
> plugins. Using the GUI client in a standalone fashion is no problem and
> everything works as expected. However, I’ve had difficulties when trying to
> connect to a pvserver instance.
>
> The server dies with the following error messages:
> #######################################
> Waiting for client...
> Connection URL: cs://aia257:11111
> Accepting connection(s): aia257:11111
> Client connected.
> Warning: In
> /home/mic/.pool/.src/ParaView-v4.3.1-source/ParaViewCore/ClientServerCore/Rendering/vtkPVClientServerSynchronizedRenderers.cxx,
> line 170
> vtkPVClientServerSynchronizedRenderers (0x1dfa530): Could not create the
> compressor by name .
>
> ERROR: In
> /home/mic/.pool/.src/ParaView-v4.3.1-source/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
> line 878
> vtkSocketCommunicator (0xbe1f50): Tag mismatch: got 10, expecting 1.
>
> Exiting…
> #######################################
>
> While the client spills out a ton of messages like the following and finally
> dies with “xcb_io.c…” error:
>
> #######################################
> X Error: GLXBadContextTag 152
> Extension: 145 (Uknown extension)
> Minor opcode: 115 (Unknown request)
> Resource id: 0x1
> X Error: GLXBadContextTag 152
> Extension: 145 (Uknown extension)
> Minor opcode: 1 (Unknown request)
> Resource id: 0x1
> X Error: GLXBadContextTag 152
> Extension: 145 (Uknown extension)
> Minor opcode: 145 (Unknown request)
> Resource id: 0x1
> paraview: xcb_io.c:549: _XRead: Assertion `dpy->xcb->reply_data != ((void
> *)0)' failed.
> #######################################
>
> Any ideas what I’m doing wrong? This happens directly on attempting to
> connect. I’ve added the configure command I used below.
>
> Thanks a lot in advance,
>
> Michael
>
>
> P.S:
>
> Used command to configure ParaView:
> CC=gcc CXX=g++ cmake $PV_SRC \
> -DBUILD_DOCUMENTATION:BOOL=ON \
> -DBUILD_SHARED_LIBS:BOOL=ON \
> -DCMAKE_BUILD_TYPE:STRING=Release \
> -DCMAKE_INSTALL_PREFIX:PATH=$PREFIX \
> -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
> -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON \
> -DPARAVIEW_USE_MPI:BOOL=ON \
> -DPYTHON_LIBRARY:FILEPATH=$PYTHON27/lib/libpython2.7.so \
> -DPYTHON_INCLUDE_DIR:PATH=$PYTHON27/include/python2.7
>
>
> --
> Michael Schlottke
>
> Chair of Fluid Mechanics and Institute of Aerodynamics
> RWTH Aachen University
> Wüllnerstraße 5a
> 52062 Aachen
> Germany
>
> Phone: +49 (241) 80 95188
> Fax: +49 (241) 80 92257
> Mail: m.schlottke at aia.rwth-aachen.de
> Web: http://www.aia.rwth-aachen.de
>
>
> _______________________________________________
> 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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
More information about the ParaView
mailing list