On 22/02/2012 17:54, Utkarsh Ayachit wrote:
Goodwin,
Thanks for the update.
Utkarsh
Here's the backtrace on the remote server:
The server has no GPU and uses OSMesa.
It's stuck in vtkSocket::Receive() too! (so is the client)
#0 0x772868a2 in recv () from /lib64/libpthread.so.0
Hi Goodwin,
Did you also apply the patch on the server side? Again it may not help,
but without it if there is an error during recv the call would silently
restart and you'd never know about the error. I had a similar deadlock
as you do here with version 3.10 on our Cray XE which is how I
Hi Burlen,
I applied your patch before recompiling.
This problem is only happen on versions = 3.12 that are on
headless/gpuless servers.
I'm guessing that it's a problem with offscreen rendering on the server.
Or it could be a similar subtle bug in vtkSocket... I'll keep looking.
Thanks
Subject: Re: [Paraview] ParaView 3.12.0 hanging
The server is expected to complain once the client is killed. The real
issue is the hanging part. Are these debug builds? Is it possible to
produce a backtrace?
Utkarsh
On Mon, Jan 30, 2012 at 7:13 AM, Goodwin Lawlorgoodwin.law...@ucd.ie
wrote
] ParaView 3.12.0 hanging
The server is expected to complain once the client is killed. The
real
issue is the hanging part. Are these debug builds? Is it possible to
produce a backtrace?
Utkarsh
On Mon, Jan 30, 2012 at 7:13 AM, Goodwin
Lawlorgoodwin.law...@ucd.ie
wrote:
Hi All,
We
To: Goodwin Lawlor
Cc: paraview@paraview.org
Subject: Re: [Paraview] ParaView 3.12.0 hanging
The server is expected to complain once the client is killed. The real
issue is the hanging part. Are these debug builds? Is it possible to
produce a backtrace?
Utkarsh
On Mon, Jan 30, 2012 at 7:13 AM
] ParaView 3.12.0 hanging
The server is expected to complain once the client is killed. The real
issue is the hanging part. Are these debug builds? Is it possible to
produce a backtrace?
Utkarsh
On Mon, Jan 30, 2012 at 7:13 AM, Goodwin Lawlorgoodwin.law...@ucd.ie
wrote:
Hi All,
We upgraded
Ayachit
Sent: 30 January 2012 14:38
To: Goodwin Lawlor
Cc: paraview@paraview.org
Subject: Re: [Paraview] ParaView 3.12.0 hanging
The server is expected to complain once the client is killed. The real
issue is the hanging part. Are these debug builds? Is it possible to
produce a backtrace
-Original Message-
From: paraview-boun...@paraview.org
[mailto:paraview-boun...@paraview.org] On Behalf Of Utkarsh Ayachit
Sent: 30 January 2012 14:38
To: Goodwin Lawlor
Cc: paraview@paraview.org
Subject: Re: [Paraview] ParaView 3.12.0 hanging
The server is expected to complain
: paraview-boun...@paraview.org
[mailto:paraview-boun...@paraview.org] On Behalf Of Utkarsh Ayachit
Sent: 30 January 2012 14:38
To: Goodwin Lawlor
Cc: paraview@paraview.org
Subject: Re: [Paraview] ParaView 3.12.0 hanging
The server is expected to complain once the client is killed. The real
issue
[mailto:paraview-boun...@paraview.org] On Behalf Of Utkarsh Ayachit
Sent: 30 January 2012 14:38
To: Goodwin Lawlor
Cc: paraview@paraview.org
Subject: Re: [Paraview] ParaView 3.12.0 hanging
The server is expected to complain once the client is killed. The real
issue is the hanging part. Are these debug
Hi All,
We upgraded pvserver from 3.10 to 3.12
Now when the client (Win7 64bit) connects remotely to the pvserver
(linux 64it), it hangs.
When you kill the client, the server complains:
Waiting for client
Connection URL: cs://localhost:1
Client connected.
ERROR: In
The server is expected to complain once the client is killed. The real
issue is the hanging part. Are these debug builds? Is it possible to
produce a backtrace?
Utkarsh
On Mon, Jan 30, 2012 at 7:13 AM, Goodwin Lawlor goodwin.law...@ucd.ie wrote:
Hi All,
We upgraded pvserver from 3.10 to 3.12
: Re: [Paraview] ParaView 3.12.0 hanging
The server is expected to complain once the client is killed. The real issue is
the hanging part. Are these debug builds? Is it possible to produce a backtrace?
Utkarsh
On Mon, Jan 30, 2012 at 7:13 AM, Goodwin Lawlor goodwin.law...@ucd.ie wrote:
Hi All
Lawlor
Cc: paraview@paraview.org
Subject: Re: [Paraview] ParaView 3.12.0 hanging
The server is expected to complain once the client is killed. The real issue is
the hanging part. Are these debug builds? Is it possible to produce a backtrace?
Utkarsh
On Mon, Jan 30, 2012 at 7:13 AM, Goodwin
15 matches
Mail list logo