F@H: some help please?

[bgeh]

i recently re-fired up my p2 400 back into the fray(slow but yet it makes deadlines although by 1-2 days)
as of now it seems to have problems sending the completed WU
i am naturally quite worried since the deadline is in about 1.5 days time
so i copied the whole folder to the main rig and fired it up with the -send all arguement.....
yet the console reports that it can't send the WU
i've checked server stats and most of them are up

[14:13:06] + Attempting to send results
[14:13:07] Working on Unit 09 [March 30 14:13:07]
[14:13:07] + Working ...
[14:13:10] Folding@Home Client Core Version 2.47 (June 14, 2002)
[14:13:10]
[14:13:10] Proj: work/wudata_09
[14:13:10] Done: 22972 -> 142973 (decompressed 622.3 percent)
[14:13:11] nsteps: 5000000 dt: 2.000000 dt_dump: 250.000000 temperature: 298.000000
[14:13:11] xyzfile:
[14:13:11] " 393 p638_L939_K12M_ext
[14:13:11] 1 N -2.298497 -55.257436 68.097214 20..."
[14:13:11] keyfile:
[14:13:11] "parameters ./proj638.prm
[14:13:11] NOVERSION
[14:13:11] ARCHIVE
[14:13:11]
[14:13:11] cutoff 16.0
[14:13:11] taper 12...."
[14:13:11]
[14:13:11] - Couldn't get size info for dyn file: work/wudata_09.dyn
[14:13:11] Starting from initial work packet
[14:13:11]
[14:13:11] Protein: p638_L939_K12M_ext
[14:13:11] - Run: 262 (Clone 71, Gen 33)
[14:13:11] - Frames Completed: 0, Remaining: 400
[14:13:11] - Dynamic steps required: 5000000
[14:13:11]
[14:13:11] Writing local files:
[14:13:11]
[14:13:11] parameters work/wudata_09.prm
[14:13:11] - Writing "work/wudata_09.key": (overwrite) successful.
[14:13:11] - Writing "work/wudata_09.xyz": (overwrite) successful.
[14:13:12] - Writing "work/wudata_09.prm": (overwrite) successful.
[14:13:16] - Writing "work/wudata_09.key": (append) successful.
[14:13:16]
[14:13:16] PROJECT="work/wudata_09", NSTEPS=5000000, DT=2.0000, DTDUMP=25.000000, TEMP=298.00
[14:13:16] TINKER: Software Tools for Molecular Design
[14:13:16] Version 3.8 October 2000
[14:13:16] Copyright (c) Jay William Ponder 1990-2000
[14:13:16] portions Copyright (c) Michael Shirts 2001
[14:13:16] portions Copyright (c) Vijay S Pande 2001
[14:17:26] - Couldn't send HTTP request to server
[14:17:26] + Could not connect to Work Server (results)
[14:17:26] (171.67.89.152:8080)
[14:17:26] - Error: Could not transmit unit 08 (completed March 30). Keeping unit in queue.

 

[r0tt3n1]

Well, according to their server logs, that server seems to be accepting. But we all know how accurate those logs are.......

The F@H client will try to resend automatically, but as you say, time is against us. I would let the client work on a fresh work unit and let the auto-send have at it til this evening if you think there is enough time. If the unit in queue happens to be late, you will still be given partial credit. Or, if ya got the time, keep shutting down the client every 10 minutes or whatever, and restart, it will automatically try to send units in the queue every time it starts up.

 

[r0tt3n1]

Sure hope that unit was sent by now.