ENCUT problem

Problems running VASP: crashes, internal errors, "wrong" results.


Moderators: Global Moderator, Moderator

Post Reply
Message
Author
User avatar
TAT
Newbie
Newbie
Posts: 39
Joined: Thu Aug 02, 2007 7:28 pm
License Nr.: 691 5-1

ENCUT problem

#1 Post by TAT » Wed Jun 04, 2008 6:46 am

Hi,
I have started to get a strange problem all of a sudden. My machine suddenly shut down due to problem with its powersupply. after that when I restarted the machine and run VASP in parallel somehow when I include the
ENCUT tag it gives me following error
----------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.

PID 4644 failed on node n0 (127.0.0.1) due to signal 11.
--------------------------------------------------------
If I comment this tag then everything works well. Earlier there was no problem in using this tag in parallel also.

any suggestions?
Last edited by TAT on Wed Jun 04, 2008 6:46 am, edited 1 time in total.

admin
Administrator
Administrator
Posts: 2921
Joined: Tue Aug 03, 2004 8:18 am
License Nr.: 458

ENCUT problem

#2 Post by admin » Wed Jun 04, 2008 11:36 am

strange... if you had been able to run that job with exactly the same ENCUT (PREC,k-points,...) without problems before, the signal 11 kill most probably is NOT caused by memory problems. I hope that your machines are not damaged by the powersupply problems. Please try to repeat a job which was finished before the shutdown.
please also do the following:
1) check which parallel node was chosen as node0 for your run
2) re-submit your job, avoiding that that node (node0) is used again and / or check if small test runs can be done on that node without memory problems
Last edited by admin on Wed Jun 04, 2008 11:36 am, edited 1 time in total.

Post Reply