hi,
the same from here, cant no upload work
18.02.2010 08:51:05 SETI@home Started upload of 15fe07ac.10146.290720.11.10.4_0_0
18.02.2010 08:51:26 SETI@home Temporarily failed upload of 15fe07ac.10146.290720.11.10.4_0_0: HTTP error
18.02.2010 08:51:26 SETI@home Backing off 44 min 32 sec on upload of 15fe07ac.10146.290720.11.10.4_0_0

---

D5400XS V8-Xeon

hi,
the same from here, cant no upload work
18.02.2010 08:51:05 SETI@home Started upload of 15fe07ac.10146.290720.11.10.4_0_0
18.02.2010 08:51:26 SETI@home Temporarily failed upload of 15fe07ac.10146.290720.11.10.4_0_0: HTTP error
18.02.2010 08:51:26 SETI@home Backing off 44 min 32 sec on upload of 15fe07ac.10146.290720.11.10.4_0_0

And yet, the Cricket graphs show total bandwidth at a very lazy pace....does not make sense to me. Have never seen quite this scenario that I can remember.

These kinds of comms problems are usually seen when the bandwidth is saturated.

Maybe it will get sorted tomorrow. Until then, I got two of my prime rigs with no Cuda work. Sigh.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Hi, still got a day, I guess, of work for SETI, but also can't upload about 100 task's.
Probably a good time, to clean out the dust in all rig's and reseat a heatsink which doesn't make much contact with the CPU, as it get's too hot (96C) and only has a mild (10%) OC.
BOINC doesn't even try to UPLoad, since yesterday!

---

I still wish answers as to just WTF is going on.......

Seti server problems, or external inet comms problems.

These have both bean postulated, but not answered.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Pappa wrote:

This recovery will take a while! Go read the Tech News!

All things considered it is doing okay.

Regards

No it isn't.

The sequence was:

1) Uploads stopped (problem with HTTP service on Bruno)
2) Regular backup/compression maintenance
3) A/C failure

They've dealt with (3): (2) is history, as it always is by the following day: but reading Matt's posts, I honestly don't think he's noticed (1) yet. First day back after vacation, everything showing green on the monitors, just enough uploads trickling in to make it look like a normal/quiet day.

I'm running a very lean mix at the moment, for testing. CUDA cards switched to GPUGrid ages ago, and even big steady old Octo has finished the 2-day CPU cache. So all I'm doing at the moment is grinding through a backlog of rebranded VLARs on CPUs. But I've still got 303 uploads waiting to go through - about 20 more than when I went to bed last night.

If the uploader can't even keep up with CPU production, it's broken: I tried to say as much in Technical News last night, but it got buried in an avalanche of 15-year old UPSs. Somebody else can try using back-channels to attract attention if they want.

I'm out of work on this main machine for the 1st time since I started 6 mnths ago. Secondary machine has about an hour of work to go.

There is a basic comms problem going on here..........

It may be within Seti, it may be not.


All I know, is it is starting to piss me off. LOL.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Monitoring my upload process, I see a very few making it through at present. What is frustrating is that I see a lot that get as far as 100% uploaded to be subsequently rejected and queued up to try again. The last bit of handshaking fails and causes the system to repeat work (upload) that appears to have been completed. This is not an new observation.

Because it obviously takes bandwidth and server resources to execute this type of failure, and because the behavior has been around 'forever', has any effort been made to remedy it? (Doning manager hat: If not why not?!)

Hi, still got a day, I guess, of work for SETI, but also can't upload about 100 task's.
Probably a good time, to clean out the dust in all rig's and reseat a heatsink which doesn't make much contact with the CPU, as it get's too hot (96C) and only has a mild (10%) OC.
BOINC doesn't even try to UPLoad, since yesterday!

Hi Fred,

