Nabble - musicbrainz-datafeed

Official NGS notification

2009-07-30T14:37:55Z

Hi!

This serves as your official notification that we're planning on
rolling out NGS in the fall:

http://blog.musicbrainz.org/?p=398

Please make a point of reading this post ASAP -- there are many
drastic changes coming!

--

--ruaok A village in Texas has its idiot back!

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Start working with our NGS database today!

2009-06-20T13:00:52Z

Hi!

We've reached a significant milestone in our work towards NGS: The
database migration script is complete enough to import and convert
data from the main server. This gives you the opportunity to take a
look and actually play with the database schema we plan to use for the
NGS release. Please note that we do no guarantee this database format
to be stable -- I'm certain that we'll have to make minor adjustments
as we finish NGS. But overall, you should be able to get a solid idea
as to where we are heading with the database for NGS.

In order to get started, you'll need to follow these steps:

1. Create and import a copy of the data for the 20090524 release using
a data dump from 20090619 or later (important!):

http://bugs.musicbrainz.org/browser/mb_server/branches/RELEASE_20090524-BRANCH/INSTALL

2. Convert the data using the current NGS codebase.

http://bugs.musicbrainz.org/browser/mb_server/trunk/INSTALL

I would recommend reading both sets of INSTALL documents *before* you
get started on this process. Please note that you will need Postgres
8.3 to make this install work!

Finally, to see the first bits of NGS in action, check out my copy
running on my dev server:

http://musicbrainz.homeip.net:3000

--

--ruaok "Vague, but exciting..." -- Mike Sendall on the WWW
proposal.

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Upgrading to Postgres 8.3

2009-05-25T14:44:22Z

Hello!

I hope that the upgrade went smoothly for everyone here. Now that
we're past the Release Groups release, I would like to make everyone
aware of the fact that MusicBrainz needs to move to Postgres version
8.3 for the NGS release. Given that the NGS release itself will be
quite complicated enough we do not want to further complicate things
by switching databases at the same time. This means that sometime in
late June/early July we will upgrade the main MusicBrainz server to
Postgres 8.3. At the time of this upgrade we will _not_ be releasing
any new features. We're only upgrading the database and nothing else.

What does this mean for you?

It means that as soon as NGS comes about you are required to run
Postgres 8.3 in order to keep up to date with MusicBrainz. You'll have
to choose one of these courses of action:

1. Do nothing until the NGS release. Right after the NGS release,
install postgres 8.3 and re-import the first post-NGS data dump into
8.3.
2. Upgrade to Postgres 8.3 sometime *before* the NGS release, and then
use our provided migration scripts to move the data to NGS.

I suspect that option #1 will take less time overall, but its entirely
up to you on how to proceed. However, I suspect that existing mirrors
running 8.1/8.2 will continue to function until NGS comes out.

Once we nail down a firm date for this upgrade, I will post that info
here and on the blog.

--

--ruaok A village in Texas has its fool back!

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Upgrade instructions for the 20090524 release

2009-05-24T17:37:56Z

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 #11, but the
database is currently at #10
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_20090524-BRANCH
mb_server-20090524

3. Configure your new codebase and copy new config files:

cd mb_server-20090524/cgi-bin
cp DBDefs.pm.default DBDefs.pm

4. Edit cgi-bin/DBDefs.pm 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.

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. In admin/apache you will want to create startup.pl,
vh_mb_backend.conf by
copying them from the .default files and adjusting all the sections
marked with TODO. Include startup.pl and vh_mb_backend.conf in your
apache configuration if you actually run the MusicBrainz site on your
system. If you have a database only install, you can skip this step.

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
be ready for the new features.

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 A village in Texas has its idiot back!

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

More information for the schema change release on May 24th

2009-05-14T16:20:09Z

Hi!

I've just posted a call for testing for the May 24th release:

http://blog.musicbrainz.org/?p=388

This release is a "normal" release, meaning that we're still working
with our old Mason/apache-perl based codebase. There should be no real
gotchas in this release. Our next release, the major NGS release will,
of course, be quite a different story. Expect to hear from me loads
before this happens.

As usual on May 24th I'll post upgrade instructions here that will let
you bring your installation up to date. Stay tuned!

--

--ruaok A village in Texas has its fool back!

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Next schema change release: May 24th

2009-05-04T15:21:41Z

The next update of the MusicBrainz server will happen on May 24th.
This release is a schema change release which means that you will need
to upgrade your copy of the MusicBrainz server in order for it to
continue fetching updates from the main server. For more details, see:

http://blog.musicbrainz.org/?p=387

--

--ruaok A village in Texas has its fool back!

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: [musicbrainz] Upgrade instructions for the 20081123 release

