I think they are messing with the scheduler, InProgess is now dropping off.
With
Astro -yes
Seti - yes
Other - no

2 boxes are acting like "other" is stuck on.
- No tasks sent
- No tasks available for AP v7

And now thy flood gates have opened .... for now at least. 2 boxes just got big lumps in.

No probs at all here, but then I use an old school version of BOINC. :-)

Cheers.

And it's back "No tasks available for AP v7 "
GGGRRRRR, I'm not set for AP only!

No probs at all here, but then I use an old school version of BOINC. :-)

My C2D has the same version of BOINC as the i7, and continues to get work.
It really is rather perplexing.

---

Grant
Darwin NT

No probs at all here, but then I use an old school version of BOINC. :-)

My C2D has the same version of BOINC as the i7, and continues to get work.
It really is rather perplexing.

Yet none of my 3 rigs have ever shown signs of that behaviour.

It's certainly seems to be a very perplexing problem for those with later BOINC versions at least (a code problem maybe?).

I wonder if it can be established what versions are being effected by that problem.

Cheers.

Here's an old time favorite...

With only 28 GPU tasks onboard I now get...

"16 Jun 17 12:17:29 | SETI@home | This computer has reached a limit on tasks in progress"

Takes about nine hours for my rig to run 28 tasks...

---

Having AstroPulse v7 7.0 in the CPU queue seems to limit the cache size considerably here.

---

Humans may rule the world...but bacteria run it...

I'm having trouble getting work on my Windows 7 machines. Down below 100 tasks when it should be 200. Windows 10 machine seems to be staying up. From my daily driver Windows7 log.

Keith-Windows7

4828 SETI@home 6/16/2017 14:16:00 Sending scheduler request: To report completed tasks.
4829 SETI@home 6/16/2017 14:16:00 Reporting 4 completed tasks
4830 SETI@home 6/16/2017 14:16:00 Requesting new tasks for CPU and NVIDIA GPU
4831 SETI@home 6/16/2017 14:16:10 Scheduler request completed: got 0 new tasks
4832 SETI@home 6/16/2017 14:16:10 No tasks sent
4833 SETI@home 6/16/2017 14:16:10 No tasks are available for AstroPulse v7
4834 SETI@home 6/16/2017 14:16:10 This computer has reached a limit on tasks in progress

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I wonder if it can be established what versions are being effected by that problem.

By running AP i'm not affected anywhere nearly as much as when I didn't.
Whatever it is, it all comes back to the late Dec borking of the application preferences after one of the weekly outages & server/Scheduler updates.

---

Grant
Darwin NT

I wonder if it can be established what versions are being effected by that problem.

By running AP i'm not affected anywhere nearly as much as when I didn't.
Whatever it is, it all comes back to the late Dec borking of the application preferences after one of the weekly outages & server/Scheduler updates.

I never took Wiggo up on his offer to backlevel to a much earlier client to see if that fixed the problem. Every time it gets really bad and I've about had with it to actually pull the trigger on installing an 6.XX client, the problem disappears for a while. We'll see if this current episode finally gets me off my duff to try it. Toggling preferences in all permutations hasn't done anything for me.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Here's an old time favorite...

With only 28 GPU tasks onboard I now get...

"16 Jun 17 12:17:29 | SETI@home | This computer has reached a limit on tasks in progress"

Takes about nine hours for my rig to run 28 tasks...

