It means that you asked 32 seconds ago, which is sooner than the project back off time.
e.g. For cpdn, the back off is 1 hour and a couple of minutes.

And I think that asking will reset the timer to whatever value they use.

So a different message could be: "Stop being so impatient." :)

As Les says. The calculation of 'too recent' is done on project servers, so will only change as projects update their server code.

Every project also sends a message saying how long you should wait between contacts, but at the moment you can only see it if you enable <sched_op_debug> Event Log messaging. I've got a request in at the moment to change both of those: so far, two separate programmers have misunderstood 'asking will reset the timer', so maybe third time lucky.

Thanks Richard - it would be nice to be told how long I've to wait instead of having to guess!

If using manager under status it says communication deferred and counts down to when you can request work again. under the projects tab.

If using manager under status it says communication deferred and counts down to when you can request work again. under the projects tab.

I get caught out by that sometimes when using a local Manager to view a remote client.

If the clocks on the two machines are out of synchronisation (and most drift slightly over the course of a week), the clock difference is applied to the countdown timer.

If using manager under status it says communication deferred and counts down to when you can request work again. under the projects tab.

[Slaps self on face] I forgot about checking in there (I use Boinctasks to control all my machines which shows the above). Although I still stand by my assertion that the response I got should have told me the time before possible communication, not how long since I last asked.

It’s a countdown timer, so it is the time until you can make another scheduler request. Once the timer goes away you can tell it to update, or let BOINC do it on its own.

Note that you can sometimes manually make another request before the timer expires provided you aren’t asking for work, example you set it to ”no new task” and then tell it to update which would report any completed work and update any prefs changed on the project website. The timer would then restart from the project back-off interval again.

---

MarkJ

Because you reset the timer to what ever, so it's no longer 30 seconds.
You need to look at each project to see what delay they're using.
And the current system works fine when used with the Manager that's part of the "official" version.

I can't find an instance of where I got it wrong last, but I'm sure that BOINC Manager shows the back off used in it's Error Log.

If BOINCtasks doesn't show the amount of back off, then that's the program that needs changing.

OK, that's wrong. It must be a different back off.
I just got the chance to upload some zips, waited 48 seconds, then did an update.
This was "54 seconds too recent".

But BOINC knows the correct moment to do this, so it's still "working as required."

According to the repository, those words were added to the server code 11 years ago. The message comes from the server, so downloading a new client won't change it: and knowing how often some projects update their servers, we'll probably go on seeing it for another 11 years.

Oooh, we could have a birthday party: "... committed on Dec 22, 2008"

Edit - it's even older than that. It first appeared as "last RPC too recent" - committed on Dec 23, 2003. Put back the birthday party until Monday!

It's coming of age, let's give it a sweet 16 party and show it its Ford F250.

---

I get "Not sending work - last request too recent: 22 sec". To me that means I have to wait 22 sec (which is clearly not true - it's actually telling me a useless piece of information - when I last made a request). This is shown the same in the standard Boinc Manager and in Boinctasks (although in Boinc manager I have to go into the event log to see it - Boinctasks shows it in the messages tab). Why doesn't it say "Please wait a further 2.5 minutes"?

Those messages are in the log (Messages tab in BOINCtasks and Event log in BOINC Manager).

The back-off timer is shown on the Projects tab in BOINCtasks and BOINC Manager. In both cases it is shown on the right side where it displays other info such as “No new tasks” and “Scheduler request in progress”, etc.

---

MarkJ