http://assign-GPU.stanford.edu:8080 - Issues?

Moderators: Site Moderators, FAHC Science Team

v00d00
Posts: 390
Joined: Sun Dec 02, 2007 4:53 am
Hardware configuration: FX8320e (6 cores enabled) @ stock,
- 16GB DDR3,
- Zotac GTX 1050Ti @ Stock.
- Gigabyte GTX 970 @ Stock
Debian 9.

Running GPU since it came out, CPU since client version 3.
Folding since Folding began (~2000) and ran Genome@Home for a while too.
Ran Seti@Home prior to that.
Location: UK
Contact:

http://assign-GPU.stanford.edu:8080 - Issues?

Post by v00d00 »

Im unable to get work at present for the gpu client.

I cant remember if its meant to say OK or not, but at the minute its downloading a binary file.

I've rebooted, and tried from both my machines and one on a different network to no avail.

Code: Select all

[11:49:16] + Attempting to send results [May 21 11:49:16 UTC]
[11:49:16] - Reading file work/wuresults_07.dat from core
[11:49:16]   (Read 185546 bytes from disk)
[11:49:16] Connecting to http://171.64.65.106:8080/
[11:49:23] Posted data.
[11:49:23] Initial: 0000; - Uploaded at ~26 kB/s
[11:49:23] - Averaged speed for that direction ~20 kB/s
[11:49:23] + Results successfully sent
[11:49:23] Thank you for your contribution to Folding@Home.
[11:49:23] + Number of Units Completed: 506

[11:49:27] Trying to send all finished work units
[11:49:27] + No unsent completed units remaining.
[11:49:27] - Preparing to get new work unit...
[11:49:27] + Attempting to get work packet
[11:49:27] - Will indicate memory of 1024 MB
[11:49:27] - Connecting to assignment server
[11:49:27] Connecting to http://assign-GPU.stanford.edu:8080/
[11:49:28] Posted data.
[11:49:28] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[11:49:28] + News From Folding@Home: Welcome to Folding@Home
[11:49:28] Loaded queue successfully.
[11:49:28] Connecting to http://171.64.65.106:8080/
[11:49:28] Posted data.
[11:49:28] Initial: 0000; + Could not connect to Work Server
[11:49:28] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[11:49:36] + Attempting to get work packet
[11:49:36] - Will indicate memory of 1024 MB
[11:49:36] - Connecting to assignment server
[11:49:36] Connecting to http://assign-GPU.stanford.edu:8080/
[11:49:37] Posted data.
[11:49:37] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[11:49:37] + News From Folding@Home: Welcome to Folding@Home
[11:49:37] Loaded queue successfully.
[11:49:37] Connecting to http://171.64.65.106:8080/
[11:49:38] Posted data.
[11:49:38] Initial: 0000; + Could not connect to Work Server
[11:49:38] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[11:49:58] + Attempting to get work packet
[11:49:58] - Will indicate memory of 1024 MB
[11:49:58] - Connecting to assignment server
[11:49:58] Connecting to http://assign-GPU.stanford.edu:8080/
[11:49:59] Posted data.
[11:49:59] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[11:49:59] + News From Folding@Home: Welcome to Folding@Home
[11:49:59] Loaded queue successfully.
[11:49:59] Connecting to http://171.64.65.106:8080/
[11:50:00] Posted data.
[11:50:00] Initial: 0000; + Could not connect to Work Server
[11:50:00] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[11:50:22] + Attempting to get work packet
[11:50:22] - Will indicate memory of 1024 MB
[11:50:22] - Connecting to assignment server
[11:50:22] Connecting to http://assign-GPU.stanford.edu:8080/
[11:50:23] Posted data.
[11:50:23] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[11:50:23] + News From Folding@Home: Welcome to Folding@Home
[11:50:23] Loaded queue successfully.
[11:50:23] Connecting to http://171.64.65.106:8080/
[11:50:23] Posted data.
[11:50:23] Initial: 0000; + Could not connect to Work Server
[11:50:23] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[11:51:09] + Attempting to get work packet
[11:51:09] - Will indicate memory of 1024 MB
[11:51:09] - Connecting to assignment server
[11:51:09] Connecting to http://assign-GPU.stanford.edu:8080/
[11:51:10] Posted data.
[11:51:10] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[11:51:10] + News From Folding@Home: Welcome to Folding@Home
[11:51:11] Loaded queue successfully.
[11:51:11] Connecting to http://171.64.65.106:8080/
[11:51:11] Posted data.
[11:51:11] Initial: 0000; + Could not connect to Work Server
[11:51:11] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[11:52:43] + Attempting to get work packet
[11:52:43] - Will indicate memory of 1024 MB
[11:52:43] - Connecting to assignment server
[11:52:43] Connecting to http://assign-GPU.stanford.edu:8080/
[11:52:44] Posted data.
[11:52:44] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[11:52:44] + Couldn't get work instructions.
[11:52:44] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[11:55:28] + Attempting to get work packet
[11:55:28] - Will indicate memory of 1024 MB
[11:55:28] - Connecting to assignment server
[11:55:28] Connecting to http://assign-GPU.stanford.edu:8080/
[11:55:29] Posted data.
[11:55:29] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[11:55:29] + Couldn't get work instructions.
[11:55:29] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[12:00:51] + Attempting to get work packet
[12:00:51] - Will indicate memory of 1024 MB
[12:00:51] - Connecting to assignment server
[12:00:51] Connecting to http://assign-GPU.stanford.edu:8080/
[12:00:52] Posted data.
[12:00:52] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[12:00:52] + Couldn't get work instructions.
[12:00:52] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[12:11:40] + Attempting to get work packet
[12:11:40] - Will indicate memory of 1024 MB
[12:11:40] - Connecting to assignment server
[12:11:40] Connecting to http://assign-GPU.stanford.edu:8080/
[12:11:41] Posted data.
[12:11:41] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[12:11:41] + Couldn't get work instructions.
~
[14:07:30] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
I've tried different flags and all still generate the same issue.

