Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI devel] Debugger problem with srun and openmpi 1.5 (hang in OMPI)
From: Ralph Castain (rhc_at_[hidden])
Date: 2011-02-10 10:46:51

If you srun a job, then there is no "mpirun" to provide a proc_table. So running a job directly via srun means you cannot run TV on it.

On Feb 10, 2011, at 8:34 AM, Nikolay Piskun wrote:

> Hi,
> I am trying to use Totalview with srun and hit interesting problem. Looks like if OMPI is started by “srun –mpi=ompi ”, mpi job is hang in ompi_wait_for_debugger() subroutine. What happen, I think is ompi was compiled without ORTE_DISABLE_FULL_SUPPORT and as result rank 0 is waiting for message from HNP (by the way what is HNP?) that was supposed to be send by orterun. The problem is that orterun was never invoked because MPI was initiated by srun, not orterun. So what is the solution? Should we always compile OMPI with ORTE_DISABLE_FULL_SUPPORT=true for anything that uses different starters like srun from SLURM?
> Thanks
> Nikolay
> Nikolay Piskun | Director of Continuing Engineering | Totalview Technologies |
> Rogue Wave Software Inc | 24 Prime Parkway, Natick, MA 01760 | p 508-652-7739|
> nikolay.piskun_at_[hidden]
> _______________________________________________
> devel mailing list
> devel_at_[hidden]