Folding Forum

Posted: **Mon Jul 27, 2009 2:16 pm**

It's currently up, but out of work

Posted: **Mon Jul 27, 2009 4:47 pm**

Nope.

It is thin in available WUs due to the fiasco with xx.108.24 however I have received at least three WUs from this server over the past couple of hours. Apparently, when it is not "503" or "AS blocked", a ton of Quads (not mine) are being assigned to it so there should be a huge supply of xx.56 WUs tomorrow.

Meanwhile, MOST of my damn Quads were assigned p5102's or equivalent and are less than 50% utilized. Argh!!!
This truly irks me given the presence of the "special bonus" for dual Quads that produces 50k plus/WU (effectively + or minus a 100% bonus).
The logic behind that program totally escapes me and I would love to see the private discussion related to implementing that "plan".

We fold on.......happily or unhappily........

Posted: **Mon Jul 27, 2009 5:10 pm**

The server that serves BidAdv WUs is down too ... we're all in the same boat

Posted: **Mon Jul 27, 2009 6:41 pm**

Hey toTOW,

Do the math! You're a bright chap!

Given the timeframe that these servers were down, the net effect on a Quad that typically returns 3 WUs/day (and gets stuck with "a1s" as happened here) is SIGNIFICANTLY different than a dual Quad that takes 2 days plus to complete those "biggies".

This is accurate for those of us with SMP "farms" and also for the aggregate throughput of the Project.

Most of my 13 Quads are just spinning their wheels at this stage.
Several of my dualies are challenged to make preferred deadlines.

<--sad not "mad"

Posted: **Fri Jul 31, 2009 12:31 am**

[00:03:41] Folding@home Core Shutdown: FINISHED_UNIT
[00:06:55] CoreStatus = 64 (100)
[00:06:55] Unit 4 finished with 66 percent of time to deadline remaining.
[00:06:55] Updated performance fraction: 0.667433
[00:06:55] Sending work to server
[00:06:55] Project: 2677 (Run 32, Clone 38, Gen 29)

[00:06:55] + Attempting to send results [July 31 00:06:55 UTC]
[00:06:55] - Reading file work/wuresults_04.dat from core
[00:06:55] (Read 49146012 bytes from disk)
[00:06:55] Connecting to http://171.64.65.56:8080/
[00:06:55] - Couldn't send HTTP request to server
[00:06:55] + Could not connect to Work Server (results)
[00:06:55] (171.64.65.56:8080)
[00:06:55] + Retrying using alternative port
[00:06:55] Connecting to http://171.64.65.56:80/
[00:06:55] - Couldn't send HTTP request to server
[00:06:55] (Got status 503)
[00:06:55] + Could not connect to Work Server (results)
[00:06:55] (171.64.65.56:80)
[00:06:55] - Error: Could not transmit unit 04 (completed July 31) to work server.
[00:06:55] - 1 failed uploads of this unit.
[00:06:55] Keeping unit 04 in queue.
[00:06:55] Trying to send all finished work units
[00:06:55] Project: 2677 (Run 32, Clone 38, Gen 29)

[00:06:55] + Attempting to send results [July 31 00:06:55 UTC]
[00:06:55] - Reading file work/wuresults_04.dat from core
[00:06:55] (Read 49146012 bytes from disk)
[00:06:55] Connecting to http://171.64.65.56:8080/
[00:06:56] - Couldn't send HTTP request to server
[00:06:56] + Could not connect to Work Server (results)
[00:06:56] (171.64.65.56:8080)
[00:06:56] + Retrying using alternative port
[00:06:56] Connecting to http://171.64.65.56:80/
[00:06:56] - Couldn't send HTTP request to server
[00:06:56] + Could not connect to Work Server (results)
[00:06:56] (171.64.65.56:80)
[00:06:56] - Error: Could not transmit unit 04 (completed July 31) to work server.
[00:06:56] - 2 failed uploads of this unit.

