On Tue, 20 Jan 2004, Sam Watson wrote:
>
> This doesn't seem to work. Each time I try I get
>
>
> <complicated path>/mpirun .exa_mpi_cmd_file
> mpirun (set_stdio): Bad file descriptor
It seems that the error is not related to the appschema so I would suggest
that you should try running a program without using appschema.
>
> I found some old emails in the archives about such a problem, but they
> were two years old and inconclusive.
>
> This is an exact replication of what we're doing with 6.5.1, which works.
> The only difference in the schema files is the paths to the executables,
> but at any rate it looks like mpirun is not evening opening the file.
Can you include your application schema?
> I've tried mpiexec, but ran into two problems, which might be related.
>
> 1. make install did not install mpiexec, though it was built. I copied it
> into the bin directory and tried to use it from there.
Please check your config.log for following
"checking if installed perl can support mpiexec... yes"
mpiexec will not be installed if the configure test fails.
> 2. When I try to use mpiexec, this happens:
>
> <path1>/mpiexec -v -n 0 <path2>exa_sim_sp_mpi -mpi_environment : -n 0
> <path2>exa_sim_sp_mpi -mpi_environment : -n 0 <path3>/exa_sim -cdi_file
> sliptest.cdi -mpi_environment sliptest_d.lgi
> Cannot run Lamnodes! No such file or directory
> Check if you had booted lam before calling mpiexec else pass -machinefile to mpiexec
>
This can be related to the mpiexec being not installed properly as the
perl support is not sufficient.
> However, I can run lamnodes, using the same path that's used for mpiexec:
>
> <path1>/lamnodes
> n0 sleet.exa.com:1:origin,this_node
>
> As you can see, I'm trying an extremely simple configuration; a single node, three
> processes.
>
> Thanks, as always, for your help.
>
> --
> Sam Watson
> Exa Corporation
> 781-676-8572
> sam_at_[hidden]
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