2008-12-09T03:06:14Z

On Mon, 8 Dec 2008, Sandro Mancuso wrote:

> I believe that the main problem here is the Symbolic link that is not
> correct. I'll need to work on something else now but I'll come back to this
> at some point. I'll try to fix the symbolic link and I'll put the outcome of
> it here in this thread soon.
>
Try adding a

Options FollowSymLinks

in an appropriate place in your apache config.

Steve

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: [musicbrainz] Upgrade instructions for the 20081123 release

2008-12-08T00:39:06Z

Hi Steve,

I have changed the htdocs folder permission to read/write to all users. The htdocs folder is owned by the mbserver user and I'm starting Apache with the root user. (I cannot start apache with mbserver user).

After changing it, I was still getting "403 Forbidden" from Apache. In Apache logs if found the following problems:

[Thu Dec 4 12:37:18 2008] [error] (2)No such file or directory: mod_mime_magic: can't read magic file /usr/share/misc/file/magic.mime
[Thu Dec 4 12:37:18 2008] [notice] Apache/1.3.34 (Debian) mod_perl/1.29 configured -- resuming normal operations
[Thu Dec 4 12:37:18 2008] [notice] Accept mutex: sysvsem (Default: sysvsem)
Cache MISS on istagger-192.168.234.1 at /home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/Handlers.pm line 274
[Thu Dec 4 12:37:23 2008] [error] [client 192.168.234.1] Symbolic link not allowed: /home/httpd/musicbrainz/mb_server/
Cache MISS on istagger-192.168.234.1 at /home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/Handlers.pm line 274
[Thu Dec 4 12:37:24 2008] [error] [client 192.168.234.1] Symbolic link not allowed: /home/httpd/musicbrainz/mb_server/
Cache MISS on istagger-192.168.234.1 at /home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/Handlers.pm line 274
[Thu Dec 4 12:37:25 2008] [error] [client 192.168.234.1] Symbolic link not allowed: /home/httpd/musicbrainz/mb_server/
Cache MISS on istagger-192.168.234.1 at /home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/Handlers.pm line 274
[Thu Dec 4 12:37:26 2008] [error] [client 192.168.234.1] Symbolic link not allowed: /home/httpd/musicbrainz/mb_server/
Cache MISS on istagger-192.168.234.1 at /home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/Handlers.pm line 274
[Thu Dec 4 12:49:54 2008] [error] [client 192.168.234.1] Symbolic link not allowed: /home/httpd/musicbrainz/mb_server/
[Thu Dec 4 12:50:10 2008] [warn] child process 10112 still did not exit, sending a SIGTERM
[Thu Dec 4 12:50:14 2008] [notice] caught SIGTERM, shutting down
[Thu Dec 4 12:50:16 2008] [error] (2)No such file or directory: mod_mime_magic: can't read magic file /usr/share/misc/file/magic.mime
[Thu Dec 4 12:50:16 2008] [error] (2)No such file or directory: mod_mime_magic: can't read magic file /usr/share/misc/file/magic.mime
[Thu Dec 4 12:50:16 2008] [notice] Apache/1.3.34 (Debian) mod_perl/1.29 configured -- resuming normal operations
[Thu Dec 4 12:50:16 2008] [notice] Accept mutex: sysvsem (Default: sysvsem)
Cache MISS on istagger-192.168.234.1 at /home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/Handlers.pm line 274
[Thu Dec 4 12:50:23 2008] [error] [client 192.168.234.1] Symbolic link not allowed: /home/httpd/musicbrainz/mb_server/
Cache MISS on istagger-192.168.234.1 at /home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/Handlers.pm line 274
[Thu Dec 4 12:50:27 2008] [error] [client 192.168.234.1] Symbolic link not allowed: /home/httpd/musicbrainz/mb_server/

I believe that the main problem here is the Symbolic link that is not correct. I'll need to work on something else now but I'll come back to this at some point. I'll try to fix the symbolic link and I'll put the outcome of it here in this thread soon.

Many thanks,

Sandro

Steve Wyles wrote:

On Thu, 4 Dec 2008, Sandro Mancuso wrote:

> Now, another problem. When I type in the ip in the browser, I get a 403
> back:
>
> 403 Forbidden
> You don't have permission to access / on this server.
>
> Apache/1.3.34 Server at <My MBServer IP> Port 80
>
> Any ideias?

This is normally a file or directory permission problem. Check the htdocs
directory and the files under it are readable by the user that apache is
running as. The apache error log might give more information.

Steve (inhouseuk)

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@lists.musicbrainz.org
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: [musicbrainz] Upgrade instructions for the 20081123 release

