mpi problem in fresh install ubuntu 16.04

497 views
Skip to first unread message

Sebastian Gonzalez pintor

unread,
Oct 14, 2016, 10:29:57 AM10/14/16
to fenics-support
Hi, 

I have a fresh install of Ubuntu 16.04, and I installed Fenics through the PPA repositories. When I try to run, for example d1_p2D.py
I get the following error:

me@mycomputer:~/fenics-example/stationary/poisson $ python d1_p2D.py 
Reading DOLFIN parameters from file "dolfin_parameters.xml".
[segonpin-maths:07514] mca: base: component_find: unable to open /usr/lib/openmpi/lib/openmpi/mca_shmem_sysv: /usr/lib/openmpi/lib/openmpi/mca_shmem_sysv.so: undefined symbol: opal_show_help (ignored)
[segonpin-maths:07514] mca: base: component_find: unable to open /usr/lib/openmpi/lib/openmpi/mca_shmem_posix: /usr/lib/openmpi/lib/openmpi/mca_shmem_posix.so: undefined symbol: opal_shmem_base_framework (ignored)
[segonpin-maths:07514] mca: base: component_find: unable to open /usr/lib/openmpi/lib/openmpi/mca_shmem_mmap: /usr/lib/openmpi/lib/openmpi/mca_shmem_mmap.so: undefined symbol: opal_show_help (ignored)
--------------------------------------------------------------------------
It looks like opal_init failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems.  This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):

  opal_shmem_base_select failed
  --> Returned value -1 instead of OPAL_SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems.  This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):

  opal_init failed
  --> Returned value Error (-1) instead of ORTE_SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during MPI_INIT; some of which are due to configuration or environment
problems.  This failure appears to be an internal failure; here's some
additional information (which may only be relevant to an Open MPI
developer):

  ompi_mpi_init: ompi_rte_init failed
  --> Returned "Error" (-1) instead of "Success" (0)
--------------------------------------------------------------------------
*** An error occurred in MPI_Init_thread
*** on a NULL communicator
*** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
***    and potentially your MPI job)
[segonpin-maths:7514] Local abort before MPI_INIT completed successfully; not able to aggregate error messages, and not able to guarantee that all other processes were killed!

I have look for similar errors in the previous questions but I did not find anything. Any idea about how can it be fixed?

Garth N. Wells

unread,
Oct 14, 2016, 10:36:12 AM10/14/16
to Sebastian Gonzalez pintor, fenics-support
Looks like something is wrong with your MPI installation. Try
compiling and running a MPI 'hello world' program, e.g.
http://mpitutorial.com/tutorials/mpi-hello-world/.

Garth


On 14 October 2016 at 15:29, Sebastian Gonzalez pintor
> --
> You received this message because you are subscribed to the Google Groups
> "fenics-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to fenics-suppor...@googlegroups.com.
> To post to this group, send email to fenics-...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/fenics-support/44dc3bfd-f427-4857-8fec-6604924f0fa0%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Sebastian Gonzalez pintor

unread,
Oct 14, 2016, 10:52:07 AM10/14/16
to fenics-support
Hi Garth,

Thaks for the quick answer. I have downloaded the code you suggested


compiled the example

$ cd mpitutorial/tutorials/mpi-hello-world/code/
$ make
mpicc -o mpi_hello_world mpi_hello_world.c

and the code seems to run without problems

$ cd ../../
$ ./run.py mpi_hello_world
mpirun -n 4  ./mpi-hello-world/code/mpi_hello_world
Hello world from processor segonpin-maths, rank 1 out of 4 processors
Hello world from processor segonpin-maths, rank 2 out of 4 processors
Hello world from processor segonpin-maths, rank 0 out of 4 processors
Hello world from processor segonpin-maths, rank 3 out of 4 processors

Any other idea that can help to identify the problem?
Sebas

Sebastian Gonzalez pintor

unread,
Oct 14, 2016, 11:01:14 AM10/14/16
to fenics-support
Because the error makes some reference to the file "dolfin_parameters.xml", I have moved the file to a different folder and run it there instead. The file is the following one

from dolfin import *

# Create mesh and define function space
mesh = UnitSquare(6, 4)
#mesh = UnitCube(6, 4, 5)
V = FunctionSpace(mesh, 'Lagrange', 1)

# Define boundary conditions
u0 = Expression('1 + x[0]*x[0] + 2*x[1]*x[1]')

def u0_boundary(x, on_boundary):
   
return on_boundary

bc = DirichletBC(V, u0, u0_boundary)

# Define variational problem
u = TrialFunction(V)
v = TestFunction(V)
f = Constant(-6.0)
a = inner(nabla_grad(u), nabla_grad(v))*dx
L = f*v*dx

# Compute solution
u = Function(V)
solve(a == L, u, bc)

# Plot solution and mesh
plot(u)
plot(mesh)

# Dump solution to file in VTK format
file = File('poisson.pvd')
file << u

# Hold plot
interactive()

And when I run it the error now is
$ python poisson.py 
Traceback (most recent call last):
  File "poisson.py", line 4, in <module>
    mesh = UnitSquare(6, 4)
NameError: name 'UnitSquare' is not defined
Aborted (core dumped)
I do not really understand why the error is different, but this one makes me think that there is some problem loading dolfin... I do not know if you know any simpler test.


Jan Blechta

unread,
Oct 14, 2016, 11:27:25 AM10/14/16
to Sebastian Gonzalez pintor, fenics-support
d1_2D.py comes from very outdated tutorial. Start with the new tutorial
or documented demos.

https://fenicsproject.org/documentation/dolfin/2016.1.0/python/demo/index.html
http://hplgit.github.io/fenics-tutorial/doc/web/index.html

Jan


On Fri, 14 Oct 2016 08:01:14 -0700 (PDT)
Sebastian Gonzalez pintor <sego...@gmail.com> wrote:

Sebastian Gonzalez pintor

unread,
Oct 14, 2016, 11:34:21 AM10/14/16
to fenics-support
Hi,

I run the new file and it worked fine:

$ python demo_poisson.py 
Calling FFC just-in-time (JIT) compiler, this may take some time.
Calling DOLFIN just-in-time (JIT) compiler, this may take some time.
Calling DOLFIN just-in-time (JIT) compiler, this may take some time.
Calling FFC just-in-time (JIT) compiler, this may take some time.
Calling FFC just-in-time (JIT) compiler, this may take some time.
Solving linear variational problem.


Thanks for your help, and sorry for wasting your time with such a silly question. I did not find the new tutorial at all. 

Sebas.

Anders Logg

unread,
Oct 14, 2016, 12:02:54 PM10/14/16
to Sebastian Gonzalez pintor, fenics-support
The new tutorial is being prepared and will be made available here within a couple of weeks: https://fenicsproject.org/tutorial

You can find the latest draft of the tutorial here:


--
Anders


--
You received this message because you are subscribed to the Google Groups "fenics-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fenics-suppor...@googlegroups.com.
To post to this group, send email to fenics-...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages