fah-web.stanford.edu DOWN?

[bollix47]

Can't return/get WUs. Most links at top of forum timing out.

[HendricksSA]

No problem here. Did get short pop-up warning indicating a move of fah-web.stanford.edu to folding.stanford.edu.

[texinga]

I'm having the same problem on 2 PC's today not being able to get WU's from the Assignment Server. Both PC's have been attempting to get WUs since 7:55am Eastern and have had no success (just repeatedly connecting, being denied, waiting, re-requesting, etc). My 3rd PC did get a WU at 6:07am today.

This is what I'm seeing on the other 2 PC's:

Waiting before retry.
[12:23:30] + Attempting to get work packet
[12:23:30] Passkey found
[12:23:30] - Connecting to assignment server
[12:23:51] - Couldn't send HTTP request to server
[12:23:51] + Could not connect to Assignment Server
[12:24:12] - Couldn't send HTTP request to server
[12:24:12] + Could not connect to Assignment Server 2
[12:24:12] + Couldn't get work instructions.
[12:24:12] - Attempt #9 to get work failed, and no other work to do.
Waiting before retry.

[mephistopheles]

Doesn't work here either. Links like Project Summary don't work, and neither does ping:

Code: Select all

$ ping fah-web.stanford.edu
PING vspm27.stanford.edu (171.65.103.94) 56(84) bytes of data.
^C
--- vspm27.stanford.edu ping statistics ---
51 packets transmitted, 0 received, 100% packet loss, time 50088ms


[Mactin]

I was able to send back SMP2 @ 1226U
But am unable to get any work back !
Stats dont work either

[bollix47]

The problem may be somewhere between here and Stanford.

Code: Select all

traceroute stanford.edu
traceroute to stanford.edu (171.64.13.26), 30 hops max, 60 byte packets
 1  * * *
 2  66.49.236.139 (66.49.236.139)  42.635 ms  46.204 ms  48.391 ms
 3  66.49.255.161 (66.49.255.161)  50.579 ms  52.771 ms  56.471 ms
 4  66.49.255.246 (66.49.255.246)  59.151 ms  61.097 ms  62.807 ms
 5  gw-distributel.torontointernetxchange.net (198.32.245.14)  67.481 ms  69.656 ms  71.852 ms
 6  fibre6.tor.cia.com (216.58.0.16)  74.813 ms  44.630 ms  43.811 ms
 7  xe-1-0-0.cr1.tor1.ca.nlayer.net (69.31.142.129)  114.299 ms  114.590 ms *
 8  xe-3-1-0.cr2.ord1.us.nlayer.net (69.22.142.77)  58.385 ms  59.440 ms  60.092 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


[314159]

Stanford appesrs down entirely.
No upload, no new work, and it will take all day to clear the completed WUs from my farm.

What's up? When can we expect restoration of service?

[Pick2]

Hey John , How you Doin' !
I've two waiting so far ... My fastest ones , naturally

[CBT]

From where I am, the entire *.stanford.edu domain doesn't seem to be reachable!
Not only are some of my clients idle, I can't reach the FAH-website 'folding.stanford.edu' and their main website 'www.stanford.edu' doesn't work either.

Btw. I'm in The Netherlands (Europe).


Corné

[CBT]

An nslookup from my computer for the stanford.edu-domain gets a 'DNS request timed out.'-reply.

Using a webbased nslookup in Germany does get me a propper result.

[bruce]

From the Los Angeles area, a tracert fah-web.stanford.edu looks like this:

Code: Select all

. . .
  5    11 ms    11 ms    10 ms  cenic.laap.net [198.32.146.32]
  6    12 ms    12 ms    12 ms  dc-lax-core2--lax-peer1-ge.cenic.net [137.164.46.119]
  7    21 ms    22 ms    21 ms  dc-svl-core1--lax-core2-10ge-1.cenic.net [137.164.46.95]
  8    21 ms    21 ms    21 ms  dc-svl-agg1--svl-core1-10ge.cenic.net [137.164.47.120]
  9    22 ms    22 ms    21 ms  dc-stanford--svl-agg1-10ge.cenic.net [137.164.50.158]
 10    22 ms    22 ms    23 ms  boundarya-rtr.Stanford.EDU [68.65.168.33]
 11    22 ms    22 ms    22 ms  bbra-rtr.Stanford.EDU [171.64.255.129]
 12    22 ms    22 ms    23 ms  moza-rtr-a.Stanford.EDU [171.64.255.140]
 13     *        *        *     Request timed out.
 14    23 ms    23 ms    23 ms  vspm27.Stanford.EDU [171.65.103.94]

Trace complete.

[toTOW]

Everything is connecting fine here in France (ISP Orange)

[CBT]

Connection is just restored.

Restarted the affected clients and they're working again.

Corné

[bollix47]

Yes, connectivity has returned.

[314159]

Ok here too -finally- (except for some crummy WU assignments).