Thanks Paul. That was basically what the problem was. I had both mpich2 and openmpi installed. PETSc was linking to openmpi and libMesh to mpich2. To fix this I did the following:
1) Removed mpich2 using Synaptic package manager 2) Did a make distclean in the libMesh directory so we dont try to link to mpich2 anymore 3) Reconfigured and recompiled libMesh It works now. Thanks. On Thu, Oct 6, 2011 at 12:14 PM, Paul T. Bauman <[email protected]> wrote: > On Thu, Oct 6, 2011 at 12:10 PM, Vikram Garg > <[email protected]>wrote: > >> Fatal error in PMPI_Comm_dup: Invalid communicator, error stack: >> PMPI_Comm_dup(176): MPI_Comm_dup(comm=0x50933220, new_comm=0x2b1443b36350) >> failed >> PMPI_Comm_dup(133): Invalid communicator >> > > Are you sure there is not more than 1 MPI installation? I've gotten > something similar when I built code with one MPI library and did mpiexec > with another. Check "which mpiexec" and "ldd libmesh.so" to make sure it's > the same MPI. > -- Vikram Garg PhD Candidate Institute for Computational and Engineering Sciences The University of Texas at Austin http://users.ices.utexas.edu/~vikram/ http://www.runforindia.org/runners/vikramg ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
