On 30/10/13 16:18, Johannes Ring wrote:

>>> $ mpirun -np 3 ./demo_bcs
>>> [debian-bbot:22320] *** An error occurred in MPI_Barrier
>>> [debian-bbot:22320] *** on communicator MPI_COMM_WORLD
>>> [debian-bbot:22320] *** MPI_ERR_COMM: invalid communicator
>>> [debian-bbot:22320] *** MPI_ERRORS_ARE_FATAL (your MPI job will now abort)
>>> [debian-bbot:22319] 2 more processes have sent help message
>>> help-mpi-errors.txt / mpi_errors_are_fatal
>>> [debian-bbot:22319] Set MCA parameter "orte_base_help_aggregate" to 0
>>> to see all help / error messages
>>> $ OMPI_MCA_orte_base_help_aggregate=0 mpirun -np 3 ./demo_bcs
>>> [debian-bbot:22324] *** An error occurred in MPI_Barrier
>>> [debian-bbot:22324] *** on communicator MPI_COMM_WORLD
>>> [debian-bbot:22324] *** MPI_ERR_COMM: invalid communicator
>>> [debian-bbot:22324] *** MPI_ERRORS_ARE_FATAL (your MPI job will now abort)
>>> [debian-bbot:22325] *** An error occurred in MPI_Barrier
>>> [debian-bbot:22325] *** on communicator MPI_COMM_WORLD
>>> [debian-bbot:22325] *** MPI_ERR_COMM: invalid communicator
>>> [debian-bbot:22325] *** MPI_ERRORS_ARE_FATAL (your MPI job will now abort)
>>> [debian-bbot:22326] *** An error occurred in MPI_Barrier
>>> [debian-bbot:22326] *** on communicator MPI_COMM_WORLD
>>> [debian-bbot:22326] *** MPI_ERR_COMM: invalid communicator
>>> [debian-bbot:22326] *** MPI_ERRORS_ARE_FATAL (your MPI job will now abort)
>>
>> I have no idea what this is, but since it appears in two places, both
>> Wheezy in next and master, I would assume a problem with MPI in Wheezy?
> 
> I am trying to figure out this one.

I suspect dolfin (or something down the chain) was built against one mpi
library (say mpich) but is being run with another (openmpi, by the look
of it).

Lawrence

_______________________________________________
fenics mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics

Reply via email to