[. . Hey guys,
. . Can I do a quick poll?
. . What setting is in your "get additional days of work field"? Both for those getting work and those having problems getting any.
Stephen.

7.6.22 with no issues, setting are:
Store at least 10 days of work
Store up to an additional 10 days of work

Doesn't matter in my case, as those parameters are never enforced.
The hard limit of 100 tasks per CPU and 100 tasks per GPU keep me limited to a total of less than 12 hours work for most of the machines here.

My default BOINC web settings are also 10/10 days of work. I did have a mix of 7.2.42, 7.4.42, 7.6.23, & 7.6.33 on my machines, but recently switched all of the Windows machines to 7.6.33. I wasn't having any issues getting work. I just wanted to bring them all up to the same version.

---

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

l believe that is a high rac class users who have this cache empty problem

with my small 4K rac , i have no bad issues with my small WU cache , and my settings for asking new tasks is set to 30mn

perhaps with a shorter time , it could be seen as a DDOS attack by the servers ? X shorts demands by X users made a lot of network activity for Seti servers ?

---

7.6.22 with no issues, setting are:
Store at least 10 days of work
Store up to an additional 10 days of work
Settings are Yes Yes and No.
Running Window$ 8.1 on two machines.
No issues on maintaining cache.

---

"Sour Grapes make a bitter Whine." <(0)>

Only on Tuesday evenings when the outrage is in full flow.

---

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

The minimum time interval between data requests is just over five minutes. This is "hard wired" in the server code so can't be "broken" at the cruncher end. Having a low "extra work" figure has the effect of requesting a small number of tasks at each request rather than requesting a large amount of work at long time intervals, and probably not having it fully satisfied for several five minute cycles.

---

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

I'm at 10/10, and still have a 100% full cache.

Meow.

---

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

[. . Hey guys,
. . Can I do a quick poll?
. . What setting is in your "get additional days of work field"? Both for those getting work and those having problems getting any.
Stephen.

7.6.22 with no issues, setting are:
Store at least 10 days of work
Store up to an additional 10 days of work

Doesn't matter in my case, as those parameters are never enforced.
The hard limit of 100 tasks per CPU and 100 tasks per GPU keep me limited to a total of less than 12 hours work for most of the machines here.

. . And you are having no problems getting work either are you?

Stephen

.

Nope, not once since this whole deal started

---

shows over 500,000 available but reports no tasks available ... after the outage

Ed F

Edit: shut my mouth!! I just got 9 on one computer and 39 on another ... 2 more still at 0 .. o.k. I can wait this only took 30 min's

My settings are for 4 days and an extra 0.05. Maybe I should try for more, even though it's not possible?

After the outage (would be an idea for the Project to change the times to 10-12 hours), no joy getting work. Changed the preferences to Yes, Yes, Yes. Still no joy. Changed them back to No, Yes, No and have been getting work with every single request since then- even after such an extended outage.



Are all of those who aren't having issue also AP crunchers?

---

Grant
Darwin NT

shows over 500,000 available but reports no tasks available ... after the outage

Ed F

Edit: shut my mouth!! I just got 9 on one computer and 39 on another ... 2 more still at 0 .. o.k. I can wait this only took 30 min's

. . 3 rigs saying "no tasks available" at this end

Stephen

:(

Greetings All

FWIW I am running latest build of 7.6.33 (x64) on my two Win 7 machines and 7.6.32 on my Linux Mint 18.2, and my cache setting for all 3 machines are set at the follows:

Store at leat 1 days of work
Store up to an additional 0 days of work.

I have been seeing the no tasks available on my 3 machines event logs, but my caches last over 14+ hours so its not a big issue for me.

Thought cache settings might be and issue, but also you have some pretty fast GPU's compared to my GTX 580, 770 and 960 lol.

Hope you find what you are looking for.

Regards

. . Hey guys,

. . Can I do a quick poll?

. . What setting is in your "get additional days of work field"? Both for those getting work and those having problems getting any.

Stephen

.

Stephen, I was only set for 4 days of work and 0.1 days of additional work. I just changed it to 10/10 days. Was set that way to prevent Einstein from downloading too much work but that has gone tit$ up anyway with the new tasks. Have to go back to my manual NNT intervention on that project to prevent too much work being downloaded and forcing that project into "High Priority" mode. As was mentioned, doesn't really make any difference what your cache settings are these days with the hard server enforced CPU/GPU limits. First request on all empty machines after the project came back onlne ..." No tasks available" SIGH.

---

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

A proud member of the OFA (Old Farts Association)

So why is only my Windows 10 machine getting work?? I have 15 tasks there already. Nothing so far on my Windows 7 machines. The Win 10 machine ALWAYS has a full cache. NO issues at all. Can't get any work lately on my Win 7 machines.

---

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

A proud member of the OFA (Old Farts Association)

So why is only my Windows 10 machine getting work?? I have 15 tasks there already. Nothing so far on my Windows 7 machines. The Win 10 machine ALWAYS has a full cache. NO issues at all. Can't get any work lately on my Win 7 machines.

Try changing the application settings as I've been doing.
Hit update on the client. Next time it requests work, with luck it will pick up some. If not, change the application settings back to what they were, hit Update on the client. Then with the next request for work, you should get some.
I've no idea why things are so screwed, or why sometimes just changing the settings is enough to get work and yet other times I have to change them, update, change them back, update, then it's happy to get work with each request.

---

Grant
Darwin NT

Stephen, I was only set for 4 days of work and 0.1 days of additional work. I just changed it to 10/10 days. Was set that way to prevent Einstein from downloading too much work but that has gone tit$ up anyway with the new tasks. Have to go back to my manual NNT intervention on that project to prevent too much work being downloaded and forcing that project into "High Priority" mode. As was mentioned, doesn't really make any difference what your cache settings are these days with the hard server enforced CPU/GPU limits. First request on all empty machines after the project came back onlne ..." No tasks available" SIGH.

. . Same here, all three rigs came up empty when they asked for new work so I did the trick of changing the settings to yes,Yes,YES (nod to TBar) and while the caches are not yet full I started getting new work.

Stephen

:)

So why is only my Windows 10 machine getting work?? I have 15 tasks there already. Nothing so far on my Windows 7 machines. The Win 10 machine ALWAYS has a full cache. NO issues at all. Can't get any work lately on my Win 7 machines.

. . I was getting "No tasks available" on all 3 rigs, 2 with Win10, one with Win7

Stephen

:(

So why is only my Windows 10 machine getting work?? I have 15 tasks there already. Nothing so far on my Windows 7 machines. The Win 10 machine ALWAYS has a full cache. NO issues at all. Can't get any work lately on my Win 7 machines.

. . I was getting "No tasks available" on all 3 rigs, 2 with Win10, one with Win7

Stephen

:(

Don't know if this is significant, but after the servers ran me out of work just before the maintenance outage and left me high and dry for half a day, I changed one of the parameters in my TCP settings last night and started to receive work.

Back when the servers were still in the lab, we were having trouble connecting to them. One of the guys here in the forum found out that if you enabled timestamps in your TCP settings you could connect with the servers much better.
My settings have been like that since then. Last night I disabled the timestamp setting and immediately started getting work and it has stayed topped off all night.

Don't know what could have changed at the servers to cause this, but hope this might help someone.

It worked for me. It might also explain why Win 10 does not seem to be affected.

---

Bruce

I'm not sure it that makes a difference or not, I was lucky and got filled up right before maintenance so I had my 4.5 hour cache at least, and since the servers came back I have not seen any problem getting work.

I'm not sure about it either. It could just be a coincidence. Maybe Eric and the guys found the problem and fixed it, and everybody has had their cache staying topped off.
I hope so.

---

Bruce

Bruce, just what exactly is the key in the registry that you are talking about with regard to TCP timestamp setting? I haven't yet searched the forum for the thread you are referring to. I still don't have full caches on my Win 7 machines. Only about 50 CPU tasks and about 150 GPU tasks. Still see a majority of "no work available" messages every 5 minutes.

---

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

A proud member of the OFA (Old Farts Association)

Bruce, just what exactly is the key in the registry that you are talking about with regard to TCP timestamp setting? I haven't yet searched the forum for the thread you are referring to. I still don't have full caches on my Win 7 machines. Only about 50 CPU tasks and about 150 GPU tasks. Still see a majority of "no work available" messages every 5 minutes.

Once again my cache had run down, but not as much as in past days. Changed my application settings to Yes, Yes, Yes, hit Update & on the next work request it filled up.

This is on my Win10 system.
I'd be surprised if the TCP settings have any effect- i'm having no issues in contacting the Scheduler and getting a response. I'm just having issues with it allocating work even though I haven't hit the server side limits & I haven't reached my full cache settings.

---

Grant
Darwin NT