[EDIT]

Someone fixed it.

Thanks

Mods. Feel free to lock this.
Image
Fernando_Celio
Posts: 28
Joined: Thu Dec 13, 2007 6:02 pm
Location: Rio de Janeiro - Brazil

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by Fernando_Celio »

Gentlemen,

It's seems that this server is always redirect the request of WU's to server 171.64.65.106, which fails to send any work to the requesting machine.

Is there any other NVIDIA GPU work server capable to send jobs available ?

Best Regards, Fernando.
Always remember Dick Howell.
dhoshaw
Posts: 1
Joined: Fri May 15, 2009 12:17 am
Hardware configuration: Intel Q9550 @3.6 GHz
XFX 9800GX2
Hyper TX2 lapped
Gigabyte GA-EP45-UD3P
2 x 2 GB Corsair XMS2 1066C5
1 x 500 GB + 1 x 1 TB
X-Fi XtremeGamer
Antec P180 / Corsair 750TX
Windows 7 RC x64
Location: Florida

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by dhoshaw »

I'm having the same issue; currently, one of my gpu client has failed 11 times to get a new wu. The other client just finished one so we'll see if it can get a new wu. This has been happening since the upgrade.
Image
Ragnar Dan
Posts: 52
Joined: Fri Dec 07, 2007 3:21 am
Location: U.S. (TechReport.com's Team 2630)

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by Ragnar Dan »

I've been having problems for the last 13.5 hours on the same servers. I've seen problems with the GPU server(s) increasing lately, with failures to upload completed WU's and to download new ones.
Shadowtester
Posts: 79
Joined: Tue Dec 04, 2007 4:18 am

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by Shadowtester »

Yea it seems to becoming a larger issue lately over the last few days it seems like we almost have to fight for a work unit to fold not good especially going into a holiday weekend!

Code: Select all

[18:58:12] Folding@home Core Shutdown: FINISHED_UNIT
[18:58:15] CoreStatus = 64 (100)
[18:58:15] Unit 1 finished with 94 percent of time to deadline remaining.
[18:58:15] Updated performance fraction: 0.965291
[18:58:15] Sending work to server
[18:58:15] Project: 5749 (Run 11, Clone 244, Gen 25)
[18:58:15] - Read packet limit of 540015616... Set to 524286976.


[18:58:15] + Attempting to send results [May 21 18:58:15 UTC]
[18:58:15] - Reading file work/wuresults_01.dat from core
[18:58:15]   (Read 155321 bytes from disk)
[18:58:15] Connecting to http://171.67.108.11:8080/
[18:58:15] - Couldn't send HTTP request to server
[18:58:15] + Could not connect to Work Server (results)
[18:58:15]     (171.67.108.11:8080)
[18:58:15] + Retrying using alternative port
[18:58:15] Connecting to http://171.67.108.11:80/
[18:58:15] - Couldn't send HTTP request to server
[18:58:15] + Could not connect to Work Server (results)
[18:58:15]     (171.67.108.11:80)
[18:58:15] - Error: Could not transmit unit 01 (completed May 21) to work server.
[18:58:15] - 1 failed uploads of this unit.
[18:58:15]   Keeping unit 01 in queue.
[18:58:15] Trying to send all finished work units
[18:58:15] Project: 5749 (Run 11, Clone 244, Gen 25)
[18:58:15] - Read packet limit of 540015616... Set to 524286976.


[18:58:15] + Attempting to send results [May 21 18:58:15 UTC]
[18:58:15] - Reading file work/wuresults_01.dat from core
[18:58:15]   (Read 155321 bytes from disk)
[18:58:15] Connecting to http://171.67.108.11:8080/
[18:58:15] - Couldn't send HTTP request to server
[18:58:15] + Could not connect to Work Server (results)
[18:58:15]     (171.67.108.11:8080)
[18:58:15] + Retrying using alternative port
[18:58:15] Connecting to http://171.67.108.11:80/
[18:58:15] - Couldn't send HTTP request to server
[18:58:15] + Could not connect to Work Server (results)
[18:58:15]     (171.67.108.11:80)
[18:58:15] - Error: Could not transmit unit 01 (completed May 21) to work server.
[18:58:15] - 2 failed uploads of this unit.
[18:58:15] - Read packet limit of 540015616... Set to 524286976.


[18:58:15] + Attempting to send results [May 21 18:58:15 UTC]
[18:58:15] - Reading file work/wuresults_01.dat from core
[18:58:15]   (Read 155321 bytes from disk)
[18:58:15] Connecting to http://171.67.108.25:8080/
[18:58:15] - Couldn't send HTTP request to server
[18:58:15] + Could not connect to Work Server (results)
[18:58:15]     (171.67.108.25:8080)
[18:58:15] + Retrying using alternative port
[18:58:15] Connecting to http://171.67.108.25:80/
[18:58:15] - Couldn't send HTTP request to server
[18:58:15] + Could not connect to Work Server (results)
[18:58:15]     (171.67.108.25:80)
[18:58:15]   Could not transmit unit 01 to Collection server; keeping in queue.
[18:58:15] + Sent 0 of 1 completed units to the server
[18:58:15] - Preparing to get new work unit...
[18:58:15] + Attempting to get work packet
[18:58:15] - Will indicate memory of 1024 MB
[18:58:15] - Connecting to assignment server
[18:58:15] Connecting to http://assign-GPU.stanford.edu:8080/
[18:58:16] Posted data.
[18:58:16] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[18:58:16] + Couldn't get work instructions.
[18:58:16] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[18:58:26] + Attempting to get work packet
[18:58:26] - Will indicate memory of 1024 MB
[18:58:26] - Connecting to assignment server
[18:58:26] Connecting to http://assign-GPU.stanford.edu:8080/
[18:58:27] Posted data.
[18:58:27] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[18:58:27] + Couldn't get work instructions.
[18:58:27] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[18:58:45] + Attempting to get work packet
[18:58:45] - Will indicate memory of 1024 MB
[18:58:45] - Connecting to assignment server
[18:58:45] Connecting to http://assign-GPU.stanford.edu:8080/
[18:58:45] Posted data.
[18:58:45] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[18:58:45] + Couldn't get work instructions.
[18:58:45] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[18:59:11] + Attempting to get work packet
[18:59:11] - Will indicate memory of 1024 MB
[18:59:11] - Connecting to assignment server
[18:59:11] Connecting to http://assign-GPU.stanford.edu:8080/
[18:59:11] Posted data.
[18:59:11] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[18:59:11] + Couldn't get work instructions.
[18:59:11] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[18:59:58] + Attempting to get work packet
[18:59:58] - Will indicate memory of 1024 MB
[18:59:58] - Connecting to assignment server
[18:59:58] Connecting to http://assign-GPU.stanford.edu:8080/
[18:59:59] Posted data.
[18:59:59] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[18:59:59] + Couldn't get work instructions.
[18:59:59] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[19:01:27] + Attempting to get work packet
[19:01:27] - Will indicate memory of 1024 MB
[19:01:27] - Connecting to assignment server
[19:01:27] Connecting to http://assign-GPU.stanford.edu:8080/
[19:01:27] Posted data.
[19:01:27] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[19:01:27] + Couldn't get work instructions.
[19:01:27] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[19:04:17] + Attempting to get work packet
[19:04:17] - Will indicate memory of 1024 MB
[19:04:17] - Connecting to assignment server
[19:04:17] Connecting to http://assign-GPU.stanford.edu:8080/
[19:04:17] Posted data.
[19:04:17] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[19:04:17] + Couldn't get work instructions.
[19:04:17] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[19:09:44] + Attempting to get work packet
[19:09:44] - Will indicate memory of 1024 MB
[19:09:44] - Connecting to assignment server
[19:09:44] Connecting to http://assign-GPU.stanford.edu:8080/
[19:09:44] Posted data.
[19:09:44] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[19:09:44] + News From Folding@Home: Welcome to Folding@Home
[19:09:45] Loaded queue successfully.
[19:09:45] Connecting to http://171.64.65.106:8080/
[19:09:45] Posted data.
[19:09:45] Initial: 0000; + Could not connect to Work Server
[19:09:45] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[19:20:31] + Attempting to get work packet
[19:20:31] - Will indicate memory of 1024 MB
[19:20:31] - Connecting to assignment server
[19:20:31] Connecting to http://assign-GPU.stanford.edu:8080/
[19:20:31] Posted data.
[19:20:31] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[19:20:31] + Couldn't get work instructions.
[19:20:31] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
Shadowtester

Image
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by bruce »

According to the News Blog, that problem has been fixed. Please post again if that is inaccurate.
http://folding.typepad.com/
franzforfolding
Posts: 1
Joined: Thu May 21, 2009 7:51 pm

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by franzforfolding »

One of my GPUs is having trouble with this server, but my other card just found work a few minutes ago after I restarted the client.

Problem GPU.

Code: Select all

Launch directory: C:\Users\Administrator\AppData\Roaming\Folding@home-gpu
Arguments: -gpu 0 -verbosity 9 -advmethods 

[20:32:40] - Ask before connecting: No
[20:32:40] - User name: franz (Team 37726)
[20:32:40] - User ID: A14A9DC7B2C4D98
[20:32:40] - Machine ID: 6
[20:32:40] 
[20:32:40] Loaded queue successfully.
[20:32:40] Initialization complete
[20:32:40] - Preparing to get new work unit...
[20:32:40] + Attempting to get work packet
[20:32:40] - Autosending finished units... [May 21 20:32:40 UTC]
[20:32:40] Trying to send all finished work units
[20:32:40] + No unsent completed units remaining.
[20:32:40] - Autosend completed
[20:32:40] - Will indicate memory of 2045 MB
[20:32:40] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 15, Stepping: 6
[20:32:40] - Connecting to assignment server
[20:32:40] Connecting to http://assign-GPU.stanford.edu:8080/
[20:32:41] Posted data.
[20:32:41] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:32:41] + News From Folding@Home: Welcome to Folding@Home
[20:32:41] Loaded queue successfully.
[20:32:41] Connecting to http://171.64.65.106:8080/
[20:32:42] Posted data.
[20:32:42] Initial: 0000; + Could not connect to Work Server
[20:32:42] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[20:32:56] + Attempting to get work packet
[20:32:56] - Will indicate memory of 2045 MB
[20:32:56] - Connecting to assignment server
[20:32:56] Connecting to http://assign-GPU.stanford.edu:8080/
[20:32:56] Posted data.
[20:32:56] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:32:56] + News From Folding@Home: Welcome to Folding@Home
[20:32:57] Loaded queue successfully.
[20:32:57] Connecting to http://171.64.65.106:8080/
[20:32:57] Posted data.
[20:32:57] Initial: 0000; + Could not connect to Work Server
[20:32:57] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[20:33:07] + Attempting to get work packet
[20:33:07] - Will indicate memory of 2045 MB
[20:33:07] - Connecting to assignment server
[20:33:07] Connecting to http://assign-GPU.stanford.edu:8080/
[20:33:08] Posted data.
[20:33:08] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:33:08] + News From Folding@Home: Welcome to Folding@Home
[20:33:08] Loaded queue successfully.
[20:33:08] Connecting to http://171.64.65.106:8080/
[20:33:08] Posted data.
[20:33:08] Initial: 0000; + Could not connect to Work Server
[20:33:08] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[20:33:43] + Attempting to get work packet
[20:33:43] - Will indicate memory of 2045 MB
[20:33:43] - Connecting to assignment server
[20:33:43] Connecting to http://assign-GPU.stanford.edu:8080/
[20:33:43] Posted data.
[20:33:43] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:33:43] + News From Folding@Home: Welcome to Folding@Home
[20:33:44] Loaded queue successfully.
[20:33:44] Connecting to http://171.64.65.106:8080/
[20:33:44] Posted data.
[20:33:44] Initial: 0000; + Could not connect to Work Server
[20:33:44] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[20:34:28] + Attempting to get work packet
[20:34:28] - Will indicate memory of 2045 MB
[20:34:28] - Connecting to assignment server
[20:34:28] Connecting to http://assign-GPU.stanford.edu:8080/
[20:34:29] Posted data.
[20:34:29] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:34:29] + News From Folding@Home: Welcome to Folding@Home
[20:34:29] Loaded queue successfully.
[20:34:29] Connecting to http://171.64.65.106:8080/
[20:34:30] Posted data.
[20:34:30] Initial: 0000; + Could not connect to Work Server
[20:34:30] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[20:36:02] + Attempting to get work packet
[20:36:02] - Will indicate memory of 2045 MB
[20:36:02] - Connecting to assignment server
[20:36:02] Connecting to http://assign-GPU.stanford.edu:8080/
[20:36:02] Posted data.
[20:36:02] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:36:02] + News From Folding@Home: Welcome to Folding@Home
[20:36:02] Loaded queue successfully.
[20:36:02] Connecting to http://171.64.65.106:8080/
[20:36:03] Posted data.
[20:36:03] Initial: 0000; + Could not connect to Work Server
[20:36:03] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
Working GPU.

