Re: [OMPI users] mpirun error only with one node

I hope this replies correctly. I previously had a problem with replies. Anyhow, thank you for the advice. It turns out NUMA was disabled in the BIOS. All other nodes showed 2 NUMA nodes but node125 showed 1 NUMA node. I was able to see this by diffing lscpu on node125 and another node.

Re: [OMPI users] mpirun error only with one node

Are you SURE node125 is identical to the others? systems can boot up and disable DIMMs for instance. I would log on there and runfreelscpu lspci dmidecode Take those outputs and run a diff against outputs from a known good node Also hwloc/lstopo might show some difference? On Thu, 2

[OMPI users] mpirun error only with one node

I'm getting the following error with openmpi/3.1.4 and openmpi/3.1.6 compiled with intel/19.5 (openmpi/2 and openmpi/4 do not exhibit the problem). When I run 'mpirun -display-devel-allocation hostname' over 2 nodes including node125 of our cluster, I get an error stating there are not enough

Re: [OMPI users] mpirun error on MAC OSX 10.6.8

I believe 10.6 goes back well before 2011, but that’s beside the point - just haven’t heard someone running that old a version of OSX. I doubt that 1.8.4 supports it, or that homebrew built it and tested it on something that old (I know we don’t). Only thing I can suggest is perhaps getting

Re: [OMPI users] mpirun error on MAC OSX 10.6.8

On Feb 17, 2015, at 11:36 AM, Tarandeep Kalra wrote: > > It is a 2011 Macbook pro. Depends on what you think is old. :-) I can't say we've tested Open MPI 1.8.x on OS X 10.6.x -- there may well be some kind of weirdness there. Can you try Open MPI 1.6.5? You'll likely

Re: [OMPI users] mpirun error on MAC OSX 10.6.8

It is a 2011 Macbook pro. Depends on what you think is old. Taran On Tue, Feb 17, 2015 at 11:21 AM, Ralph Castain wrote: > OSX 10.6.8?? Are you sure? That is incredibly old - I haven't seen such a > system in quite some time. > > > On Feb 17, 2015, at 8:04 AM, Tarandeep

Re: [OMPI users] mpirun error on MAC OSX 10.6.8

OSX 10.6.8?? Are you sure? That is incredibly old - I haven’t seen such a system in quite some time. > On Feb 17, 2015, at 8:04 AM, Tarandeep Kalra wrote: > > Hello friends, > > I am using mpi for the first time on my MAC OSX (10.6.8). The MPI that I > installed is

[OMPI users] mpirun error on MAC OSX 10.6.8

Hello friends, I am using mpi for the first time on my MAC OSX (10.6.8). The MPI that I installed is Open MPI. I have installed it through homebrew. It is installed as I can autocomplete mpi--- commands from my terminal. *When i run mpirun --versionIt returns to mpirun (Open MPI) 1.8.4*

Re: [OMPI users] mpirun error

On Tuesday, November 04, 2014 11:06:06 PM Jeff Squyres wrote: > mpirun -np 4 ./test Oh man, THANKS for your quick answer. LOL, nice, now it's running. III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu

Re: [OMPI users] mpirun error

On Nov 4, 2014, at 5:56 PM, jfsanchez wrote: > mpirun -np 4 test Try: mpirun -np 4 ./test To specifically get the "test" executable in your directory (vs. /bin/test, which OMPI may have found in your PATH). -- Jeff Squyres jsquy...@cisco.com For corporate

[OMPI users] mpirun error

Hello, I'm very new using OpenMPI, so I was testing it and wrote this program: //main.c #include #include int main(int argc, char **argv) { int rank; char hostname[256]; MPI_Init(,); MPI_Comm_rank(MPI_COMM_WORLD, ); gethostname(hostname,255);

Re: [OMPI users] mpirun error

> It looks like your PATH is pointing to the Intel MPI mpirun, > not to the Open MPI mpirun/mpiexec. [Tom] Just to expand a little on this, it looks like your path is pointing to the Intel MPI run-time version (mpirt) that is included with the Intel Compiler and it's PATH/LD_LIBRARY_PATH is set

Re: [OMPI users] mpirun error

Hi It looks like your PATH is pointing to the Intel MPI mpirun, not to the Open MPI mpirun/mpiexec. echo $PATH may give you a clue of what is going on. Make sure you use the same MPI implementation to compile (mpicc, mpif90, etc) and to launch the program (mpirun/mpiexec). Check the OpenMPI

