# Updated VM available for replication/reindexation test
**URL:** https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477
**Category:** Development
**Tags:** virtualbox, musicbrainz-vm, virtualmachine
**Created:** [July 17, 2018, 11:18am UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477 "2018-07-17T11:18:06Z")
**Posts on this page:** 15
**Page:** 2
### Author:  [@InvisibleMan78](https://community.metabrainz.org/u/InvisibleMan78)
#### Post date: [August 7, 2018, 7:23am UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/21 "2018-08-07T07:23:21Z")
Thank you again for your fixes @yvanzo, especially for the documentation enhancement!
This version looks really good now 👍🎉
Just to be sure:
If I start this VM from time to time and want to manually replicate the changed data when I need it (=no automatic cronjob), I can also execute `bin/update-indexes now` after a manual `bin/replicate now` ?
Should this index update run much faster than the initial (first-time-only) `bin/reindex` ?
> [@yvanzo](#):
>
> Normal start/shutdown should do now.
Do you recommend to stop the VM with
`docker-compose stop && sudo shutdown -h now`
or
`docker-compose down && sudo shutdown -h now`
or only
`sudo shutdown -h now`
_Just for the record:_
_The first replication (28.07.2018 until 07.08.2018) took 46 minutes._
---
### Author:  [@yvanzo](https://community.metabrainz.org/u/yvanzo)
#### Post date: [August 7, 2018, 12:53pm UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/22 "2018-08-07T12:53:02Z")
> [@InvisibleMan78](#):
>
> I can also execute `bin/update-indexes now` after a manual `bin/replicate now` ?
Yes.
> [@InvisibleMan78](#):
>
> Should this index update run much faster than the initial (first-time-only) `bin/reindex` ?
Yes. (It is still necessary to build initial index data at least once after setting replication access token.)
Note: This is the last MBVM to include the old search indexer. Next MBVMs will board the new SOLR-based search server along with prebuilt initial index data (to be tracked as [MBVM-38](https://tickets.metabrainz.org/browse/MBVM-38)).
> [@InvisibleMan78](#):
>
> Do you recommend to stop the VM with […] only
> `sudo shutdown -h now`
Yes (to the latter).
_Edit:_
> [@InvisibleMan78](#):
>
> `docker-compose stop && sudo shutdown -h now`
It is okay to manually _stop_ containers, but I guess you will have to manually _start_ it on next boot.
> [@InvisibleMan78](#):
>
> `docker-compose down && sudo shutdown -h now`
This will remove containers and any change you made, including access token and server name.
---
### Author:  [@InvisibleMan78](https://community.metabrainz.org/u/InvisibleMan78)
#### Post date: [August 8, 2018, 6:45am UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/23 "2018-08-08T06:45:55Z")
@yvanzo
The scripts work well, my access token and the GUI are preserved as expected.
> [@yvanzo](#):
>
> > Should this index update run much faster than the initial (first-time-only) `bin/reindex` ?
>
> Yes. (It is still necessary to build initial index data at least once after setting replication access token.)
Unfortunately, I can’t confirm this speed gain.
It took the same time for `bin/update-indexes now` as for `bin/reindex`. In my environment about 5 hours.
---
### Author:  [@yvanzo](https://community.metabrainz.org/u/yvanzo)
#### Post date: [August 8, 2018, 7:43am UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/24 "2018-08-08T07:43:07Z")
Even for further runs of `bin/update-indexes now`?
---
### Author:  [@InvisibleMan78](https://community.metabrainz.org/u/InvisibleMan78)
#### Post date: [August 8, 2018, 9:49pm UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/25 "2018-08-08T21:49:46Z")
After two more attempts (replication/index update) I have to say:
**No speed gain!**
It seems as `bin/update-indexes now` does exactly the same task as `bin/reindex`.
---
### Author:  [@yvanzo](https://community.metabrainz.org/u/yvanzo)
#### Post date: [August 13, 2018, 2:27pm UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/26 "2018-08-13T14:27:08Z")
Thanks for testing at full scale. 😢 I will revert hourly indexation and publish final VM on tomorrow.
Yet another reason to switch to SOLR-based search server and its indexer for further VM images.
---
### Author:  [@InvisibleMan78](https://community.metabrainz.org/u/InvisibleMan78)
#### Post date: [August 13, 2018, 3:26pm UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/27 "2018-08-13T15:26:18Z")
> [@yvanzo](#):
>
> publish final VM on tomorrow.
With replicated data until tonight? 😇😉👍
---
### Author:  [@yvanzo](https://community.metabrainz.org/u/yvanzo)
#### Post date: [August 14, 2018, 10:12pm UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/28 "2018-08-14T22:12:01Z")
Well, there was no dump last night, it contains latest dump which is 2018-08-11.
> **[Server update, 2018-08-14, with new virtual machine – MetaBrainz Blog](https://blog.musicbrainz.org/2018/08/14/server-update-2018-08-14/)**
[ftp://ftp.eu.metabrainz.org/pub/musicbrainz-vm/musicbrainz-server-2018-08-14.ova.torrent](ftp://ftp.eu.metabrainz.org/pub/musicbrainz-vm/musicbrainz-server-2018-08-14.ova.torrent)
---
### Author:  [@InvisibleMan78](https://community.metabrainz.org/u/InvisibleMan78)
#### Post date: [August 15, 2018, 3:39pm UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/29 "2018-08-15T15:39:12Z")
Thank you for the newest VM @yvanzo
I got his error message
**“Possible EventEmitter memory leak detected. 12 resolve listeners added. Use emitter.setMaxListeners() to increase limit”**
after setting the IP-Address for the newest OVA:
I have no idea what this means and if I have to do something (what?) now.
---
### Author:  [@InvisibleMan78](https://community.metabrainz.org/u/InvisibleMan78)
#### Post date: [August 15, 2018, 4:04pm UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/30 "2018-08-15T16:04:58Z")
There is another warning message
**cannot access ‘/mnt/docker-volumes/volumes/musicbrainzdocker\_indexddata/\_data/’: Permission denied**
after the command `bin/reindex:`
The reindex-process seems to run. We will see in about 5 hours if it works.
---
### Author:  [@yvanzo](https://community.metabrainz.org/u/yvanzo)
#### Post date: [August 15, 2018, 6:25pm UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/31 "2018-08-15T18:25:46Z")
> [@InvisibleMan78](#):
>
> **“Possible EventEmitter memory leak detected. 12 resolve listeners added. Use emitter.setMaxListeners() to increase limit”**
> I have no idea what this means and if I have to do something (what?) now.
Sorry about this spurious message, you can safely ignore this one. I will take a look at the other.
---
### Author:  [@InvisibleMan78](https://community.metabrainz.org/u/InvisibleMan78)
#### Post date: [August 15, 2018, 8:14pm UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/32 "2018-08-15T20:14:14Z")
Not so pretty java.io.FileNotFoundException:
---
### Author:  [@InvisibleMan78](https://community.metabrainz.org/u/InvisibleMan78)
#### Post date: [August 16, 2018, 11:16am UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/33 "2018-08-16T11:16:08Z")
A VM reboot and executing
`sudo bin/reindex`
solved the above java.io.FileNotFoundException and the “Permission denied” errors.
---
### Author:  [@yvanzo](https://community.metabrainz.org/u/yvanzo)
#### Post date: [August 16, 2018, 4:27pm UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/34 "2018-08-16T16:27:28Z")
> [@InvisibleMan78](#):
>
> **cannot access ‘/mnt/docker-volumes/volumes/musicbrainzdocker\_indexddata/\_data/’: Permission denied**
This is a bug in the script `bin/reindex` that can be fixed by running the following command:
```sh
sudo sed -i '/sudo/!s/ls\|rm/sudo &/' bin/reindex
```
_Edit: by the way, running `sudo bin/reindex` is a correct workaround_
_Edit: troubleshooting notes have been added to [doc/MusicBrainz Server/Setup](https://musicbrainz.org/doc/MusicBrainz_Server/Setup)._
---
### Author:  [@Freso](https://community.metabrainz.org/u/Freso)
#### Post date: [October 25, 2018, 10:39am UTC](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477/35 "2018-10-25T10:39:59Z")
2 posts were split to a new topic: [Issue with 2018-08-14 VM](https://community.metabrainz.org/t/issue-with-2018-08-14-vm/402948)
[Previous page](https://community.metabrainz.org/t/updated-vm-available-for-replication-reindexation-test/390477.md?page=1)