Code: Select all

Arguments: -gpu 2 -verbosity 9 -advmethods 

[20:32:31] - Ask before connecting: No
[20:32:31] - User name: franz (Team 37726)
[20:32:31] - User ID: A14A9DC7B2C4D98
[20:32:31] - Machine ID: 2
[20:32:31] 
[20:32:31] Loaded queue successfully.
[20:32:31] Initialization complete
[20:32:31] - Preparing to get new work unit...
[20:32:31] + Attempting to get work packet
[20:32:31] - Autosending finished units... [20:32:31]
[20:32:31] Trying to send all finished work units
[20:32:31] + No unsent completed units remaining.
[20:32:31] - Autosend completed
[20:32:31] - Will indicate memory of 2045 MB
[20:32:31] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 15, Stepping: 6
[20:32:31] - Connecting to assignment server
[20:32:31] Connecting to http://assign-GPU.stanford.edu:8080/
[20:32:31] Posted data.
[20:32:31] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:32:31] + News From Folding@Home: Welcome to Folding@Home
[20:32:31] Loaded queue successfully.
[20:32:31] Connecting to http://171.64.65.106:8080/
[20:32:32] Posted data.
[20:32:32] Initial: 0000; + Could not connect to Work Server
[20:32:32] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[20:32:45] + Attempting to get work packet
[20:32:45] - Will indicate memory of 2045 MB
[20:32:45] - Connecting to assignment server
[20:32:45] Connecting to http://assign-GPU.stanford.edu:8080/
[20:32:45] Posted data.
[20:32:45] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:32:45] + News From Folding@Home: Welcome to Folding@Home
[20:32:45] Loaded queue successfully.
[20:32:45] Connecting to http://171.64.65.106:8080/
[20:32:46] Posted data.
[20:32:46] Initial: 0000; + Could not connect to Work Server
[20:32:46] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[20:32:58] + Attempting to get work packet
[20:32:58] - Will indicate memory of 2045 MB
[20:32:58] - Connecting to assignment server
[20:32:58] Connecting to http://assign-GPU.stanford.edu:8080/
[20:32:58] Posted data.
[20:32:58] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:32:58] + News From Folding@Home: Welcome to Folding@Home
[20:32:59] Loaded queue successfully.
[20:32:59] Connecting to http://171.64.65.106:8080/
[20:32:59] Posted data.
[20:32:59] Initial: 0000; + Could not connect to Work Server
[20:32:59] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[20:33:33] + Attempting to get work packet
[20:33:33] - Will indicate memory of 2045 MB
[20:33:33] - Connecting to assignment server
[20:33:33] Connecting to http://assign-GPU.stanford.edu:8080/
[20:33:33] Posted data.
[20:33:33] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:33:33] + News From Folding@Home: Welcome to Folding@Home
[20:33:34] Loaded queue successfully.
[20:33:34] Connecting to http://171.64.65.106:8080/
[20:33:34] Posted data.
[20:33:34] Initial: 0000; + Could not connect to Work Server
[20:33:34] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[20:34:18] + Attempting to get work packet
[20:34:18] - Will indicate memory of 2045 MB
[20:34:18] - Connecting to assignment server
[20:34:18] Connecting to http://assign-GPU.stanford.edu:8080/
[20:34:20] Posted data.
[20:34:20] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:34:20] + News From Folding@Home: Welcome to Folding@Home
[20:34:20] Loaded queue successfully.
[20:34:20] Connecting to http://171.64.65.106:8080/
[20:34:20] Posted data.
[20:34:20] Initial: 0000; - Receiving payload (expected size: 66814)
[20:34:21] - Downloaded at ~65 kB/s
[20:34:21] - Averaged speed for that direction ~74 kB/s
[20:34:21] + Received work.
[20:34:21] + Closed connections
[20:34:21] 
[20:34:21] + Processing work unit
[20:34:21] Core required: FahCore_11.exe
[20:34:21] Core found.
[20:34:21] Working on queue slot 09 [May 21 20:34:21 UTC]
[20:34:21] + Working ...
[20:34:21] - Calling '.\FahCore_11.exe -dir work/ -suffix 09 -priority 96 -nocpulock -checkpoint 15 -verbose -lifeline 1172 -version 623'

