This was reported many hours ago in "number crunching" - http://setiathome.berkeley.edu/forum_thread.php?id=70730

Or if you want to see how the servers are behaving take a look at the cricket graphs http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=%2Frouter-interfaces%2Finr-250%2Fgigabitethernet2_3;view=Octets The blue line is the data requests being fed to the servers, and the green mass the data coming out of the servers for us to work on. Normally one would expect the blue to be about 10MBs and the green to be about 90MBs, but as I type they are both down in the noise.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Last update on the server status page was 22:30 UTC Saturday (2013-02-09)

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Thanks for that info guys - problem seems to have been resolved now.

---

-------------------------------------
By Hook or by Crook....We Will
-------------------------------------

I've got a problem guys, no idea why, but all my transfers/uploads get stuck at 16.00/27.70 or 16.00/33.06 or 16.00/34.86 (always on 16.00). Anyone with some idea why, and what I can do to fix it?

Is there still problems with the scheduler or other servers, as I had to abort a 8.0 MB transfer, that kept stalling and had been going on 12 hours downloading. I checked my internet speed, and according to the results, the download should have taken less than 30 seconds , at worst. I have another download trying to come down, I have had to hit retry download 3 times in the last 40 minutes, as it has now been downloading for 45 minutes having downloaded 5.7 of the 8 MB?

---

Is there still problems with the scheduler or other servers, as I had to abort a 8.0 MB transfer, that kept stalling and had been going on 12 hours downloading. I checked my internet speed, and according to the results, the download should have taken less than 30 seconds , at worst. I have another download trying to come down, I have had to hit retry download 3 times in the last 40 minutes, as it has now been downloading for 45 minutes having downloaded 5.7 of the 8 MB?

Don't worry about it, the Hurricane link on which downloads, uploads and scheduler contacts rely on is normally very heavily utilised, making everyone's downloads slow, with frequent timeouts, they'll download eventually, resuming from where they got to earlier,

Claggy

Look at the cricket graph (posted above)
As long as the green is pegged at 90, everything is going to be slow

---

Look at the cricket graph (posted above)
As long as the green is pegged at 90, everything is going to be slow

Too general a statement, You can't tell if downloads are just pegged at 90, or if we're in a middle of a Shortie Storm with 5 times as many downloads attempting to go through, in both instances it will still be pegged at 90.

Claggy

Look at the cricket graph (posted above)
As long as the green is pegged at 90, everything is going to be slow

Too general a statement, You can't tell if downloads are just pegged at 90, or if we're in a middle of a Shortie Storm with 5 times as many downloads attempting to go through, in both instances it will still be pegged at 90.

Claggy

Which, parenthetically, is the same kind of lack of information that hid the root cause of the Apollo 13 accident.

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

Which, parenthetically, is the same kind of lack of information that hid the root cause of the Apollo 13 accident.

Now that is not a fair comparison, and I think you know that.

+1

---

Which, parenthetically, is the same kind of lack of information that hid the root cause of the Apollo 13 accident.

Now that is not a fair comparison, and I think you know that.

Sorry but as Swiss I need more explanation(s), I can't understand these words! If explanation is too heavy for public eyes, please put it in private mail.

Which, parenthetically, is the same kind of lack of information that hid the root cause of the Apollo 13 accident.

Now that is not a fair comparison, and I think you know that.

Only in the consequences. If you think I meant otherwise, you took my statement way too seriously. I was not trying to imply that the limitations of the Cricket graph in any way could lead to potential loss of life or anything of the like.

I was just noticing in passing that just as we can't tell how much more attempted traffic there is when the graph is pegged, NASA was also unable to see that the interior of the oxygen tank had gotten much hotter than it should because the thermometer didn't read any higher than the intended maximum.

Geez. Ya can't say anything anymore without someone misinterpreting it.

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

NASA was also unable to see that the interior of the oxygen tank had gotten much hotter than it should because the thermometer didn't read any higher than the intended maximum.

I understand! Missing imagination?