Page 1 of 1

Project: 6509 (Run 12, Clone 50, Gen 29) - GROMACS Error

Posted: Sun May 08, 2011 5:20 pm
by Tobit
Project: 6509 (Run 12, Clone 50, Gen 29) - GROMACS Error

This could very likely be a bad WU. There are no machine level, OS or hardware, issues. This is a Dell PowerEdge server with no overclocking. Running Gentoo Linux and the V6 client. Client terminates to OS the instant the gromacs error occurs. Had to delete work files and machineindependent.dat in order to receive new work which is folding fine.

Code: Select all

Folding@Home Client Version 6.34

Launch directory: /home/tobit/fah/core1
Executable: ./fah6
Arguments: -verbosity 9 -forceasm 

[13:47:44] - Calling './FahCore_78.exe -dir work/ -nice 19 -suffix 03 -checkpoint 15 -forceasm -verbose -lifeline 30836 -version 634'

[13:47:44] 
[13:47:44] *------------------------------*
[13:47:44] Folding@Home Gromacs Core
[13:47:44] Version 1.90 (March 8, 2006)
[13:47:44] 
[13:47:44] Preparing to commence simulation
[13:47:44] - Assembly optimizations manually forced on.
[13:47:44] - Not checking prior termination.
[13:47:44] - Expanded 997981 -> 4984785 (decompressed 499.4 percent)
[13:47:44] - Starting from initial work packet
[13:47:44] 
[13:47:44] Project: 6509 (Run 12, Clone 50, Gen 29)
[13:47:44] 
[13:47:44] Assembly optimizations on if available.
[13:47:44] Entering M.D.
[13:47:50] Gromacs error.
[13:47:50] 
[13:47:50] Folding@home Core Shutdown: UNKNOWN_ERROR
[13:47:51] CoreStatus = 79 (121)
[13:47:51] Client-core communications error: ERROR 0x79
[13:47:51] This is a sign of more serious problems, shutting down.

Re: Project: 6509 (Run 12, Clone 50, Gen 29) - GROMACS Error

Posted: Sun May 08, 2011 5:53 pm
by toTOW
There's no data in the DB yet for this WU :(

Re: Project: 6509 (Run 12, Clone 50, Gen 29) - GROMACS Error

Posted: Sun May 08, 2011 5:58 pm
by Tobit
toTOW wrote:There's no data in the DB yet for this WU :(
and there likely never will be, if this is a bad WU, as the client exits to the OS when a GROMACS error like this occurs. This project also has a deadline of 53 days so it's going to be awhile before it times out and gets reassigned. :(