[Paraview] pvserver does not terminate after gui disconnects

pratik pratik.mallya at gmail.com
Mon May 30 10:00:26 EDT 2011


Hi Utkarsh,

Please excuse me on this, but the cluster that I was working on will not 
be available for me for the next
week or so. As soon as it is back up, i will test this and send it to 
you (most likely by saturday/sunday)

Thanks,
pratik
On Monday 30 May 2011 07:01 PM, Utkarsh Ayachit wrote:
> Partik,
>
> Is the call stack the same for both mpi-processes ?
>
> Utkarsh
>
> On Sat, May 28, 2011 at 5:00 PM, pratik<pratik.mallya at gmail.com>  wrote:
>    
>> Hi Utkarsh,
>> this is what i get:
>>
>>
>> (gdb) where
>> #0  0x00002b58ed6e41f0 in __nanosleep_nocancel () from
>> /lib64/libpthread.so.0
>> #1  0x00002b58e5b2f8c8 in MPI_SGI_millisleep (milliseconds=<value optimized
>> out>) at sleep.c:36
>> #2  0x00002b58e5b27c2c in MPI_SGI_slow_request_wait (request=0x7fffc53bdb5c,
>> status=0x7fffc53bdb30, set=0x7fffc53bdb58, gen_rc=0x7fffc53bdb54) at
>> req.c:1416
>> #3  0x00002b58e5adc463 in MPI_SGI_slow_barrier (comm=1) at barrier.c:190
>> #4  0x00002b58e5ad06aa in MPI_SGI_finalize () at adi.c:734
>> #5  0x00002b58e5af18bc in PMPI_Finalize () at finalize.c:29
>> #6  0x00002b58e682b49c in vtkPVMain::Finalize () at
>> /home/pratikm/source/ParaView/ParaView-3.10.1/Servers/Filters/vtkPVMain.cxx:160
>> #7  0x000000000040268e in main (argc=5, argv=0x7fffc53bdd88) at
>> /home/pratikm/source/ParaView/ParaView-3.10.1/Servers/Executables/pvserver.cxx:52
>>
>> best,
>> pratik
>>
>> On Sunday 29 May 2011 02:16 AM, Utkarsh Ayachit wrote:
>>      
>>> Once the pvserver process has hanged, connect to any one of the processes
>>> with gdb. Use gdb --pid= to attach to a particular process. Then type
>>> "where" and that will give you the call stack. Do this for both the
>>> processes and we'd know where they ate stuck.
>>>
>>> Utkarsh
>>>
>>>
>>>
>>> On May 27, 2011, at 10:58 AM, pratik<pratik.mallya at gmail.com>    wrote:
>>>
>>>
>>>        
>>>> Also,
>>>> 1) pvserver disconnects properly when run on head node standalone
>>>> 2) pvserver disconnects properly when run on *one* node via PBS job
>>>> scheduler.
>>>>
>>>> problem arises when i try to use more than one node in the cluster.
>>>>
>>>> thanks,
>>>> pratik
>>>> On Friday 27 May 2011 08:25 PM, pratik wrote:
>>>>
>>>>          
>>>>> Hi Utkarsh,
>>>>> This problem always shows up, even if i do not load any data.
>>>>> The build is: CMAKE_BUILD_TYPE=DEBUG (PV 3.10.1, both server and client)
>>>>> Can you please tell me how I can do a stack trace of pvserver?
>>>>>
>>>>> best,
>>>>> pratik
>>>>>
>>>>> On Friday 27 May 2011 06:51 PM, Utkarsh Ayachit wrote:
>>>>>
>>>>>            
>>>>>> pvserver is designed to quit after the client disconnects. Does this
>>>>>> show up after a particular operations or always? Is this a debug
>>>>>> build? Can you post the stack track for the place where the server is
>>>>>> wainting after client quits?
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, May 27, 2011 at 12:16 AM, pratik<pratik.mallya at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>              
>>>>>>> Hi everyone,
>>>>>>> I have pvserver connecting to my client through reverse connection.
>>>>>>> However,
>>>>>>> after i disconnect from the gui, the job (submitted through PBSPro
>>>>>>> 10.6)
>>>>>>> continues to run, and i checked and saw that pvserver was still
>>>>>>> running on
>>>>>>> the nodes. Is there any option by which the pbs job will terminate
>>>>>>> when i
>>>>>>> disconnect from paraview client gui?
>>>>>>>
>>>>>>> thanks,
>>>>>>> pratik
>>>>>>> _______________________________________________
>>>>>>> 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://www.paraview.org/mailman/listinfo/paraview
>>>>>>>
>>>>>>>
>>>>>>>                
>>>>>
>>>>>            
>>>>
>>>>          
>>
>>      



More information about the ParaView mailing list