LHC@home

Hi

Have just download BOINC Version 5

The project rejects the client

is thier a reason.

---

<img border="0" src="http://boinc.mundayweb.com/one/stats.php?userID=2104" />

Hi again

THis client going to get really hard to debug

Extract from log.

20:24:13||request_reschedule_cpus: exit_tasks
20:24:13|SETI@home|Detaching from project
20:32:08|http://einstein.phys.uwm.edu/|Master page download succeeded
20:32:09|http://einstein.phys.uwm.edu/|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
20:32:09|http://einstein.phys.uwm.edu/|Requesting 345600 seconds of work, returning 0 results
20:32:10|http://einstein.phys.uwm.edu/|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
20:32:10|Einstein@Home|Message from server: Need major version 4 of the BOINC core client. You have 5.
20:32:10|Einstein@Home|Resetting project
20:32:10||request_reschedule_cpus: exit_tasks
20:32:10|Einstein@Home|Detaching from project
20:37:20|http://setiweb.ssl.berkeley.edu/beta/|Master page download succeeded
20:37:21|http://setiweb.ssl.berkeley.edu/beta/|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi
20:37:21|http://setiweb.ssl.berkeley.edu/beta/|Requesting 345600 seconds of work, returning 0 results
20:37:22|http://setiweb.ssl.berkeley.edu/beta/|Scheduler request to http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi succeeded
20:37:22|SETI@home Beta Test|Message from server: Need major version 4 of the BOINC core client. You have 5.
20:37:22|SETI@home Beta Test|Resetting project
20:37:22||request_reschedule_cpus: exit_tasks
20:37:22|SETI@home Beta Test|Detaching from project

It only appears to work with CPDN

Mind you I have found one error.

It tells me wrong account ID used. clearly not true from the log.

---

<img border="0" src="http://boinc.mundayweb.com/one/stats.php?userID=2104" />

Thank you to informe us!
-this shows me: that I have to wait for a better one....-

greetz littleBouncer

> Have just download BOINC Version 5
> The project rejects the client
> is thier a reason.

Yes there is a reason
http://boinc.berkeley.edu/download.php?dev=1
Development version (MAY BE UNSTABLE - USE ONLY FOR TESTING)

The 5.00 client was released for the ALPHA SETI project, so most projects are not ready for it.
They don't put those warnings there just for kicks.

---

As SunRedRX7 said, the warning is there so you cannot complain about things when they go sour. At this moment only Seti Beta's site is optimized for use of the 5.00 client of the Boinc you use. So if you want to test Seti Enhanced (Seti Beta) only, you can do so.

Just don't expect any other project to be updated until they do so.
Read this thread for more information.

---

Jord

BOINC FAQ Service

> As SunRedRX7 said, the warning is there so you cannot complain about things
> when they go sour. At this moment only Seti Beta's site is optimized for use
> of the 5.00 client of the Boinc you use. So if you want to test Seti Enhanced
> (Seti Beta) only, you can do so.
>
> Just don't expect any other project to be updated until they do so.
> Read this
> thread for more information.
>
I'm a member of seti/Beta. The 5.00 client was issued to Alpha group ONLY. Not Beta. Beta is testing an application that doubles the sensitivity of the Seti search software, and is supposed to allow for the testing of Astropulse WUs (although, I haven't seen an Astropulse WU yet).

Here's what Rom Walton has said in Email (Boinc_Alpha mail list):

Howdy Gang,

I'm releasing 5.00 for Windows to you all even before I've completed
my test pass. This release includes Account Management improvements and is
enabled out of the box as well as dial-up improvements.

Issues I know about are:
1. The manager doesn't currently pick-up preferences changes after
downloading new preferences from a project server.
2. The manager doesn't ever stop trying to connect when the modem fails to
be able to establish a connection.

Let me know of anything else. :)

----- Rom

Also.

I've removed the major version check in the scheduler and updated the
component on the alpha server.

I'll be sending email to all the project people informing them of the needed
change.

----- Rom

This CC is intended ONLY for the Alpha group

hope this helps

tony

---

Formerly
mmciastro. Name and avatar changed for a change

The New Online Helpsytem help is just a call away.

We saw the same thing occur when the 4.x core clients were released and the applications were using the 3.x versions. So this does not surprise me in the slightest....

---

Until recently the server side software was programmed such that it would refuse a connection from any core client that wasn't at the same major version as it. With the versioning system being used they ran out of 4.x numbers so they had to bump the version number up to 5 although there aren't any "major" changes. The server code was updated to allow a version 4 server to accept connections from a version 5 client however most projects haven't updated their server code yet so v5.x will not work until they do.

---

- A member of The Knights Who Say NI!
My BOINC stats site

I believe, what they have done was take the version "5.00" and call it version "4.70" so as to bypass that problem in the short term. Correct me if I am wrong.

Jim

> Until recently the server side software was programmed such that it would
> refuse a connection from any core client that wasn't at the same major version
> as it. With the versioning system being used they ran out of 4.x numbers so
> they had to bump the version number up to 5 although there aren't any "major"
> changes. The server code was updated to allow a version 4 server to accept
> connections from a version 5 client however most projects haven't updated
> their server code yet so v5.x will not work until they do.
>

4.70 is the current build of the client only ...

---

> I believe, what they have done was take the version "5.00" and call it version
> "4.70" so as to bypass that problem in the short term. Correct me if I am
> wrong.
>
> Jim
>
> > Until recently the server side software was programmed such that it
> would
> > refuse a connection from any core client that wasn't at the same major
> version
> > as it. With the versioning system being used they ran out of 4.x numbers
> so
> > they had to bump the version number up to 5 although there aren't any
> "major"
> > changes. The server code was updated to allow a version 4 server to
> accept
> > connections from a version 5 client however most projects haven't
> updated
> > their server code yet so v5.x will not work until they do.
> >
Yes and No. 4.70 is actually a rev past 5.00.

There were also some problems with even the most up to date server code and different major version numbers. Hopefully all that will be fixed before we run out of developement version numbers.

---

BOINC WIKI

BOINCing since 2002/12/8

Hi All

I have download 4.70 a few days ago. It seems to work fine.

It has some odd behaviour problems with the update all button. Seems to get hung up on a non responsive project server.

My impression - could be wrong are:

THe WU crunching is concurrent, but the comms queues are not.

---

<img border="0" src="http://boinc.mundayweb.com/one/stats.php?userID=2104" />

> Hopefully all that will be fixed before we run out of developement version
> numbers.
>

Are they limited to only 2 digits for the minor version? That seems a little restrictive.

---

<img src="http://www.boincstats.com/stats/teambanner.php?teamname=GasBuddy"> <img src="http://www.boincstats.com/stats/banner.php?cpid=84c0cf7846cbf28338406e54b3eb8a83">

> Are they limited to only 2 digits for the minor version? That seems a little
> restrictive.

For the moment, yes. However, the plan is to go to a system that has x.yy.zzz, and this should fix the minor version problem zzz is the release of a particular minor version, and I would assume would be used for development builds, and the next released version would increment the .yy field.

---

BOINC WIKI