INCOMPATIBILITY WARNING FOR UPCOMING 6.13.3 BUILD

Howdy Folks,

I'm getting ready to release a new build of 6.13, this new build contains changes to support volunteer storage. You can see some of the details here: http://boinc.berkeley.edu/trac/wiki/VolunteerStorage

Basically when you upgrade to this build there will be some changes to the client_state.xml file which will make it incompatible with older client software.

I strongly suggest making a backup copy of the data directory before upgrading to the new build just in case something happens and you need to roll-back to an earlier build of BOINC.


----- Rom

When you upgrade to this build from any 6.12 or previous versions, or from 6.13.0 or 6.13.1, then do know that here will be some changes to the client_state.xml file which will make it incompatible with older client software. We strongly suggest making a backup copy of the data directory before upgrading to the new build just in case something happens and you need to roll-back to an earlier build of BOINC.

EXTRA WARNING

The new BOINC 6.13 range is using completely new, from the ground up rewritten code for many of its parts. It is not to be used if you are not an alpha tester. It is not to be used on all of your machines, just on one. When it doesn't work, report your problems to the developers and return to the latest 6.12.recommended.

At this time we're specifically testing whether or not the new CPU/GPU scheduling code works without using debt, and if projects will fetch work.

This is not a version that you install and walk away from, it needs constant checking, including the use of all the correct client configuration flags. Make sure your log files are of sufficient size so you can log through the night.

Minimum required flags to report with are <cpu_sched_debug>, <rr_simulation>, <sched_op_debug>, <work_fetch_debug>

Do not run experimental versions of BOINC on live projects, unless you also subscribe to the associated BOINC Alpha email list, and have time to read and act upon any recall or hotfix notices for builds which turn out to be buggy.

Remember, these early 6.13s are not for prolonged use if you aren't going to send regular logs back to the developer. These versions will only annoy the heck out of you, since they will do work fetch completely different from what you have come to expect of BOINC. Just don't use it if you're not serious about it!


If you must be bleeding edge without being an alpha tester, and things go wrong, you only have yourself to blame. Don't say we didn't warn you... :-)

Keep up-to-date on BOINC 6.13 changes through the BOINC 7 Change Log 6.13 and news thread.

David Anderson wrote:

There are (at least) two issues with 6.13.3:

1) For GPU apps, it passes an additional command-line argument that causes some apps to fail (usually by exiting immediately). This will be fixed in 6.13.4.

2) 6.13.3 handles file upload certificates (a mechanism that prevents DoS attacks on upload servers) differently than previous versions.
This change was necessary to make scheduler requests and replies readable by standard XML parsers. But it means that file uploads will fail to projects that a) use upload certificates, and b) aren't running current server code.

I sent email to boinc_projects describing this change, and recommending that projects disable upload certificates until they're able to upgrade their server code. Not all project admins read boinc_projects, so it may be necessary to contact them via their message boards or email, and I urge Alpha-testers to do so.

-- David

David Anderson, boinc_projects email list wrote:

"Upload certificates" are a mechanism that keeps bad guys from DoS'ing your upload servers (note: such an attack has never happened, as far as I know).

We're changing the format of upload certificates, and we're starting to test a version of the client for which old-format certificates won't work. Volunteers testers won't be able to upload completed jobs, and they may complain to you.

I suggest that all projects disable upload certificates. To do so, add the following to your config.xml file:

<dont_generate_upload_certificates/>
<ignore_upload_certificates/>

To resume using upload certificates, if you wish:

1) upgrade to the current server source code (from trunk)
2) wait for all jobs with old-format certificates to be dispatched
3) re-enable certificates by removing the above lines.

Let me know if any questions.

-- David

6.13.4 has been retracted from the download pages until the installation problems can be solved. If you're using 6.13.4, please uninstall it and go back to the client you were using before.

I'm working with Rom on the service installation problem that's also plaguing the 6.12 range since 6.12.34; I've managed to throw a whole batch of work away already anyway, let me be the fall guy. Don't let it happen to you. :-)

Service installation problem?

The problem is still with the ATI 11.7 (or 11.8) catalysts, which break the detection of the card. If you do not use your GPU, you can get around this with a cc_config.xml file that contains the following lines:

<cc_config>
    <options>
        <no_gpus>1</no_gpus>
    </options>
</cc_config> 

This will require a restart of the client.

If you do use your GPU, you shouldn't install as a service on Windows 7 and Vista anyway due to the session 0 problem.

In the mean time, Rom is including a fix that will disable the GPU detection. It'll be in the forthcoming 6.12.38. This will however break GPU detection when installed as a service on Windows XP as well. Sorry for that, but it's either, or. That will get fixed in a future release, until that time, go complain at ATI/AMD that they need to fix their drivers! And please report back when they said they did. ;-)