- InitDb.pl failed on macOS
- Resolving name failed
- Loadable library and perl binaries are mismatched
- ImportError: No module named
- Unknown error executing apt-key
- amqp.exceptions.AccessRefused
When creating the database:
Wed Feb 24 14:29:01 2021 : Creating indexes ... (CreateIndexes.sql)
Wed Feb 24 14:29:12 2021 : psql:/musicbrainz-server/admin/sql/CreateIndexes.sql:467: server closed the connection unexpectedly
Wed Feb 24 14:29:12 2021 : This probably means the server terminated abnormally
Wed Feb 24 14:29:12 2021 : before or while processing the request.
Wed Feb 24 14:29:12 2021 : psql:/musicbrainz-server/admin/sql/CreateIndexes.sql:467: fatal: connection to server was lost
Error during CreateIndexes.sql at /musicbrainz-server/admin/InitDb.pl line 117.
Wed Feb 24 14:29:12 2021 : InitDb.pl failed
Solution:
Add more than 2GB memory to containers on macOS.
When building Docker images:
Err:1 http://security.debian.org/debian-security buster/updates InRelease
Temporary failure resolving 'security.debian.org'
Solution:
That can be your bridge nework has no default gateway yet.
That can be checked by running:
docker network inspect bridgeIn such case, try restarting docker daemon:
sudo service docker restartUsing MusicBrainz server’s development setup only,
when musicbrainz service doesn’t work as expected,
and after retrieving its logs as follows:
docker compose logs --timestamps musicbrainzreturned logs contain the following error message:
ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xdb00080, needed 0xcd00080)
That means the Perl dependencies have been installed with another
version of Perl. It happens after the required version of Perl for
MusicBrainz Server has changed, mostly when switching from/to
different branches or versions of musicbrainz-server.
Solution:
Remove installed Perl dependencies and restart musicbrainz service;
It will automatically reinstall them all using current Perl version:
sudo rm -fr "$MUSICBRAINZ_SERVER_LOCAL_ROOT/perl_modules/
docker compose restart musicbrainzUsing Search Index Rebuilder’s development setup only,
when indexer service doesn’t work as expected,
and python commands return the following:
Traceback (most recent call last):
[...]
ImportError: No module named [...]
(where the latest [...] may be sqlalchemy or any other dependency)
Solution:
Remove all installed Python packages and installation cache as follows:
docker compose exec indexer rm -fr /code/.cache /code/venv-musicbrainz-docker
docker compose restart indexerPython packages are downloaded again and installed again when the
service indexer restarts.
When building Docker image for the service musicbrainz:
Err:1 https://deb.nodesource.com/node_20.x nodistro InRelease
Unknown error executing apt-key
[...]
W: GPG error: https://deb.nodesource.com/node_20.x nodistro InRelease: Unknown error executing apt-key
E: The repository 'https://deb.nodesource.com/node_20.x nodistro InRelease' is not signed.
This may happen if your system is hindering file permissions.
You can find out by adding RUN ls -l file commands in the
Dockerfile.
Solution:
Configure your system to keep the file permissions defined in the Git repository and to preserve the permissions of the files copied through Docker.
If it isn’t possible, for example with the Unraid operating system,
run additional chmod commands in the Dockerfile; See comments to the
issue #263.
When running sir amqp_setup to prepare live indexing:
amqp.exceptions.AccessRefused: (0, 0): (403) ACCESS_REFUSED - Login was refused using authentication mechanism AMQPLAIN. For details see the broker logfile.
The service mq is sometimes not creating the user sir as expected.
Solution:
Recreate the container mq as follows:
docker compose up --force-recreate -d mqCheck if it started with creating the user sir:
docker compose logs -t mq | grep 'Creating user .sir.'If it doesn’t mention creating user sir, try recreating mq again.