History:MusicBrainz Server Virtual Machine
|Status: This Page is Glorious History!
If you're looking to run MusicBrainz server, we suggest you use the Docker-based option.
Running a MusicBrainz Server as a virtual machine requires some Linux knowledge, but it is vastly simpler than installing the server from scratch. (Have a look at the open issues in the bug tracker, though.) The pre-built virtual image can be imported into either VirtualBox or VMware. If you are using Amazon EC2 you can not use this virtual image and will instead have to follow the steps outlined in the source code INSTALL.md. To set up a virtual machine instance, download the torrent file and follow these steps:
Running with VMware
We no longer support running our VM under VMWare, since VirtualBox has become stable enough for our needs. If you intend to run this with other VM software, we doubt it will work and we're not going to support other software.
Running with VirtualBox
Before you start, make sure you have the lastest version of VirtualBox installed.
- Start VirtualBox and choose Import Appliance from the File menu. Select the downloaded file.
- Once VirtualBox has imported the appliance, select the imported virtual machine from the list of virtual machines and click on Start.
/home/vagrant/binis missing, fix your VirtualBox setup or upgrade your Ubuntu system from 16.04 (Xenial) to 18.04 (Bionic).
Using the VM
- Once the instance has started up, log in on the console using the username vagrant and password vagrant. This account has sudo privileges -- if you would like to set a root password, you can do that via sudo.
- You can SSH into the machine via the port 2222 on localhost of the host OS. (e.g. ssh -p 2222 vagrant@localhost )
- To access the MusicBrainz web site and web service, go to: http://localhost:5000
- To access the Search Server web service, go to: http://localhost:8080
Resetting Docker Containers
This new VM is based on docker containers. The docker containers should start automagically at boot time, but sometimes they don't. If any of the commands listed below do not work or give you strange docker/container errors, reset the containers with this command from the VM:
Then try your command again.
Tuning your VM
We recommend that you give your VM 4GB of ram and 2 CPU cores, if that is possible. The more RAM you give to the VM, the faster it is going to run. To change the memory settings, you will need to shut down the VM, change the settings and then re-start the VM.
This VM comes "replication ready". To enable replication, and have the database catch up with the latest replication packets, you will need to sign up for a Live Data Feed access token on the MetaBrainz web site. Then SSH into the machine as described above then:
bin/set-token <replication token>
To start replication, do this:
This will load all of the changes to the database since the VM update. Unlike the previous versions of this VM, this command will not give you any output as it applies replication packets. If you want to see the progress, open another terminal window to the VM and then:
This will allow you to see the output of the replication packets being applied.
To turn on background replication, run:
to turn it off:
We recommend leaving replication off for the time being, until you've built search indexes for the VM.
Building search indexes
The VM comes with support to build search indexes. In order to build the indexes, log in to the account and then:
Depending on your machine, this may take quite a long time. We recommend that you leave this running overnight. After the indexes are complete, you should be able to carry out indexed searches in your VM.
sudo sed -i '/sudo/!s/ls\|rm/sudo &/' bin/reindex
Accessing the database
To access the main postgres database from the outside, first run once (from the VM):
bin/turn-port db on
dbcontainer after running
turn-portby running (from the VM):
docker-compose -f ~/musicbrainz/musicbrainz-docker/docker-compose.yml up -d db
then you can do this (from the host):
psql -h localhost -U musicbrainz -p 15432
You'll need to install the psql postgres command line client on your host OS.
By default, the password for the user musicbrainz is
musicbrainz, as specified in the doc “Installing MusicBrainz Server”.
Accessing from a remote host
To access the MusicBrainz web site and web service from a remote host, run once (from the VM):
where something.that.works can be an IP address, or a host name, or a fully qualified domain name.
Then go to: http://something.that.works:5000
(node:80) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 resolve listeners added. Use emitter.setMaxListeners() to increase limit
Turning the VM into development box
If you need neither replication nor search, you may prefer to use the lighter virtual machine that contains sample data only.
If you would like to use the VM to do development instead of using it as a simple database slave, you'll need to edit lib/DBDefs.pm and set REPLICATION_TYPE to RT_STANDALONE and run admin/psql READWRITE and execute the following queries:
DELETE FROM annotation WHERE editor > (SELECT max(id) FROM editor); DELETE FROM release_annotation WHERE NOT EXISTS (SELECT 1 FROM annotation WHERE annotation.id = release_annotation.annotation);
then from the command line execute:
admin/psql READWRITE < admin/sql/CreateFKConstraints.sql admin/psql READWRITE < admin/sql/CreateFunctions.sql
Migrating the MusicBrainz Server from a Virtual Machine to a Physical Machine
Taken from AskUbuntu.
It is possible to migrate the MusicBrainz Server image (or any virtual image) from a virtual machine onto bare metal, should you desire to.
- A LiveCD or LiveUSB (this walkthrough will assume you are using a Ubuntu variant as that is what the image is based on.) If you are using an image from 2013-08-01 or earlier, you must have a Ubuntu 12.04.1 Live media.
- USB media large enough to store the raw disk image for writing on a new computer.
Step 1: Converting the Disk to a Raw format
This step is included mostly for the sake of convenience. By doing some prep work on the image before writing, standard Linux tools can be used to write to and manipulate the disk afterwards. This can be done from your current host environment without booting to your LiveCD.
- Load a terminal
cd /path/to/image/ # for VMWare sudo apt-get install qemu-kvm qemu-img convert your-vmware-disk.vmdk -O raw disk.img # For VirtualBox VBoxManage internalcommands converttoraw your-virtualbox-disk.vdi disk.img
disk.imgto somewhere that you're not about to write to. If your target is another physical machine, then an external medium is probably the most convenient way to move the image. These instructions assume that you have moved it to
/media/external/disk.img. Adjust accordingly.
- Before you do anything permanent, make sure you do backups. These instructions will erase anything on the target disk or partition. It's better to be safe than sorry.
Option 1: Write the Image to it's Own Disk
This assumes that you're going to overwrite an entire disk. This is the most ideal situation since the server will have an entire disk to work with. If you're looking to have the image installed along side an existing operating system, skip to Option 2.
- Boot into your LiveCD and Click Try Ubuntu.
- Mount the volume where
disk.imgresides to somewhere safe (like /media/external).
- Determine which volume is your target using a command like
- Then we copy the contents of the image to the drive Replace
sdXwith the correct destination disk. The password for
sudo dd if=/media/external/disk.img of=/dev/sdX
- After this has finished, you can use
gpartedor another utility to manipulate the partition table to the desired layout. It is recommended to have a sizeable swap partition (see this article for some recommendations on how big it should be) as well as expand the root partition to use all remaining available space on the disk. If you desire a seperate boot partition for the system as well, set aside some space here. (Steps for this can be found in the Ubuntu community documentation)
- If you are using an image from 2013-08-01 or earlier, please see here.
Option 2: Installing the Image Alongside Another OS
This is potentially safer than the above method and is very similar. Your LiveCD must be the same Ubuntu version as the virtual image.
- Boot into the LiveCD and click Install Ubuntu.
- Follow the installer prompts, repartition things as you see fit. When the installer finishes, it will ask you to reboot. Do not reboot. You must be in the Live environment for the next instructions.
- Mount your new Ubuntu install (target) and your external disk where you stored
sudo mkdir /media/oldinstall sudo mount -o loop /media/external/disk.img /media/oldinstall
- From there you can either cherry pick files or copy over everything on top of your target. For example, using
sudo rsync /media/oldinstall /media/newinstall
- Reboot and you should be greeted by your virtual machine, but on bare metal. If you have GRUB errors, see this article from the Ubuntu community documentation
Changing Kernel Versions
Parts taken from the Ubuntu community documentation.
For images from 2013-08-01 and older, you will need to change the kernel flavour from -virtual to -generic. The -virtual kernel flavour is lighter, but only supports hardware typically seen in virtual environments while -generic provides support for a wider range of hardware, such as what you would see in a physical server. Both of these versions are provided in the default Ubuntu repositories.
- Boot into your LiveCD. Click "Try Ubuntu"
- Open a terminal.
- Determine which disk is yours using a command like
- Mount your root partition. X is the drive letter and Y is the partition number:
sudo mount /dev/sdXY /mnt
- If you have a seperate boot partition, mount it as well (Z is the boot partition number):
sudo mount /dev/sdXZ /mnt/boot
- Mount the virtual filesystems using the following single command:
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
- Chroot into your installation
sudo chroot /mnt
- Install the latest -generic image and headers by installing the metapackage. This will regenerate GRUB's configuration.
sudo apt-get install linux-image-generic linux-header-generic
- Purge the -virtual image and headers. This should also regenerate GRUB's configuration:
sudo apt-get purge --auto-remove linux-image-virtual linux-header-virtual
- Check for leftover -virtual images in
/boot. If you find any, remove them and then run
- Reboot into your installation.