torque+mpiexec+mvapich = strange behavior

[Anton Starikov]

Addition.

OK, I really understand nothing.
When the first line in batch file is "#!" , as it should be, I get
"mpiexec: Error: read_ib_startup_ports: accept iter 0: Invalid argument"

But if I modify first line to
#!/bin/bash
which has no sense for me, mpiexec starts to work.

Does somebody have some ideas why it is?

Anton.


Anton Starikov wrote:
> Hello!
> 
> I've found really strange thing.
> 
> I'm using torque-1.1.0p4 + mvapich-0.9.4-103 mpiexec-cvs
> And observe something strange.
> When I submit interactive job, I can start mpi job without any problem 
> in interactive session.
> But when I submit non-interactive MPI job, I see:
> "mpiexec: Error: read_ib_startup_ports: accept iter 0: Invalid argument"
> 
> Do you have ideas what can be responsible for a such behavior?
> I fill that there is something around fork (in start_tasks), but can't 
> proove :))
> 
> I'm not a big specialist in multithreading, but it seems that both, 
> parent and child call "prepare_ib_startup_port", and in interactive job 
> only after this call to "read_ib_startup_ports". In case of 
> non-interactive job call to "read_ib_startup_ports" is executed after 
> first call of "prepare_ib_startup_port" and before second one.
> 
> Best regards,
>     Anton Starikov.
> 
> _______________________________________________
> mpiexec mailing list
> mpiexec at osc.edu
> http://email.osc.edu/mailman/listinfo/mpiexec
> 
>