[mb-datafeed] Upgrade instructions for 20071014 server release

[Nicholas Humfrey]

That all worked fine on our slave server. Thanks Rob :)

nick.

On 15/10/07 00:31, "Robert Kaye" <rob at eorbit.net> wrote:

> Please follow these steps to upgrade your installation:
> 
> 0. Make sure that all packets have been applied to current database.
> You should
>     see an error like this:
> 
>       This replication packet matches schema sequence #9, but the
> database is currently at #8
>       You must upgrade your database in order to apply this
> replication packet
> 
> 1. Check out the new code base from subversion and place it in the
> same top level
>     directory as the current codebase:
> 
>       svn co http://svn.musicbrainz.org/mb_server/branches/
> RELEASE_20071014-BRANCH mb_server-20071014
> 
> 3. Configure your new codebase and copy new config files:
> 
>       cd mb_server-20071014/cgi-bin
>       cp DBDefs.pm.default DBDefs.pm
>       cd ../admin
>       cp startup.pl.default startup.pl
> 
> 4. Edit cgi-bin/DBDefs.pm and admin/startup.pl and copy over the
> appropriate
>     configuration items from the old codebase:
> 
>     a. DBDefs.pm needs DB config settings changed. Also make sure
> that REPLICATION_TYPE is
>        set to RT_SLAVE. Set the WEB_SERVER and RDF_SERVER settings to
> match your old
>        configuration. Then review the file to make sure nothing else
> needs changing.
>        It might be useful to diff your old config file against the
> new one to make sure
>        you handled everything.
>     b. startup.pl should only need the use lib line changed, if at
> all. Look for TODO.
> 
>     Test your configuration by doing:
> 
>     cd <to admin dir>
>     ./psql READWRITE
> 
>     That should get you to your database server shell if everything
> is configured right. \q to exit.
> 
> 5. Turn off cron jobs that might affect the server update.
> 
> 6. Run the automatic database upgrade script:
> 
>     cd <top level mb_server dir>
>     ./upgrade.sh
> 
>     This should run for quite some time as it updates the database to
> the latest and greatest.
> 
> 7. Test the update by loading more replication changes:
> 
>     cd replication
>     ./LoadReplicationChanges
> 
>     You should see your database catch up to the latest replication
> sequence.
> 
> 8. Turn cron jobs back on.
> 
> 9. You're done!
> 
> Please post any questions/issues you might have here.
> 
> Thanks!
> --
> 
> --ruaok      Somewhere in Texas a village is *still* missing its idiot.
> 
> Robert Kaye     --     rob at eorbit.net     --    http://mayhem-chaos.net
> 
> 
> 
> _______________________________________________
> Musicbrainz-datafeed mailing list
> Musicbrainz-datafeed at lists.musicbrainz.org
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed


http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.