| 查看: 1925 | 回复: 6 | |||
[交流]
【求助】跑vasp时, mpich2运行有时有问题已有4人参与
|
|
Hi, All 我在RHEL 5.4; mpich2-1.2.1p1;pgi-9.0.1;双核Xeon E5504 (intel CPU)环境下跑并行的vasp。有些作业，能够正常并行计算（使用命令：mpiexec -n 8 vasp.pgi >out& 或者mpiexec -n 8 vasp.pgi out&，有些作业却不能运行（我安装mpich2, pgi.9.0.1没有问题），这时程序读了INCAR，POTCAR，POSCAR和KPOINTS文件后，屏幕提示如下的错误： ---------------------------------------------------------------------- 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 ---------------------------------------------------------- 不知道这是什么原因。苦恼了很久，特请大家帮忙解决下，谢谢！ |
回复此楼» 猜你喜欢
心脉受损
已经有4人回复
-
博士读完未来一定会好吗
已经有13人回复
-
Springer期刊投稿求助
已经有4人回复
-
读博
已经有3人回复
-
小论文投稿
已经有3人回复
-
Bioresource Technology期刊，第一次返修的时候被退回好几次了
已经有9人回复
-
到新单位后，换了新的研究方向，没有团队，持续积累2区以上论文，能申请到面上吗
已经有8人回复
-
申请2026年博士
已经有6人回复
-
请问哪里可以有青B申请的本子可以借鉴一下。
已经有5人回复
» 本主题相关价值贴推荐，对您同样有帮助:
石墨烯纳米带 vasp建模 边缘如何加氢
已经有28人回复- 一些凝聚态专业的知识和关于vasp的知识
已经有83人回复
- vasp5.2计算光学性质
已经有22人回复
- vasp跨节点运行出错，mpiexec_node-1 (handle_stdin_input 1089)
已经有5人回复
- vasp5.2 openmpi+intel+mkl编译，能量正值问题
已经有7人回复
- vasp5.2计算误差太大
已经有11人回复
- 【求助】vasp5.2为什么连接网线才能运行
已经有5人回复
- 【求助成功】vasp5.2并行安装不上
已经有18人回复
- 【分享】vasp2cif.f90 for vasp5.2
已经有4人回复
- 【求助】vasp并行安装mpich2的错误
已经有10人回复
- 【求助】vasp 编译时候没有错误提示，但是运行时出现“段错误”
已经有14人回复
- 【求助】Performing VASP: mpich2 someties breaks down
已经有21人回复
- 【求助】为什么vasp运行时cpu使用率很不均衡？
已经有9人回复
2楼2010-06-15 19:34:54
|
命令确实是mpiexec -n 8 vasp.pgi out&或mpiexec -n 8 vasp.pgi >out& 我按照你的：mpiexec -n 8 vasp.pgi &> out&，结果也出现同样的报错信息： -------------------------------------------- [qltang@qltang1 pgi]$ vi out 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) Assertion failed in file /opt/software/tmp/mpich2-1.2.1p1/src/mpid/ch3/channels/nemesis/nemesis/include/mpid_nem_inline.h at line 728: local_rank < MPID_nem_mem_region.num_local internal ABORT - process 1 rank 5 in job 44 qltang1_54199 caused collective abort of all ranks exit status of rank 5: killed by signal 11 rank 1 in job 44 qltang1_54199 caused collective abort of all ranks exit status of rank 1: return code 1 ------------------------------------------------------------ 我注意到报错信息里有这样一句话：“Assertion failed in file /opt/software/tmp/mpich2-1.2.1p1/src/mpid/ch3/channels/nemesis/nemesis/include/mpid_nem_inline.h at line 728: local_rank < MPID_nem_mem_region.num_local”。不知道mpich2为什么有时会出现这样的错误？ 请达人指教，谢谢！ |
3楼2010-06-15 20:27:34
4楼2010-06-15 22:19:39
5楼2010-06-16 09:37:55
ApolloYang
木虫 (正式写手)
- 应助: 15 (小学生)
- 金币: 2209.6
- 散金: 114
- 红花: 4
- 帖子: 390
- 在线: 236.9小时
- 虫号: 582657
- 注册: 2008-07-25
- 性别: GG
- 专业: 凝聚态物性 II ：电子结构
6楼2010-07-31 10:51:54
ApolloYang
木虫 (正式写手)
- 应助: 15 (小学生)
- 金币: 2209.6
- 散金: 114
- 红花: 4
- 帖子: 390
- 在线: 236.9小时
- 虫号: 582657
- 注册: 2008-07-25
- 性别: GG
- 专业: 凝聚态物性 II ：电子结构
7楼2010-07-31 20:15:33