[20:34:21] 
[20:34:21] *------------------------------*
[20:34:21] Folding@Home GPU Core - Beta
[20:34:21] Version 1.19 (Mon Nov 3 09:34:13 PST 2008)
[20:34:21] 
[20:34:21] Compiler  : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86 
[20:34:21] Build host: amoeba
[20:34:21] Board Type: Nvidia
[20:34:21] Core      : 
[20:34:21] Preparing to commence simulation
[20:34:21] - Looking at optimizations...
[20:34:21] - Created dyn
[20:34:21] - Files status OK
[20:34:21] - Expanded 66302 -> 348500 (decompressed 525.6 percent)
[20:34:21] Called DecompressByteArray: compressed_data_size=66302 data_size=348500, decompressed_data_size=348500 diff=0
[20:34:21] - Digital signature verified
[20:34:21] 
[20:34:21] Project: 5780 (Run 11, Clone 832, Gen 24)
[20:34:21] 
[20:34:21] Assembly optimizations on if available.
[20:34:21] Entering M.D.
[20:34:28] Working on Protein
[20:34:29] Client config found, loading data.
[20:34:29] Starting GUI Server
Is there still a problem with the server or should I start looking at my hardware?
Image
doglived
Posts: 1
Joined: Sat May 16, 2009 10:06 am

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by doglived »