2008-12-04T08:51:46Z

On Thu, 4 Dec 2008, Sandro Mancuso wrote:

> Now, another problem. When I type in the ip in the browser, I get a 403
> back:
>
> 403 Forbidden
> You don't have permission to access / on this server.
>
> Apache/1.3.34 Server at <My MBServer IP> Port 80
>
> Any ideias?

This is normally a file or directory permission problem. Check the htdocs
directory and the files under it are readable by the user that apache is
running as. The apache error log might give more information.

Steve (inhouseuk)

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: [musicbrainz] Upgrade instructions for the 20081123 release

2008-12-04T08:31:16Z

Hello again, Steve.

That was spot on. Thanks for that. I've installed JSON and I was able to start Apache.

brainzvm:~# /etc/init.d/apache-perl start
Starting apache-perl 1.3 web server...Preloading 241 components

Now, another problem. When I type in the ip in the browser, I get a 403 back:

403 Forbidden
You don't have permission to access / on this server.

Apache/1.3.34 Server at <My MBServer IP> Port 80

Any ideias?

Steve Wyles wrote:

On Thu, 4 Dec 2008, Sandro Mancuso wrote:

> [Thu Dec 4 10:16:15 2008] [error] Error during compilation of
> /home/httpd/musicbrainz/mb_server/htdocs/bare/rate.html:\nCan't locate
> JSON.pm in @INC (@INC contains: /home/mbserver/svn/mb_server/cgi-bin
> /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8
> /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8
> /usr/local/lib/site_perl /usr/local/lib/perl/5.8.7
> /usr/local/share/perl/5.8.7 . /etc/apache-perl/ /etc/apache-perl/lib/perl)

It appears you don't have the JSON perl modules installed. This is a
dependancy in the server install docs.

You can grab it from http://search.cpan.org/dist/JSON/

or better still, use the perl cpan module to install it.

as root do:

perl -MCPAN -e shell

and at cpan> prompt do:

install JSON

Steve (inhouseuk)

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@lists.musicbrainz.org
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: [musicbrainz] Upgrade instructions for the 20081123 release

2008-12-04T07:58:18Z

On Thu, 4 Dec 2008, Sandro Mancuso wrote:

> [Thu Dec 4 10:16:15 2008] [error] Error during compilation of
> /home/httpd/musicbrainz/mb_server/htdocs/bare/rate.html:\nCan't locate
> JSON.pm in @INC (@INC contains: /home/mbserver/svn/mb_server/cgi-bin
> /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8
> /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8
> /usr/local/lib/site_perl /usr/local/lib/perl/5.8.7
> /usr/local/share/perl/5.8.7 . /etc/apache-perl/ /etc/apache-perl/lib/perl)

It appears you don't have the JSON perl modules installed. This is a
dependancy in the server install docs.

You can grab it from http://search.cpan.org/dist/JSON/

or better still, use the perl cpan module to install it.

as root do:

perl -MCPAN -e shell

and at cpan> prompt do:

install JSON

Steve (inhouseuk)

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: [musicbrainz] Upgrade instructions for the 20081123 release

2008-12-04T07:24:58Z

Hi Steve,

Thanks for your response. You were right about the SMTP_SECRET_CHECKSUM and now I was able to move a bit further. However, I'm facing another problem now.

Configuration syntax error detected, not starting/reloading...
Preloading 241 components
[Thu Dec 4 10:16:15 2008] [error] Error during compilation of /home/httpd/musicbrainz/mb_server/htdocs/bare/rate.html:\nCan't locate JSON.pm in @INC (@INC contains: /home/mbserver/svn/mb_server/cgi-bin /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl /usr/local/lib/perl/5.8.7 /usr/local/share/perl/5.8.7 . /etc/apache-perl/ /etc/apache-perl/lib/perl) at /home/httpd/musicbrainz/mb_server/htdocs/bare/rate.html line 49.\nBEGIN failed--compilation aborted at /home/httpd/musicbrainz/mb_server/htdocs/bare/rate.html line 49.\n\n\nStack:\n [/usr/share/perl5/HTML/Mason/Interp.pm:445]\n [/usr/share/perl5/HTML/Mason/Interp.pm:283]\n [/usr/share/perl5/HTML/Mason/Interp.pm:203]\n [/usr/share/perl5/HTML/Mason/Interp.pm:155]\n [/usr/share/perl5/Class/Container.pm:329]\n [/usr/share/perl5/Class/Container.pm:53]\n [/usr/share/perl5/HTML/Mason/ApacheHandler.pm:639]\n [/home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/Mason.pm:109]\n [/home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/Mason.pm:136]\nCompilation failed in require at /home/httpd/musicbrainz/mb_server/admin/apache/startup.pl line 118.\nCompilation failed in require at (eval 9) line 1.\n
Syntax error on line 32 of /etc/apache-perl/conf.d/vh_httpd.conf:
Error during compilation of /home/httpd/musicbrainz/mb_server/htdocs/bare/rate.html:
Can't locate JSON.pm in @INC (@INC contains: /home/mbserver/svn/mb_server/cgi-bin /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl /usr/local/lib/perl/5.8.7 /usr/local/share/perl/5.8.7 . /etc/apache-perl/ /etc/apache-perl/lib/perl) at /home/httpd/musicbrainz/mb_server/htdocs/bare/rate.html line 49.
BEGIN failed--compilation aborted at /home/httpd/musicbrainz/mb_server/htdocs/bare/rate.html line 49.

