• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Problems sending completed work for F@H

T

trevinom

Golden Member


I'm having problems sending my completed work up to the servers.
This is what got my attention:

[02:04:35] Writing local files
[02:04:37] Completed 125000 out of 125000 steps (100)
[02:04:39] Writing final coordinates.
[02:04:40] Past main M.D. loop
[02:05:40]
[02:05:40] Finished Work Unit:
[02:05:40] - Reading up to 824304 from "work/wudata_02.arc": Read 824304
[02:05:40] - Reading up to 740364 from "work/wudata_02.xtc": Read 740364
[02:05:40] goefile size: 0
[02:05:40] Leaving Run
[02:05:41] - Writing 1570468 bytes of core data to disk...
[02:05:41] ... Done.
[02:05:41] - Shutting down core
[02:05:41]
[02:05:41] Folding@home Core Shutdown: FINISHED_UNIT
[02:05:44] CoreStatus = 64 (100)
[02:05:44] Sending work to server



[02:05:44] + Attempting to send results
[02:06:37] + Results successfully sent
[02:06:37] Thank you for your contribution to Folding@home.
[02:06:37] + Number of Units Completed: 31





[02:06:41] + Attempting to send results
[02:06:46] Couldn't send HTTP request to server (wininet)
[02:06:46] + Could not connect to Work Server (results)
[02:06:46] (171.64.122.143:8080)
[02:06:46] - Error: Could not transmit unit 01 (completed April 20). Keeping unit in queue.
[02:06:46] - Preparing to get new work unit...
[02:06:46] + Attempting to get work packet
[02:06:46] - Connecting to assignment server
[02:06:47] - Successful: assigned to (171.67.89.148).
[02:06:47] + News From Folding@Home: Welcome to Folding@Home
[02:06:47] Loaded queue successfully.



[02:06:51] + Attempting to send results
[02:06:57] Couldn't send HTTP request to server (wininet)
[02:06:57] + Could not connect to Work Server (results)
[02:06:57] (171.64.122.143:8080)
[02:06:57] - Error: Could not transmit unit 01 (completed April 20). Keeping unit in queue.
[02:06:57] + Closed connections
[02:06:57]
[02:06:57] + Processing work unit
[02:06:57] Core required: FahCore_78.exe
[02:06:57] Core found.
[02:06:57] Working on Unit 03 [April 21 02:06:57]
[02:06:57] + Working ...
[02:06:58]
[02:06:58] *------------------------------*
[02:06:58] Folding@home Gromacs Core
[02:06:58] Version 1.56 (February 2, 2004)
[02:06:58]
[02:06:58] Preparing to commence simulation
[02:06:58] - Looking at optimizations...
[02:06:58] - Created dyn
[02:06:58] - Files status OK
[02:06:58] - Go method
[02:06:59] - Expanded 544756 -> 3588917 (decompressed 658.8 percent)
[02:06:59] - Starting from initial work packet
[02:06:59]
[02:06:59] Project: 572 (Run 108, Clone 59, Gen 5)
[02:06:59]
[02:06:59] Assembly optimizations on if available.
[02:06:59] Entering M.D.
[02:07:29] Protein: p572_L939_K12M
[02:07:29]
[02:07:29] Writing local files
[02:07:29] Extra SSE boost OK.
[02:07:33] Writing local files
[02:07:35] Completed 0 out of 500000 steps (0)
.... it continued with this new WU, completed it and uploaded the results successfully.
It still had errors interspersed while completed this WU involving unit 1.




Here is the file with the results of command 'fah4console -queueinfo' and 'fah4console -send all'

Arguments: -queueinfo