I'm having the same issue on two systems, each GPU client cannot send or receive work. (My SMP and CPU clients are working normally.)

Both machines can ping assign-gpu.stanford.edu (vsp10v-vz01.stanford.edu [171.67.108.201] )

The same error on both clients:

Code: Select all

[20:44:49] Connecting to http://assign-GPU.stanford.edu:8080/
[20:44:49] Posted data.
[20:44:49] Initial: 0000; + No appropriate work server was available; will try a
gain in a bit.
[20:44:49] + Couldn't get work instructions.
[20:44:49] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
a more detailed listing from one of the clients

Code: Select all

[20:33:43] - Connecting to assignment server
[20:33:43] Connecting to http://assign-GPU.stanford.edu:8080/
[20:33:43] Trying to send all finished work units
[20:33:43] Project: 5752 (Run 7, Clone 190, Gen 214)
[20:33:43] - Read packet limit of 540015616... Set to 524286976.


[20:33:43] + Attempting to send results [May 21 20:33:43 UTC]
[20:33:43] - Reading file work/wuresults_01.dat from core
[20:33:43]   (Read 155752 bytes from disk)
[20:33:43] Connecting to http://171.67.108.11:8080/
[20:33:43] Posted data.
[20:33:43] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:33:43] + News From Folding@Home: Welcome to Folding@Home
[20:33:43] Loaded queue successfully.
[20:33:43] Connecting to http://171.64.65.106:8080/
[20:33:43] Posted data.
[20:33:43] Initial: 0000; + Could not connect to Work Server
[20:33:43] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[20:33:44] - Couldn't send HTTP request to server
[20:33:44] + Could not connect to Work Server (results)
[20:33:44]     (171.67.108.11:8080)
[20:33:44] + Retrying using alternative port
[20:33:44] Connecting to http://171.67.108.11:80/
[20:33:45] - Couldn't send HTTP request to server
[20:33:45] + Could not connect to Work Server (results)
[20:33:45]     (171.67.108.11:80)
[20:33:45] - Error: Could not transmit unit 01 (completed May 21) to work server
.
[20:33:45] - 4 failed uploads of this unit.
[20:33:45] - Read packet limit of 540015616... Set to 524286976.


