I have never seen this error message before. In our team three users get this when we try to read stats.

The account is available, but not the show_user feature.

http://setiweb.ssl.berkeley.edu/sah/show_user.php?userid=53694

---

Kind regards
Kirsten

PS. I installed version 4.16 today as Rom Walston recommended us to do that asap. Maybe the there's a bug in 4.16...

---

Kind regards
Kirsten

> PS. I installed version 4.16 today as Rom Walston recommended us to do that
> asap. Maybe the there's a bug in 4.16...
>
I must have missed Rom's message. What (and where) is his message?

---

<img src='http://www.boincsynergy.com/images/stats/comb-912.jpg'>

...installed version 4.16 today as Rom Walston recommended...
I'd like to see that message too! Is that just for x86 or PPC as well? And if it's so good, why is 4.13 listed in the downloads page??

---

> ...installed version 4.16 today as Rom Walston recommended...
> I'd like to see that message too! Is that just for x86 or PPC as well? And
> if it's so good, why is 4.13 listed

Good question - Could be that 4.16 is not to consider as a final release yet ...???
But where can I find 4.16?

---

Happy crunching

> ...installed version 4.16 today as Rom Walston recommended...

the only place i have seen such a message is from Jan 20 over at einstein.

EDIT: i also got this error on the top participants page for credit for page 880
http://setiweb.ssl.berkeley.edu/top_users.php?sort_by=total_credit&offset=880

---

S@h Berkeley's Staff Friends Club

Rule of thumb when dealing with software (especially shareware, freeware, GPL-ware, and WTF-ware):
Even though you've heard about it, don't use it until the developer makes it available for everyone else. That way everyone crashes simultaneously, and you don't look like an idiot.

Corollary to previous rule:
Don't invoke the developers by name - you're liable to be kicked out of the secret kabbal sooner if you do...

---

As one user already has said then the message from Rom Walston is found at Einstein@home - the download link is at BOINC all right, but not on their usual download page instead we get this link http://boinc.berkeley.edu/dl/boinc_4.16_windows_intelx86.exe. In http://boinc.berkeley.edu/dl/ you find all the versions from 4.05 and up.

In EAH users are told they should only use 4.16 or higher. It's not told whether this version of BOINC is BETA or not. EAH is still in beta though... You should be warned, though, that on install some users have experienced that wu's were deleted.

Rom's message:

Jan 20. 2005

The BOINC developers have once again released a new version of the client (4.16) that fixes two bugs. Here is what Rom said in the release notes.


This release contains two fixes:

- don't unsuspend tasks before restarting them
- allow large command lines (backpatched from 4.5x)

----- Rom

Please upgrade to 4.16 as soon as possible.

---

Kind regards
Kirsten

as the path in the error message indicates, this is a caching related error. The server caches a lot of pages so that it doesn't have to hit the database every time the page is called up. The cache is set to expire every so often. Not sure what the time period is for seti@home. Usually these errors go away after the cache expires and forces the page to be refreshed from the database. How long have these pages been displaying the error?

4.16 is strictly a client-side upgrade as far as I know so it shouldn't be affecting anything on the server.

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

Thanks Kirsten,

Hmmm... I'm a bit surprised that one project has a different "official" Boinc version than the others. I thought, except for the testers, that we were all supposed to be using the same Boinc version.

So does that mean all projects should upgrade to 4.16 (or maybe 4.17 which seems to be ready for release real soon)?

---

<img src='http://www.boincsynergy.com/images/stats/comb-912.jpg'>

> How long have these pages been displaying the error?
>
> 4.16 is strictly a client-side upgrade as far as I know so it shouldn't be
> affecting anything on the server.

I DID sleep tonight :-) but overnight the cache problem had solved itself.

I didn't think before I suggested that the new BOIBC version had anything to do with the problem, so thank you for informing me.

---

Kind regards
Kirsten

> Thanks Kirsten,
>
> Hmmm... I'm a bit surprised that one project has a different "official" Boinc
> version than the others. I thought, except for the testers, that we were all
> supposed to be using the same Boinc version.
>
> So does that mean all projects should upgrade to 4.16 (or maybe 4.17 which
> seems to be ready for release real soon)?