[00:18:35] - Ask before connecting: No
[00:18:35] - Use IE connection settings: Yes
[00:18:35] - User name: Martin_Trevino (Team 198)
[00:18:35] - User ID = 4DAAE36C4A79650A
[00:18:35] - Machine ID: 1
[00:18:35]
[00:18:35] Loaded queue successfully.
[00:18:35] Printing Queue Information
CURRENT QUEUE:
00 EMPTY
01 DONE "Folding@Home" (65) 171.64.122.143:8080 April 17 11:41:09->April 20 10:01:10
02 EMPTY
03 EMPTY
04 *READY "Folding@Home" (78) 171.67.89.148:8080 April 21 20:56:39 | May 5 20:56
05 EMPTY
06 EMPTY
07 EMPTY
08 EMPTY
09 EMPTY



Folding@home Client Shutdown.

Arguments: -send all



[00:18:50] - Ask before connecting: No
[00:18:50] - Use IE connection settings: Yes
[00:18:50] - User name: Martin_Trevino (Team 198)
[00:18:50] - User ID = 4DAAE36C4A79650A
[00:18:50] - Machine ID: 1
[00:18:50]
[00:18:50] Loaded queue successfully.
[00:18:50] Attempting to return result(s) to server...




[00:18:50] + Attempting to send results
[00:18:56] Couldn't send HTTP request to server (wininet)
[00:18:56] + Could not connect to Work Server (results)
[00:18:56] (171.64.122.143:8080)
[00:18:56] - Error: Could not transmit unit 01 (completed April 20). Keeping unit in queue.
[00:18:56] - Failed to send all units to server



Folding@home Client Shutdown.

Can anyone help me?

Thanks,
Martin





 
Take a look here and see if the server your client is trying to send to is down. When I checked a few minutes ago, there were several servers 'not accepting` and server 143 is 'down'. I too have a stuck wu. Its trying to send to 143 of course which is down.....
Let the client run, it will autosend periodically.
 
Originally posted by: r0tt3n1
Take a look here and see if the server your client is trying to send to is down. When I checked a few minutes ago, there were several servers 'not accepting` and server 143 is 'down'. I too have a stuck wu. Its trying to send to 143 of course which is down.....
Let the client run, it will autosend periodically.
Click to expand...
Yep, this is it. I had a stuck WU the other day due to a server being down. Have patience, it will send eventually.
 
Originally posted by: jliechty
Originally posted by: r0tt3n1 Take a look here and see if the server your client is trying to send to is down. When I checked a few minutes ago, there were several servers 'not accepting` and server 143 is 'down'. I too have a stuck wu. Its trying to send to 143 of course which is down..... Let the client run, it will autosend periodically.
Click to expand...
Yep, this is it. I had a stuck WU the other day due to a server being down. Have patience, it will send eventually.
Click to expand...

OK, I'll just let it keep trying then.
Thanks
 
Originally posted by: trevinom
Originally posted by: jliechty
Originally posted by: r0tt3n1 Take a look here and see if the server your client is trying to send to is down. When I checked a few minutes ago, there were several servers 'not accepting` and server 143 is 'down'. I too have a stuck wu. Its trying to send to 143 of course which is down..... Let the client run, it will autosend periodically.
Click to expand...
Yep, this is it. I had a stuck WU the other day due to a server being down. Have patience, it will send eventually.
Click to expand...
OK, I'll just let it keep trying then. Thanks
Click to expand...

OK, now 3 of my machines have a stuck WU. Can we change the server it sends to manually?
 
hmmm, I dont think so, never heard of anyone trying that. There are still 3 servers not accepting and server .143 is still down. 🙁
The client can queue up to 12 units, I think, so you will just have a big dump in the next day or so.
 
How long are the servers usually down for? On weekends?

I've got a work unit for VSP52, which has been down all day - the problem is, this computer is going back tomorrow, as it's my school laptop (essentially leased). Since it takes like a week for me to do WU's on this machine Celeron 1ghz; not on 24/7), it'd be a shame if I couldn't get it in before I return it. When it finished the last big honker I requested a Genome@home WU, so I could finish something before I go.. 😉
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top