Does both Seti & Einstein lac work units at the moment?

SETI is backlogged - Einstein is fine. However, if you JUST attached to CPDN and downloaded a WU from them, and have any other WUs on your system from any project - even completed WUs that are trying and failing to upload to SETI, for example - the Work Scheduler may have temporarily decided that downloading a WU from Einstein would "push" your computer and possibly cause a missed deadline.

Things you might check:

The Resource Share for each project you've attached - if they are all equal (say the default 100) then whichever project you've done the "most" on lately might be turned off until you "catch up" on others. If they aren't equal, then Einstein might simply be too low, it won't download more work until the other(s) are that far "ahead".

The "Connect To Network Every x" value - if it's too high (more than 2.5, preferably less than 1) it can cause the scheduler to "short" whichever project is looked at last on this cycle of downloading. It will make up for it on the next connection.

WUs currently on your computer that are getting close to deadline - in "panic mode", depending on the reasons, etc., the scheduler can go into "NO work fetch" mode until the current unit is completed.

SETI upload problem - if you have WUs that you haven't been able to upload to SETI, all work fetch calculations (assuming BOINC 4.45 or below, this is fixed in the beta versions) will be low until you finish uploading.

Hitting "Update" to try to get work - once might work. More than that only makes the problem worse, because only one 'connect' is allowed every 10 minutes, and a failed connect resets the timer.

-----

I suspect there isn't really a problem - yet - because you just recently added CPDN, and have two or more other projects attached. BOINC work is not "balanced" to the second, or even to the hour, and only a little bit to the day. It balances over weeks. It has to be this way, because some projects don't always have work available. If you still have no Einstein work after two or three days, there may be a problem. Posting any error messages will certainly help us (Bernd that is, I'm clueless) find out.

I am getting this same problem. I haven't looked deep into the logs, so I don't know how long its been going on, but I'm currently w/o any Einstein work units.

@ Bill Michael

For someone who claims to be "clueless", you are doing a mighty fine job of explaining, in extremely clear terms, the precise reasons for the BOINC behaviour that Tomas and Marc are reporting. I'm simply here to thank you for explaining it so well and to advise those who think there may be a problem that there really isn't. Please keep up the good work and I'll continue to enjoy reading your "clueless" posts :).

@ Tomas and Marc

One of the features of the newest versions of BOINC (4.45 has some bugs which are corrected in 4.72) is that you do not have to micromanage your work queues as BOINC will do it all for you. 4.72 is a test version but enough people have reported safe and consistent bahaviour for it to be considered a worthy replacement for 4.45 if the scheduling bugs in 4.45 are causing you problems. A long outage at Seti with a lot of completed work waiting to be uploaded can cause 4.45 not to get work from other projects even though the other projects are able to supply. This is where the "suspend" trick becomes useful.

If you have multiple projects to support, the most important thing to do is to decide on the resource share you wish to allocate to each and then stick to it. If BOINC reports "Requesting 0 seconds of work, returning 0 results" for a particular project you should not interfere and try to force BOINC to download more work as all you are doing is breaking your own resource share rules and giving BOINC a mess to clean up. Go change your resource share itself if you must and let BOINC get on with the job of honouring whatever you set.

As Boinc needs time to stabilize, there can be periods where BOINC refuses to get work from a particular project because that project has already had more than its fair share. If this seems to occur a lot, it's a good sign that your "connect to network" interval is too large. If it bothers you, the best remedy is to use a "connect" interval around 0.1 - 0.5 until everything stabilizes. With a low number, this will happen quite quickly. Then you can start to increase it a bit if you wish to keep "stale" work around :). I'm talking about "always on" type connections. Things are quite different for dialup.

One final point to emphasise. You are reporting on the bahaviour of BOINC and not EAH. Whilst it is fine to post here, you may find more help and information on the new BOINC message boards where BOINC specific issues are likely to be addressed more fully and where BOINC developers may see problems reported by users more quickly.

Hope some of this helps. For more detailed help please also read the Wiki.