I think version 4.16 has a serious problem: at random the installation deletes work units (one user in our team among other units had two CPDN units - those enormous units - deleted). He changed version on 5 or 6 machines. In two cases work units were deleted. In the remaining cases they were not.

But this is off topic. So sorry.

---

Kind regards
Kirsten

> Thanks Kirsten,
>
> Hmmm... I'm a bit surprised that one project has a different "official" Boinc
> version than the others. I thought, except for the testers, that we were all
> supposed to be using the same Boinc version.
>
> So does that mean all projects should upgrade to 4.16 (or maybe 4.17 which
> seems to be ready for release real soon)?

4.15 and above are only being used by Einstein@home. They are using some features that no other project is using and found some bugs in the client that had to be fixed for the project to function correctly. All the other projects work with 4.15+ but I wouldn't recomend upgrading unless you are doing Einstein. And Einstein is in a beta stage and using unstable versions of the client so it should be expected that some things will go wrong with it, possibly causing loss of credits and/or work units. That is the cost of being on the bleeding edge :)

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

I'm seeing too many different versions...

I can understand if the project executable (the actual S@H, E@H, CP app) keeps getting updated, but how many different BOINC clients are there? I can't tell if what I'm running is good or bad with all of this chatter!

I don't need bleeding edge - I need a stable (ie: it's not screw up my system more than I can on my own) version. PPC. OS X and YDL4/FC3. Preferably taking advantage of the vector unit. With GUI would be nice, but not really necessary...

Oh - and that claims credits correctly.

---

As a general rule just stick whith whichever build is listed here, as far as stability goes:
http://boinc.berkeley.edu/download.php

It looks like we'll be changing our stable build from 4.13 to 4.17 today.

---

----- Rom
BOINC Development Team, U.C. Berkeley
My Blog

Great! I'll polish of this last WU and then update.

Thanks for clarifying the version issue!

---

It looks like 4.18 will be the next stable version now. A proxy problem in 4.17 caused a new build.

PP@H also needs 4.16 or later due to the new and better CPU identification.

---

BOINC WIKI

BOINCing since 2002/12/8

> I'm seeing too many different versions...
>
> I can understand if the project executable (the actual S@H, E@H, CP app) keeps
> getting updated, but how many different BOINC clients are there? I
> can't tell if what I'm running is good or bad with all of this chatter!
>
> I don't need bleeding edge - I need a stable (ie: it's not screw up my system
> more than I can on my own) version. PPC. OS X and YDL4/FC3. Preferably
> taking advantage of the vector unit. With GUI would be nice, but not really
> necessary...
>
> Oh - and that claims credits correctly.
========

I agree, it's like it's the Version of the Hour, I just got done Updating all my Computers to v4.17 this morning and when I get home from work theres a new version out already, how's a person supposed to get any crunching done when their Updating 5 times a day ... ;)

---

> As a general rule just stick whith whichever build is listed here, as far as
> stability goes:
> http://boinc.berkeley.edu/download.php
>
> It looks like we'll be changing our stable build from 4.13 to 4.17 today.
>
>
Thanks Rom. I (my own opinion) think that each project should be designed to work with the current "public released" Boinc version. If there's a problem for one project, it's that project's problem and that project should work with the Boinc team to get a solution. That's one of the reasons I've stuck to just working one project (Seti) at this time.

If it takes changing the project to work with the current Boinc or helping to get an updated Boinc that works for everyone (all projects) so be it. But I assume the one goal of Boinc is that all project's, new and old, can work under the existing Boinc infrastructure.

---

<img src='http://www.boincsynergy.com/images/stats/comb-912.jpg'>

Well that is why the http://boinc.berkeley.edu/download.php page was developed.

A few of the projects have quite been comfortable with turning over the release schedule to us yet. We are working on it though.

Eventually we will get this whole shared infrastructure ironed out.

---

----- Rom
BOINC Development Team, U.C. Berkeley
My Blog