Re: [gmx-users] abnormal stop of job

ackground. > Thanks > Atanu > > > > From: Elton Carvalho > To: Discussion list for GROMACS users > Sent: Thu, August 5, 2010 1:59:39 PM > Subject: Re: [gmx-users] abnormal stop of job > > On Thu, Aug 5, 2010 at 1:37 PM, Samrat

Re: [gmx-users] abnormal stop of job

On 05/08/10 17:37, Samrat Pal wrote: Hi all, I have been running a simulation of 200 ns length and it suddenly stoped at 67 ns showing the following line - Received the TERM signal, stopping at the next step I have checked the time steps properly and there is no error. What should I

[gmx-users] abnormal stop of job

Sounds like you killed the job, or your sysadmin killed it, or it timed out if you are on a cluster with a walltime limit. -- original message -- Hi all, I have been running a simulation of 200 ns length and it suddenly stoped at 67 ns showing the following line - Received the TERM

Re: [gmx-users] abnormal stop of job

Hi, The message is quite obvious about what happened: mdrun received a TERM signal and therefor it stopped (see: man 7 signal or http://linux.die.net/man/7/signal). Figuring out the reason who and why sent a TERM signal to your mdrun will be your task, but I can think of 2 basic scenarios: (I) yo

Re: [gmx-users] abnormal stop of job

Samrat Pal wrote: Hi all, I have been running a simulation of 200 ns length and it suddenly stoped at 67 ns showing the following line - Received the TERM signal, stopping at the next step I have checked the time steps properly and there is no error. What should I do now? Please

Re: [gmx-users] abnormal stop of job

-users] abnormal stop of job On Thu, Aug 5, 2010 at 1:37 PM, Samrat Pal wrote: > > Received the TERM signal, stopping at the next step The TERM signal is the default signal sent by the command "kill" to stop a job. Pressing Ctrl-C while the program is running on the foreground has

[gmx-users] abnormal stop of job

This sounds like you, or your sysadmin, killed the job. It is also possible if you are using a cluster that there is a walltime limit and you exceeded that, so your job was sent the term signal. You should restart the run. Check the manual on how to do that since it depends on what version

Re: [gmx-users] abnormal stop of job

On Thu, Aug 5, 2010 at 1:37 PM, Samrat Pal wrote: > > Received the TERM signal, stopping at the next step The TERM signal is the default signal sent by the command "kill" to stop a job. Pressing Ctrl-C while the program is running on the foreground has the same effect. -- Elton Carvalho Tel.: +

[gmx-users] abnormal stop of job

Hi all, I have been running a simulation of 200 ns length and it suddenly stoped at 67 ns showing the following line - Received the TERM signal, stopping at the next step I have checked the time steps properly and there is no error. What should I do now? Please suggest. Thanks Samr