F@H work unit not progressing

[natethegreat]

Problem is a p1481_tet_2nm that has been stuck at frame 1 for over half a day now.

here is my log:

[10:01:25] - Preparing to get new work unit...
[10:01:25] + Attempting to get work packet
[10:01:25] - Connecting to assignment server
[10:01:26] - Successful: assigned to (171.65.103.150).
[10:01:26] + News From Folding@Home: Welcome to Folding@Home
[10:01:26] Loaded queue successfully.
[11:01:29] + Could not get Work unit data from Work Server
[11:01:29] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[11:01:43] + Attempting to get work packet
[11:01:43] - Connecting to assignment server
[11:01:44] - Successful: assigned to (171.64.122.128).
[11:01:44] + News From Folding@Home: Welcome to Folding@Home
[11:01:44] Loaded queue successfully.
[11:02:56] + Closed connections
[11:02:56]
[11:02:56] + Processing work unit
[11:02:56] Core required: FahCore_78.exe
[11:02:56] Core found.
[11:02:56] Working on Unit 03 [January 12 11:02:56]
[11:02:56] + Working ...
[11:03:03]
[11:03:03] *------------------------------*
[11:03:03] Folding@Home Gromacs Core
[11:03:03] Version 1.86 (August 28, 2005)
[11:03:03]
[11:03:03] Preparing to commence simulation
[11:03:03] - Assembly optimizations manually forced on.
[11:03:03] - Not checking prior termination.
[11:03:46] - Expanded 3972620 -> 20311029 (decompressed 511.2 percent)
[11:04:03] - Starting from initial work packet
[11:04:03]
[11:04:03] Project: 1481 (Run 1, Clone 496, Gen 22)
[11:04:03]
[11:04:03] Assembly optimizations on if available.
[11:04:03] Entering M.D.
[11:04:24] Protein: p1481_tet_2nm
[11:04:24]
[11:04:24] Writing local files
[11:05:06] Extra SSE boost OK.
[11:05:16] Writing local files
[11:05:23] Completed 0 out of 125000 steps (0)
[15:08:52] Writing local files
[15:09:06] Completed 1250 out of 125000 steps (1)

Should I delete it and move on?

 

[Malak]

Might be a good idea. Have you restarted the machine to see if it just needs a nudge?

 

[biodoc]

Just out of curiosity, did you try running it w/o the -forceasm?

 

[GLeeM]

Yeah, I would try restarting the computer. If it is a bad WU it might delete on its own then. If it doesn't finish another frame in the time it took to finish the first frame then delete.

Too bad because it is one of those rare, very good PPD WUs.

Is that a slower computer?

EDIT: the -forceasm flag only does anything when the client is restarted. It tells the client to not check how it was last shutdown. This makes sure the client uses all optimizations. If the computer is unstable, do not use -forceasm.

 

[natethegreat]

Hey everyone the reboot seemed to do the trick :thumbsup: Pic

I have the -forceasm on because I have little-ones running around the house who like to play with Daddy's things