Stack:
[/usr/share/perl5/HTML/Mason/Interp.pm:445]
[/usr/share/perl5/HTML/Mason/Interp.pm:283]
[/usr/share/perl5/HTML/Mason/Interp.pm:203]
[/usr/share/perl5/HTML/Mason/Interp.pm:155]
[/usr/share/perl5/Class/Container.pm:329]
[/usr/share/perl5/Class/Container.pm:53]
[/usr/share/perl5/HTML/Mason/ApacheHandler.pm:639]
[/home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/Mason.pm:109]
[/home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/Mason.pm:136]
Compilation failed in require at /home/httpd/musicbrainz/mb_server/admin/apache/startup.pl line 118.
Compilation failed in require at (eval 9) line 1.

failed!
brainzvm:~#

I'll come back to the update script later, to avoid discussing two different problems at the same time. :-)

Once again I would like to thanks for your help.

Sandro

Steve Wyles wrote:

On Thu, 4 Dec 2008, Sandro Mancuso wrote:

> I'm having the same problem but in my case, even running the script many
> times, it still gets stuck on the same place.

Where does it get stuck?

> I've done that and I get the following error after running
> /etc/init.d/apache-perl start:
>
> [Thu Dec 4 08:25:09 2008] [error] SMTP_SECRET_CHECKSUM not set at

You need to set SMTP_SECRET_CHECKSUM in DBDefs.pm to something and apache
should then start.

Steve (inhouseuk)

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@lists.musicbrainz.org
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: [musicbrainz] Upgrade instructions for the 20081123 release

2008-12-04T06:48:49Z

On Thu, 4 Dec 2008, Sandro Mancuso wrote:

> I'm having the same problem but in my case, even running the script many
> times, it still gets stuck on the same place.

Where does it get stuck?

> I've done that and I get the following error after running
> /etc/init.d/apache-perl start:
>
> [Thu Dec 4 08:25:09 2008] [error] SMTP_SECRET_CHECKSUM not set at

You need to set SMTP_SECRET_CHECKSUM in DBDefs.pm to something and apache
should then start.

Steve (inhouseuk)

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: [musicbrainz] Upgrade instructions for the 20081123 release

2008-12-04T05:24:43Z

Hi,

I'm having the same problem but in my case, even running the script many times, it still gets stuck on the same place.

Another thing that I'm a bit unsure is about the Apache configuration. Do I need to do change the symbolic link /etc/apache-perl/conf/vh_httpd.conf to point to /home/mbserver/svn/mb_server/admin/apache/vh_mb_backend.conf?

I've done that and I get the following error after running /etc/init.d/apache-perl start:

brainzvm:~# /etc/init.d/apache-perl start
Configuration syntax error detected, not starting/reloading...
[Thu Dec 4 08:25:09 2008] [error] SMTP_SECRET_CHECKSUM not set at /home/mbserver/svn/mb_server/cgi-bin/UserStuff.pm line 823.\nCompilation failed in require at /home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/AutomodElection.pm line 51.\nBEGIN failed--compilation aborted at /home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/AutomodElection.pm line 51.\nCompilation failed in require at /home/httpd/musicbrainz/mb_server/admin/apache/startup.pl line 62.\nCompilation failed in require at (eval 9) line 1.\n
Syntax error on line 32 of /etc/apache-perl/conf.d/vh_httpd.conf:
SMTP_SECRET_CHECKSUM not set at /home/mbserver/svn/mb_server/cgi-bin/UserStuff.pm line 823.
Compilation failed in require at /home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/AutomodElection.pm line 51.
BEGIN failed--compilation aborted at /home/mbserver/svn/mb_server/cgi-bin/MusicBrainz/Server/AutomodElection.pm line 51.
Compilation failed in require at /home/httpd/musicbrainz/mb_server/admin/apache/startup.pl line 62.
Compilation failed in require at (eval 9) line 1.

