Re: [OMPI users] Error in file base/plm_base_launch_support.c: OPAL_HWLOC_TOPO

2018 at 7:52 AM r...@open-mpi.org wrote: >> >> More than likely the problem is the difference in hwloc versions - sounds >> like the topology to/from xml is different between the two versions, and the >> older one doesn’t understand the new one. >> >> >

[OMPI users] Error in file base/plm_base_launch_support.c: OPAL_HWLOC_TOPO

Greetings, I'm having trouble getting openmpi 2.1.2 to work when launching a process from debian 8 on a remote debian 9 host. To keep things simple in this example, I'm just launching date on the remote host. deb8host$ mpirun -H deb9host date [deb8host:01552] [[32763,0],0] ORTE_ERROR_LOG: Error i

Re: [OMPI users] Processes stuck after MPI_Waitall() in 1.4.1

s. Many thanks for your assistance. I'll report back with my findings. -Brian -- Brian Smith Senior Systems Administrator IT Research Computing, University of South Florida 4202 E. Fowler Ave. ENB204 Office Phone: +1 813 974-1467 Organization URL: http://rc.usf.edu On Wed, 2010-07-28 at 06:

Re: [OMPI users] Processes stuck after MPI_Waitall() in 1.4.1

Also, the application I'm having trouble with appears to work fine with MVAPICH2 1.4.1, if that is any help. -Brian On Tue, 2010-07-27 at 10:48 -0400, Terry Dontje wrote: > Can you try a simple point-to-point program? > > --td > > Brian Smith wrote: > > After runnin

Re: [OMPI users] Processes stuck after MPI_Waitall() in 1.4.1

haven't had the slightest hiccup. Does this fit the bill for a simple point-to-point app? Thanks a lot for your help. -Brian On Tue, 2010-07-27 at 10:48 -0400, Terry Dontje wrote: > Can you try a simple point-to-point program? > > --td > > Brian Smith wrote: > > After

Re: [OMPI users] Processes stuck after MPI_Waitall() in 1.4.1

ems ok have you tried to run a simpler OMPI test like > connectivity? I would see if a simple np=2 run spanning across two > nodes fails? > > What OS distribution and version you are running on? > > --td > Brian Smith wrote: > > In case my previous e-mail is too vague for anyone

Re: [OMPI users] Processes stuck after MPI_Waitall() in 1.4.1

OMPI test like > connectivity? I would see if a simple np=2 run spanning across two > nodes fails? > > What OS distribution and version you are running on? > > --td > Brian Smith wrote: > > In case my previous e-mail is too vague for anyone to address, here

Re: [OMPI users] Processes stuck after MPI_Waitall() in 1.4.1

#15 0x004ffc5e in rhosym_ () #16 0x00610dc6 in us_mp_set_charge_ () #17 0x00771c43 in elmin_ () #18 0x00453853 in MAIN__ () #19 0x0042f15c in main () I set up padb to collect a full report on the process and I've attached it to this message. Let me know if

[OMPI users] Processes stuck after MPI_Waitall() in 1.4.1

y suggestions besides the obvious, "well, down-grade from >= 1.4"? What additional info can I provide to help? Thanks, -Brian -- Brian Smith Senior Systems Administrator IT Research Computing, University of South Florida 4202 E. Fowler Ave. ENB204 Office Phone: +1 813 974-1467 Organization URL: http://rc.usf.edu

[OMPI users] MPI and DRMAA

Hi, All, This may seem like an odd query (or not; perhaps it has been brought up before). My work recently involves HPC usability i.e. making things easier for new users by abstracting away the scheduler. I've been working with DRMAA for interfacing with DRMs and it occurred to me: what would be