Hi,<div><br></div><div>the reason turned out to be that the lock daemon (lockd) on the NFS server was hanging. The error could be found by dmesg. </div><div><br></div><div>BTW: Is it somehow possible to print the kernel error messages that are shown by dmesg to the user from within GROMACS? That would help the user to directly see the reason of the error. Thus I'm looking for a function similar to strerror but which returns the kernel message not just the message of the error code (which in this case was just "Input/Output errror".</div>
<div><br></div><div>Roland</div><div><br></div><div> <br><br><div class="gmail_quote">On Wed, Nov 3, 2010 at 12:05 PM, Carsten Kutzner <span dir="ltr"><<a href="mailto:ckutzne@gwdg.de" target="_blank">ckutzne@gwdg.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
there was also an issue with the locking of the general md.log<br>
output file which was resolved for 4.5.2. An update might help.<br>
<font color="#888888"><br>
Carsten<br>
</font><div><div></div><div><br>
<br>
On Nov 3, 2010, at 3:50 PM, Florian Dommert wrote:<br>
<br>
> -----BEGIN PGP SIGNED MESSAGE-----<br>
> Hash: SHA1<br>
><br>
> On 11/03/2010 03:38 PM, Hong, Liang wrote:<br>
>> Dear all,<br>
>> I'm performing a three-day simulation. It runs well for the first day, but stops for the second one. The error message is below. Does anyone know what might be the problem? Thanks<br>
>> Liang<br>
>><br>
>> Program mdrun, VERSION 4.5.1-dev-20101008-e2cbc-dirty<br>
>> Source code file: /home/z8g/download/gromacs.head/src/gmxlib/checkpoint.c, line: 1748<br>
>><br>
>> Fatal error:<br>
>> Failed to lock: md100ns.log. Already running simulation?<br>
>> For more information and tips for troubleshooting, please check the GROMACS<br>
>> website at <a href="http://www.gromacs.org/Documentation/Errors" target="_blank">http://www.gromacs.org/Documentation/Errors</a><br>
>> -------------------------------------------------------<br>
>><br>
>> "Sitting on a rooftop watching molecules collide" (A Camp)<br>
>><br>
>> Error on node 0, will try to stop all the nodes<br>
>> Halting parallel program mdrun on CPU 0 out of 32<br>
>><br>
>> gcq#348: "Sitting on a rooftop watching molecules collide" (A Camp)<br>
>><br>
>> --------------------------------------------------------------------------<br>
>> MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD<br>
>> with errorcode -1.<br>
>><br>
>> NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.<br>
>> You may or may not see output from other processes, depending on<br>
>> exactly when Open MPI kills them.<br>
>> --------------------------------------------------------------------------<br>
>> [node139:04470] [[37327,0],0]-[[37327,1],0] mca_oob_tcp_msg_recv: readv failed: Connection reset by peer (104)<br>
>> --------------------------------------------------------------------------<br>
>> mpiexec has exited due to process rank 0 with PID 4471 on<br>
>> node node139 exiting without calling "finalize". This may<br>
>> have caused other processes in the application to be<br>
>> terminated by signals sent by mpiexec (as reported here).<br>
><br>
> Perhaps the queueing system of your cluster does not allow running a job<br>
> longer than 24h. Or the default is 24h and you have to supply the<br>
> corresponding information to the submission script.<br>
><br>
> /Flo<br>
><br>
> - --<br>
> Florian Dommert<br>
> Dipl.-Phys.<br>
><br>
> Institute for Computational Physics<br>
><br>
> University Stuttgart<br>
><br>
> Pfaffenwaldring 27<br>
> 70569 Stuttgart<br>
><br>
> Phone: +49(0)711/685-6-3613<br>
> Fax: +49-(0)711/685-6-3658<br>
><br>
> EMail: <a href="mailto:dommert@icp.uni-stuttgart.de" target="_blank">dommert@icp.uni-stuttgart.de</a><br>
> Home: <a href="http://www.icp.uni-stuttgart.de/~icp/Florian_Dommert" target="_blank">http://www.icp.uni-stuttgart.de/~icp/Florian_Dommert</a><br>
> -----BEGIN PGP SIGNATURE-----<br>
> Version: GnuPG v1.4.10 (GNU/Linux)<br>
> Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a><br>
><br>
> iEYEARECAAYFAkzRdrEACgkQLpNNBb9GiPm1sgCg3LkRUWgiZvOOH/GIjp5ifbZI<br>
> bJcAn1aamCMWlWTokD1+eDCLG1WhT/rd<br>
> =4Vs3<br>
> -----END PGP SIGNATURE-----<br>
> --<br>
> gmx-users mailing list <a href="mailto:gmx-users@gromacs.org" target="_blank">gmx-users@gromacs.org</a><br>
> <a href="http://lists.gromacs.org/mailman/listinfo/gmx-users" target="_blank">http://lists.gromacs.org/mailman/listinfo/gmx-users</a><br>
> Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/Search" target="_blank">http://www.gromacs.org/Support/Mailing_Lists/Search</a> before posting!<br>
> Please don't post (un)subscribe requests to the list. Use the<br>
> www interface or send it to <a href="mailto:gmx-users-request@gromacs.org" target="_blank">gmx-users-request@gromacs.org</a>.<br>
> Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists" target="_blank">http://www.gromacs.org/Support/Mailing_Lists</a><br>
<br>
<br>
<br>
<br>
<br>
--<br>
gmx-users mailing list <a href="mailto:gmx-users@gromacs.org" target="_blank">gmx-users@gromacs.org</a><br>
<a href="http://lists.gromacs.org/mailman/listinfo/gmx-users" target="_blank">http://lists.gromacs.org/mailman/listinfo/gmx-users</a><br>
Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/Search" target="_blank">http://www.gromacs.org/Support/Mailing_Lists/Search</a> before posting!<br>
Please don't post (un)subscribe requests to the list. Use the<br>
www interface or send it to <a href="mailto:gmx-users-request@gromacs.org" target="_blank">gmx-users-request@gromacs.org</a>.<br>
Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists" target="_blank">http://www.gromacs.org/Support/Mailing_Lists</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>ORNL/UT Center for Molecular Biophysics <a href="http://cmb.ornl.gov" target="_blank">cmb.ornl.gov</a><br>865-241-1537, ORNL PO BOX 2008 MS6309<br>
</div>