Page 1 of 1

Problems uploading to http://171.64.65.54:8080/

Posted: Fri Apr 23, 2010 3:24 pm
by dchamberlain
I'm recently having problems uploading large 6041 work units to http://171.64.65.54:8080/.

Here is what happens when the work unit finishes.

Code: Select all

[09:43:19] Completed 200000 out of 250000 steps  (80%)
[10:16:28] Completed 202500 out of 250000 steps  (81%)
[10:49:42] Completed 205000 out of 250000 steps  (82%)
[11:22:52] Completed 207500 out of 250000 steps  (83%)
[11:56:04] Completed 210000 out of 250000 steps  (84%)
[12:29:10] Completed 212500 out of 250000 steps  (85%)
[13:02:19] Completed 215000 out of 250000 steps  (86%)
[13:35:31] Completed 217500 out of 250000 steps  (87%)
[14:08:35] Completed 220000 out of 250000 steps  (88%)
[14:41:40] Completed 222500 out of 250000 steps  (89%)
[15:14:44] Completed 225000 out of 250000 steps  (90%)
[15:47:53] Completed 227500 out of 250000 steps  (91%)
[16:20:52] Completed 230000 out of 250000 steps  (92%)
[16:53:38] Completed 232500 out of 250000 steps  (93%)
[17:26:40] Completed 235000 out of 250000 steps  (94%)
[18:00:40] Completed 237500 out of 250000 steps  (95%)
[18:33:51] Completed 240000 out of 250000 steps  (96%)
[19:07:00] Completed 242500 out of 250000 steps  (97%)
[19:40:02] Completed 245000 out of 250000 steps  (98%)
[20:12:59] Completed 247500 out of 250000 steps  (99%)
[20:46:20] Completed 250000 out of 250000 steps  (100%)
[20:46:25] DynamicWrapper: Finished Work Unit: sleep=10000
[20:46:35] 
[20:46:35] Finished Work Unit:
[20:46:35] - Reading up to 31748256 from "work/wudata_01.trr": Read 31748256
[20:46:36] trr file hash check passed.
[20:46:36] - Reading up to 31965188 from "work/wudata_01.xtc": Read 31965188
[20:46:37] xtc file hash check passed.
[20:46:37] edr file hash check passed.
[20:46:37] logfile size: 223048
[20:46:37] Leaving Run
[20:46:41] - Writing 63954376 bytes of core data to disk...
[20:46:44]   ... Done.
[20:46:52] - Shutting down core
[20:46:52] 
[20:46:52] Folding@home Core Shutdown: FINISHED_UNIT
[20:46:55] CoreStatus = 64 (100)
[20:46:55] Sending work to server
[20:46:55] Project: 6041 (Run 0, Clone 225, Gen 2)


[20:46:55] + Attempting to send results [April 22 20:46:55 UTC]

Folding@Home Client Shutdown at user request.

Folding@Home Client Shutdown.
Two hours had elapsed since the "Attemping to send results" and the shutdown after I discovered nothing was happening. I did a "send all" with verbosity set to 9 here...

Code: Select all

# Windows CPU Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.29

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Program Files\FAH
Executable: fah6
Arguments: -verbosity 9 -send all 

[00:22:40] - Ask before connecting: No
[00:22:40] - User name: dchamberlain (Team 53449)
[00:22:40] - User ID: 1B2CC11E76584ED7
[00:22:40] - Machine ID: 5
[00:22:40] 
[00:22:40] Loaded queue successfully.
[00:22:40] Attempting to return result(s) to server...
[00:22:40] Trying to send all finished work units
[00:22:40] Project: 6041 (Run 0, Clone 225, Gen 2)
[00:22:40] - Read packet limit of 540015616... Set to 524286976.


[00:22:40] + Attempting to send results [April 23 00:22:40 UTC]
[00:22:40] - Reading file work/wuresults_01.dat from core
[00:22:40]   (Read 63954376 bytes from disk)
[00:22:40] Connecting to http://171.64.65.54:8080/
[00:22:48] ***** Got a SIGTERM signal (2)
[00:22:48] Killing all core threads

