you need to run the ulimit command before mpirun and on the same node.
if it still does not work, then you can use a wrapper.
you would do
a.sh is a script
ulimit -c unlimited
the core is created in the current directory
Note that open MPI v2.0.0 is not ABI compatible with prior releases of open
MPI. If you are trying to run an MPI executable created by a prior version of
open MPI, you will need to recompile your application with open MPI v2.0.0.
Sent from my phone. No type good.
> On Sep 2, 2016, at 12:48
Thanks for your help. Please see below
mahmood@compute-0-1:~$ ldd /share/apps/chemistry/siesta-3.2-pl-5/tpar/transiesta
linux-vdso.so.1 => (0x7fffba9a8000)
libmpi_f90.so.1 => /opt/openmpi/lib/libmpi_f90.so.1 (0x2b472b64)
Thankyou. That is helpful.
Could you run an 'ldd' on your executable, on one of the compute nodes if
I will nto be able to solve your problem, but at least we now know what the
and can look at the libraries it is using.
On 2 September 2016 at 17:19, Mahmood Naderan
The application is Siesta-3.2 and the command I use is
/share/apps/computer/openmpi-1.6.5/bin/mpirun -hostfile hosts.txt -np
15 /share/apps/chemistry/siesta-3.2-pl-5/tpar/transiesta <
There is one node in the hosts.txt file. I have built transiesta
binary from the
are you compiling and linking this application?
Or are you using an executable which someone else has prepared?
It would be very useful if we could know the application.
On 2 September 2016 at 16:35, Mahmood Naderan wrote:
> >Did you ran
> >ulimit -c unlimited
>Did you ran
>ulimit -c unlimited
>before invoking mpirun ?
Yes. On the node which says that error. Is that file created in the
current working directory? Or it is somewhere in the system folders?
As another question, I am trying to use OpenMPI-2.0.0 as a new one.
Problem is that the
Also, the error message suggested that TCP is not the issue here -- the TCP
hangups are likely because some other process exited unexpectedly.
mpirun noticed that process rank 0 with PID 4989 on node compute-0-1 exited on
signal 4 (Illegal instruction).
This might be the
Mahmood, as Giles says start by looking at how that application is compiled
Run 'ldd' on the executable and look closely at the libraries. Do this on
a compute node if you can.
There was a discussion on another mailign list recently about how to
fingerpritn executables and see which
Did you ran
ulimit -c unlimited
before invoking mpirun ?
if your application can be ran with only one tasks, you can try to run it
you will hopefully be able to see where the illegal instruction occurs.
since you are running on AMD processors, you have to make sure you are not
>Are you running under a batch manager ?
>On which architecture ?
Currently I am not using the job manager (which is actually PBS). I am
running from the terminal.
The machines are AMD Opteron 64 bit
>Hopefully you will get a core file that points you to the illegal instruction
Where is that
In absence of a clear error message, the btl_tcp_frag related error
messages can suggest a process was killed by the oom-killer.
This is not your case, since rank 0 died because of an illegal instruction.
Are you running under a batch manager ?
On which architecture ?
do your compute node have
An MPI job is running on two nodes and everything seems to be fine.
However, in the middle of the run, the program aborts with the following
mca_btl_tcp_frag_recv: readv failed: Connection reset by peer (104)
Mail list logo