No New Tasks Set in BOINC - STILL Getting New Tasks

I had a different, but similar problem some time ago.

I finally had to resolve it by removing the project and re-adding it.

It's nothing anyone is doing on purpose.

Humm... do you realize that the components which decide on work request are BOINC components not Einstein components?

This same thing has happened to me when turning off new tasks... I still get more tasks.

A couple of points.

It's not helpful to resurrect a four year old 'dead' thread where you haven't provided any information to support your guess that this is the 'same thing'.  There are a lot of incorrect assertions and misinformation about what is going on (by the OP) and where the 'blame' should be attributed.  Needless to say, there will be a logical explanation and a simple solution to whatever your problem happens to be.  You just need to describe what you have done and what has happened.  Since your computers are hidden, people wishing to help will be unable to get the sort of information that would help pin down the problem.

You would be far better off ignoring that rambling diatribe that you have 'discovered' and start a new thread on the 'Problems' board, explaining exactly what your problem really is.  When you describe the circumstances around your problem, it would be helpful if you would mention the host ID that has been assigned to your machine.  That would allow a helper to look at scheduler logs that document the transactions between your host and the scheduler which sends any work requested by your BOINC client.

Until you explain your problem and get a response, just leave NNT (no new tasks) set in BOINC manager and let your BOINC client manage the situation as it is designed to do.   Make sure your work cache settings are at nice low values - no more than say 0.5 days in total - preferably in the first setting and zero in the 'extra days'.  If you are running out of work, reverse the NNT setting once you have set the 0.5 work cache setting.

 EDIT:  Your second message arrived whilst I was composing the above.  The answer to the extra question is YES.

You're welcome!

I understand very clearly that BOINC can be a bit daunting and rather puzzling in some of its intricacies, when people first join.  That (in particular) is why I'm trying to ensure that you don't latch on to some of the misconceptions about how things really work that were being complained about in the opening post of this thread.

Here are some simple facts to chew on that weren't understood by the thread starter all those years ago.

1. The project will never send you new work if you have set NNT in BOINC Manager.  Period!!!
2. The project will ONLY send new work if your client has requested it first.
3. The project will only send the types of work that your preferences allow.
4. Understanding the full range of pref settings and how they interact is one of the hardest tasks for a new person to master.
5. The most common mistake that you can make it to set too large a work cache setting when you first start.
6. A large work cache setting coupled with too many different projects is a very good way to totally confuse BOINC.

This is just a very small subset of some of the 'rules of engagement' if you want to make participating simple and enjoyable.  It is by no means complete or comprehensive.  One of the nice things about Einstein is that it tends to be quite reliable so there really is little need to have a large store of work on hand.  Once you get used to things, you could consider a setting of a day or two, just to protect against a problem over a weekend.  There are very few problems that take more than a day or so to be resolved.

I highlighted the word 'new' above for a specific reason.  When work is first allocated to your computer it will be brand new work.  If you 'lose' work for any reason outside of directly aborting it and reporting it to the project as 'aborted', the project will 'remember' the work that has been allocated to you.  For example, lets say something gets screwed up on your host and you reinstall.  The next time you contact the project (even with NNT set) the project is quite likely to recognise your machine and will therefore 'know' what you are supposed to have.  The project will resend those tasks to you, describing the process as "resending lost tasks".

They are not new tasks, they are 'resends', and this is why NNT doesn't prevent those tasks from being resent to you.  If you really don't want them, they can be aborted and reported back to the project as 'aborted' and that is the proper way to ensure they will be gone permanently.   Resends are only sent in batches of 12 at a time.  If there are more than that, more will arrive with each successive project contact by your client.  Einstein uses customised server software based on older versions of the BOINC server code.  For that reason, there may well be differences with how other projects handle the resending of lost tasks.