[Grozni Majmun]

On my iBook it takes days to complete a WU. A few days ago I did one, as shown in the logfile:

"Completed 500000 out of 500000 steps (100%)
Writing final coordinates.
Past main M.D. loop

Finished Work Unit:
- Reading up to 1025520 from "work/wudata_01.arc": Read 1025520
- Reading up to 0 from "work/wudata_01.xtc": Read 0
goefile size: 0
logfile size: 47002
Leaving Run
- Writing 1080598 bytes of core data to disk...
... Done.
- Shutting down core

Folding@home Core Shutdown: FINISHED_UNIT"

But it hasn't shown up in the stats. As far as I understand I should get credit even if the WU had expired (which I don't know if it had)

How can I check if the WU has been uploaded properly or if it is still on my machine?

[Turias]

Does the log say if the unit was uploaded? It should say that after the FINISHED_UNIT line.

[Grozni Majmun]

Originally posted by Turias:
Does the log say if the unit was uploaded? It should say that after the FINISHED_UNIT line.

No, that was the end of it.

I just realized that I could try manually, so I did:

./fah4 -send 01

with this result:

Arguments: -send 1

[04:34:06] - Ask before connecting: No
[04:34:06] - User name: Grozni_Majmun (Team 16)
[04:34:06] - User ID = 25411390714A63D6
[04:34:06] - Machine ID: 1
[04:34:06]
[04:34:06] Loaded queue successfully.
[04:34:06] Attempting to return result(s) to server...
[04:34:06] - Failed to send unit 01 to server

Folding@home Client Shutdown.

Any ideas?

[Welnic]

If you are not seeing anything after the FINISHED_UNIT line that seems strange. I don't think that F@H has a setting for not turning in data. This is what I see after a work unit finishes and uploads successfully:

[17:01:14] Finished Work Unit:
[17:01:14] - Reading up to 1025520 from "work/wudata_00.arc": Read 1025520
[17:01:14] - Reading up to 0 from "work/wudata_00.xtc": Read 0
[17:01:14] goefile size: 0
[17:01:14] logfile size: 17246
[17:01:14] Leaving Run
[17:01:18] - Writing 1050842 bytes of core data to disk...
[17:01:18] ... Done.
[17:01:18] - Shutting down core
[17:01:18]
[17:01:18] Folding@home Core Shutdown: FINISHED_UNIT
[17:01:20] CoreStatus = 64 (100)
[17:01:20] Sending work to server


[17:01:20] + Attempting to send results
[17:01:44] + Results successfully sent
[17:01:44] Thank you for your contribution to Folding@home.
[17:01:44] + Number of Units Completed: 17

This is what I see when it is unsuccessful. I don't think that this is that uncommon:

[03:31:25] - Shutting down core
[03:31:25]
[03:31:25] Folding@home Core Shutdown: FINISHED_UNIT
[03:31:27] CoreStatus = 64 (100)
[03:31:27] Sending work to server


[03:31:27] + Attempting to send results
[03:34:36] - Couldn't send HTTP request to server
[03:34:36] + Could not connect to Work Server (results)
[03:34:36] (171.67.89.150:8080)
[03:34:36] - Error: Could not transmit unit 09 (completed March 3). Keeping unit
in queue.


[03:34:36] + Attempting to send results
[03:37:45] - Couldn't send HTTP request to server
[03:37:45] + Could not connect to Work Server (results)
[03:37:45] (171.67.89.150:8080)
[03:37:45] - Error: Could not transmit unit 09 (completed March 3). Keeping unit
in queue.
[03:37:45] - Preparing to get new work unit...
[03:37:45] + Attempting to get work packet
[03:37:45] - Connecting to assignment server
[03:37:50] - Successful: assigned to (171.64.122.124).
[03:37:50] + News From Folding@Home: v.4 client available
[03:37:50] Loaded queue successfully.

And when it does that it just keeps trying to upload at some interval while it is working on the next one:

[03:57:13] Completed 10000 out of 500000 steps (2%)
[04:05:10] Writing local files
[04:05:13] Completed 15000 out of 500000 steps (3%)
[04:13:10] Writing local files
[04:13:12] Completed 20000 out of 500000 steps (4%)


[04:14:15] + Attempting to send results
[04:17:24] - Couldn't send HTTP request to server
[04:17:24] + Could not connect to Work Server (results)
[04:17:24] (171.67.89.150:8080)
[04:17:24] - Error: Could not transmit unit 09 (completed March 3). Keeping unit
in queue.
[04:21:09] Writing local files
[04:21:11] Completed 25000 out of 500000 steps (5%)
[04:29:09] Writing local files
[04:29:11] Completed 30000 out of 500000 steps (6%)

I do have a few in this state, it seems to be happening at the moment. At least the work is being handed out.

[Grozni Majmun]

Is there an actual file that is being uploaded and then deleted? That way I could check if the file is still here...

[reader50]

There are files specific to each work unit, in the Work folder. If you see any files for unit 01 other than the logfile, then something is still there.

Try ./fah4 -send all

[Grozni Majmun]

Originally posted by reader50:
There are files specific to each work unit, in the Work folder. If you see any files for unit 01 other than the logfile, then something is still there.

Try ./fah4 -send all

No, in the work folder, I have a whole bunch of files for WU 02, which i am now folding, but just the logfile for WU 01. I guess that means that it has been sent, but how come it wasn't received.... :-(

any ideas and help would be appreciated. Now that we have 138 days till the next takeover, we need all we can get, or?

[reader50]

Open up your client.cfg file, make sure it lists your correct folding username, and team 16. If more than one instance of folding is running on the same box, make sure each has a different machineid.

[Welnic]

If you are looking at work units that are actually in your folding folder, then you are running with the -local flag. I think that this means that you would need both -local and -send all to send those units. I ran it with -queueinfo and the WU that it told me about was something that I downloaded last August when I started up the client without the local switch by mistake. I ran -queueinfo -local and it listed the WU I am currently working on.

[Grozni Majmun]

good point, but the output is the same when I use the -local flag

oh well, I guess the WU is lost in the great nothingness of the internet. too bad..