Let me add that it seems to be runned locally in a virtual machine (VM). Virtual machines will likely consume a lot of ram, hence your program could be killed due to limited resources. Try and see if you can increase the available ram for the VM and/or (preferably) fully convert to an unix environment.
Kind regards Nick 2013/6/11 Abraham Hmiel <[email protected]> > Hello Mohammad, > > We'd like to help you solve your problem, but we are going to need more > information from you. You should attach: > > 1) the last ~10 lines of your output file which can provide a guide for us > to see where the program halted > 2) a copy of the .fdf you used to run SIESTA > 3) a copy of the arch.make file that was used to compile SIESTA, if you can > 4) tell us the bash shell command that you used to run SIESTA > > Any or all of that information would be appreciated. In the meantime, > check with your sysadmin to make sure there is no limit placed on how much > CPU time you are allowed to use on your cluster and that the memory > required by SIESTA is something that you are able to furnish, as both a > user on a node (ulimit -a) and on the cluster's hardware itself. Can you > reproduce the error if you use fewer processors or a totally different > system? > > Best regards, > > > On Tue, Jun 11, 2013 at 11:25 AM, mohammad mahdi Tavakoli < > [email protected]> wrote: > >> >> Dear siesta users >> >> Hi >> >> I have an error which is killed my run. >> >> mpirun noticed that process rank 3 with PID 3026 on node >> user-virtual-machine exited on signal 9 (Killed). >> >> Can you guide me? >> >> Thanks. >> >> > > > -- > *Abraham Hmiel* > Katherine Belz Groves Fellow in Nanoscience > Xue Group, College of Nanoscale Science and Engineering at SUNY Albany > http://abehmiel.net/about > >
