I haven't seen this one in a LONG while:

9/21/2011 9:57:48 AM SETI@home Message from server: This computer has reached a limit on tasks in progress

- but I got it today on one of my two crunchers; the other didn't get this on the same request (for new work). Both are way down in work in their queues - like a few hundred WUs now vs. 1500-2000 before the latest bout of no downloads...

Any ideas why this showed up?

Thanks for your help!

---

yes. The lab has implimented a limit (temporary) on tasks in progress. They use this as a temporary measure to allow everyone to get SOME work before everyone starts loading up their caches.

Hopefully they implemented the seperate limits on CPU and GPU, in order for all devices to have some work. As the load on the servers ease, the lab tends to increase the amount, eventually removing these restrictions.

As long as resend lost tasks is used, this should not cause any real issue other than filling your cache completely. But be patient, and they will get there.

---

Janice

The "limit" message seems a bit random as one of my pc's got this message when it asked for GPU work when it had no tasks left.

It could be that the number of tasks in progress comes from the replica database. The replica is still hours behind and since the work comes in waves of mainly shorties there can be a big difference between the replica data and reality.

---

Seti@Netherlands website

yes. The lab has implimented a limit (temporary) on tasks in progress. They use this as a temporary measure to allow everyone to get SOME work before everyone starts loading up their caches.

Hopefully they implemented the seperate limits on CPU and GPU, in order for all devices to have some work. As the load on the servers ease, the lab tends to increase the amount, eventually removing these restrictions.

As long as resend lost tasks is used, this should not cause any real issue other than filling your cache completely. But be patient, and they will get there.

I know the WHY of the message, but as I said, I haven't seen it in a LONG time - like several months. So far as I know, the limits haven't been set in months, as I have had no trouble getting work after the usual crunch times.

My question was why only one of two machines in essentially the same state got the message.

And, for John: the replica is at 0 seconds behind. So I am baffled...

---

And, for John: the replica is at 0 seconds behind. So I am baffled...

When I wrote my reply, it was 6800 seconds behind...