failed!

I would really appreciate any help.

Many thanks in advance.

Sandro

Robert Kaye wrote:

On Nov 25, 2008, at 9:37 AM, Matthew Paradis wrote:

>
> Dear Rob,
>
> I have been working through your installation instructions.
>
> On running ./upgrade.sh
>
> We get the following error
>
> Tue Nov 25 17:10:22 GMT 2008 : Upgrading to RELEASE-20081123-BRANCH
> Tue Nov 25 17:10:22 GMT 2008 : Update script, language and country
> tables
> BEGIN
> ERROR: duplicate key violates unique constraint "country_pkey"
>
> Please can you advise?

I don't know how or why, but running this script twice more fixes this
problem. On the second run it gets stuck somewhere else. On the third
run it works fine.

No clue. I hate computers. :)

--

--ruaok Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye -- rob@eorbit.net -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@lists.musicbrainz.org
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

FYI: Increased replication packet sizes

2008-11-28T15:16:56Z

Hi!

I am running a cleanup script that will fix some data accent issues in
the search tables. This will cause all the artists and releases to be
reindexed for the "direct search" functionality. This in turn causes
some larger than normal replication packets, which will take a little
longer to apply than usual.

For more info on this bug, see:

http://bugs.musicbrainz.org/ticket/3039

Also, if your mirror starts falling behind and taking more than an
hour to apply the packets, you should probably give your postgres
server more resources (this can happen with vanilla postgres
installs). Usually upping the shared_segments makes a drastic
difference in the performance of Postgres. Consult the docs for more
information in how to tune you database server.

--

--ruaok A village in Texas will soon be reunited with its fool!

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: [musicbrainz] Upgrade instructions for the 20081123 release

2008-11-25T10:53:41Z

On Nov 25, 2008, at 9:37 AM, Matthew Paradis wrote:

Dear Rob,

I have been working through your installation instructions.

On running ./upgrade.sh

We get the following error

Tue Nov 25 17:10:22 GMT 2008 : Upgrading to RELEASE-20081123-BRANCH
Tue Nov 25 17:10:22 GMT 2008 : Update script, language and country
tables
BEGIN
ERROR: duplicate key violates unique constraint "country_pkey"

Please can you advise?

I don't know how or why, but running this script twice more fixes this problem. On the second run it gets stuck somewhere else. On the third run it works fine.

No clue. I hate computers. :)

--

--ruaok Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Upgrade instructions for the 20081123 release

2008-11-24T20:19:51Z

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 #10, but the
database is currently at #9
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_20081123-BRANCH
mb_server-20081123

3. Configure your new codebase and copy new config files:

cd mb_server-20081123/cgi-bin
cp DBDefs.pm.default DBDefs.pm

4. Edit cgi-bin/DBDefs.pm 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.

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. The web server configuration files have significantly changed and
are now in tune with what we're running on the main servers. In admin/
apache you will want to create startup.pl, vh_mb_backend.conf by
copying them from the .default files and adjusting all the sections
marked with TODO. Include startup.pl and vh_mb_backend.conf in your
apache configuration if you actually run the MusicBrainz site on your
system. If you have a database only install, you can skip this step.

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
be ready for the new features.

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@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Server release postponed

2008-11-23T15:19:12Z

We ran out of time to complete the release today:

http://blog.musicbrainz.org/?p=364

We're on for tomorrow. Sorry for the hassle. :-(

--

--ruaok A village in Texas will soon be reunited with its fool!

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Next schema change server update: November 23, 2008

2008-10-22T16:26:11Z

Hi!