Folding@Home Client Shutdown.
As soon as it gets to "Connecting to http://171.64.65.54:8080/ it just seems to hang. No data is being transmitted. I tried doing -send all's a couple of times and at one point got this one.

Code: Select all

# Windows CPU Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.29

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Program Files\FAH
Executable: fah6
Arguments: -send all -verbosity 9 

[00:39:12] - Ask before connecting: No
[00:39:12] - User name: dchamberlain (Team 53449)
[00:39:12] - User ID: 1B2CC11E76584ED7
[00:39:12] - Machine ID: 5
[00:39:12] 
[00:39:12] Loaded queue successfully.
[00:39:12] Attempting to return result(s) to server...
[00:39:12] Trying to send all finished work units
[00:39:12] Project: 6041 (Run 0, Clone 225, Gen 2)
[00:39:12] - Read packet limit of 540015616... Set to 524286976.


[00:39:12] + Attempting to send results [April 23 00:39:12 UTC]
[00:39:12] - Reading file work/wuresults_01.dat from core
[00:39:12]   (Read 63954376 bytes from disk)
[00:39:12] Connecting to http://171.64.65.54:8080/
[00:55:47] Posted data.
[00:56:47] Initial: 683C; + Could not connect to Work Server (results)
[00:56:47]     (171.64.65.54:8080)
[00:56:47] + Retrying using alternative port
[00:56:47] Connecting to http://171.64.65.54:80/
[00:56:48] - Couldn't send HTTP request to server
[00:56:48] + Could not connect to Work Server (results)
[00:56:48]     (171.64.65.54:80)
[00:56:48] - Error: Could not transmit unit 01 (completed April 22) to work server.
[00:56:48] - 1 failed uploads of this unit.
[00:56:48]   Keeping unit 01 in queue.
[00:56:48] + Sent 0 of 1 completed units to the server
[00:56:48] - Failed to send all units to server
[00:56:48] ***** Got a SIGTERM signal (2)
[00:56:48] Killing all core threads

Folding@Home Client Shutdown.
I've had this happen now on the last two work units this machine has done. Both of them being 6041's. I've done 6041's on this machine before and on another similar machine I have running. I've changed nothing on either machine. Both times I've ended up dumping the work unit in order to get the machine folding again.

When I try to connect to http://171.64.65.54:8080/ with Internet Explorer I typically get "OK" although once I got a message about not being able to read the content. When I try to connect to that server with Firefox I get a message about trying to download "application/octet-stream" and asking me to either pick a program to open it or save the file.

Here is my client.cfg file.

Code: Select all

[settings]
username=dchamberlain
team=53449
passkey=**********************************
asknet=no
machineid=5
bigpackets=normal
local=290

[http]
active=no
host=localhost
port=8080
usereg=no

[power]
battery=no

[core]
checkpoint=5
cpuusage=100
priority=0
addr=

[clienttype]
type=3
Does anyone have any suggestions? I've picked up yet another 6041 and I figure it'll do the same thing when it finishes. It takes about 1 day and 16 hours to run one of these, I've lost two already so I've wasted this machine's effort for most of a week now.

Re: Problems uploading to http://171.64.65.54:8080/

Posted: Fri Apr 23, 2010 3:27 pm
by kasson
Octet stream is the new version of server ok (for odd reasons it processes the index.html file that way). It's if you get an error connecting that there's a problem.

Re: Problems uploading to http://171.64.65.54:8080/

Posted: Fri Apr 23, 2010 6:08 pm
by toTOW
What's your upload speed ? If it's too slow, it might be timing out ... :?

Re: Problems uploading to http://171.64.65.54:8080/

Posted: Fri Apr 23, 2010 6:17 pm
by dchamberlain
My upload speed is 320 Kpbs. I just uploaded a 6025 (20361897 of data, according to the log) in about 10 minutes.

