Changes between Version 16 and Version 17 of ToolUpgrade
- Timestamp:
- Oct 8, 2008, 9:58:52 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ToolUpgrade
v16 v17 1 1 = Upgrading server software = 2 2 3 The BOINC server software (scheduler, daemons, web pages) is continually improved and debugged. We recommend that projects upgrade to the latest version every few weeks or so. There may also be points where upgrades are mandatory to continue working with current client software. 3 The BOINC server software (scheduler, daemons, web pages) is continually improved and debugged. 4 We recommend that projects upgrade whenever a new server_stable version is released. 5 There may also be points where upgrades are mandatory to continue working with current client software. 4 6 We maintain a list of [ServerUpdates recent changes]. 5 7 6 8 The steps required to upgrade are as follows: 7 9 8 1. (Optional) Stop the project, and make backups of the project database and the project tree. 9 1. [SourceCode Download] (using SVN) the current source code. [ServerIntro#cookbook-compiling Compile] it in your BOINC source directory (called `source' below). 10 1. (Optional) Stop the project. 11 1. [SourceCode Download] (using SVN) the server_stable branch (or the trunk). [ServerIntro#cookbook-compiling Compile] it in your BOINC source directory (called `source' below). 12 1. Recompile all project-specific back end programs (validators, assimilators). 10 13 1. Run the upgrade script: 11 14 {{{ … … 19 22 $ ./upgrade --project_root=/path/to/projects project_name 20 23 }}} 21 The project directory would then be `/path/to/projects/project_name`. This allows for several BOINC projects to co-exist on the same server.24 The project directory would then be `/path/to/projects/project_name`. 22 25 23 26 It is possible to update only the web pages (PHP files), using the `--web_only` flag: … … 25 28 $ ./upgrade --web_only project_name 26 29 }}} 27 (There is no option to update only the server software but not the web pages, but there should be. I'm working on it now... -EAM)28 30 29 4. Update your project's database, if needed. First 31 5. Start the project, and check log files to make sure everything is OK. Run the BOINC client and test basic functions (attaching to project, getting work). 32 33 == Updating the database structure == 34 35 Starting with SVN changeset [16160], database updates are performed automatically by '''upgrade'''. 36 Older updates must be done as follows. 37 30 38 {{{ 31 39 $ cd project/html/ops … … 35 43 update_8_05_2005() 36 44 }}} 37 Each function performs a particular database update. You must perform all updates, in sequence, starting from your last server software upgrade. If you are not sure when that was, you can use `mysql` to see that current format of your database. For example, to see the fields in the `user` table, type 45 Each function performs a particular database update. 46 You must perform all updates, in sequence, starting from your last server software upgrade. 47 If you are not sure when that was, you can use `mysql` to see that current format of your database. 48 For example, to see the fields in the `user` table, type 38 49 {{{ 39 50 $ mysql project_name … … 45 56 }}} 46 57 Repeat this for the necessary updates, in increasing chronological order. 47 1. Check file permissions and ownership of the feeder, scheduler, etc.48 1. Start the project, and check log files to make sure everything is OK. Run the BOINC client and test basic functions (attaching to project, getting work).