Its been a looong time since we updated the main server. :-( But, now
we have lots of new features in store and we plan to update the main
server on the 23rd of November. Please be aware that this is a schema
change release which will require you to update your own installation
of the MusicBrainz server.

For more details on the next release see here:

http://blog.musicbrainz.org/?p=358
http://blog.musicbrainz.org/?p=348

--

--ruaok Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

IMPORTANT: Clients using Postgres 8.0.x need to upgrade to Postgres 8.1.x

2007-11-28T14:10:20Z

Hi!

The main server, running postgres 8.1, emitted a replication packet
that contains a UNICODE character that clients using postgres 8.0
cannot process. In order to continue the replication stream, you must
upgrade your postgres installation to 8.1.

To upgrade Postgres, download the 8.1.10 tarball and read INSTALL. In
the INSTALL file is a section that contains detailed instructions on
how to upgrade an existing postgres installation. Follow those
instructions and empty the "Pending" and "PendingData" tables (see
step 9) should be all that is required to upgrade your installation.

In order to upgrade one client that I have access to, I did:

0. Download and compile a new postgres installation.

1. Disable cron jobs.

2. Using the *OLD* postgres installation, dump all the tables with:

pg_dumpall -h localhost -U postgres > /tmp/postgres-8.0.dumpall

3. Stop the old postgres instance

4. Install the new postgres version. I installed mine into a directory
parallel to the old installation and used an entirely new database
data directory.

5. copy configuration settings from my old postgres install
(postgres.conf, pg_hba.conf) to the new postgres install.

6. Create a new postgres data directory using initdb as specified in
INSTALL. Remember to specify the locale=C argument to initdb

7. Start new instance of postgres.

8. Import the data from the old postgres using the *NEW* postgres
installation:

psql -d postgres -U postgres -f /tmp/postgres-8.0.7.dumpall

9. Empty the "Pending" and "PendingData" tables.

cd mb_server/admin
./psql READWRITE
delete from "Pending";
delete from "PendingData";

10. Catch up replication packets and make sure all is well

cd mb-server/admin/replication
./LoadReplicationChanges

11. Re enable cron jobs.

That should be it. Sorry for the inconvenience!

--

--ruaok Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: Upgrade instructions for 20071014 server release

2007-10-16T04:18:19Z

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

nick.

On 15/10/07 00:31, "Robert Kaye" <rob@...> 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@... -- http://mayhem-chaos.net
>
>
>
> _______________________________________________
> Musicbrainz-datafeed mailing list
> Musicbrainz-datafeed@...
> 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.

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Upgrade instructions for 20071014 server release

2007-10-14T17:31:19Z

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@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: Server release post-poned to Oct 14th

2007-10-09T10:50:15Z

On Oct 8, 2007, at 1:30 PM, Ben wrote:

Hey, thanks for holding off! I'm personally looking forward to a smooth upgrade more than new features. :)

Sweet -- thanks for being on the same page as me. :)

--ruaok Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: Server release post-poned to Oct 14th

2007-10-08T14:30:20Z

Hey, thanks for holding off! I'm personally looking forward to a smooth
upgrade more than new features. :)

On Mon, 8 Oct 2007, Robert Kaye wrote:

> After finding a couple of serious issues upon doing a final code review, I've
> decided to post-pone the server release until Oct 14th. I've had to make
> invasive changes that require more testing, so I do not feel comfortable
> doing the update today.
>
> Sorry if you've been looking forward to this release, but I want to ensure
> that things go smooth when we do make the switch. And it also seems that we
> have record traffic right now, so there are too many things telling me to
> wait with the upgrade.
>
> Sorry for the inconvenience!
>
> --
>
> --ruaok Somewhere in Texas a village is *still* missing its idiot.
>
> Robert Kaye -- rob@... -- http://mayhem-chaos.net
>
>
>
> _______________________________________________
> Musicbrainz-datafeed mailing list
> Musicbrainz-datafeed@...
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Server release post-poned to Oct 14th

2007-10-08T14:28:47Z

After finding a couple of serious issues upon doing a final code
review, I've decided to post-pone the server release until Oct 14th.
I've had to make invasive changes that require more testing, so I do
not feel comfortable doing the update today.

Sorry if you've been looking forward to this release, but I want to
ensure that things go smooth when we do make the switch. And it also
seems that we have record traffic right now, so there are too many
things telling me to wait with the upgrade.

Sorry for the inconvenience!

--

--ruaok Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Server update delayed by 24 hours!

2007-10-07T14:34:51Z

Due to a number of loose ends that we still need to tighten up (and
lack of sleep on part of the people doing the work) we're going to
rest, then fix issues and aim to complete the server update tomorrow.

Sorry for the delay!

--

--ruaok Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

IMPORTANT: Schema change server release on October 7th

2007-09-23T15:10:30Z

Hi!

This is your two weeks warning that we're going to update the main
MusicBrainz server on October 7th!

We've just entered the two week final testing phase, where all the
major changes have stabilized. From this point on we will do no
further database schema changes and will only make minor changes to
the release to fix outstanding bugs.

To find out more about this release:

- Blog entry: http://blog.musicbrainz.org/archives/2007/09/
next_server_rel_2.html
- Wiki page: http://wiki.musicbrainz.org/ServerReleaseNotes/200709XX

We will post more details as to how to use the provided scripts to
update your installation of MusicBrainz as we prepare for the release.

Don't hesitate to ask any questions!

--

--ruaok Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: Instructions on how to update your live data feed

2007-04-03T14:55:52Z

On Apr 3, 2007, at 11:53 AM, Nicholas J Humfrey wrote:

> Hi Rob,
>
> I'm afraid I didn't have complete success with your instructions.
> It all went wrong when trying to update the SQL (20061104-1.sql).
>
> I since thought I would go for a fresh install and wiped the
> database, but forgot that there hasn't been a full dump since the
> schema sequence changed. When is the next full dump scheduled for?

Tonight at midnight GMT.

> $ dpkg -l postgresql
> ii postgresql 7.4.7-6sarge4 object-relational SQL database
> management sy

That's the problem -- you should probably upgrade to Postgres 8.0 in
order for the upgrade to work cleanly.

--

--ruaok Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: Instructions on how to update your live data feed

2007-04-03T12:53:26Z

Hi Rob,

I'm afraid I didn't have complete success with your instructions. It
all went wrong when trying to update the SQL (20061104-1.sql).

I since thought I would go for a fresh install and wiped the
database, but forgot that there hasn't been a full dump since the
schema sequence changed. When is the next full dump scheduled for?

nick.

$ dpkg -l postgresql
ii postgresql 7.4.7-6sarge4 object-relational SQL database
management sy

./psql READWRITE < sql/updates/20061104-1.sql

BEGIN
NOTICE: CREATE TABLE will create implicit sequence "label_id_seq"
for "serial" column "label.id"
CREATE TABLE
CREATE TABLE
NOTICE: CREATE TABLE will create implicit sequence
"l_album_label_id_seq" for "serial" column "l_album_label.id"
CREATE TABLE
NOTICE: CREATE TABLE will create implicit sequence
"l_artist_label_id_seq" for "serial" column "l_artist_label.id"
CREATE TABLE
NOTICE: CREATE TABLE will create implicit sequence
"l_label_label_id_seq" for "serial" column "l_label_label.id"
CREATE TABLE
NOTICE: CREATE TABLE will create implicit sequence
"l_label_track_id_seq" for "serial" column "l_label_track.id"
CREATE TABLE
NOTICE: CREATE TABLE will create implicit sequence
"l_label_url_id_seq" for "serial" column "l_label_url.id"
CREATE TABLE
NOTICE: CREATE TABLE will create implicit sequence
"lt_album_label_id_seq" for "serial" column "lt_album_label.id"
CREATE TABLE
NOTICE: CREATE TABLE will create implicit sequence
"lt_artist_label_id_seq" for "serial" column "lt_artist_label.id"
CREATE TABLE
NOTICE: CREATE TABLE will create implicit sequence
"lt_label_label_id_seq" for "serial" column "lt_label_label.id"
CREATE TABLE
NOTICE: CREATE TABLE will create implicit sequence
"lt_label_track_id_seq" for "serial" column "lt_label_track.id"
CREATE TABLE
NOTICE: CREATE TABLE will create implicit sequence
"lt_label_url_id_seq" for "serial" column "lt_label_url.id"
CREATE TABLE
INSERT 282401600 1
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ERROR: adding columns with defaults is not implemented
HINT: Add the column, then use ALTER TABLE SET DEFAULT.

On 2 Apr 2007, at 01:19, Robert Kaye wrote:

> As promised, here are the instructions for upgrading your MB
> installation!
>
> -----
>
>
> 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 #8, but the
> database is currently at #7
> 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_20070401-BRANCH mb_server-20070401
>
> 3. Configure your new codebase and copy new config files:
>
> cd mb_server-20070401/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 following scripts to update the database:
>
> cd admin
> ./psql READWRITE < sql/updates/20061104-1.sql
> ./psql READWRITE < sql/updates/20061104-2.sql
> ./psql READWRITE < sql/updates/20061104-4.sql
>
> NOTE: Make sure you don't accidentally run the -3 script!
>
> 7. Vacuum the database
>
> ./psql READWRITE
> vacuum analyze;
> \q
>
> 8. Test the update by loading more replication changes:
>
> cd replication
> ./LoadReplicationChanges
>
> You should see your database catch up to the latest replication
> sequence.
>
> 9. Turn cron jobs back on.
>
> 10. You're done!
>
> ----
>
> Please let me know if you have any questions!
>
> --
>
> --ruaok Somewhere in Texas a village is *still* missing its
> idiot.
>
> Robert Kaye -- rob@... -- http://mayhem-
> chaos.net
>
>
>
> _______________________________________________
> Musicbrainz-datafeed mailing list
> Musicbrainz-datafeed@...
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Instructions on how to update your live data feed

2007-04-01T18:19:09Z

As promised, here are the instructions for upgrading your MB
installation!

-----

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 #8, but the
database is currently at #7
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_20070401-BRANCH mb_server-20070401