When it tries to upload the 6041's, it never actually sends any data. I can see the line on my DSL router that goes to my computer room. When I upload from the other machine, I can see data (rapidly flashing light) for as long as the upload takes. When the 6041's from this machine try to go up, I so no activity on that line at all.

Re: Problems uploading to http://171.64.65.54:8080/

Posted: Fri Apr 23, 2010 7:57 pm
by Mactin
I get the same (or similar) problem on both my machines (Q6600 and i7-980x). I've never had it on the laptop.
It just stands there for hours doing nothing. The client should have code to control sending the results and aggressively trying to connect.
Usually, stopping it (Ctrl-C) and restarting the client solves the problem. But since returning these fast is better for points, this is a little maddening.
I'm not always next to the computers (I have to sleep and work).

Re: Problems uploading to http://171.64.65.54:8080/

Posted: Sat Apr 24, 2010 5:44 am
by Sahkuhnder
I had this same problem before too but dismissed it as a connection glitch on my end. Earlier today I again had the same problem with a 6041 hanging at Attempting to send.

WU finished and shut down normally. At 21:11:05 "+ Attempting to send results". After a couple minutes I noticed that there was no internet activity. I opened a browser window and it loaded correctly. I disabled and then enabled the high-speed internet connection (didn't help) while I also switched to a WiFi connection through which the completed WU was sent and a new WU was received.

Code: Select all

[20:45:14] Completed 247500 out of 250000 steps  (99%)
[21:10:34] Completed 250000 out of 250000 steps  (100%)
[21:10:38] DynamicWrapper: Finished Work Unit: sleep=10000
[21:10:48] 
[21:10:48] Finished Work Unit:
[21:10:48] - Reading up to 23811192 from "work/wudata_07.trr": Read 23811192
[21:10:48] trr file hash check passed.
[21:10:48] - Reading up to 31967228 from "work/wudata_07.xtc": Read 31967228
[21:10:48] xtc file hash check passed.
[21:10:48] edr file hash check passed.
[21:10:48] logfile size: 233222
[21:10:48] Leaving Run
[21:10:52] - Writing 56029526 bytes of core data to disk...
[21:10:54]   ... Done.
[21:11:01] - Shutting down core
[21:11:01] 
[21:11:01] Folding@home Core Shutdown: FINISHED_UNIT
[21:11:05] CoreStatus = 64 (100)
[21:11:05] Sending work to server
[21:11:05] Project: 6041 (Run 0, Clone 172, Gen 7)


[21:11:05] + Attempting to send results [April 23 21:11:05 UTC]
[21:14:43] - Couldn't send HTTP request to server
[21:14:43] + Could not connect to Work Server (results)
[21:14:43]     (171.64.65.54:8080)
[21:14:43] + Retrying using alternative port
[21:14:43] - Couldn't send HTTP request to server
[21:14:43] + Could not connect to Work Server (results)
[21:14:43]     (171.64.65.54:80)
[21:14:43] - Error: Could not transmit unit 07 (completed April 23) to work server.
[21:14:43]   Keeping unit 07 in queue.
[21:14:43] Project: 6041 (Run 0, Clone 172, Gen 7)


[21:14:43] + Attempting to send results [April 23 21:14:43 UTC]
[21:14:43] - Couldn't send HTTP request to server
[21:14:43] + Could not connect to Work Server (results)
[21:14:43]     (171.64.65.54:8080)
[21:14:43] + Retrying using alternative port
[21:14:43] - Couldn't send HTTP request to server
[21:14:43] + Could not connect to Work Server (results)
[21:14:43]     (171.64.65.54:80)
[21:14:43] - Error: Could not transmit unit 07 (completed April 23) to work server.


[21:14:43] + Attempting to send results [April 23 21:14:43 UTC]
[21:14:43] - Couldn't send HTTP request to server
[21:14:43] + Could not connect to Work Server (results)
[21:14:43]     (171.67.108.25:8080)
[21:14:43] + Retrying using alternative port
[21:14:43] - Couldn't send HTTP request to server
[21:14:43] + Could not connect to Work Server (results)
[21:14:43]     (171.67.108.25:80)
[21:14:43]   Could not transmit unit 07 to Collection server; keeping in queue.
[21:14:43] - Preparing to get new work unit...
[21:14:43] Cleaning up work directory
[21:14:43] + Attempting to get work packet
[21:14:43] Passkey found
[21:14:43] - Connecting to assignment server
[21:14:45] + Could not connect to Assignment Server
[21:14:45] + Could not connect to Assignment Server 2
[21:14:45] + Couldn't get work instructions.
[21:14:45] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[21:14:59] + Attempting to get work packet
[21:14:59] Passkey found
[21:14:59] - Connecting to assignment server
[21:15:09] + Could not connect to Assignment Server
[21:15:11] + Could not connect to Assignment Server 2
[21:15:11] + Couldn't get work instructions.
[21:15:11] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[21:15:22] + Attempting to get work packet
[21:15:22] Passkey found
[21:15:22] - Connecting to assignment server
[21:15:44] - Couldn't send HTTP request to server
[21:15:44] + Could not connect to Assignment Server
[21:15:44] + No appropriate work server was available; will try again in a bit.
[21:15:44] + Couldn't get work instructions.
[21:15:44] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[21:16:12] + Attempting to get work packet
[21:16:12] Passkey found
[21:16:12] - Connecting to assignment server
[21:16:14] - Successful: assigned to (130.237.232.140).
[21:16:14] + News From Folding@Home: Welcome to Folding@Home
[21:16:14] Loaded queue successfully.
[21:17:13] Project: 6041 (Run 0, Clone 172, Gen 7)


[21:17:13] + Attempting to send results [April 23 21:17:13 UTC]
[21:22:27] + Results successfully sent
[21:22:27] Thank you for your contribution to Folding@Home.
[21:22:27] + Number of Units Completed: 47

[21:22:29] + Closed connections
[21:22:29] 
[21:22:29] + Processing work unit
[21:22:29] Core required: FahCore_a3.exe
[21:22:29] Core found.
[21:22:29] Working on queue slot 08 [April 23 21:22:29 UTC]
[21:22:29] + Working ...
[21:22:29] 
[21:22:29] *------------------------------*
[21:22:29] Folding@Home Gromacs SMP Core
[21:22:29] Version 2.17 (Mar 12, 2010)
[21:22:29] 
[21:22:29] Preparing to commence simulation
[21:22:29] - Looking at optimizations...
[21:22:29] - Created dyn
[21:22:29] - Files status OK
[21:22:31] - Expanded 4300447 -> 10427873 (decompressed 242.4 percent)
[21:22:31] Called DecompressByteArray: compressed_data_size=4300447 data_size=10427873, decompressed_data_size=10427873 diff=0
[21:22:31] - Digital signature verified
[21:22:31] 
[21:22:31] Project: 6013 (Run 0, Clone 96, Gen 137)
[21:22:31] 
[21:22:32] Assembly optimizations on if available.
[21:22:32] Entering M.D.
[21:22:43] Completed 0 out of 250000 steps  (0%)
[21:30:36] Completed 2500 out of 250000 steps  (1%)
[21:38:07] Completed 5000 out of 250000 steps  (2%)

Re: Problems uploading to http://171.64.65.54:8080/

Posted: Sat Apr 24, 2010 6:32 pm
by dchamberlain
The problem is resolved.

The latest 6041 failed to send, just as the previous 2. When I was looking at the machine, I noticed a 20% processor utilization that shouldn't have been there. Upon further investigation, I found that an AVG network scanner process was consuming that 20% and also increasing in memory usage fairly rapidly. I uninstalled AVG and restarted and the upload is now proceeding as it should.

Hopefully this will help if anyone else encounters this problem in the future.

Re: Problems uploading to http://171.64.65.54:8080/

Posted: Sat Apr 24, 2010 11:27 pm
by Sahkuhnder
After the problem sending the 6041 posted above the next two WUs 6013 and 6024 sent normally.

I am not using an anti-virus on this computer.