I made it by opening an SSH console with PuTTY to the IP of the MB virtual machine on Port 22 (in my bridged environment actually 192.168.1.33). Then I entered: bin/set-web-server-name 192.168.1.33
without :5000 as port (the attempt with 192.168.1.33:5000 didn’t work)
The GUI appears nice and colored.
.
Then I entered bin/set-token myOfficialMB40characterReplicationToken
and bin/replicate now
everything works fine
.
The last step is now running for several hours: bin/reindex
I will let you know if the second and the following replication attempts will work without a disk space problem in a few days.
Today I tried to start my second replication attempt.
Unfortunately this doesn’t work with the following error:
Thu Aug 2 08:04:07 UTC 2018 : LoadReplicationChanges failed (rc=25) - see /musicbrainz-server/slave.log
Thu Aug 2 08:04:07 UTC 2018: Replication has been run successfully
vagrant@musicbrainz:~$ bin/tail-replication-log
Invalid or missing REPLICATION_ACCESS_TOKEN in DBDefs.pm -- get one at https://metabrainz.org at ./admin/replication/LoadReplicationChanges line 116.
No big thing just re-run bin/set-tokenmyOfficialMB40characterReplicationToken
I don’t know which of my commands to start and stop the VM let my token get lost.
And just to be sure:
There is no other way to only reindex the new replicated data?
We have to reindex always the complete set of existing data (delete the index data completely and then rebuild it)?
I ask because this reindex-job takes at least 5 hours even with 8GB RAM, 8 Cores and running on a SSD.
Fixed potential access token loss due to helper scripts reindex and turn-port;
Added helper script update-indexes to be automatically called after hourly replication;
Improved documentation.
Your token get lost when musicbrainz container is recreated. It may incidentally happen with docker-compose up. This command was called in scripts reindex and turn-port. That is most probably the reason CSS was gone after your successful reindex run. These scripts have been fixed to use option --no-recreate which prevents this issue.
reindex is usually not required at all, but it is the same as initial build of index data which is required and takes a very long time. Further updates of search indexes will be made upon existing index data. Helper script update-indexes has been added for this purpose. By default, it is automatically called at the end of replication cronjob.
Docker containers were not started on VM boot, it required to enter any docker command, such as docker ps, to start docker daemon. It has been fixed so as to start docker daemon (and containers) on VM boot. Normal start/shutdown should do now.
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 ?
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.
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).
Yes (to the latter).
Edit:
It is okay to manually stop containers, but I guess you will have to manually start it on next boot.
This will remove containers and any change you made, including access token and server name.
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:
There is another warning message cannot access ‘/mnt/docker-volumes/volumes/musicbrainzdocker_indexddata/_data/’: Permission denied
after the command bin/reindex: