LHC@home

same thing for 12 hours:

10/14/2007 11:20:06 AM|lhcathome|Message from server: Not sending work - last request too recent: 66 sec

10/14/2007 11:21:12 AM|lhcathome|Message from server: Not sending work - last request too recent: 66 sec

10/14/2007 11:23:13 AM|lhcathome|Message from server: Not sending work - last request too recent: 122 sec

its always too recent, no matter what

---

Try modifying your general preferences so that you don't connect more then .1 times per day. I think if you don't stretch out your connections you will not get work for the moment.

same thing for 12 hours:

10/14/2007 11:20:06 AM|lhcathome|Message from server: Not sending work - last request too recent: 66 sec
...
10/14/2007 11:23:13 AM|lhcathome|Message from server: Not sending work - last request too recent: 122 sec

its always too recent, no matter what

---

Try modifying your general preferences so that you don't connect more then .1 times per day. I think if you don't stretch out your connections you will not get work for the moment.

same thing for 12 hours:

10/14/2007 11:20:06 AM|lhcathome|Message from server: Not sending work - last request too recent: 66 sec
...
10/14/2007 11:23:13 AM|lhcathome|Message from server: Not sending work - last request too recent: 122 sec

its always too recent, no matter what

you need to get your client(s) to not request more work for an hour ie 3600 seconds easiest way would be to disable network activity

(In [13849]) - client: fix bug where delay request from project is ignored if no results are returned.

Expect the fix on 5.10.23. Now for the bad part: the "Deferring communication for..." is now shown only if you have debugging enabled. Who thinks the delay should be always shown?

---

(In [13849]) - client: fix bug where delay request from project is ignored if no results are returned.

Expect the fix on 5.10.21. Now for the bad part: the "Deferring communication for..." is now shown only if you have debugging enabled. Who thinks the delay should be always shown?

Me!

---

Dublin, California
Team: SETI.USA

(In [13849]) - client: fix bug where delay request from project is ignored if no results are returned.

Expect the fix on 5.10.21. Now for the bad part: the "Deferring communication for..." is now shown only if you have debugging enabled. Who thinks the delay should be always shown?

Me!

And me. Now it would only show with the <sched_op_debug> flag on? I don't need to see all the details of all the scheduler RPCs all the time. It gives a lot of clutter for a simple message:

16-Oct-07 1:17:40||[sched_op_debug] SCHEDULER_OP::init_master_fetch(): Fetching master file for http://lhcathome.cern.ch/lhcathome/
16-Oct-07 1:17:40|lhcathome|Fetching scheduler list
16-Oct-07 1:17:45||[sched_op_debug] SCHEDULER_OP::poll(): Got master file from http://lhcathome.cern.ch/lhcathome/; parsing
16-Oct-07 1:17:45||[sched_op_debug] SCHEDULER_OP::parse_master_file(): got 1 scheduler URLs
16-Oct-07 1:17:45|lhcathome|Master file download succeeded
16-Oct-07 1:17:51||[sched_op_debug] SCHEDULER_OP::init_op_project(): starting op for http://lhcathome.cern.ch/lhcathome/

---

Jord

BOINC FAQ Service

I think the delay should always show. It's a huge help when trying to figure out why something is not crunching WU's the way I would expect it to.

--Mike

(In [13849]) - client: fix bug where delay request from project is ignored if no results are returned.

Expect the fix on 5.10.23. Now for the bad part: the "Deferring communication for..." is now shown only if you have debugging enabled. Who thinks the delay should be always shown?

Me too!! I realize you can see the current deferment in the projects tab, but it is nice to see the history (like 1 min deferrals growing to 2 hours or more, etc) so you have a better idea of what's going on.

---

Don't get distracted by shiny objects.

Me too!! I realize you can see the current deferment in the projects tab, but it is nice to see the history (like 1 min deferrals growing to 2 hours or more, etc) so you have a better idea of what's going on.

My MSG tab shows deferral amounts and why. (.10.20)

In fact, if you compare in my log the entries for SETI and LHC you will see the problem. Seti says "deferring for x" and then on the next line it says Reason: requested by project.

LHC says "deferring for y" but the reason is "no work from project"

What I'm trying to point out is that LHC does not seem to be communicating the required backoff time to the client. Maybe this is because doing so requires the server code upgrade they've been mentioning.

---

What I'm trying to point out is that LHC does not seem to be communicating the required backoff time to the client. Maybe this is because doing so requires the server code upgrade they've been mentioning.

No, the bug was client-side, v5.10.14 introduced a bug that means every time you asks for work but don't get any, the deferral-message from project are not used.

If you did get work, or didn't ask for work (like only reporting), even LHC@home will show "Reason: requested by project".

---

"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."

What I'm trying to point out is that LHC does not seem to be communicating the required backoff time to the client. Maybe this is because doing so requires the server code upgrade they've been mentioning.

No, the bug was client-side, v5.10.14 introduced a bug that means every time you asks for work but don't get any, the deferral-message from project are not used.

FYI: it's now fixed, fix will be available on 5.10.23.

---

Me too!! I realize you can see the current deferment in the projects tab, but it is nice to see the history (like 1 min deferrals growing to 2 hours or more, etc) so you have a better idea of what's going on.

My MSG tab shows deferral amounts and why. (.10.20)

The next version of BOINC will not show it anymore, that's what I was talking about. I think five people against the change is enough to get it reverted :)

---

I think five people against the change is enough to get it reverted :)

YAAAAAAAHHH!!!

I think five people against the change is enough to get it reverted :)

YAAAAAAAHHH!!!

Or not. 5.10.23 released, deferral messages are gone.

---

I think five people against the change is enough to get it reverted :)

YAAAAAAAHHH!!!

Or not. 5.10.23 released, deferral messages are gone.

BOOOOOOO!!

(man what a roller coaster of emotions....) :)