After this WU was complete, I never got a confirmation that it was sent but it was deleted from the queue. It appears as if there might be something wrong with the client or WU as I have never had this issue before. I know it wasn't sent as even at 20Mbps, it immediately got a new WU. Typically the results are over 20MB.
[17:45:33] Completed 237500 out of 250000 steps (95 percent)
[18:12:46] Writing local files
[18:12:46] Completed 240000 out of 250000 steps (96 percent)
[18:39:48] Writing local files
[18:39:48] Completed 242500 out of 250000 steps (97 percent)
[19:07:40] Writing local files
[19:07:40] Completed 245000 out of 250000 steps (98 percent)
[19:35:14] Writing local files
[19:35:15] Completed 247500 out of 250000 steps (99 percent)
[20:03:45] Writing local files
[20:03:45] Completed 250000 out of 250000 steps (100 percent)
[20:03:46] Writing final coordinates.
[20:03:47] Past main M.D. loop
[20:03:47] Will end MPI now
[20:05:13] CoreStatus = 1 (1)
[20:05:13] Sending work to server
[20:05:13] Project: 2665 (Run 1, Clone 720, Gen 163)
[20:05:13] - Error: Could not get length of results file work/wuresults_07.dat
[20:05:13] - Error: Could not read unit 07 file. Removing from queue.
[20:05:13] - Preparing to get new work unit...
[20:05:13] Cleaning up work directory
[20:05:13] + Attempting to get work packet
[20:05:13] - Connecting to assignment server
[20:05:13] - Successful: assigned to (171.64.65.64).
[20:05:13] + News From Folding@Home: Welcome to Folding@Home
[20:05:13] Loaded queue successfully.
[20:05:25] + Closed connections
[20:05:30]
[20:05:30] + Processing work unit
[20:05:30] Work type a1 not eligible for variable processors
[20:05:30] Core required: FahCore_a1.exe
[20:05:30] Core found.
[20:05:30] Using generic mpiexec calls
[20:05:30] Working on queue slot 08 [December 31 20:05:30 UTC]
[20:05:30] + Working ...
[20:05:39]
[20:05:39] *------------------------------*
[20:05:39] Folding@Home Gromacs SMP Core
[20:05:39] Version 1.74 (March 10, 2007)
[20:05:39]
[20:05:39] Preparing to commence simulation
[20:05:39] - Ensuring status. Please wait.
[20:05:56] - Looking at optimizations...
[20:05:56] - Working with standard loops on this execution.
[20:05:56] - Files status OK
[20:05:56] les status OK
[20:06:02] 6972 -> 12883625 (decompressed 526.5 percent)
[20:06:02] 26.5 percent)
[20:06:03] - Starting from initial work packet
[20:06:03]
[20:06:03] Project: 2653 (Run 35, Clone 125, Gen 132)
[20:06:03]
[20:06:04] Entering M.D.
[20:06:10] kpoint
[20:06:11] OPC
[20:06:11] Writing local files
[20:06:11] g local files
[20:06:12] Extra SSE boost OK.
[20:06:13] st OK.
[20:06:13] Writing local files
[20:06:14] Completed 0 out of 500000 steps (0 percent)
Project: 2665 (Run 1, Clone 720, Gen 163)
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 85
- Joined: Fri Feb 13, 2009 12:38 pm
- Hardware configuration: Linux & CPUs
- Location: USA
Re: Project: 2665 (Run 1, Clone 720, Gen 163)
That will happen sometimes when you stop and restart a WU somewhere in the middle. Sometimes it will do that at restart , other times at the finish. No one knows why.
Re: Project: 2665 (Run 1, Clone 720, Gen 163)
Code: Select all
[20:05:13] CoreStatus = 1 (1)
Code: Select all
[20:05:13] - Error: Could not read unit 07 file. Removing from queue.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: Project: 2665 (Run 1, Clone 720, Gen 163)
Having it do that at a restart would be much preferred. The machine was restarted when it was at 10%. So it was a waste of computing time for the remaining 90%.
Re: Project: 2665 (Run 1, Clone 720, Gen 163)
Agreed.lanbrown wrote:Having it do that at a restart would be much preferred. The machine was restarted when it was at 10%. So it was a waste of computing time for the remaining 90%.
There are many things about FahCore_a1 that are less than ideal. Most of the problems that were noted during early testing were deemed unfixable and everybody is waiting for the release of what they're calling SMP2 which solves them all by replacing it with another core that (hopefully) no longer has those problems. See the News blog
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.