Re: [OMPI users] mpirun error

Pradeep Jha ccs.engg.nagoya-u.ac.jp> writes: > > Hello, > When I am trying to run a perfectly running parallel code on a new Linux machine, using the following command: > > -- > > mpirun -np 16 name_of_executable > >

Re: [OMPI users] mpirun error

Hello, thanks for the responses. But I have no idea how to do that. Which environment variables should I look at? How do I find out where is the openMPI installed and make the mpif90 use the openMPI? Thanks, Pradeep 2013/4/2 Elken, Tom > > The Intel Fortran 2013 compiler

Re: [OMPI users] mpirun error

> The Intel Fortran 2013 compiler comes with support for Intel's MPI runtime and > you are getting that instead of OpenMPI. You need to fix your path for all > the > shells you use. [Tom] Agree with Michael, but thought I would note something additional. If you are using OFED's mpi-selector to

Re: [OMPI users] mpirun error

The Intel Fortran 2013 compiler comes with support for Intel's MPI runtime and you are getting that instead of OpenMPI. You need to fix your path for all the shells you use. On Apr 1, 2013, at 5:12 AM, Pradeep Jha wrote: > /opt/intel/composer_xe_2013.1.117/mpirt/bin/intel64/mpirun: line 96:

[OMPI users] mpirun error

Hello, When I am trying to run a perfectly running parallel code on a new Linux machine, using the following command: -- mpirun -np 16 name_of_executable -- I am getting the

Re: [OMPI users] mpirun error output

Am 20.03.2013 um 18:58 schrieb Ralph Castain: > Well, a couple of things come to mind - see below > > On Mar 20, 2013, at 9:41 AM, Bruno Cramer wrote: > >> Hi, >> 1) Openmpi in PC1 >> I installed openmpi-1.4.3 using the OpenSuse 32b v. 12.1 repository >> as well as

Re: [OMPI users] mpirun error output

Well, a couple of things come to mind - see below On Mar 20, 2013, at 9:41 AM, Bruno Cramer wrote: > Hi, > 1) Openmpi in PC1 > I installed openmpi-1.4.3 using the OpenSuse 32b v. 12.1 repository > as well as openmpi devel > All mpi executables are present so are the

[OMPI users] mpirun error output

Hi, 1) Openmpi in PC1 I installed openmpi-1.4.3 using the OpenSuse 32b v. 12.1 repository as well as openmpi devel All mpi executables are present so are the libraries in lib directory. I set the environment as ( .bashrc) PATH=$PATH:/usr/lib/mpi/gcc/openmpi/bin

Re: [OMPI users] mpirun error with " The MPI_Comm_f2c() function was called before MPI_INIT was invoked."

On May 21, 2012, at 2:40 PM, Reuti wrote: >> I encountered a question about openmpi running. I have compiled >> successfully a paralle VASP program with openmpi 1.4.2. But when I run > > Which version of VASP are you using? By default I can't spot any direct call > to MPI_Comm_f2c in the

Re: [OMPI users] mpirun error with " The MPI_Comm_f2c() function was called before MPI_INIT was invoked."

Hi, Am 13.05.2012 um 14:37 schrieb Dongshan Wei: > Hi All, > > I encountered a question about openmpi running. I have compiled > successfully a paralle VASP program with openmpi 1.4.2. But when I run Which version of VASP are you using? By default I can't spot any direct call to MPI_Comm_f2c

Re: [OMPI users] mpirun error with " The MPI_Comm_f2c() function was called before MPI_INIT was invoked."

More specifically -- are you calling any MPI function before calling MPI_Init? (particularly from Fortran) I.e., you may be seeing a side-effect of calling a fortran MPI function before calling MPI_Init. On May 13, 2012, at 9:53 AM, Ralph Castain wrote: > I believe the error message is

Re: [OMPI users] mpirun error with " The MPI_Comm_f2c() function was called before MPI_INIT was invoked."

I believe the error message is pretty clear, actually - your program needs to call MPI_INIT -before- it calls any MPI function. On May 13, 2012, at 6:37 AM, Dongshan Wei wrote: > Hi All, > > I encountered a question about openmpi running. I have compiled > successfully a paralle VASP program

[OMPI users] mpirun error with " The MPI_Comm_f2c() function was called before MPI_INIT was invoked."

