more problems.
cheers,
axel.
From: users-boun...@open-mpi.org [users-boun...@open-mpi.org] On Behalf Of
Ralph Castain [r...@open-mpi.org]
Sent: Friday, July 24, 2009 7:27 AM
To: Open MPI Users
Subject: Re: [OMPI users] Open MPI:Problem with 64-bit openMPI andin
esn't work.
From: users-boun...@open-mpi.org [users-boun...@open-mpi.org] On Behalf Of
Ralph Castain [r...@open-mpi.org]
Sent: Wednesday, August 12, 2009 7:47 AM
To: Open MPI Users
Subject: Re: [OMPI users] Open MPI:Problem with 64-bit openMPI andintel compiler
We use T
We use Torque with OMPI here on almost every cluster, running 64-bit
jobs with the Intel compilers, so I doubt the problem is with Torque.
It is probably an issue with library paths.
Torque doesn't automatically forward your environment, nor does it
execute your remote .bashrc (or equivalen
Back to this problem.
The last suggestion was to upgrade to 1.3.3, which has been done. Still cannot
get this code to
run in 64 bit mode with torque. What I can do is run the job in l6 bit mode
using a hostfile.
Specifically, if I use
qsub -I -l nodes=2:ppn=1 torque allocates two nodes to the
iday, July 24, 2009 7:27 AM
To: Open MPI Users
Subject: Re: [OMPI users] Open MPI:Problem with 64-bit openMPI andintel
compiler
Good point.
Other thing you might consider (though it is unlikely to be part of
this problem) is upgrading to 1.3.3. It probably isn't a good idea to
be
Good point.
Other thing you might consider (though it is unlikely to be part of
this problem) is upgrading to 1.3.3. It probably isn't a good idea to
be using a release candidate for anything serious.
On Jul 24, 2009, at 5:21 AM, Jeff Squyres wrote:
On Jul 23, 2009, at 11:14 PM, Ralph Ca
On Jul 23, 2009, at 11:14 PM, Ralph Castain wrote:
3. get a multi-node allocation and run "pbsdsh echo $LD_LIBRARY_PATH"
and see what libs you are defaulting to on the other nodes.
Be careful with this one; you want to ensure that your local shell
doesn't expand $LD_LIBRARY_PATH and simply