. . Yep, I have been getting that for the last 12 hours or more. Only a partial cache but the servers say I am on the limit ... :(

Stephen

??

Running on fumes, I have only received 2 GPU tasks in the last 3 hours on my i7.

EDIT: just got 7, woohoo that will last 5 minutes more.

Running on fumes, I have only received 2 GPU tasks in the last 3 hours on my i7.

EDIT: just got 7, woohoo that will last 5 minutes more.

. . I did an experiment. I had a full CPU queue and an almost empty GPU queue. So I moved 10 WUs to the GPU q to make space and waited for the refresh. The CPU Q was topped u with Arecibo VLARs but nada, zip, nothing for the GPU. So I went to preferences and turned off Nvidia processing and did a refresh, waited a couple of minutes then went back in and turned Nvidia back on did another refresh. Next work request aI got a full load and GPU Q now full again. It may be coincidence but it may be worth a try.

Stephen

. . It seemed to behave like it had lost the "setting" to send me nvidia work :(

.

There may be something to that. I turned off NVidia and got 190 tasks. I know the setting doesn't actually appy until the NEXT request, but it may have been enough just to have the server access that table in prefs. will see what happens the next few requests ....

EDIT: ... Next request was for CPU only (as expected)
Set NVidia 'on', request was for CPU only (as expected)
Then request for NVidia/CPU tasks and 93 came in, cache full.

It also filled my i7-960 cache too (on the same profile)
So toggling NVidia IS an option to kick the server in the knackers.
I would guess toggling CPU would do the same since it is likely the same table to update.

There may be something to that. I turned off NVidia and got 190 tasks. I know the setting doesn't actually appy until the NEXT request, but it may have been enough just to have the server access that table in prefs. will see what happens the next few requests ....

EDIT: ... Next request was for CPU only (as expected)
Set NVidia 'on', request was for CPU only (as expected)
Then request for NVidia/CPU tasks and 93 came in, cache full.

It also filled my i7-960 cache too (on the same profile)
So toggling NVidia IS an option to kick the server in the knackers.
I would guess toggling CPU would do the same since it is likely the same table to update.

. . That was my experience as well. My 2 windows boxes are both on "Home" setting. When I did that from one box they both got full caches from it.

Stephen

There may be something to that. I turned off NVidia and got 190 tasks. I know the setting doesn't actually appy until the NEXT request, but it may have been enough just to have the server access that table in prefs. will see what happens the next few requests ....

EDIT: ... Next request was for CPU only (as expected)
Set NVidia 'on', request was for CPU only (as expected)
Then request for NVidia/CPU tasks and 93 came in, cache full.

It also filled my i7-960 cache too (on the same profile)
So toggling NVidia IS an option to kick the server in the knackers.
I would guess toggling CPU would do the same since it is likely the same table to update.

My system has been keeping the cache full for that last hour or so.
Will give that option a go the next time it goes stupid on me.

---

Grant
Darwin NT

I too tried the Nvidia toggle Stephen and it caused my lagging Windows7 crunchers to fill their caches. But my Windows10 cruncher is now lagging. I didn't perform a clean experiment though because I had also set work_fetch_debug in the log to try and and get the system to recognize the deficit on the GPU's. I am doing some memory tuning on the Ryzen system now so it is offline for the moment but I had set the work_fetch_debug in its log for a few cycles before I shut it down. We shall see if if picks itself back up after I bring it back online.

Thanks for tip and heads up. Definitely goes into the toolbag of tricks.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

My Windows10 Ryzen system immediately began picking up batches of GPU work as soon as I brought it back online. It has a full cache now along with the Windows7 systems. Further circumstantial evidence I think that goes back to the change for the AMD 8.23 app FUBAR in the schedulers. I think it messed with the Nvidia platforms too.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

My Windows10 Ryzen system immediately began picking up batches of GPU work as soon as I brought it back online. It has a full cache now along with the Windows7 systems. Further circumstantial evidence I think that goes back to the change for the AMD 8.23 app FUBAR in the schedulers. I think it messed with the Nvidia platforms too.

I seems to tie in with the work type as well- GBT v Arecibo.
It used to be you would get a fairly even split between then (1/3 Arecibo & 2/3 GBT when they had most of the Arecibo splitters disabled) these days I seem to get all Arecibo or all GBT a lot of the time, particularly when getting work is an issue and it finally arrives. Then at other times when the scheduler is behaving I usually get more of a mix of both.

---

Grant
Darwin NT