Right now work is restricted to BOINC v6.
If a v5 client contacts the server the Pirates team field is wiped blank (and stats aren’t updated) in the BOINC manager.
Similar to problems discovered here a long while back.
"It's déjà vu all over again"?
____________

Click and enter your name for your BOINC Statistics

Got this message:


14.04.2008 17:44:51|Pirates@Home|Message from server: Your version of the BOINC core client (5.10.28) is temporarily disallowed for testing.



Never seen this message.
____________

Scheduler restrictions won't give work to any other client than the 6.1.14 ... so even a 6.1.12 won't get work. The test is for 6.1.14 only.
____________
Jord.

The BOINC FAQ Service.

Right now work is restricted to BOINC v6.
If a v5 client contacts the server the Pirates team field is wiped blank (and stats aren’t updated) in the BOINC manager.
Similar to problems discovered here a long while back.
"It's déjà vu all over again"?

Finally found the relevant thread:
Team not showing in BOINC manager

After trying out the nowork_skip tag:

So what happens is, the client connects to the server, but gets back a very terse (perhaps even more or less empty) reply, and from that the client concludes that you don't belong to a team, and it also doesn't update any of your other stats. Your last time of contact is not updated in the database because the database never got contacted.

I can understand that most stats won't get updated, but the loss of the team is indeed confusing. This probably deserves a Trac ticket as a bug. [edit]I just posted it[/edit] If you are in a team, but the RPC response doesn't mention a team, then don't make any changes. It's possible that the current RPC response has a blank team entry (rather than none at all).

I'm sure that's easily fixed by those who know how to do it. I'll bet they can apply the same principle to other items in the RPC response, though it might also require some changes in how the client processes the response. I will leave that to the RPC experts.

Finally found the relevant thread:
Team not showing in BOINC manager

I'm using version 6.1.14 now but when trying to fetch new work I'm getting

15.04.2008 21:40:50|Pirates@Home|[error][error] handle_trickle_down failed: unexpected null pointer

Hatte ich auch, machte aber nichts, danach kamen die Units an Bord!
Viel Glück und gute Jagd!

I had the same Problem, but it didn't matter, just after the message the work came to me!
____________
Dragons can fly because they don't fit into pirate ships

Danke, hab ich inzwischen auch gemerkt und zwei neue "Goldnuggets" runtergeladen! *gg*

Yeah, thanks - I noticed that I have dowloaded two fresh gold nuggets again! :-)
____________
Arrrrr! I'm a proud member o' the pirates' ship crew BOINC@Heidelberg

What the heck is that? ;-)))

Client restriction is now 6.1.14 and above. This is because 6.1.15 is released to Alpha for the Mac and Linux. Let's hope that the Linux versions will now return work without errors.
____________
Jord.

The BOINC FAQ Service.

As far as we could see a project can require a boinc version of x.x.x or higher.

Can a project than also exclude one or two special versions of the boinc client?
____________
Dragons can fly because they don't fit into pirate ships

Yes.
____________
Jord.

The BOINC FAQ Service.

Thanks Jord.

Is there a reason why you left out the now popular 6.1.0?
Did we use this kind of restrictions here at pirates before?
Will we?
____________
Dragons can fly because they don't fit into pirate ships

I didn't leave anything out as I didn't write that. It's only an example of a scheduler restriction. Admins can add more of them if they want to.
____________
Jord.

The BOINC FAQ Service.