http://assign.stanford.edu/ is down

[kasson]

The primary assignment server required an old-fashioned yank on the power cables and a little TLC, but it's up now and should be assigning shortly.

[toTOW]

P.S. Meanwhile, we plan on taking up a collection to purchase a clock set to PST for toTOW...who has absolutely no reason to be embarassed.

Save you money, there is a better way Check the forum header now .. a convenient clock showing the time in Stanford.

That's sweet ... but my meteo station can display two different hours, and I of course chose my local time and San Francisco time (the closest location it has). It's 5:45pm here in France and 8:45am at Stanford

[shdbcamping]

The primary assignment server required an old-fashioned yank on the power cables and a little TLC, but it's up now and should be assigning shortly.

And the Stats update? It's my only way to monitor from work.



Stats update in progress
update started at Tue Feb 10 05:00:03 UTC 2009 (Mon Feb 9 21:00:03 PST 2009)

[BrokenWolf]

I don't mean to nag but do we have any update yet? I am getting 502 errors when my folding clients are trying to get work. They are RHEL4 most running 6.02 and some running 6.24 Beta release.

Code: Select all

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

Sorry for buggin you folks.

BrokenWolf

[toTOW]

That's a different issue. In your case, the AS works, but the work server (171.64.65.56) sends a 502 error.

Error 502 is "Bad Gateway" ... make sure that there's not something down in your side of the route the Stanford server (a traceroute output might help to find what's wrong).

[brityank]

Seems the Update Server is hosed too:

Stats update in progress
update started at Tue Feb 10 05:00:03 UTC 2009 (Mon Feb 9 21:00:03 PST 2009)

As of now, it's 10:15 EST, 15:15 UTC, and 07:15 PST.

Maybe a partial power failure in the data center?

Thank you, Dr. Pande, for all you and your team do, along with the gang of miscreants here on the boards.

It's still broke as of 14:45 EST / 19:45 UTC / 11:45 PST - Stanford Time. (Tuesday Feb 10 2009)

Same "Update Started" time as above.

[brityank]

Guess I need to learn to check around more before I spout off!

As usual, Dr. Pande already has the situation in hand: http://folding.typepad.com/news/2009/02 ... -time.html

[Exeon]

so, I guess stats won't be back for a while?

[VijayPande]

Everything should be back to normal now, although 3rd party stats may take a while to sync up.

[Exeon]

Everything should be back to normal now, although 3rd party stats may take a while to sync up.

Thank you for all your hard work.

[bruce]

Is the OP server an SMP assignment server?
Just curious because I got home from work (3rd Shift) and all my GPU clients have been sending and receiving all night.
I'm in the middle of 3 SMP's so they weren't affected and chugging away. Whew!

The same two Assignment Servers provide services for both Classic clients and SMP clients. They're currently at 171.65.103.93 and 171.64.65.121 (though that may change when Vijay finds some new hardware). Once your client converses with either AS, you are redirected to a specific Work Server, and they are are categorized separately as either Classic or SMP.

[shdbcamping]

Is the OP server an SMP assignment server?
Just curious because I got home from work (3rd Shift) and all my GPU clients have been sending and receiving all night.
I'm in the middle of 3 SMP's so they weren't affected and chugging away. Whew!

The same two Assignment Servers provide services for both Classic clients and SMP clients. They're currently at 171.65.103.93 and 171.64.65.121 (though that may change when Vijay finds some new hardware). Once your client converses with either AS, you are redirected to a specific Work Server, and they are are categorized separately as either Classic or SMP.

Ty Bruce

[anandhanju]

Is the assign.stanford.edu AS supposed to be working on port 80? http://assign.stanford.edu/ shows a "Connection refused" when opened in my browser but http://assign.stanford.edu:8080/ works fine.

[toTOW]

Is the assign.stanford.edu AS supposed to be working on port 80? http://assign.stanford.edu/ shows a "Connection refused" when opened in my browser but http://assign.stanford.edu:8080/ works fine.

No, it's a normal behavior.

It's assign2.stanford.edu that accepts connections on port 80.

[anandhanju]

Thanks toTOW.