[mpich-discuss] A problem of carrying out mpich2
Dr. Qian-Lin Tang
qltang at xidian.edu.cn
Tue Jun 15 21:06:03 CDT 2010
Hi, Dave
I also tried the command of mpiexec -n 8 vasp.pgi </dev/null& as suggested in the error message. But the same thing occurs. I invoked mpiexec by "mpiexec -n 8 vasp.pgi >out&" or "mpiexec -n 8 vasp.pgi </dev/null>out&". The version of MPICH2 installed in my system is mpich2-1.2.1p1. With the shown error message, the problem I encountered comes maybe from mpich2 itself. I expect you help me further. Thanks a lot.
Best regards,
Qian-Lin
======= 2010-06-16 00:47:57 您在来信中写道:=======
>Did you try the suggestion given in the error message? (mpiexec -n $NP my_app < /dev/null &)
r>
>How are you invoking mpiexec?
> th ed
>What version of MPICH2 are you using?
> s
Dave
>
>On Jun 15, 2010, at 6:25 AM PDT, Dr. Qian-Lin Tang wrote:
>
>> Dear mpich2-support,
>>
>> Based on mpif90, I have installed the parallel version of a commercilal code VASP . Sometimes mpich2 can work well with vasp, but it also failed for some VASP-treated jobs with the following error messages:
>> -----------------------------------
>> running on 8 nodes
>> distr: one band on 1 nodes, 8 groups
>> vasp.4.6.21 23Feb03 complex
>> POSCAR found : 3 types and 30 ions
>> LDA part: xc-table for Ceperly-Alder, Vosko type interpolation para-ferro
>> POSCAR, INCAR and KPOINTS ok, starting setup
>> WARNING: wrap around errors must be expected
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> FFT: planning ... 2
>> reading WAVECAR
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> mpiexec_qltang1 (handle_stdin_input 1089): stdin problem; if pgm is run in background, redirect from /dev/null
>> mpiexec_qltang1 (handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out < /dev/null &
>> WARNING: random wavefunctions but no delay for mixing, default for NELMDL
>> entering main loop
>> N E dE d eps ncg rms rms(c)
>> rank 6 in job 36 qltang1_54199 caused collective abort of all ranks
>> exit status of rank 6: killed by signal 9
>> rank 3 in job 36 qltang1_54199 caused collective abort of all ranks
>> exit status of rank 3: killed by signal 9
>> -----------------------------
>> I want to know how to solve the above question. Thank you alot.
>>
>> Best regards,
>> Qianlin
>>
>> _______________________________________________
>> mpich-discuss mailing list
>> mpich-discuss at mcs.anl.gov
>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>
>_______________________________________________
>mpich-discuss mailing list
>mpich-discuss at mcs.anl.gov
>https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
= = = = = = = = = = = = = = = = = = = =
致
礼!
Dr. Qian-Lin Tang
qltang at xidian.edu.cn
2010-06-16
More information about the mpich-discuss
mailing list