[Paraview-developers] BUG?: Where can I get "mpirun" other than the folder of a released ParaView?

[Biddiscombe, John A.]

My mistake, I'm so used to using reverse connection from the cluster back to the client that I forgot that the local servers on the workstation are normal client/server, not reverse-connection.
I just double checked and I'm sure now. Honest.

The odd thing is that it looks as though the servers are in fact connected, it's just that the client doesn't realize it. I should attach the debugger and see what's really going on. I suspect when all the serverlaunch code was tweaked something got munged.

JB

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: 02 February 2012 15:58
To: Biddiscombe, John A.
Cc: Mingcheng Chen; David E DeMarle; ParaView Developers
Subject: Re: [Paraview-developers] BUG?: Where can I get "mpirun" other than the folder of a released ParaView?

> But it is actually not working for me - the servers are started 
> correctly, but the connection is never made in reverse connection 
> mode, the trouble is that the client sits waiting, and only when you 
> cancel the client connect and shut the client down the server produces 
> N(=4 here) dialogs of the kind

Your pvserver command line doesn't not have the "-rc" flag. The server is not starting in reverse-connection mode. That could explain the issue. I verified it works on linux.

> If you omit the -use-offscreen-rendering, the dialogs do not appear, but the server connection is not made and there's just a hang. The same code is working fine on linux machines. The problem of the annoying pop-up dialogs is a long term one (ie it has been doing that for months but I never bothered to fix it), the non-connection is new.

the stereo capable related errors are no longer there on master, as far as I can tell. If someone can verify that'd be great.

Utkarsh