Hi All, I encountered a question about openmpi running. I have compiled successfully a paralle VASP program with openmpi 1.4.2. But when I run the compiled program with mpirun, I got the following information at very beginning: *** The MPI_Comm_f2c() function was called before MPI_INIT was

Re: [OMPI users] mpirun error: "error while loading shared libraries: libopen-rte.so.0: cannot open shared object file:"

More specifically -- ensure that LD_LIBRARY_PATH is set properly *on all nodes where you are running Open MPI processes*. For example, if you're using a hostfile to launch across multiple machines, ensure that your shell startup files (e.g., .bashrc) are setup to set your LD_LIBRARY_PATH

Re: [OMPI users] mpirun error: "error while loading shared libraries: libopen-rte.so.0: cannot open shared object file:"

you need to set up LD_LIBRARY_PATH to point to the folder where your shared libraries are located LD_LIBRARY_PATH=/usr/local/library/folder On Mon, Feb 28, 2011 at 3:03 AM, Sonyx Wonda wrote: > > Hello! > > I am a newbie to openmpi and I am having some trouble running openmpi >

[OMPI users] mpirun error: "error while loading shared libraries: libopen-rte.so.0: cannot open shared object file:"

Hello! I am a newbie to openmpi and I am having some trouble running openmpi programs. I downloaded and installed the latest version from the web site (openmpi-1.4.3) and the whole process completed successfully. Both ./configure and make all install commands were successful. I am able to

Re: [OMPI users] mpirun error in OpenMPI 1.5

Dear Ralph, Thank you for your reply. I did check the ld_library_path and recompile with the new version and it worked perfectly. Thank you again. Best Regards, Toan On Thu, Dec 9, 2010 at 12:30 AM, Ralph Castain wrote: > That could mean you didn't recompile the code using

Re: [OMPI users] mpirun error in OpenMPI 1.5

That could mean you didn't recompile the code using the new version of OMPI. The 1.4 and 1.5 series are not binary compatible - you have to recompile your code. If you did recompile, you may be getting version confusion on the backend nodes - you should check your ld_library_path and ensure it

[OMPI users] mpirun error in OpenMPI 1.5

Dear all, I am having a problem while running mpirun in OpenMPI 1.5 version. I compiled OpenMPI 1.5 with BLCR 0.8.2 and OFED 1.4.1 as follows: ./configure \ --with-ft=cr \ --enable-mpi-threads \ --with-blcr=/home/nguyen/opt/blcr \ --with-blcr-libdir=/home/nguyen/opt/blcr/lib \

Re: [OMPI users] MPIRUN Error on Mac pro i7 laptop and linux desktop

Thanks for your answers, the execution of this parallel program works fine at my work, but we used MPICH2. I thought this will run with OPEN-MPI too. Here is the f90 source where MPI_CART_SHIFT is called : program heat

Re: [OMPI users] MPIRUN Error on Mac pro i7 laptop and linux desktop

