Frank, It does indeed look like there was a problem with the source code packaging.
A fix has been merged into the packaging script: https://gitlab.kitware.com/paraview/paraview/merge_requests/541 Thanks for helping us find it by pointing out the problem. We'll get an updated tar file posted sometime soon. Cory On Fri, Dec 18, 2015 at 2:52 PM, Cory Quammen <[email protected]> wrote: > Hi Frank, > > The official binaries of 5.0.0-RC1 on Mac work fine for me the way you > tried. Everything works fine on the master branch as well > > However, when I build the same configuration as you for the 5.0.0-RC2 tar > file on the downloads page of www.paraview.org on a Mac, I get a similar > error and a crash in the client. Partial stack trace from the client: > > 0 org.python.python 0x0000000109b6a1b6 PyObject_Call + 23 > 1 org.python.python 0x0000000109be8e83 > PyEval_CallObjectWithKeywords + 165 > 2 libvtkClientServer-pv5.0.1.dylib 0x000000010715c253 > CommandFunctionCallback(vtkClientServerInterpreter*, vtkObjectBase*, char > const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 3971 > 3 libvtkClientServer-pv5.0.1.dylib 0x000000010714600b > vtkClientServerInterpreter::CallCommandFunction(char const*, > vtkObjectBase*, char const*, vtkClientServerStream const&, > vtkClientServerStream&) + 155 > 4 libvtkClientServer-pv5.0.1.dylib 0x000000010714493b > vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream > const&, int) + 331 > 5 libvtkClientServer-pv5.0.1.dylib 0x0000000107143c45 > vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, > int) + 741 > 6 libvtkClientServer-pv5.0.1.dylib 0x000000010714392d > vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 45 > 7 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3c744 > vtkSIProperty::ProcessMessage(vtkClientServerStream&) + 52 > 8 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3bf8e > vtkSIVectorPropertyTemplate<int, int>::Push(int*, int) + 654 > 9 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3ba1f > vtkSIVectorPropertyTemplate<int, int>::ReadXMLAttributes(vtkSIProxy*, > vtkPVXMLElement*) + 271 > 10 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3eeb6 > vtkSIProxy::ReadXMLProperty(vtkPVXMLElement*) + 742 > 11 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3e9ed > vtkSIProxy::ReadXMLAttributes(vtkPVXMLElement*) + 797 > 12 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3e346 > vtkSIProxy::CreateVTKObjects(paraview_protobuf::Message*) + 2086 > 13 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3ce01 > vtkSIProxy::Push(paraview_protobuf::Message*) + 33 > 14 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e248ec > vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) + 2220 > 15 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e24ba6 > vtkPVSessionCore::PushState(paraview_protobuf::Message*) + 262 > 16 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e220f6 > vtkPVSessionBase::PushState(paraview_protobuf::Message*) + 38 > 17 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106d2630a > vtkSMSessionClient::PushState(paraview_protobuf::Message*) + 426 > 18 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106d0040c > vtkSMProxy::CreateVTKObjects() + 1276 > 19 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106d42aab > vtkSMSettingsProxy::CreateVTKObjects() + 27 > 20 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106cffa61 > vtkSMProxy::UpdateVTKObjects() + 33 > 21 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106ceccc5 > vtkSMParaViewPipelineController::PostInitializeProxy(vtkSMProxy*) + 517 > 22 libvtkPVServerManagerRendering-pv5.0.1.dylib 0x0000000109e288b3 > vtkSMParaViewPipelineControllerWithRendering::PostInitializeProxy(vtkSMProxy*) > + 51 > 23 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106cec898 > vtkSMParaViewPipelineController::UpdateSettingsProxies(vtkSMSession*) + 296 > 24 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106ce9d74 > vtkSMParaViewPipelineController::InitializeSession(vtkSMSession*) + 452 > 25 libvtkpqCore-pv5.0.1.dylib 0x0000000106688e5c > pqServerManagerModel::onConnectionCreated(long long) + 636 > > On the server, I get > > ERROR: In > /Users/cory.quammen/src/ParaView-v5.0.0-RC2-source/VTK/Parallel/Core/vtkSocketCommunicator.cxx, > line 809 > > vtkSocketCommunicator (0x7fbc2a4e8930): Could not receive tag. 1 > > I'll check around to see what might be up with the source code packaging. > > Thanks for the report, > Cory > > On Fri, Dec 18, 2015 at 10:00 AM, Albina, Frank < > [email protected]> wrote: > >> Hi Cory! >> >> Thank you very much for that. >> >> As said earlier in another post, I am very keen to see PV v5.0.0 release >> so I am happy to help and report issues before the new version gets >> unleashed. >> >> Cheers, >> >> Frank. >> >> *From:* Cory Quammen [mailto:[email protected]] >> *Sent:* Freitag, 18. Dezember 2015 15:39 >> >> *To:* Albina, Frank >> *Cc:* [email protected] >> *Subject:* Re: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend >> failing to start in parallel >> >> >> >> Frank, >> >> >> >> Thanks for the info on where you got the code. Maybe there's a problem >> with the source packaging? I'll try out that download and see if I can >> reproduce the problem. >> >> >> >> Thanks, >> >> Cory >> >> >> >> On Fri, Dec 18, 2015 at 9:15 AM, Albina, Frank < >> [email protected]> wrote: >> >> Hi Cory! >> >> >> >> I have compiled the source code from the Paraview v5.0.0-RC2 source files >> that I downloaded earlier this week from >> http://www.paraview.org/download/. >> No GIT repository there and none to be found in the top-level directory >> of the source files. >> >> >> >> Paraview client & server are from the same build, since I am starting >> both server and client from the same command line on the (Linux) >> workstation, hence I am using the same environement. >> >> >> >> HTH, >> >> >> Frank. >> >> >> >> *From:* Cory Quammen [mailto:[email protected]] >> *Sent:* Freitag, 18. Dezember 2015 15:08 >> *To:* Albina, Frank >> *Cc:* [email protected] >> *Subject:* Re: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend >> failing to start in parallel >> >> >> >> Hi Frank, >> >> >> >> Since you said you recompiled ParaView, I suspect that maybe you forgot >> to update the submodules ParaView uses. In the ParaView source tree, run >> >> >> >> git status >> >> >> >> If VTK is listed, it may say there are new commits available for VTK. To >> update VTK, run >> >> >> >> git submodule update >> >> >> >> This has been an issue a few folks have encountered in the past. >> >> >> >> Also, double-check that your ParaView client and server are truly from >> the same build. >> >> >> >> HTH, >> >> Cory >> >> >> >> On Fri, Dec 18, 2015 at 8:30 AM, Albina, Frank < >> [email protected]> wrote: >> >> Dear all! >> >> >> >> I recompiled Paraview-v5.0.0-rc2 from scratch using OpenMPI v1.6.5 and >> GCC v4.7.2 on my workstation. >> >> The QT & Python versions are the default system versions and are resp. >> 4.8.4 & 2.7.3. >> >> >> >> After successful compilation and installation, I start 8 parallel >> pvserver instances with: >> >> mpirun –np 8 pvserver –sp=7436 >> >> >> >> Then, I start paraview and connect to the server running on the same >> machine. After connection is established, paraview fails with a >> segmentation fault. >> >> >> >> Waiting for client... >> >> Connection URL: cs://ws334:7436 >> >> Accepting connection(s): ws334:7436 >> >> Client connected. >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Parallel/Core/vtkSocketCommunicator.cxx, >> line 809 >> >> vtkSocketCommunicator (0x2b7a600): Could not receive tag. 1 >> >> >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> […] >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> >> >> -------------------------------------------------------------------------- >> >> mpirun noticed that process rank 0 with PID 13964 on node ws334 exited on >> signal 11 (Segmentation fault). >> >> -------------------------------------------------------------------------- >> >> >> >> I have included hereafter how Paraview was compiled: >> >> cmake $sourceDir \ >> >> -DBUILD_SHARED_LIBS:BOOL=ON\ >> >> -DBUILD_TESTING:BOOL=OFF\ >> >> -DBUILD_DOCUMENTATION:BOOL=ON\ >> >> -DCMAKE_BUILD_TYPE:STRING=Release\ >> >> -DPARAVIEW_ENABLE_CATALYST:BOOL=ON\ >> >> -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ >> >> -DPARAVIEW_USE_MPI:BOOL=ON\ >> >> -DPARAVIEW_USE_UNIFIED_BINDINGS:BOOL=ON\ >> >> -DPARAVIEW_ENABLE_WEB:BOOL=ON\ >> >> -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF\ >> >> -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=TRUE\ >> >> -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ >> >> -DVTK_USE_OFFSCREEN:BOOL=OFF\ >> >> -DVTK_USE_X:BOOL=ON\ >> >> -DVTK_USE_QT=ON\ >> >> -DVTK_USE_DISPLAY=ON\ >> >> -DVTK_USE_GUI_SUPPORT:BOOL=ON\ >> >> -DPARAVIEW_BUILD_QT_GUI:BOOL=ON\ >> >> -DCMAKE_INSTALL_PREFIX:PATH=$installDir\ >> >> -DPARAVIEW_ENABLE_PYTHON:BOOL=ON\ >> >> -DPYTHON_ENABLE_MODULE_MPIPython:BOOL=ON\ >> >> -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake\ >> >> -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python2\ >> >> -DPYTHON_INCLUDE_DIR:FILEPATH=/usr/include/python2.7\ >> >> -DPYTHON_LIBRARY:FILEPATH=/usr/lib64/libpython2.7.so\ >> >> -DPYTHON_UTIL_LIBRARY:FILEPATH=/usr/lib64/libutil.so\ >> >> -DVTK_RENDERING_BACKEND:STRING=OpenGL2\ >> >> -DModule_vtkRenderingLICOpenGL2:BOOL=ON >> >> >> >> I must have missed something since I guess that Paraview using parallel >> servers should run, even when there is only one GPU available. Any hints >> would be greatly appreciated. >> >> >> >> Best regards, >> >> >> >> *Frank Albina * >> >> >> _______________________________________________ >> 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 >> >> >> >> >> >> -- >> >> Cory Quammen >> R&D Engineer >> Kitware, Inc. >> >> >> >> >> >> -- >> >> Cory Quammen >> R&D Engineer >> Kitware, Inc. >> > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc.
_______________________________________________ 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
