Re: [OMPI users] Openmpi 1.0.3svn10374 not launching apps through TM interface

2006-06-16 Thread Martin Schafföner
On Thursday 15 June 2006 16:08, Brock Palen wrote: > Jezz i really cant read this morning, you are using torque and the > mpiexec is the one with openmpi. I cant help you then someone else > is going to have to. Sorry Would it be much of a hassle to run a very simple mpi job (may even in an i

Re: [OMPI users] Openmpi 1.0.3svn10374 not launching apps throughTM interface

2006-06-16 Thread Jeff Squyres (jsquyres)
Try two things: 1. Use the pbsdsh command to try to launch a trivial non-MPI application (e.g., hostname): (inside a PBS job) pbsdsh - -v hostname where is the number of vcpu's in your job. 2. If that works, try mpirun'ing a trivial non-MPI application (e.g., hostname): (inside a PBS job) mp

Re: [OMPI users] Openmpi 1.0.3svn10374 not launching apps throughTM interface

2006-06-16 Thread Martin Schafföner
On Friday 16 June 2006 15:00, Jeff Squyres (jsquyres) wrote: > Try two things: > > 1. Use the pbsdsh command to try to launch a trivial non-MPI application > (e.g., hostname): > > (inside a PBS job) > pbsdsh - -v hostname > > where is the number of vcpu's in your job. > > 2. If that works, try mpi

[OMPI users] pls:rsh: execv failed with errno=2

2006-06-16 Thread Eric Thibodeau
Hello everyone, Well, first off, I hope this problem I am reporting is of some validity, I tried finding simmilar situations off Google and the mailing list but came up with only one reference [1] which seems invalid in my case since all executions are local (naïve assumptions that it m

Re: [OMPI users] Openmpi 1.0.3svn10374 not launching apps throughTMinterface

2006-06-16 Thread Jeff Squyres (jsquyres)
> -Original Message- > From: users-boun...@open-mpi.org > [mailto:users-boun...@open-mpi.org] On Behalf Of Martin Schafföner > Sent: Friday, June 16, 2006 9:50 AM > To: us...@open-mpi.org > Subject: Re: [OMPI users] Openmpi 1.0.3svn10374 not launching > apps throughTMinterface > > > (ins

Re: [OMPI users] OpenMPI C++ examples of user defined MPI types(inherited classes)?

2006-06-16 Thread Jeff Squyres (jsquyres)
It's on the to-do list to include some simple MPI examples in Open MPI. Here's a sample C++ MPI program from the LAM MPI test suite. It creates a bunch of different derived datatypes with the C++ MPI API: https://sourcehaven.osl.iu.edu/svn/trillium/trunk/lamtests/dtyp/datatype _cxx.cc Although

Re: [OMPI users] pls:rsh: execv failed with errno=2

2006-06-16 Thread Pak Lui
Hi, I noticed your prefix set to the lib dir, can you try without the lib64 part and rerun? Eric Thibodeau wrote: Hello everyone, Well, first off, I hope this problem I am reporting is of some validity, I tried finding simmilar situations off Google and the mailing list but came up with only

Re: [OMPI users] Openmpi 1.0.3svn10374 not launching apps throughTMinterface

2006-06-16 Thread Martin Schafföner
On Friday 16 June 2006 16:03, Jeff Squyres (jsquyres) wrote: > Can you repeat this and run a non-MPI executable such as "hostname"? I > want to take MPI out of the equation and just test the launching system. Sorry, forgot that. So I executed mpiexec -np 1 -d --mca pls tm --mca pls_tm_debug 1 -

Re: [OMPI users] pls:rsh: execv failed with errno=2

2006-06-16 Thread Eric Thibodeau
Hello, I don't want to get too much off topic in this reply but you're brigning out a point here. I am unable to run mpi apps on the AMD64 platform with the regular exporting of $LD_LIBRARY_PATH and $PATH, this is why I have no choice but to revert to using the --prefix approach. Here ar

Re: [OMPI users] pls:rsh: execv failed with errno=2

2006-06-16 Thread Pak Lui
Hi Eric, I started to see what you are saying. You tried to point out that you are using the libdir to lib64 instead of just lib and somehow it doesn't get picked up. I personally have not tried this option though, so I don't think I can help you much here. But I saw that there are changes i

Re: [OMPI users] pls:rsh: execv failed with errno=2

2006-06-16 Thread Eric Thibodeau
Thanks for pointing out the LD_LIBRARY_PATH64 ...that explains much. As for the original error, I am still "a duck out of watter". I will try the 1.1rxxx trunck though (creating an ebuild for it as we speak) Eric Le vendredi 16 juin 2006 11:44, Pak Lui a écrit : > Hi Eric, > > I started to see

Re: [OMPI users] pls:rsh: execv failed with errno=2

2006-06-16 Thread Jeff Squyres (jsquyres)
Sorry for jumping in late... The /lib vs. /lib64 thing as part of --prefix was definitely broken until recently. This behavior has been fixed in the 1.1 series. Specifically, OMPI will take the prefix that you provided and append the basename of the local $libdir. So if you configured OMPI w

Re: [OMPI users] OpenMPI, debugging, and Portland Group's pgdbg

2006-06-16 Thread Jeff Squyres (jsquyres)
I'm afraid that I'm not familiar with the PG debugger, so I don't know how it is supposed to be launched. The intent with --debugger / --debug is that you could do a single invocation of some command and it launches both the parallel debugger and tells that debugger to launch your parallel MPI pro

Re: [OMPI users] pls:rsh: execv failed with errno=2

2006-06-16 Thread Eric Thibodeau
Hello Jeff, Fristly, don't worry about jumping in late, I'll send you a skid rope ;) Secondly, thanks for your nice little artilces on clustermonkey.net (good refresher on MPI). And finally, down to my issues, thanks for clearing out the --prefix LD_LIBRARY_PATH and all. The ebuild I ma