My 100+ downloads just went through.

---

IMHO the SETI powers need to rethink about the rise of the WU limits, sometimes roll back to a lower level (something like 150 CPU +200 GPU) could help the servers stability.

Thanks for voicing your opinion

---

IMHO the SETI powers need to rethink about the rise of the WU limits, sometimes roll back to a lower level (something like 150 CPU +200 GPU) could help the servers stability.

. . If they can confirm that is the problem. It would be a shame though, I am liking the 300 limit :(
Stephen
:(

I agree but after the change the system never returned to the normal, always something is happening from time to time.
If you look at the SSP each time the total WU reaches close to 23 MM something weird happening, download stalls, no new work, slow Web pages or spliting, etc. could be a hell of a coincidence of course.
Even post this msg takes a while.

. . Yes things are certainly 'not well', and some of the symptoms existed before the unfortunate change of the server software to 7.15, but that is what really brought things into disarray. But I guess when things are not going well being conservative makes sense so reducing the limits to what you suggested might at least give an indication if that is at all part of the problem..

. . Time to bite the bullet ... :(

Stephen

:(

Well, looking at the graphs the Scheduler likes to take a bit of time off most days, but it's not a fixed time. And the length of time it takes off varies too.

---

Grant
Darwin NT

Auto resend is on it seems

Mon 30 Dec 2019 09:25:36 CET | SETI@home | Sending scheduler request: To report completed tasks.
Mon 30 Dec 2019 09:25:36 CET | SETI@home | Reporting 183 completed tasks
Mon 30 Dec 2019 09:25:36 CET | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
Mon 30 Dec 2019 09:25:44 CET | SETI@home | Scheduler request completed: got 212 new tasks
Mon 30 Dec 2019 09:25:44 CET | SETI@home | Didn't resend lost task 22dc19ab.14994.13762.10.37.157_0 (expired)
Mon 30 Dec 2019 09:25:44 CET | SETI@home | Didn't resend lost task blc46_2bit_guppi_58692_69621_NGC3379_0055.14940.409.22.45.150.vlar_0 (expired)
Mon 30 Dec 2019 09:25:44 CET | SETI@home | Didn't resend lost task blc46_2bit_guppi_58692_68985_NGC3379_0053.15006.409.22.45.145.vlar_0 (expired)
Mon 30 Dec 2019 09:25:44 CET | SETI@home | Didn't resend lost task blc46_2bit_guppi_58692_69621_NGC3379_0055.14940.409.22.45.174.vlar_0 (expired)
Mon 30 Dec 2019 09:25:44 CET | SETI@home | Didn't resend lost task blc46_2bit_guppi_58692_68985_NGC3379_0053.14913.409.21.44.177.vlar_1 (expired)
Mon 30 Dec 2019 09:25:44 CET | SETI@home | Didn't resend lost task blc46_2bit_guppi_58692_68985_NGC3379_0053.14924.409.22.45.176.vlar_1 (expired)
Mon 30 Dec 2019 09:25:44 CET | SETI@home | Didn't resend lost task blc46_2bit_guppi_58692_68985_NGC3379_0053.14913.409.21.44.180.vlar_0 (expired)
Mon 30 Dec 2019 09:25:44 CET | SETI@home | Didn't resend lost task blc46_2bit_guppi_58692_68985_NGC3379_0053.15006.409.22.45.177.vlar_0 (expired)

Auto resend is on it seems

Surprised the servers are still functioning if that is the case.

---

Grant
Darwin NT

Yeh, it would appear that resends got turned on when the abortive update took place,and didn't get turned off when the reversion took place. It's a well known fact that resends puts such a high load on the database that everything else suffers

---

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

Well, it certainly wasn't on for me a couple of days ago. I waited a couple of days to make sure, then proceeded to recover them the Hard way. I was down to the last machine, about half way finished, and suddenly a normal attempt decided to 'Expire' All the remaining Ghosts. I hadn't done anything different from the previous successful procedures. I think the Server just decides to arbitrarily do whatever it wants at certain times. Any way, all my Ghosts are gone, and I had to do it manually.

Yeh, it would appear that resends got turned on when the abortive update took place,and didn't get turned off when the reversion took place. It's a well known fact that resends puts such a high load on the database that everything else suffers

And it might explain why the Scheduler has been taking time off each day recently.
Maybe disabling Resend lost task before changing the server side limits again & see how things go for a while would be the way to go.

---

Grant
Darwin NT

I have a problem getting CPU work on my main host for days now.

BOINC do ask for both GPU and CPU work on each request but don't send any CPU work. Tried lowering cache to 0.1 days, but then BOINC says cache is full, even with 0 CPU in cache. Tried getting WCG work, but BOINC says it doesn't need any work.

Looking at BOINC SETI properties is says

CPU task request deferred for 00:04:28
CPU task request deferral interval 00:10:00

So any idea what to do??

Sit back and join the rest of us waiting.

---

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

I have a problem getting CPU work on my main host for days now.

The one with the spoofed client?
You won't get any CPU work until the GPU reaches it's cache limit, or the server side limit.
Lowering the cache setting with the spoofed GPUs should allow you to get some CPU work- if the spoofed cache is full/has reached the server side limit.
is it actually asking for any CPU work? If not, i'd reduce the spoofing level & see if that lets it pickup some CPU work.

I'd suggest posting the Logs for work requests for people to take a look at to see what is going on.

---

Grant
Darwin NT

With cache of 1 day it asks for both GPU and CPU work but don't get any CPU work. With a cache of 0.1 day, it says cache is full even though I have 0 CPU in cache.

I do use the spoofed client from the beginning I think, have not been a problem before.

Another strange thing. I tried deselecting GPU work in prefs, then BOINC did only ask for CPU work BUT it still send GPU work.

Edit: tried going from 33 to 25 spoofed GPUs, then I got 35 CPU WUs. Hope it's working OK now :)

If you run the old spoofed client it has a 10000 WU cache limit, with the new SETI limit a 33 then 33 x 300 + 200 ) or 10100 so close to the edge, that could be the cause of your problem.

You have 2 options

- Reduce the number of spoofed GPUs - like you done
or
-DL the 20000 WU Limit version from my repository.

---

No outrage today.... it will be a Confluence: A Thorsday Outrage as the first of the decade! This must be an omen...

Weekly Outage will be on Thursday
Because of the holidays, we are conducting the weekly maintenance outage on Thursday this week.
31 Dec 2019, 16:09:25 UTC

---

No outrage today.... it will be a Confluence: A Thorsday Outrage as the first of the decade! This must be an omen...

Weekly Outage will be on Thursday
Because of the holidays, we are conducting the weekly maintenance outage on Thursday this week.
31 Dec 2019, 16:09:25 UTC

So instead of a Tuesday "hangover" we get a Thursday "hangover" just in time to start drinking (again) on Friday.

Tom

---

A proud member of the OFA (Old Farts Association).

It maybe a Thursday "hangover" for you Tom, but it'll be P.O.E.T.S. Day down under. ;-)

Cheers.

It maybe a Thursday "hangover" for you Tom, but it'll be P.O.E.T.S. Day down under. ;-)

Cheers.

Now that I have a reference, I would say its not just "down under" either. ;)

Tom

---

A proud member of the OFA (Old Farts Association).

Just checked my systems to find a bunch of downloads in extended backoff. A couple of retries & Suspend/Enable Networking got them moving again.

---

Grant
Darwin NT