MusicBrainz slave server with search and replication


I’m testing MusicBrainz slave server with search and replication on a vm as described at (

On the step:
docker-compose exec indexer python -m sir amqp_setup
2020-04-15 18:54:01,619: Connecting to RabbitMQ
Traceback (most recent call last):
File “/usr/local/lib/python2.7/”, line 174, in _run_module_as_main
main”, fname, loader, pkg_name)
File “/usr/local/lib/python2.7/”, line 72, in _run_code
exec code in run_globals
File “/code/sir/”, line 127, in
File “/code/sir/”, line 123, in main
File “sir/amqp/”, line 22, in setup_rabbitmq
conn = util.create_amqp_connection()
File “sir/”, line 138, in create_amqp_connection
File “/usr/local/lib/python2.7/site-packages/amqp/”, line 180, in init
(10, 30), # tune
File “/usr/local/lib/python2.7/site-packages/amqp/”, line 67, in wait
self.channel_id, allowed_methods, timeout)
File “/usr/local/lib/python2.7/site-packages/amqp/”, line 241, in _wait_method
channel, method_sig, args, content = read_timeout(timeout)
File “/usr/local/lib/python2.7/site-packages/amqp/”, line 330, in read_timeout
return self.method_reader.read_method()
File “/usr/local/lib/python2.7/site-packages/amqp/”, line 189, in read_method
raise m
socket.error: [Errno 104] Connection reset by peer

Seems rabbitmq is not running. Already tried to run it manually but got this error anyway.

Some lights?



Docker Compose mq service running RabbitMQ must be up to set up AMQP.

Make sure all services are up before enabling live indexing:

docker-compose up -d
docker-compose ps
1 Like

Hello @yvanzo

mq service is running:
musicbrainz-docker_mq_1 / Up 15671/tcp, 15672/tcp, 25672/tcp, 4369/tcp, 5671/tcp, 5672/tcp

but all those ports are closed,


How do you test these ports? They are not published to the host by default. They should be accessible from other services of this compose project only.

Try to refresh the image and the container for the service mq:

docker-compose rm --stop mq
docker-compose build --no-cache --pull mq
docker-compose up -d

Otherwise the bug might come from your Docker host. Here are similar issues:

1 Like

Hi @yvanzo, I thought ports would be open for the host.
The refresh of the image you suggested didn’t work.
I switched from docker engine I was running from 19.03.8 to 18.09.9 and was finally able to successfully run
docker-compose exec indexer python -m sir amqp_setup

So it seems it was a problem with new docker version.

1 Like

I’m glad your problem is resolved, but there was likely another cause as I’m using Docker 19.03.8 too.