@ |
Home | Help | Status | Forums | Glossary | Account
|
log in |
Message boards : Help! : client 6.4.0 is disallowed
Author | Message |
---|---|
[size=-1]11/18/08 10:38:14 AM|Pirates@Home|Message from server: Your version of the BOINC core client (6.4.0) is disallowed.[/size] | |
ID: 8050 | Rating: 0 | rate: / Reply Quote | |
Contact wrote: [size=-1]11/18/08 10:38:14 AM|Pirates@Home|Message from server: Your version of the BOINC core client (6.4.0) is disallowed.[/size] Ah, good to know that the scheduler restrictions are still working.
This is a consequence of being blocked at the scheduler. But... the new client is supposed to be better about dealing with that. So re-open that bug ticket (or open a ticket, if there never was one). ____________ -- Eric Myers "Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats | |
ID: 8052 | Rating: 0 | rate: / Reply Quote | |
The relevant tickets are 417 and 633, both closed as fixed. | |
ID: 8053 | Rating: 0 | rate: / Reply Quote | |
I think I see why this bug is back: On the BOINC alpha list Rom W. wrote:
____________ -- Eric Myers "Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats | |
ID: 8055 | Rating: 0 | rate: / Reply Quote | |
Wormholio wrote: Previous posts describing the problem are Message 6542 and... Capt'n, you might want to repair your link to Message 6542, no idea why but it is missing '&' character in the middle: "...id=842&nowrap=true..." ____________ Peter .-) | |
ID: 8057 | Rating: 0 | rate: / Reply Quote | |
Pirates was the first project contacted, after I've installed the 6.4.0 client yesterday morning (with the "Your version of the BOINC core client (6.4.0) is disallowed." message). | |
ID: 8058 | Rating: 0 | rate: / Reply Quote | |
Pepo wrote: It has not got any work from any project since. Just "got 0 new tasks" without any other reason. There is still a lot of free space and the client is requesting work from various projects. The client just downloaded one 12-hour task from Einstein, but is still lacking at least 36 CPU hours of work. Nevertheless, at least my work fetch problem definitely seems not to be bound to this Pirates' issue. ____________ Peter .-) | |
ID: 8059 | Rating: 0 | rate: / Reply Quote | |
Wormholio wrote: I think I see why this bug is back... Nicely done! Mystery solved. I saw Rom's note, but I just didn't connect it to this bug. After BOINC be back to current code and no work is to be had here, we can ask for the nowork_skip to make sure team name etc. doesn't disappear. | |
ID: 8060 | Rating: 0 | rate: / Reply Quote | |
Contact wrote:
I saw it too, but forgot that 6.2.x was branched that far ago (exactly 2 weeks prior to this bug being repaired in 6.3.x trunk). ____________ Peter .-) | |
ID: 8063 | Rating: 0 | rate: / Reply Quote | |
Wormholio wrote: I think I see why this bug is back: So? How is parsing scheduler replies a manager feature? ____________ | |
ID: 8064 | Rating: 0 | rate: / Reply Quote | |
Wormholio wrote:
What would happen if I connected with a client that claims to be version 0.1.1? ____________ | |
ID: 8065 | Rating: 0 | rate: / Reply Quote | |
Nicolas wrote:
My algorithm for "what would happen" questions is something like if( !dangerous_chemicals && !high_voltage && !break_something ){ go_for_it(); } So good question. What would happen? ____________ -- Eric Myers "Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats | |
ID: 8066 | Rating: 0 | rate: / Reply Quote | |
Nicolas wrote:
Another good question. Maybe they reverted back on more than manager code? Maybe the bug was in display but not in processing the response? I don't know the details of how this bug works, I only observe that it looks like the same thing we've seen before. ____________ -- Eric Myers "Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats | |
ID: 8067 | Rating: 0 | rate: / Reply Quote | |
Pepo wrote: (exactly 2 weeks prior to this bug being repaired in 6.3.x trunk). That changeset is affects only server code! So it's irrelevant what they did with the core client versions; it's the Pirate ship that is lacking the fix. ____________ | |
ID: 8068 | Rating: 0 | rate: / Reply Quote | |
Wormholio wrote:
I haven't seen your server code that detects the version number :) And anyway, I remembered that client claims to be 6.2.something in the scheduler request precisely to avoid this kind of problem. ____________ | |
ID: 8069 | Rating: 0 | rate: / Reply Quote | |
Well, I've not checked the exact code changes, neither back then nor now, I was not even aware that the changes applied just to the server code. My understanding was that it is clear that the client behaves incorrectly too (among others, by deleting existing team name) and had to be repaired as well (and I've naively thought that the client has been fixed too :-) | |
ID: 8070 | Rating: 0 | rate: / Reply Quote | |
As I understand it: the client already worked correctly, by not changing the team name if there is no tag at all, and changing it to the empty string if there was an empty tag. The server was wrongly sending an empty tag instead of no tag at all if it hadn't even fetched that information from the database. | |
ID: 8071 | Rating: 0 | rate: / Reply Quote | |
Nicolas wrote:
Well then check it out in the Pirates' Glossary: [[Scheduler restrictions]] ____________ -- Eric Myers "Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats | |
ID: 8072 | Rating: 0 | rate: / Reply Quote | |
Message boards : Help! : client 6.4.0 is disallowed
Home | Help | Status | Forums | Glossary | Account
|