To be correct, it isn`t BOINC, it`s SETI. I`m on some other projects right now,
and uploads/downloads are doing just fine.

All the best !

Kurt

---

Monitoring my upload process, I see a very few making it through at present. What is frustrating is that I see a lot that get as far as 100% uploaded to be subsequently rejected and queued up to try again. The last bit of handshaking fails and causes the system to repeat work (upload) that appears to have been completed. This is not an new observation.

Because it obviously takes bandwidth and server resources to execute this type of failure, and because the behavior has been around 'forever', has any effort been made to remedy it? (Doning manager hat: If not why not?!)

All comms are wrecked here for now too.......
[rant]This is rather frustrating, as no acknowledgment has been made of the problem as of yet.......so I don't know WTF is going on. Nothing is happening on Cricket, nor the server status page to give a clue...
WHERE ARE THE FISH?????[/rant]

---

"Time is simply the mechanism that keeps everything from happening all at once."

I'm actually out of SETI work, for the first time in months.

Uploaded 5 out of 8 completed WUs overnight, oldest of these these have been trying to transfer for about 48 hours. No downloads, messages like this:

18/02/2010 8:26:04 AM|SETI@home|Sending scheduler request: Requested by user. Requesting 259200 seconds of work, reporting 1 completed tasks
18/02/2010 8:26:26 AM||Project communication failed: attempting access to reference site
18/02/2010 8:26:27 AM||Internet access OK - project servers may be temporarily down.
18/02/2010 8:26:29 AM|SETI@home|Scheduler request failed: Couldn't connect to server

Cricket graphs appear virtually dead. Definitely a communications problem somewhere....

Fortunately all my other projects are running nicely.

---

After many many retry attempts (automatic, not manual), I finally have all my uploads completed and tasks reported. Haven't downloaded anything for a while, but thank god for the 10 day cache. Considering myself lucky.

---

"Life is a tragedy for those who feel, and a comedy for those who think."

"I never get into an argument that I cannot win."

Same here in the land of OZ, 1 or 2 wu's upload but no luck updating, calm down and go roll in some catnip lol

---

Same here in the land of OZ, 1 or 2 wu's upload but no luck updating, calm down and go roll in some catnip lol

Catnip, hell......I wanna CRUNCH something.... LOL.
But uploading and reporting would do for now.

What I wanna know is just where the problem is....and is it gonna be addressed soon?

---

"Time is simply the mechanism that keeps everything from happening all at once."

Erhm not sure if anyone noticed the news page;

Projects are down due to a server closet air conditioning failure.
We have to power down most of our computers until this is fixed. 17 Feb 2010 2:36:55 UTC


http://setiathome.berkeley.edu/index.php


Apolagies if this has allready been pointed out but this could be whats going on :)

Erhm not sure if anyone noticed the news page;

Projects are down due to a server closet air conditioning failure.
We have to power down most of our computers until this is fixed. 17 Feb 2010 2:36:55 UTC


http://setiathome.berkeley.edu/index.php


Apolagies if this has allready been pointed out but this could be whats going on :)

My friend, if the AC had not been fixed, we would not be talking right now.......the servers would still be down.

There is a comms problem that existed before the AC failure, and still persists.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Erhm not sure if anyone noticed the news page;

Projects are down due to a server closet air conditioning failure.
We have to power down most of our computers until this is fixed. 17 Feb 2010 2:36:55 UTC


http://setiathome.berkeley.edu/index.php


Apolagies if this has allready been pointed out but this could be whats going on :)

My friend, if the AC had not been fixed, we would not be talking right now.......the servers would still be down.

There is a comms problem that existed before the AC failure, and still persists.

I see ........ then i stand corrected :)

Still its a nice chance to give the pc a clean :)

Erhm not sure if anyone noticed the news page;

Projects are down due to a server closet air conditioning failure.
We have to power down most of our computers until this is fixed. 17 Feb 2010 2:36:55 UTC


http://setiathome.berkeley.edu/index.php


Apolagies if this has allready been pointed out but this could be whats going on :)

My friend, if the AC had not been fixed, we would not be talking right now.......the servers would still be down.

There is a comms problem that existed before the AC failure, and still persists.

I see ........ then i stand corrected :)

Still its a nice chance to give the pc a clean :)

I suspect many dust bunnies are meeting their maker about now.

---

"Time is simply the mechanism that keeps everything from happening all at once."

My friend, if the AC had not been fixed, we would not be talking right now.......the servers would still be down.

You'd think they'd update the front page to reflect that the A/C is back up again.

There is a comms problem that existed before the AC failure, and still persists.

Weird that half the servers are still reporting "OK", and yet I've seen numerous complaints about not being able to report updates. All I keep getting is "rety in {some time}". I thought it might have been my connection, but tested from 3 different locations, still get it. Sniffing into the traffic, the server is throwing a 500 error when it reports the data. I'd be more than happy to post my traffic if it helps anybody resolve the issues.

My friend, if the AC had not been fixed, we would not be talking right now.......the servers would still be down.

You'd think they'd update the front page to reflect that the A/C is back up again.

There is a comms problem that existed before the AC failure, and still persists.

Weird that half the servers are still reporting "OK", and yet I've seen numerous complaints about not being able to report updates. All I keep getting is "rety in {some time}". I thought it might have been my connection, but tested from 3 different locations, still get it. Sniffing into the traffic, the server is throwing a 500 error when it reports the data. I'd be more than happy to post my traffic if it helps anybody resolve the issues.

That's the whole durned point.....
I have not had anybody confirm or deny whether this problem is within the Seti servers or is with their connection to the outside world.

I am gonna go to sleep right now, should I not freeze because the Cuda cards aren't throwing off much heat at the moment, and hope when I wake up it was all just a bad kitty dream.

WHERE ARE THE FISH???

---

"Time is simply the mechanism that keeps everything from happening all at once."