According to the error message (especially since it's consistent across 2 different platforms), it looks like you have an error in your application. Open MPI says that you're using an invalid communicator when calling MPI_Cart_shift. "Invalid" probably means that it's not a Cartesian

Re: [OMPI users] MPIRUN Error on Mac pro i7 laptop and linux desktop

First thing is to ensure you are getting the version of OMPI that you expect. Both the Mac and Debian come with their own pre-installed versions, so you have to ensure that PATH and LD_LIBRARY_PATH are correctly pointing to the version you installed and compiled against. On Jul 28, 2010, at

[OMPI users] MPIRUN Error on Mac pro i7 laptop and linux desktop

hello, i have a problem concerning the execution of a f90 program (explicitPar) compiled with openmpi-1.4.2. I get nearly the same error on my debian desktop ( AMD Phenom(tm) 9550 Quad-Core Processor) and my mac pro i7 laptop : on mac pro i7 : $ mpiexec -np 2 explicitPar

Re: [OMPI users] mpirun ERROR: The daemon exited unexpectedly with status 255.

I'll try to reinstall openmpi on a nfsdevice, maybe it works then. Thanks for your help dino Tim Prins schrieb: > Unfortunately, I am out of ideas on this one. It is very strange. Maybe > someone else has an idea. > > I would recommend trying to install Open MPI again. First be sure to get >

Re: [OMPI users] mpirun ERROR: The daemon exited unexpectedly with status 255.

Unfortunately, I am out of ideas on this one. It is very strange. Maybe someone else has an idea. I would recommend trying to install Open MPI again. First be sure to get rid of all of the old installs of Open MPI from all your nodes, then reinstall and try again. Tim Dino Rossegger wrote:

Re: [OMPI users] mpirun ERROR: The daemon exited unexpectedly with status 255.

Here the Syntax & Output of the Command: root@sun:~# mpirun --hostfile hostfile saturn [sun:28777] [0,0,0] ORTE_ERROR_LOG: Timeout in file base/pls_base_orted_cmds.c at line 275 [sun:28777] [0,0,0] ORTE_ERROR_LOG: Timeout in file pls_rsh_module.c at line 1164 [sun:28777] [0,0,0] ORTE_ERROR_LOG:

Re: [OMPI users] mpirun ERROR: The daemon exited unexpectedly with status 255.

This is very odd. The daemon is being launched properly, but then things get strange. It looks like mpirun is sending a message to kill application processes on saturn. What version of Open MPI are you using? Are you sure that the same version of Open MPI us being used everywhere? Can you

Re: [OMPI users] mpirun ERROR: The daemon exited unexpectedly with status 255.

Hi again, Tim Prins schrieb: > Hi, > > On Monday 01 October 2007 03:56:16 pm Dino Rossegger wrote: >> Hi again, >> >> Yes the error output is the same: >> root@sun:~# mpirun --hostfile hostfile main >> [sun:23748] [0,0,0] ORTE_ERROR_LOG: Timeout in file >> base/pls_base_orted_cmds.c at line 275

Re: [OMPI users] mpirun ERROR: The daemon exited unexpectedly with status 255.

Hi, On Monday 01 October 2007 03:56:16 pm Dino Rossegger wrote: > Hi again, > > Yes the error output is the same: > root@sun:~# mpirun --hostfile hostfile main > [sun:23748] [0,0,0] ORTE_ERROR_LOG: Timeout in file > base/pls_base_orted_cmds.c at line 275 > [sun:23748] [0,0,0] ORTE_ERROR_LOG:

Re: [OMPI users] mpirun ERROR: The daemon exited unexpectedly with status 255.

Hi again, Yes the error output is the same: root@sun:~# mpirun --hostfile hostfile main [sun:23748] [0,0,0] ORTE_ERROR_LOG: Timeout in file base/pls_base_orted_cmds.c at line 275 [sun:23748] [0,0,0] ORTE_ERROR_LOG: Timeout in file pls_rsh_module.c at line 1164 [sun:23748] [0,0,0] ORTE_ERROR_LOG:

Re: [OMPI users] mpirun ERROR: The daemon exited unexpectedly with status 255.

Now that the PATHs seem to be set correctly for ssh i don't know what the problem could be. Is the error message still the same on as in the first mail? Did you do the envorpnment/sshd_config on both machines? What shell are you using? On other test you could make is to start your application

Re: [OMPI users] mpirun ERROR: The daemon exited unexpectedly with status 255.

Note that you may be able to get some more error output by adding --debug-daemons to the mpirun command line. Tim On Thursday 27 September 2007 05:12:53 pm Dino Rossegger wrote: > Hi Jody, > > Thanks for your help, it really is the case that either in PATH nor in > LD_LIBRARY_PATH the path to

Re: [OMPI users] mpirun ERROR: The daemon exited unexpectedly with status 255.

Hi Jody, Thanks for your help, it really is the case that either in PATH nor in LD_LIBRARY_PATH the path to the libs is set correctly. I'll try out, hope it works. jody schrieb: > Hi Dino > > Try > ssh saturn printenv | grep PATH >>from your host sun to see what your environment variables are

Re: [OMPI users] mpirun ERROR: The daemon exited unexpectedly with status 255.

Hi Dino Try ssh saturn printenv | grep PATH from your host sun to see what your environment variables are when ssh is run without a shell. On 9/27/07, Dino Rossegger wrote: > Hi, > > I have a problem running a simple programm mpihello.cpp. > > Here is a excerp of the

[OMPI users] mpirun ERROR: The daemon exited unexpectedly with status 255.

Hi, I have a problem running a simple programm mpihello.cpp. Here is a excerp of the error and the command root@sun:~# mpirun -H sun,saturn main [sun:25213] [0,0,0] ORTE_ERROR_LOG: Timeout in file base/pls_base_orted_cmds.c at line 275 [sun:25213] [0,0,0] ORTE_ERROR_LOG: Timeout in file