[20:33:45] + Attempting to send results [May 21 20:33:45 UTC]
[20:33:45] - Reading file work/wuresults_01.dat from core
[20:33:45]   (Read 155752 bytes from disk)
[20:33:45] Connecting to http://171.67.108.25:8080/
[20:33:46] - Couldn't send HTTP request to server
[20:33:46] + Could not connect to Work Server (results)
[20:33:46]     (171.67.108.25:8080)
[20:33:46] + Retrying using alternative port
[20:33:46] Connecting to http://171.67.108.25:80/
[20:33:47] - Couldn't send HTTP request to server
[20:33:47] + Could not connect to Work Server (results)
[20:33:47]     (171.67.108.25:80)
[20:33:47]   Could not transmit unit 01 to Collection server; keeping in queue.
[20:33:47] + Sent 0 of 1 completed units to the server
[20:33:47] - Autosend completed
[20:33:55] + Attempting to get work packet
[20:33:55] - Will indicate memory of 512 MB
[20:33:55] - Connecting to assignment server
[20:33:55] Connecting to http://assign-GPU.stanford.edu:8080/
[20:33:55] Posted data.
[20:33:55] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:33:55] + News From Folding@Home: Welcome to Folding@Home
[20:33:55] Loaded queue successfully.
[20:33:55] Connecting to http://171.64.65.106:8080/
[20:33:56] Posted data.
[20:33:56] Initial: 0000; + Could not connect to Work Server
[20:33:56] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[20:34:08] + Attempting to get work packet
[20:34:08] - Will indicate memory of 512 MB
[20:34:08] - Connecting to assignment server
[20:34:08] Connecting to http://assign-GPU.stanford.edu:8080/
[20:34:08] Posted data.
[20:34:08] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:34:08] + News From Folding@Home: Welcome to Folding@Home
[20:34:08] Loaded queue successfully.
[20:34:08] Connecting to http://171.64.65.106:8080/
[20:34:08] Posted data.
[20:34:08] Initial: 0000; + Could not connect to Work Server
[20:34:08] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[20:34:31] + Attempting to get work packet
[20:34:31] - Will indicate memory of 512 MB
[20:34:31] - Connecting to assignment server
[20:34:31] Connecting to http://assign-GPU.stanford.edu:8080/
[20:34:33] Posted data.
[20:34:33] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:34:33] + News From Folding@Home: Welcome to Folding@Home
[20:34:33] Loaded queue successfully.
[20:34:33] Connecting to http://171.64.65.106:8080/
[20:34:33] Posted data.
[20:34:33] Initial: 0000; + Could not connect to Work Server
[20:34:33] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[20:35:14] + Attempting to get work packet
[20:35:14] - Will indicate memory of 512 MB
[20:35:14] - Connecting to assignment server
[20:35:14] Connecting to http://assign-GPU.stanford.edu:8080/
[20:35:14] Posted data.
[20:35:14] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[20:35:14] + News From Folding@Home: Welcome to Folding@Home
[20:35:14] Loaded queue successfully.
[20:35:14] Connecting to http://171.64.65.106:8080/
[20:35:15] Posted data.
[20:35:15] Initial: 0000; + Could not connect to Work Server
[20:35:15] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[20:36:37] + Attempting to get work packet
[20:36:37] - Will indicate memory of 512 MB
[20:36:37] - Connecting to assignment server
[20:36:37] Connecting to http://assign-GPU.stanford.edu:8080/
[20:36:37] Posted data.
[20:36:37] Initial: 0000; + No appropriate work server was available; will try a
gain in a bit.
[20:36:37] + Couldn't get work instructions.
[20:36:37] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[20:39:20] + Attempting to get work packet
[20:39:20] - Will indicate memory of 512 MB
[20:39:20] - Connecting to assignment server
[20:39:20] Connecting to http://assign-GPU.stanford.edu:8080/
[20:39:21] Posted data.
[20:39:21] Initial: 0000; + No appropriate work server was available; will try a
gain in a bit.
[20:39:21] + Couldn't get work instructions.
[20:39:21] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[20:44:49] + Attempting to get work packet
[20:44:49] - Will indicate memory of 512 MB
[20:44:49] - Connecting to assignment server
[20:44:49] Connecting to http://assign-GPU.stanford.edu:8080/
[20:44:49] Posted data.
[20:44:49] Initial: 0000; + No appropriate work server was available; will try a
gain in a bit.
[20:44:49] + Couldn't get work instructions.
[20:44:49] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
Last edited by doglived on Thu May 21, 2009 9:01 pm, edited 1 time in total.
dempaSD
Posts: 17
Joined: Tue Nov 18, 2008 2:16 am
Location: Sweden and US

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by dempaSD »

