It looks like your executable is explicitly calling MPI_ABORT in the
CmiAbort function -- perhaps in response to something happening in the
namd or CmiHandleMessage functions. The next logical step would
likely be to look in those routines and see why MPI_ABORT/CmiAbort
would be invoked.
Yes.. The executables run initially and then gives the mentioned error in
the first message!
i.e.
./mpirun -hostfile machines executable
--
MPI_ABORT was invoked on rank 2 in communicator MPI_COMM_WORLD
with errorcode 1.
NOTE
