My whole project is acting a bit weird. Scheduler timeouts, downloads that won't move but suddenly scream through the pipes (100kbs on occasion).

+1

---

Kevin

My whole project is acting a bit weird. Scheduler timeouts, downloads that won't move but suddenly scream through the pipes (100kbs on occasion).

+1

+2

If I press [ No New Tasks ] then [ Update ] I can report completed tasks, otherwise things fails all the time. Asking for WUs seems to work more often if tasks are not also being reported. Using <report_results_immediately>1</report_results_immediately> seems to help things along.

Something significantly changed Friday afternoon PDT. Suddenly it became almost impossible to get downloads to complete, and when they did the 'speed' was unusually high.

Seems somebody made an 'inprovement' that has caused my machines to starve - I repeatedly have downloads ALWAYS time out, no matter how many times I re-try. I leave it for a day, re-try and they all finish in record time. Then the next batch I get are stuck all over again.

Cripes!

---

Yeah, something got whacked after that last outage.
My top rig had about 10 downloads that took almost an hour of retrying, and then they all screamed through.
Now it has about 30 downloads that again will not budge an inch.

And when I checked it this morning, it had gotten so many failed scheduler requests that the whole project was backed off for a couple of hours.

---

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

We've been pegged at our bandwidth limit since we fixed the problem on friday.

Been pegged for most of last year & all of this year.


No problem with downloads here (other than after the outage but before Eric tweaked things downloads would timeout as soon as they started).
But still getting heaps of Scheduler request timeouts.

---

Grant
Darwin NT

Yeah, something got whacked after that last outage.
My top rig had about 10 downloads that took almost an hour of retrying, and then they all screamed through.
Now it has about 30 downloads that again will not budge an inch.

And when I checked it this morning, it had gotten so many failed scheduler requests that the whole project was backed off for a couple of hours.

Eric posted in "News":
Posted: 7 Apr 2012 | 18:39:40 UTC
"We had network problems Thursday night and since then we've been flooded with connection attempts. I just altered some server parameters to prevent clients from holding on to a connection for too long in hope that will help some downloads complete. I was able to get my home downloads done after that.

We've been pegged at our bandwidth limit since we fixed the problem on friday."
____________________________________________________________________________
I guess altering those server parameters, didn't make things better though, on the contrary, things got really bad...

Normally reporting and such would failed pretty quickly. Looking over the logs from the weekend. It looks like they all timed out on the client side at 5 minutes.

I'm not sure if that is the indented effect, but if they are/were just dropping the connection on the server side I would have thought the client would have seen it occur.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

MegaPanc:-)


Cheers,

---

Cliff,
Been there, Done that, Still no damm T shirt!

panic^2: It works, but I don't know why!

Pessimists
Accept
Nothing
In
Cache

