Message boards : Number crunching : my client will never connect
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile irzyxel

Send message
Joined: 2 Sep 04
Posts: 29
Credit: 116,231
RAC: 0
Message 18145 - Posted: 14 Oct 2007, 9:27:05 UTC

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
ID: 18145 · Report as offensive     Reply Quote
dulcimoo

Send message
Joined: 2 May 07
Posts: 39
Credit: 142,918
RAC: 0
Message 18146 - Posted: 14 Oct 2007, 9:54:35 UTC - in response to Message 18145.  

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


ID: 18146 · Report as offensive     Reply Quote
Danish Dynamite

Send message
Joined: 24 Dec 06
Posts: 5
Credit: 35,268
RAC: 0
Message 18147 - Posted: 14 Oct 2007, 10:07:30 UTC - in response to Message 18146.  

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
ID: 18147 · Report as offensive     Reply Quote
PovAddict
Avatar

Send message
Joined: 14 Jul 05
Posts: 275
Credit: 49,291
RAC: 0
Message 18175 - Posted: 15 Oct 2007, 22:40:19 UTC
Last modified: 15 Oct 2007, 23:23:37 UTC

(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?
ID: 18175 · Report as offensive     Reply Quote
zombie67 [MM]
Avatar

Send message
Joined: 24 Nov 06
Posts: 76
Credit: 6,720,840
RAC: 0
Message 18176 - Posted: 15 Oct 2007, 23:08:49 UTC - in response to Message 18175.  

(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

ID: 18176 · Report as offensive     Reply Quote
Profile Ageless
Avatar

Send message
Joined: 18 Sep 04
Posts: 143
Credit: 27,645
RAC: 0
Message 18177 - Posted: 15 Oct 2007, 23:19:07 UTC - in response to Message 18176.  

(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
ID: 18177 · Report as offensive     Reply Quote
BigMike

Send message
Joined: 24 Sep 05
Posts: 4
Credit: 1,311
RAC: 0
Message 18178 - Posted: 16 Oct 2007, 1:41:02 UTC

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
ID: 18178 · Report as offensive     Reply Quote
larry1186

Send message
Joined: 4 Oct 06
Posts: 38
Credit: 24,908
RAC: 0
Message 18213 - Posted: 16 Oct 2007, 18:35:26 UTC - in response to Message 18175.  

(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.
ID: 18213 · Report as offensive     Reply Quote
uioped1

Send message
Joined: 26 Aug 05
Posts: 18
Credit: 37,965
RAC: 0
Message 18214 - Posted: 16 Oct 2007, 22:32:31 UTC - in response to Message 18213.  


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.
ID: 18214 · Report as offensive     Reply Quote
Ingleside

Send message
Joined: 1 Sep 04
Posts: 36
Credit: 78,199
RAC: 0
Message 18215 - Posted: 16 Oct 2007, 22:53:08 UTC - in response to Message 18214.  

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."
ID: 18215 · Report as offensive     Reply Quote
PovAddict
Avatar

Send message
Joined: 14 Jul 05
Posts: 275
Credit: 49,291
RAC: 0
Message 18218 - Posted: 16 Oct 2007, 23:32:51 UTC - in response to Message 18215.  

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.
ID: 18218 · Report as offensive     Reply Quote
PovAddict
Avatar

Send message
Joined: 14 Jul 05
Posts: 275
Credit: 49,291
RAC: 0
Message 18219 - Posted: 16 Oct 2007, 23:42:12 UTC - in response to Message 18214.  

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 :)
ID: 18219 · Report as offensive     Reply Quote
larry1186

Send message
Joined: 4 Oct 06
Posts: 38
Credit: 24,908
RAC: 0
Message 18221 - Posted: 16 Oct 2007, 23:43:32 UTC - in response to Message 18219.  

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


YAAAAAAAHHH!!!
ID: 18221 · Report as offensive     Reply Quote
PovAddict
Avatar

Send message
Joined: 14 Jul 05
Posts: 275
Credit: 49,291
RAC: 0
Message 18243 - Posted: 17 Oct 2007, 14:49:22 UTC - in response to Message 18221.  

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

YAAAAAAAHHH!!!

Or not. 5.10.23 released, deferral messages are gone.
ID: 18243 · Report as offensive     Reply Quote
larry1186

Send message
Joined: 4 Oct 06
Posts: 38
Credit: 24,908
RAC: 0
Message 18254 - Posted: 17 Oct 2007, 20:42:36 UTC - in response to Message 18243.  

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....) :)
ID: 18254 · Report as offensive     Reply Quote

Message boards : Number crunching : my client will never connect


©2020 CERN