[00:06:56] + Attempting to send results [July 31 00:06:56 UTC]
[00:06:56] - Reading file work/wuresults_04.dat from core
[00:06:56] (Read 49146012 bytes from disk)
[00:06:56] Connecting to http://171.67.108.25:8080/
[00:06:56] - Couldn't send HTTP request to server
[00:06:56] (Got status 503)
[00:06:56] + Could not connect to Work Server (results)
[00:06:56] (171.67.108.25:8080)
[00:06:56] + Retrying using alternative port
[00:06:56] Connecting to http://171.67.108.25:80/
[00:06:56] - Couldn't send HTTP request to server
[00:06:56] (Got status 503)
[00:06:56] + Could not connect to Work Server (results)
[00:06:56] (171.67.108.25:80)
[00:06:56] Could not transmit unit 04 to Collection server; keeping in queue.
[00:06:56] + Sent 0 of 1 completed units to the server
[00:06:56] - Preparing to get new work unit...
[00:06:56] + Attempting to get work packet
[00:06:56] - Will indicate memory of 1950 MB
[00:06:56] - Connecting to assignment server
[00:06:56] Connecting to http://assign.stanford.edu:8080/
[00:06:56] Posted data.
[00:06:56] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[00:06:56] + News From Folding@Home: Welcome to Folding@Home
[00:06:56] Loaded queue successfully.
[00:06:56] Connecting to http://171.64.65.56:8080/
[00:06:57] - Couldn't send HTTP request to server
[00:06:57] + Could not connect to Work Server
[00:06:57] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.

Posted: **Fri Jul 31, 2009 12:36 am**

never mind

I was just inpatient, it happened on 2 server at the same time.

Posted: **Fri Jul 31, 2009 1:20 am**

This server is behaving fine at present (as you noted) - just cleared two "autosend" WUs through it and another amazingly sent to the infamous xx.25 CS after a 503 from xx.56.

HOWEVER: DL=0 on xx.56 so be prepared for the worst over the next few hours if our friend Dr. Kasson is not available (or other events occur).

If the latter IS an issue, is there any way this can be resolved prior to ~7:45 PDT when my C2D's start completing?

Posted: **Fri Jul 31, 2009 5:28 am**

We should be good for a bit--about 400G of space cleared on the server.

Posted: **Fri Jul 31, 2009 6:52 pm**

I've got one C2D machine which has been waiting since 18:16:14 UTC for a new WU. Status 503, over and over.

Posted: **Fri Jul 31, 2009 8:00 pm**

Same here

Code: Select all

[19:36:44] + Attempting to get work packet
[19:36:44] - Will indicate memory of 3912 MB
[19:36:44] - Connecting to assignment server
[19:36:44] Connecting to http://assign.stanford.edu:8080/
[19:36:45] Posted data.
[19:36:45] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[19:36:45] + News From Folding@Home: Welcome to Folding@Home
[19:36:45] Loaded queue successfully.
[19:36:45] Connecting to http://171.64.65.56:8080/
[19:36:45] - Couldn't send HTTP request to server
[19:36:45]   (Got status 503)
[19:36:45] + Could not connect to Work Server
[19:36:45] - Attempt #11  to get work failed, and no other work to do.
Waiting before retry.

Posted: **Fri Jul 31, 2009 8:43 pm**

I have 6 (most likely more @ work) systems in the same boat. Can we kick this server a bit and get it to play nicely again?

Thanks,

BW

Posted: **Fri Jul 31, 2009 10:04 pm**

Mine finally got one ~19:40.

Posted: **Fri Jul 31, 2009 10:18 pm**

The netload on this server has looked a bit fishy most of the day.

It does appear to be accepting at least some completed WUs but not assigning.

Most of my C2D's complete between 430PM PDT and 1150PM PDT and I am not looking forward to another "challenging" weekend.

@ BW: You've been putting up too many WUs recently so I personally disabled your clients.

(Keep up the GREAT WORK)

Posted: **Fri Jul 31, 2009 11:24 pm**

Just restarted the binary; hopefully that will help.

Posted: **Sat Aug 01, 2009 12:08 am**

Thanks, as always

Looks good from here. The first of several C2D WUs was sent and acknowledged at 449PM (your time), and a new one was issued with no time lag.
Xfer rate on both send and receive were actually a bit faster than ususal.

Netload appears MUCH more reasonable.

My fingers are now crossed for the weekend.
I suspect that yours are too.

Folding Forum

171.64.65.56 not responding

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status

Re: 171.64.65.56 is in Reject status