And so,
don`t post about it.
which in poop.
:¬)

The outage seemed pretty quick, so I'll panic about that :)

---

Member of the People Encouraging Niceness In Society club.

I had better post something before 24hrs is up, or Sten will have nothing to panic about.
But there was a nasty little noch in the cricket graph earlier today that nobody else bothered to mention.
I wunderz why :¬)

SETI@home	Project is temporarily shut down for maintenance

Quack?

Edit: Sorry, nevermind, it fixed itself pretty soon. Someone must be fiddling something.
Edit 2: Not sorry and do mind. It is dead after all. :( Now there's your panic.

---

11/04/2012 22:09:58 | SETI@home | update requested by user
11/04/2012 22:10:00 | SETI@home | Sending scheduler request: Requested by user.
11/04/2012 22:10:00 | SETI@home | Reporting 5 completed tasks, not requesting new tasks
11/04/2012 22:10:08 | SETI@home | Scheduler request completed
11/04/2012 22:10:08 | SETI@home | Project is temporarily shut down for maintenance
11/04/2012 22:10:28 | SETI@home | update requested by user
11/04/2012 22:10:29 | SETI@home | Sending scheduler request: Requested by user.
11/04/2012 22:10:29 | SETI@home | Reporting 5 completed tasks, not requesting new tasks
11/04/2012 22:10:34 | SETI@home | Scheduler request completed
11/04/2012 22:10:34 | SETI@home | Project is temporarily shut down for maintenance
11/04/2012 22:11:15 | SETI@home | update requested by user
11/04/2012 22:11:16 | SETI@home | Sending scheduler request: Requested by user.
11/04/2012 22:11:16 | SETI@home | Reporting 5 completed tasks, not requesting new tasks
11/04/2012 22:11:22 | SETI@home | Scheduler request completed
11/04/2012 22:11:22 | SETI@home | Project is temporarily shut down for maintenance
11/04/2012 22:11:32 | SETI@home | update requested by user
11/04/2012 22:11:38 | SETI@home | Sending scheduler request: Requested by user.
11/04/2012 22:11:38 | SETI@home | Reporting 5 completed tasks, not requesting new tasks
11/04/2012 22:11:42 | SETI@home | Scheduler request completed
11/04/2012 22:11:42 | SETI@home | Project is temporarily shut down for maintenance
11/04/2012 22:12:02 | SETI@home | update requested by user
11/04/2012 22:12:08 | SETI@home | Sending scheduler request: Requested by user.
11/04/2012 22:12:08 | SETI@home | Reporting 5 completed tasks, not requesting new tasks
11/04/2012 22:12:14 | SETI@home | Scheduler request completed


I presume there is a minor bug in new version 7.0.25.
Whereas it used to report simple failure it now reports shut down instead. Cricket is at max so I again presume there is extremely high traffic.

---

11/04/2012 22:09:58 | SETI@home | update requested by user
11/04/2012 22:10:00 | SETI@home | Sending scheduler request: Requested by user.
11/04/2012 22:10:00 | SETI@home | Reporting 5 completed tasks, not requesting new tasks
11/04/2012 22:10:08 | SETI@home | Scheduler request completed
11/04/2012 22:10:08 | SETI@home | Project is temporarily shut down for maintenance

I presume there is a minor bug in new version 7.0.25.
Whereas it used to report simple failure it now reports shut down instead. Cricket is at max so I again presume there is extremely high traffic.

Nope, it just means the project is shut down for maintenance, later when every host under the sun is trying to reach the scheduler, then you might get failures,

Claggy

Saw this in my message log and laughed.

2012-04-11 18:57:16|SETI@home|Sending scheduler request: To fetch work. Requesting 1 seconds of work, reporting 1 completed tasks

It is inevitable that there would be a 1-second work request, but I never thought I would see it. Lowest I've seen before that was 12 seconds.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Saw this in my message log and laughed.

2012-04-11 18:57:16|SETI@home|Sending scheduler request: To fetch work. Requesting 1 seconds of work, reporting 1 completed tasks

It is inevitable that there would be a 1-second work request, but I never thought I would see it. Lowest I've seen before that was 12 seconds.

If I didn't know better, I'd swear that was an April Fools joke...

I routinely see 1 second requests on my C2D. I also keep a 2 hour cache total on my machine so I never have a large request going in. I also crunch 11 total projects 1 of which is GPU only. I never try for a large cache because I like to turn my work around very fast. If a project is down so what it will get extra work later it is all balanced out later.

---

backup projects also do 1 sec requests

---

I'm not the Pope. I don't speak Ex Cathedra!

backup projects also do 1 sec requests

So does the project initialisation request when you join a new project.

backup projects also do 1 sec requests

So does the project initialisation request when you join a new project.

it felt a bit silly to mention that ;)

---

I'm not the Pope. I don't speak Ex Cathedra!

backup projects also do 1 sec requests

So does the project initialisation request when you join a new project.

it felt a bit silly to mention that ;)

Good to know. But this is my one and only project. Was just topping-off the full 10-day cache. :D

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)