| 查看: 3230 | 回复: 21 | ||||
| 当前只显示满足指定条件的回帖，点击这里查看本话题的所有回帖 | ||||
[交流]
【求助】Performing VASP: mpich2 someties breaks down 已有5人参与
|
||||
|
前面我发个同样的贴，可是问题没有得到解决。比较急，希望大家能够帮助下，谢谢! 我在RHEL 5.4; mpich2-1.2.1p1;pgi-9.0.1;双核Xeon E5504 (intel CPU)环境下跑并行的vasp。有些作业，能够正常并行计算（使用命令：mpiexec -n 8 vasp.pgi >out& or mpiexec -n 8 vasp.pgi out& or mpiexec -n 8 vasp.pgi ，有些作业却不能运行（我安装mpich2-1.2.p1), 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 希望能得到帮助，谢谢！ |
回复此楼» 收录本帖的淘帖专辑推荐
 VASP |
» 猜你喜欢
40+中年人失业后，还能找到好工作吗？
已经有13人回复
-
用NBS溴化时溶剂除了CCl4外还有什么
已经有6人回复
-
申请科研项目纯靠实力能成功吗？
已经有11人回复
-
极限拉扯，如何抉择
已经有15人回复
-
二审4个多月了还是Awaiting Reviewer Scores
已经有4人回复
-
OpenAI又攻克数学难题了，离AI做有机合成还有多远？
已经有13人回复
-
课题组会帮你通过考核么？
已经有7人回复
-
售一区SCI文章T0P，我:8O.551.O54,科目全,可十急
已经有9人回复
-
售SCI一区T0P文章，我:8.O55.1.O.54,科目全,可十急
已经有8人回复
-
售SCI一区文章，我:8O5.5.1.O5.4,科目全,可伽急
已经有10人回复
» 本主题相关价值贴推荐，对您同样有帮助:
- 一些凝聚态专业的知识和关于vasp的知识
已经有83人回复
- 以SiO2为载体的浸渍法，在浸渍后干燥前还用不用洗涤啊？
已经有32人回复
- VASP 5.2.12 以上 可以直接在INCAR中设置K点
已经有9人回复
- vasp计算中如何比较掺杂前后结合能
已经有13人回复
- 求助：vasp结构优化不能收敛
已经有18人回复
- vasp 计算表面DOS与文献对应不上 请求大家帮助.......
已经有20人回复
- 【求助】vasp 5.2中用HSE06计算不能进入主循环
已经有7人回复
- 【求助】关于水热法制备TiO2的XRD图解析
已经有29人回复
- 【求助】vasp并行安装mpich2的错误
已经有10人回复
- down-conversion in Er3+/Yb3+ co-doped YF3
已经有4人回复
- 【求助】新手求助vasp计算氧分子结合能的问题
已经有12人回复
- 【求助】求vasp.4.6 安装必备软件
已经有13人回复
- 【求助】新虫求助！哪位前辈指点一下用vasp做空位缺陷的流程
已经有7人回复
- 【求助】vasp中关于电场单位的问题
已经有12人回复
- 【求助】ＶＡＳＰ如何计算 离子
已经有10人回复
★ ★ ★
小木虫(金币+0.5):给个红包，谢谢回帖交流
hedaors(金币+2):谢谢分享 2010-06-17 22:42:32
小木虫(金币+0.5):给个红包，谢谢回帖交流
hedaors(金币+2):谢谢分享 2010-06-17 22:42:32
|
我感觉是stack size limit的问题 我试过下面这个方法，挺好用的 创建一个file叫limit.c 内容如下： #include #include #include void stacksize_() { int res; struct rlimit rlim; getrlimit(RLIMIT_STACK, &rlim); printf("Before: cur=%d,hard=%d\n",(int)rlim.rlim_cur,(int)rlim.rlim_max); rlim.rlim_cur=RLIM_INFINITY; rlim.rlim_max=RLIM_INFINITY; res=setrlimit(RLIMIT_STACK, &rlim); getrlimit(RLIMIT_STACK, &rlim); printf("After: res=%d,cur=%d,hard=%d\n",res,(int)rlim.rlim_cur,(int)rlim.rlim_max); } 把这个文件和其他的vasp source code 放在一起 编译这个文件：cc -c -Wall -O2 limit.c 在main.F 的开头加入: CALL stacksize() 具体应该加在所有的声明之后 然后在makefile里SOURCE那一大串的文件最后加入limit.o 试试吧～ |
7楼2010-06-17 22:35:59
2楼2010-06-17 12:19:32
3楼2010-06-17 15:23:13
valenhou001
至尊木虫 (职业作家)
- 1ST强帖: 13
- 应助: 241 (大学生)
- 金币: 25701.7
- 散金: 602
- 红花: 166
- 帖子: 3782
- 在线: 873.8小时
- 虫号: 1007127
- 注册: 2010-04-27
- 专业: 凝聚态物性 II ：电子结构
4楼2010-06-17 15:33:53
200