It's a mess. Problem has been coming and going several longer (at least 4) periods last 2-3 days. Most of my GPU's idle now waiting for proper response from AS. I've posted example error messages from log in other threads.
Image
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by bruce »

dempaSD wrote:It's a mess.
I agree, but there obviously have been several different problems contributing to what looks like a single problem. Several of the specific problems have been fixed and I suspect that has exposed others which will continue to be worked on until you can dependably get work. Unfortunately there's no way to predict when that will be.
Ragnar Dan
Posts: 52
Joined: Fri Dec 07, 2007 3:21 am
Location: U.S. (TechReport.com's Team 2630)

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by Ragnar Dan »

Normally one tests a new system before replacing a reliable, older one. And often it's possible to run them together, and as the new system proves its reliability, the old one can be retired.
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by bruce »

That has been happening for the past several months. The choice was to shut down FAH entirely for most of the weekend, or migrate a number of servers and keep most of it running while working out the final bugs that only show up when the servers are stressed. You're cerainly entitled to disagree, but I think they made the right choice.
VijayPande
Pande Group Member
Posts: 2058
Joined: Fri Nov 30, 2007 6:25 am
Location: Stanford

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by VijayPande »

Looking at the AS and work servers, there seems to be lots of normal assigns and jobs, but we will continue to look on our side as well to see what's up.

The server migration did prove to be much messier than we originally had thought. For now, all the known issues have been resolved, but there may be something else that we haven't caught yet.

In posting logs, we would ideally like to know

- did you client even talk to the AS
- if it did talk, what did it say (did it give a WS or say none is available)
- if it talked to the WS, what happened

Thanks in advance for your help with fixing this issue.
Prof. Vijay Pande, PhD
Departments of Chemistry, Structural Biology, and Computer Science
Chair, Biophysics
Director, Folding@home Distributed Computing Project
Stanford University
Ragnar Dan
Posts: 52
Joined: Fri Dec 07, 2007 3:21 am
Location: U.S. (TechReport.com's Team 2630)

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by Ragnar Dan »

Sorry for the wait (and my tone, which resulted from momentary annoyance), and thanks for responding so quickly.

I've got some logs from a day or two ago that show extended failures to upload now and then, but usually they got resolved when the AS eventually gave me a WS and that gave me a WU, which then made the client try to upload the previous WU again. The failure to get a new WU problem was the worse of the 2, obviously.

It appears the problems have been resolved, though, since I've gotten I think 5 successful WU uploads and downloads between my last post and this one on one GPU, and 3 on the other.

There does still seem to be a problem with incomplete deletion of data files in the work directory when a WU crashes, though, and that seems to cause later WU's in the same slot to start in the middle and then crash (though oddly not in the same frame, the crashed one in this example crashed at "Completed 56%" while the new one started at and crashed after "Competed 36%"). That happened on a GPU I still have the FAHlog file for, though I assume you want the report in a different subforum.
codysluder
Posts: 1024
Joined: Sun Dec 02, 2007 12:43 pm

Re: http://assign-GPU.stanford.edu:8080 - Issues?

Post by codysluder »

Ragnar Dan wrote:There does still seem to be a problem with incomplete deletion of data files in the work directory when a WU crashes, though, and that seems to cause later WU's in the same slot to start in the middle and then crash (though oddly not in the same frame, the crashed one in this example crashed at "Completed 56%" while the new one started at and crashed after "Competed 36%"). That happened on a GPU I still have the FAHlog file for, though I assume you want the report in a different subforum.
This problem has been reported several times and it's a problem in several different cores. Some of the cores have been fixed and others have not. Is your report associated with a gpu from ATI or from NVidia? Was it FahCore_11 or some other FahCore?

A Mod can move it to the correct forum if he has all the necessary information.
Locked