New MusicBrainz server virtual machine available

Time to check the weather forecast for hell, because it appears to have frozen over! We have finally released a new Virtual Machine that contains all of the MusicBrainz server software and fixed all of the currently outstanding bugs (for the VM).

The new VM now uses a 64-bit architecture and has 80GB of disk-space so it should be much easier to get along with. I tried to ship one VM that has the search indexes build in, but after 3 hours (and increasing time) of trying to export that VM I killed it. If someone has better luck exporting a VM after building search indexes, please let me know. Also, VirtualBox seems to have improved in stability on Mac OS, so we are not going to build a VMWare version of the VM at this time.

All the details for the new VM are on our Server Setup page.

Remember to get your Live Data Feed access token here if you plan to use the replication.

14 thoughts on “New MusicBrainz server virtual machine available

  1. Jesse

    Awesome news, I was having trouble with the last update. Unfortunately I only have Hyper-V available, I managed to get the image converted last time but have no idea how I did it, if anyone has a suggestion that works, please let me know!

  2. Distractedriver

    Thanks for putting out a new VM release! In my attempt to run the replication job, I’m constantly running into a problem with Replication packet #88525. It’s stating that it’s not available. Is this expected, or should I expect to see the “/bin/replicate now” job complete gracefully? Thanks!

  3. mwiencek

    @Distractedriver Sounds like it’s up-to-date. I see a packet #88525 is published now, so if you try again it should get it (and then stop after the last available packet again).

  4. Distractedriver

    Thanks for your prompt reply. I ran it again earlier today and it got up to packet #88527 or thereabouts (can’t confirm exactly the packet number as I’m running the indexing job). I just wanted to be sure of what to expect; a sudden message of “packet not found,” or if it would gracefully exit with a message along the lines of “Complete.” From the sounds of it, it’s expected to complete with the “packet not found” message and shouldn’t cause alarm.

    Best Regards

  5. Pingback: Wie importiert man die MusicBrainz OVA Virtual Machine in VMWare Workstation? | ict know-how

  6. smoralis

    Thanks , Working great!!
    Could you post details how to update the vm to the latest github master version.

  7. Stefan

    I found nice snippet for saving replication status to a temp log file, which made monitoring the 24hr+ process over ssh much easier.

    “`replicateLog=”/tmp/replicate_`date +%m%d%Y_%H%M%S`.log”
    bin/replicate now >> $replicateLog 2>&1 > $indexLog 2>&1 < /dev/null & “`

    Now a question, After I've brought everything up to date, cant seem to get the VM to respond on :8080 as suggested in https://musicbrainz.org/doc/MusicBrainz_Server/Setup#Using_the_VM
    – is that out of date?

  8. ruaok Post author

    Stefan:

    That should work. Check to see if the search server answers on port 80 on the guest machine. Port 8080 from the outside gets forwarded to 80 on the inside.

  9. Pingback: August Community Revisit | MusicBrainz Blog

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s