171.64.65.56 not responding

[kasson]

Right now all the vspg<x> machines appear to be unreachable. We're working with our sysadmins (some of them were up until 1 am working on a different system not associated with FAH).
We should be able to set up a backup for quad-core clients at least...

[dschief]

Lock those system guys in the server room, and feed them coffee & Krispy Creme doughnuts. The two primary food groups { caffeine and refined sugar }

[314159]

Great suggestion

What else can I do under these circumstances?

Got MY coffee - no Krispy Creme but I "ain't" drinking the coffee sans sugar as usual.

I'm getting too old (and gray) for this......

John

Dr. Kasson: Three Quads have now received work, two of which did not require "special arguments".

[kasson]

All the servers are reachable again--apparently there was an issue with a network switch. We'll leave the "overflow" option up for now, which should increase redundancy. When we have multiple servers down, the best thing is to let us know. Unfortunately, our overnight response time is a little slower (and that of the sysadmins, who are hardworking and pretty fast but not always up at 2am).

[dschief]

Looks like I've got a couple of new WU's, But the completed ones still are'nt getting accepted?

[kasson]

The max # connections might be saturated as the backlog clears from the servers. We're definitely getting a lot of uploads.

[ikerekes]

[19:23:07] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[19:23:07] + News From Folding@Home: Welcome to Folding@Home
[19:23:07] Loaded queue successfully.
[19:23:07] Connecting to http://171.64.65.56:8080/
[19:23:07] - Couldn't send HTTP request to server
[19:23:07] (Got status 503)
[19:23:07] + Could not connect to Work Server
[19:23:07] - Attempt #6 to get work failed, and no other work to do.

Edit: never mind the #9 attempt finaly successful

[spazzcat]

This keeps happening, I am to the point where I a going to pull the plug on Folding as there is no point if I am not going to get credit.

[11:02:38] + Attempting to send results
[11:02:38] - Reading file work/wuresults_03.dat from core
[11:02:38] (Read 25983397 bytes from disk)
[11:02:38] Connecting to http://171.64.65.56:8080/
[11:03:29] - Couldn't send HTTP request to server
[11:03:29] (Got status 400)
[11:03:29] + Could not connect to Work Server (results)
[11:03:29] (171.64.65.56:8080)
[11:03:29] - Error: Could not transmit unit 03 (completed February 22) to work server.
[11:03:29] - 7 failed uploads of this unit.

[05:01:33] + Attempting to send results
[05:01:33] - Reading file work/wuresults_03.dat from core
[05:01:33] (Read 25983397 bytes from disk)
[05:01:33] Connecting to http://171.67.108.25:8080/
[05:02:25] - Couldn't send HTTP request to server
[05:02:25] (Got status 400)
[05:02:25] + Could not connect to Work Server (results)
[05:02:25] (171.67.108.25:8080)
[05:02:25] Could not transmit unit 03 to Collection server; keeping in queue.
[05:02:25] + Sent 0 of 2 completed units to the server

[kasson]

400 is a different error code--503 is what usually comes up when the server is busy. What version of the core are you using?

[spazzcat]

Sorry, I didn't realize I posted this in the wrong thread. This is a Linux box running version 6.02 with smp.

[kasson]

6.02 is the client version; FAHlog.txt should also have a core version (somewhere between 1.94 and 2.05). Could you post that one as well?

[spazzcat]

6.02 is the client version; FAHlog.txt should also have a core version (somewhere between 1.94 and 2.05). Could you post that one as well?

Core version is 2.04

[314159]

Well, this is posted in the correct thread.

This server is in REJECT MODE as of 10:24 EDT - i.e. as I write this and verified by the server stats page plus two of my FAHlog.txts.

Please help!

Thank you as always.

John

P.S. Does this mean that my 12 Quads will be all running at 50% productivity as they complete WUs over the next several hours?
It truly irks me when that occurs. <---sad, not mad

[susato]

I expect the Pande Group is on the case already as they are already working on a couple of other servers. (see announcements page)

That is bad news for OSX dual core machines as there is no work for them on any other server, according to the serverstats page (Maybe they are getting work from 171.67.108.24 which is serving SMP quad work units despite being listed as "classic" only)
.
Meanwhile, are your Linux quads able to get WU from 171.64.65.63? My Mac Pro dual quad just picked up a p3065 from there. A FAHcore_a1 unit, but it's Folding work. And is the collection server accepting your finished work units OK?

[314159]

"Collection Server"?

You MUST be kidding!!

As usual, the so called collection server has no record of the WUs.
All that I am doing is wasting bandwidth during a time when I am in a heated argument with my ISP.

I am just putting all the Quads on -oneunit. Running an a1 on them is a total waste.

Do I recall that the Pande Group HIGHLY recommended Quad processors for these SMPs?

It's a joke and I guess that OSX and Linux "volunteers" are and shall remain "second class citizens" even though we triple ran hundreds of SMPs during the testing days.

Thanks for the response, Susato.

<---mad not sad....... (was here as I wrote this rant)

Just completed 2 WUs and did get a2's from xx.108.24 so I'll add a instead.