Re: [OMPI users] Controlling spawned process

2017-10-09 Thread George Reeke
To rhc, Thanks for those suggestions. Here are the results: (1) Add "--oversubscribe" to mpirun cmd (I also added "--output-filename junk" -- see other output below). Terminal output had this fairly usual error message (shortened): --- Child

Re: [OMPI users] Controlling spawned process

2017-10-06 Thread r...@open-mpi.org
Couple of things you can try: * add --oversubscribe to your mpirun cmd line so it doesn’t care how many slots there are * modify your MPI_INFO to be “host”, “node0:22” so it thinks there are more slots available It’s possible that the “host” info processing has a bug in it, but this will tell

[OMPI users] Controlling spawned process

2017-10-06 Thread George Reeke
Dear colleagues, I need some help controlling where a process spawned with MPI_Comm_spawn goes. I am in openmpi-1.10 under Centos 6.7. My application is written in C and am running on a RedBarn system with a master node (hardware box) that connects to the outside world and two other nodes connecte