strange "Deferring communication" (low priority)
14 Sep 2005 22:44:17 UTC
Topic 189888
(moderation:
On two 4.19 clients I have a somehow misguided message "Deferring communication ..." just directly after a *successful* scheduler contact.
Both PCs work just fine, no trouble contacting the Einstein servers most of the time, just this strange message when there shouldn't be any message at all.
Both PCs have in common, that they are behind a Squid with authentication. I cannot compare to a system with no proxy as I temporary switched most computers to a non-BOINC-project. Both PCs started doing this not too long ago but I cannot tell an exact date.
As there are no negative side effects, this doesn't require fixing, but maybe it would be good to know about the behaviour when errors pop up that might be related.
strange "Deferring communication" (low priority)
)
You are probably seeing something related to a change that I made to the server-side scheduler a day ago. The scheduler now asks the client to wait at least 61 seconds after each contact, before contacting the scheduler again. This is why you are seeing the 'defered' messages. But hopefully everything is working OK!
Bruce
Director, Einstein@Home
RE: You are probably seeing
)
There's no "problem" with this as far as I can tell, but after every Einstein update, 4.72 says "communication deferred 00:00:59" and counts down to 0, then does nothing, for no reason - just annoying.
RE: RE: You are probably
)
Bruce – For us version 4.45 reads as follows and presents no problems during the past 36 hours.
9/15/2005 2:29:54 AM|Einstein@Home|Computation for result w1_1024.5__1024.8_0.1_T16_S4hB_0 finished
9/15/2005 2:29:55 AM|Einstein@Home|Starting result w1_1024.5__1024.9_0.1_T16_S4hB_0 using einstein version 4.79
9/15/2005 2:29:55 AM|Einstein@Home|Started upload of w1_1024.5__1024.8_0.1_T16_S4hB_0_0
9/15/2005 2:30:06 AM|Einstein@Home|Finished upload of w1_1024.5__1024.8_0.1_T16_S4hB_0_0
9/15/2005 2:30:06 AM|Einstein@Home|Throughput 14702 bytes/sec
9/15/2005 2:30:07 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
9/15/2005 2:30:07 AM|Einstein@Home|Requesting 0 seconds of work, returning 1 results
9/15/2005 2:30:09 AM|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
9/15/2005 2:30:10 AM|Einstein@Home|Deferring communication with project for 59 seconds
Just passing along FYI!
Regards,
Tom
Theory of Gravitational Waves & LIGO
Laser Interferometer Space Antenna - LISA
JPL-Caltech
RE: RE: You are probably
)
Bill, the scheduler is (and has been, for quite some time) programmed to REJECT scheduler contacts that arrive sooner than 60 secs after the previous scheduler contact. So the only thing that has happened with this change is that now your client is telling you (explicitly) not to try to communicate before that time.
Bruce
Director, Einstein@Home
RE: RE: There's no
)
Understood, just pointing out that no other project has this message, it LOOKS like you're trying to tell me there is a communication problem and you're going to try again in 59 seconds - when in reality if I didn't plan on hitting 'update' again, I would have no error. You're saying "don't do that" if I planned on doing it or not. If it didn't show up on the "Projects" tab, if it was only a message, then it wouldn't be an issue.
If you haven't seen what I'm saying, run any 4.72 (or up?) version, hit "Update" on the projects tab. You'll see "scheduler request pending" for a moment, then, when the request has been successful, you'll see "Communication deferred 00:00:xx" - which LOOKS like there was a problem and it's having to try again.
RE: RE: RE: There's no
)
I can change the 'Communication deferred...' message. What do you suggest?
Director, Einstein@Home
RE: I can change the
)
Three spaces? :-)
I don't think it matters in the Messages tab, but is there a way to tell the BOINC Client not to reconnect for 61 seconds without having a message show up on the Projects tab? I assume that somewhere in the code is a list of messages that are to be shown, and nothing else will be - I don't know if there is a signal that will accomplish this without using that specific message that is "passed through"...
If not, it may be worthwhile to talk to the BOINC folks and have them add such a signal to the V5.x release, if this is something you need to be able to tell the Client. Right now, there aren't that many of us using 4.72 and up - I'm just afraid that you're going to get a new thread like this every week or so once BOINC goes to 5.x - as it is, while Ananas saw this in the Messages tab, most don't pay attention to that. The Projects tab, on the other hand... if EVERY project did it, everyone would expect it and ignore it. If it's only Einstein, there's likely to be confusion. "What's wrong with Einstein's servers, every time I connect, it has to try twice!" Sigh.
Yep, that was the point. In
)
Yep, that was the point. In other projects we get this message after a rejected or failed contact with a delay before the next retry, here it comes after a successful contact with a delay before the next "do nothing".
Maybe just an empty message (or spaces) would be the best idea.
RE: I can change the
)
I would suggest 'Project (or server) requested delay'. That hopefully will be enough to show that it is not a problem connecting, but something to reduce traffic.
BOINC WIKI
BOINCing since 2002/12/8
I'm seeing this exact
)
I'm seeing this exact behaviour as well and was initially suspecting there was some sort of "benign" problem firstly because that's how I interpreted the message and secondly because the BOINC manager icon in the system tray gets a red "problem" exclamation mark stuck on it. Obviously the BOINC manager (mine is 4.19) thinks it's a "problem".
Here's my suggestion. Firstly, change the message category from whatever causes the red dot with the exclamation mark on it to whatever gives the normal brighter blue dot with the white "i" (information message I assume rather than a "problem" message).
Secondly change the message text from:-
to
or something along those lines so that it is clearly interpreted as "information only".
Cheers,
Gary.