3. Configure your new codebase and copy new config files:

cd mb_server-20070401/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 following scripts to update the database:

cd admin
./psql READWRITE < sql/updates/20061104-1.sql
./psql READWRITE < sql/updates/20061104-2.sql
./psql READWRITE < sql/updates/20061104-4.sql

NOTE: Make sure you don't accidentally run the -3 script!

7. Vacuum the database

./psql READWRITE
vacuum analyze;
\q

8. Test the update by loading more replication changes:

cd replication
./LoadReplicationChanges

You should see your database catch up to the latest replication
sequence.

9. Turn cron jobs back on.

10. You're done!

----

Please let me know if you have any questions!

--

--ruaok Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: IMPORTANT: Schema Change coming April 1st 2007

2007-03-21T00:22:43Z

Kick ass. Thanks!

On Mar 20, 2007, at 10:32 PM, Robert Kaye wrote:

>
> On Mar 20, 2007, at 6:00 PM, Ben wrote:
>
>> Sorry, I don't have a lot of time between now and then to grovel
>> through bug fixes. Is there a consolidated list of schema changes
>> anywhere I can just apply after the 1st? Or will I have to dump my
>> database and reload (ick)?
>
> I will send out detailed instructions on how to update your server
> without having to reload the data.
>
> In essence the steps will be:
> 0. download the latest source from SVN
> 1. stop anything that might access the DB.
> 2. run our update scripts from our new codebase
> 3. switch your config to start the new codebase
> 4. start whatever your stopped in step 1.
>
> Unless we make a major change (possible) step 2 should only take a
> minute or two.
>
> More details to follow probably on March 31st.
>
> --
>
> --ruaok Somewhere in Texas a village is *still* missing its
> idiot.
>
> Robert Kaye -- rob@... -- http://mayhem-
> chaos.net
>
>
>
> _______________________________________________
> Musicbrainz-datafeed mailing list
> Musicbrainz-datafeed@...
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: IMPORTANT: Schema Change coming April 1st 2007

2007-03-20T23:32:01Z

On Mar 20, 2007, at 6:00 PM, Ben wrote:

> Sorry, I don't have a lot of time between now and then to grovel
> through bug fixes. Is there a consolidated list of schema changes
> anywhere I can just apply after the 1st? Or will I have to dump my
> database and reload (ick)?

I will send out detailed instructions on how to update your server
without having to reload the data.

In essence the steps will be:
0. download the latest source from SVN
1. stop anything that might access the DB.
2. run our update scripts from our new codebase
3. switch your config to start the new codebase
4. start whatever your stopped in step 1.

Unless we make a major change (possible) step 2 should only take a
minute or two.

More details to follow probably on March 31st.

--

--ruaok Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

Re: IMPORTANT: Schema Change coming April 1st 2007

2007-03-20T19:00:27Z

Sorry, I don't have a lot of time between now and then to grovel through bug fixes. Is there a consolidated list of schema changes anywhere I can just apply after the 1st? Or will I have to dump my database and reload (ick)?

On Mar 18, 2007, at 11:29 PM, Robert Kaye wrote:

Sorry, no this is not an april fools joke. :-)

We are going to update the main MusicBrainz server on April 1st with support for Labels, Data Quality, Improved Cover Art and lots of bug fixes. For more information on this release, please see the links below.

general announcement:
http://blog.musicbrainz.org/archives/2007/03/next_server_rel.html

list of bugs and tasks closed:
http://bugs.musicbrainz.org/query?status=new&status=assigned&status=reopened&milestone=Server%3A+Labels%2C+Data+quality+and+improved+cover+art

This update will happen sometime between 11am and 2pm PST -- an exact time will be announced closer to the date.

Please let me know if you have any questions!

--

--ruaok Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed

IMPORTANT: Schema Change coming April 1st 2007

2007-03-19T00:29:31Z

Sorry, no this is not an april fools joke. :-)

We are going to update the main MusicBrainz server on April 1st with support for Labels, Data Quality, Improved Cover Art and lots of bug fixes. For more information on this release, please see the links below.

general announcement:

http://blog.musicbrainz.org/archives/2007/03/next_server_rel.html

list of bugs and tasks closed:

http://bugs.musicbrainz.org/query?status=new&status=assigned&status=reopened&milestone=Server%3A+Labels%2C+Data+quality+and+improved+cover+art

This update will happen sometime between 11am and 2pm PST -- an exact time will be announced closer to the date.

Please let me know if you have any questions!

--ruaok Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye -- rob@... -- http://mayhem-chaos.net

_______________________________________________
Musicbrainz-datafeed mailing list
Musicbrainz-datafeed@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-datafeed