| 1:34:58 PM PDT - Mon, Oct 8th 2012 |
|
Qualitatively similar: see output bleow.
I suspect it has more to do with my openmpi setup that with nwchem. I first installed openmpi (via synaptic) just fot the purpose of running the mpi version of nwchem. I've not used in in any other context, and wonder if there is some staightforward way to test it. (I'll check out the openmpi website.)
by the way, in the meantime, I have the tcgmsg version running correctly (I wish I could tell you precisely how!) So I'm bot really hurting. But since you recommended the mpi version, it's become a challenge in its own right.
>>>>>>>>>>>>>>>>>>one processor output >>>>>>>>>>>>>>>>>>>>>>>>>>
bobw@winter-linux: ~...md/ache_7_mpi_1proc [132]> mpirun -np 1 nwchem_6.1_mpi mache.nw | tee mache.stdout
mpirun -np 1 nwchem_6.1_mpi mache.nw
tee mache.stdout
argument 1 = mache.nwbobw@winter-linux: ~...md/ache_7_mpi_1proc [132]> mpirun -np 1 nwchem_6.1_mpi mache.nw | tee mache.stdout
mpirun -np 1 nwchem_6.1_mpi mache.nw
tee mache.stdout
argument 1 = mache.nw
0:Segmentation Violation error, status=: 11
(rank:0 hostname:winter-linux pid:5936):ARMCI DASSERT fail. ../../ga-5-1/armci/src/common/signaltrap.c:SigSegvHandler():310 cond:0
Last System Error Message from Task 0:: No such file or directory
MPI_ABORT was invoked on rank 0 in communicator MPI COMMUNICATOR 4 DUP FROM 0
with errorcode 11.
NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
bobw@winter-linux: ~...md/ache_7_mpi_1proc
mpirun has exited due to process rank 0 with PID 5936 on
node winter-linux exiting without calling "finalize". This may
have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
|
|
|