[Paraview] Running pvserver 3.14.1 under OS X 10.6 and 10.7

[David Gobbi]

Hi Utkarsh,

It turned out that the 10.7 machine had mpi installed in /usr/local.
After installing openmpi 1.4.5 on both machines (10.6 and 10.7),
the pvserver is running on both and paraview is able to connect.

 - David


On Thu, Apr 19, 2012 at 1:42 PM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> That's strange. And you say single pvserver works fine. BTW, 10.7
> doesn't include MPI anymore. Did you install it yourself? What
> version/variant did you use?
>
> Utkarsh
>
> On Thu, Apr 19, 2012 at 2:16 PM, David Gobbi <david.gobbi at gmail.com> wrote:
>> Here is what I see when I run pvserver and paraview:
>>
>> mpirun -np 2 /Applications/ParaView.app/Contents/bin/pvserver
>> Waiting for client...
>> Connection URL: cs://sfmrc-678.crha-health.ab.ca:11111
>> [ after this, two pvserver processes are running, nothing else is printed ]
>>
>> In another shell:
>>
>> /Applications/ParaView.app/Contents/MacOS/paraview
>>
>> ParaView comes up, and when I try to connect to pvserver, there are no
>> errors reported but paraview hangs and doesn't print any information.
>>
>> If I kill the pvserver processes at this point, then paraview comes
>> back to life and prints the following in the "Output Messages" window:
>>
>> =====
>>
>> ERROR: In /Users/dgobbi/Work/Kitware/paraview-git/VTK/Parallel/vtkSocketCommunicator.cxx,
>> line 812
>> vtkSocketCommunicator (0x12819d660): Could not receive tag. 1010580540
>>
>>
>> ERROR: In /Users/dgobbi/Work/Kitware/paraview-git/VTK/Parallel/vtkSocketCommunicator.cxx,
>> line 561
>> vtkSocketCommunicator (0x12819d660): Endian handshake failed.
>>
>>
>> ERROR: In /Users/dgobbi/Work/Kitware/paraview-git/ParaViewCore/ClientServerCore/vtkTCPNetworkAccessManager.cxx,
>> line 321
>> vtkTCPNetworkAccessManager (0x10de65350): Failed to connect to
>> localhost:11111. Client-Server Handshake failed. Please verify that
>> the client and server versions are compatible with each other
>>
>>
>> ERROR: In /Users/dgobbi/Work/Kitware/paraview-git/ParaViewCore/ServerManager/vtkSMSessionClient.cxx,
>> line 257
>> vtkSMSessionClient (0x123996cc0): Some error in socket processing.
>>
>> =====
>>
>> So it seems that paraview is able to find the server, but is unable to
>> get it to respond.
>>
>>  - David
>>
>>
>>
>>
>> On Thu, Apr 19, 2012 at 11:57 AM, Utkarsh Ayachit
>> <utkarsh.ayachit at kitware.com> wrote:
>>> David,
>>>
>>> The 100% CPU for pvserver is expected. It's what the MPI
>>> implementation does for waiting processes. The locking when paraview
>>> connects is fishy. Any more details there? ANy output text or
>>> something?
>>>
>>> Utkarsh
>>>
>>> On Thu, Apr 19, 2012 at 11:08 AM, David Gobbi <david.gobbi at gmail.com> wrote:
>>>> Hi All,
>>>>
>>>> I'm having trouble getting pvserver to run on OS X.  If I run just a
>>>> single instance of pvserver everything works fine and I'm able to
>>>> connect ParaView to it.  But if I do this:
>>>>
>>>> mpirun -np 4 /path/to/pvserver
>>>>
>>>> then all the pvserver processes spin their wheels, taking up 100% of
>>>> the CPU, and if I try to connect ParaView, then ParaView freezes until
>>>> the pvserver processes are killed.  A stack trace of the pvserver
>>>> processes yields the following:
>>>>
>>>> #0  0x00007fff87c77e46 in swtch_pri ()
>>>> #1  0x00007fff87d5301f in sched_yield ()
>>>> #2  0x000000010f755ab5 in mca_pml_ob1_recv ()
>>>> #3  0x00000001091beca8 in MPI_Recv ()
>>>> #4  0x0000000102c13f35 in vtkMPICommunicator::ReceiveDataInternal
>>>> (this=0x7fff5fbff2a0, data=0x7fff5fbff2a0 "??_?", length=512,
>>>> sizeoftype=1606414376, remoteProcessId=-1, tag=1606414672,
>>>> info=0x7fff5fbff1c8, useCopy=0, senderId=@0x10f001958) at
>>>> vtkMPICommunicator.cxx:269
>>>> #5  0x0000000102c13ad8 in vtkMPICommunicator::ReceiveVoidArray
>>>> (this=0x7fff5fbff220, data=0x7fff5fbff2a0, maxlength=512,
>>>> type=1606414880, remoteProcessId=1606414880, tag=1606414880) at
>>>> vtkMPICommunicator.cxx:856
>>>> #6  0x0000000102b2c696 in vtkCommunicator::Receive () at
>>>> /Users/dgobbi/Work/Kitware/paraview-git/VTK/Parallel/vtkCommunicator.h:544
>>>> #7  0x0000000102b2c696 in vtkMultiProcessController::ProcessRMIs
>>>> (this=0x10f000240, reportErrors=1606415568, dont_loop=0) at
>>>> vtkMultiProcessController.cxx:544
>>>> #8  0x0000000102b2cbed in vtkMultiProcessController::ProcessRMIs
>>>> (this=0x10f001900) at vtkMultiProcessController.cxx:531
>>>> #9  0x0000000100015b5b in RealMain [inlined] () at
>>>> /Users/dgobbi/Work/Kitware/paraview-git/CommandLineExecutables/pvserver_common.h:81
>>>> #10 0x0000000100015b5b in main (argc=251664640,
>>>> argv=0x5fbff29000000001) at pvserver_common.h:21
>>>>
>>>> This occurs on OS X 10.6 and OS X 10.7.  This is with ParaView 3.14.1,
>>>> using the system MPI that is located in /usr/lib, and compiled with
>>>> RelWithDebInfo.  The client and server are on the same machine, and
>>>> are part of the same build.
>>>>
>>>> I might be missing some important step, because this is the first time
>>>> that I've tried running ParaView in client/server mode.  Any help is
>>>> appreciated.
>>>>
>>>>  - David