Page 3 of 3
Re: Server - 171.64.65.106
Posted: Fri May 22, 2009 6:20 pm
by dedgar
My only two GPU's are trying to get work from the 106 server. One of them has been trying for more than an hour to get work.
My status logs tell me:
[18:13:17] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[18:13:17] + Couldn't get work instructions.
When I go to the server status page, that tells me that the 106 server is accepting. So what's up (or down)?
Re: Server - 171.64.65.106
Posted: Fri May 22, 2009 6:23 pm
by sbinh
9 out of 10 gpu clients are waiting for WUs .. the last one is at 91% complete .... When would this issue got fix?
Re: Server - 171.64.65.106
Posted: Fri May 22, 2009 6:27 pm
by shdbcamping
sbinh wrote:9 out of 10 gpu clients are waiting for WUs .. the last one is at 91% complete .... When would this issue got fix?
+++ lots of 1's here.
10 of 11 here, but my electric meter is still spinning waiting at "idle"
Re: Server - 171.64.65.106
Posted: Fri May 22, 2009 6:46 pm
by Plazzman
5 Client's here waiting for work....
Re: Server - 171.64.65.106
Posted: Fri May 22, 2009 7:06 pm
by Plazzman
Just received unit's for all 5 from 171.67.108.11...
Re: Server - 171.64.65.106
Posted: Fri May 22, 2009 7:07 pm
by MichaelO
My Nvidia clients have now all received work, however based on the performance this week, my guess is that there will be huge amonts of downtime this 3-day holiday weekend.
Re: Server - 171.64.65.106
Posted: Fri May 22, 2009 7:14 pm
by bruce
shdbcamping wrote:Can we get an ETA from someone with authrity at Pande on how long the "Backlog" will take to get cleared up?
Somebody can probably estimate how many downloads per hour that a server can handle but how do you propose they count the number of clients that need work? (Then, of course, somebody can also estimate how many of them will return a result and be back for more work in X hours and what happens to them.)
Re: Server - 171.64.65.106
Posted: Tue May 26, 2009 1:41 am
by dempaSD
Was working nicely for a few days until now:
Code: Select all
[01:34:14] - Preparing to get new work unit...
[01:34:14] + Attempting to get work packet
[01:34:14] - Will indicate memory of 2815 MB
[01:34:14] - Connecting to assignment server
[01:34:14] Connecting to http://assign-GPU.stanford.edu:8080/
[01:34:15] Posted data.
[01:34:15] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[01:34:15] + News From Folding@Home: Welcome to Folding@Home
[01:34:16] Loaded queue successfully.
[01:34:16] Connecting to http://171.64.65.106:8080/
[01:34:29] - Couldn't send HTTP request to server
[01:34:29] + Could not connect to Work Server
[01:34:29] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[01:34:48] + Attempting to get work packet
[01:34:48] - Will indicate memory of 2815 MB
[01:34:48] - Connecting to assignment server
[01:34:48] Connecting to http://assign-GPU.stanford.edu:8080/
[01:34:49] Posted data.
[01:34:49] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[01:34:49] + News From Folding@Home: Welcome to Folding@Home
[01:34:50] Loaded queue successfully.
[01:34:50] Connecting to http://171.64.65.106:8080/
[01:34:51] - Couldn't send HTTP request to server
[01:34:51] + Could not connect to Work Server
[01:34:51] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[01:35:11] + Attempting to get work packet
[01:35:11] - Will indicate memory of 2815 MB
[01:35:11] - Connecting to assignment server
[01:35:11] Connecting to http://assign-GPU.stanford.edu:8080/
[01:35:12] Posted data.
[01:35:12] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[01:35:12] + News From Folding@Home: Welcome to Folding@Home
[01:35:12] Loaded queue successfully.
[01:35:12] Connecting to http://171.64.65.106:8080/
[01:35:26] - Couldn't send HTTP request to server
[01:35:26] + Could not connect to Work Server
[01:35:26] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[01:35:53] + Attempting to get work packet
[01:35:53] - Will indicate memory of 2815 MB
[01:35:53] - Connecting to assignment server
[01:35:53] Connecting to http://assign-GPU.stanford.edu:8080/
[01:35:54] Posted data.
[01:35:54] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[01:35:54] + News From Folding@Home: Welcome to Folding@Home
[01:35:54] Loaded queue successfully.
[01:35:54] Connecting to http://171.64.65.106:8080/
[01:35:55] Posted data.
[01:35:55] Initial: 0000; + Could not connect to Work Server
[01:35:55] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[01:36:39] + Attempting to get work packet
[01:36:39] - Will indicate memory of 2815 MB
[01:36:39] - Connecting to assignment server
[01:36:39] Connecting to http://assign-GPU.stanford.edu:8080/
[01:36:40] Posted data.
[01:36:40] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[01:36:40] + News From Folding@Home: Welcome to Folding@Home
[01:36:40] Loaded queue successfully.
[01:36:40] Connecting to http://171.64.65.106:8080/
[01:36:41] Posted data.
[01:36:41] Initial: 0000; + Could not connect to Work Server
[01:36:41] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[01:38:03] + Attempting to get work packet
[01:38:03] - Will indicate memory of 2815 MB
[01:38:03] - Connecting to assignment server
[01:38:03] Connecting to http://assign-GPU.stanford.edu:8080/
[01:38:05] Posted data.
[01:38:05] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[01:38:05] + News From Folding@Home: Welcome to Folding@Home
[01:38:05] Loaded queue successfully.
[01:38:05] Connecting to http://171.64.65.106:8080/
[01:38:06] Posted data.
[01:38:06] Initial: 0000; + Could not connect to Work Server
[01:38:06] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
: Luckily seems like it was a short one:
Code: Select all
[01:40:51] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[01:46:18] + Attempting to get work packet
[01:46:18] - Will indicate memory of 2815 MB
[01:46:18] - Connecting to assignment server
[01:46:18] Connecting to http://assign-GPU.stanford.edu:8080/
[01:46:19] Posted data.
[01:46:19] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[01:46:19] + News From Folding@Home: Welcome to Folding@Home
[01:46:19] Loaded queue successfully.
[01:46:19] Connecting to http://171.64.65.106:8080/
[01:46:20] Posted data.
[01:46:20] Initial: 0000; - Receiving payload (expected size: 66761)
[01:46:22] - Downloaded at ~32 kB/s
[01:46:22] - Averaged speed for that direction ~69 kB/s
[01:46:22] + Received work.
[01:46:22] Trying to send all finished work units
[01:46:22] + No unsent completed units remaining.
[01:46:22] + Closed connections
[01:46:22]
[01:46:22] + Processing work unit
[01:46:22] Core required: FahCore_11.exe
[01:46:22] Core found.
[01:46:22] Working on queue slot 00 [May 26 01:46:22 UTC]
[01:46:22] + Working ...
[01:46:22] - Calling '.\FahCore_11.exe -dir work/ -suffix 00 -priority 96 -nocpulock -checkpoint 15 -verbose -lifeline 4360 -version 623'
All goody now.
Re: Server - 171.64.65.106
Posted: Tue May 26, 2009 2:11 am
by vsekh
The server has 118 work units available. It will most likely run out. I have several GPU clients trying to get a work unit from this server, but it is not able to get a work unit. It is now saying "No appropriate work server was available; will try again in a bit".
Re: Server - 171.64.65.106
Posted: Tue May 26, 2009 2:27 am
by ihaque
Yes, this server looks like it's running low. I'm working on bringing up another server with a couple new projects to handle the load. Continuing network issues are causing problems for GPU assigns.
Re: Server - 171.64.65.106
Posted: Tue May 26, 2009 3:15 am
by vsekh
ihaque wrote:Yes, this server looks like it's running low. I'm working on bringing up another server with a couple new projects to handle the load. Continuing network issues are causing problems for GPU assigns.
Thanks ihaque. One of my gpu clients just received a 5911 project from server 171.64.65.20.