Thanks for the reply.
Initially there was storage issue and then i extended to 100GB.
Is there any command where I can execute MusicBrainz search server.
I finally executed search server which was present under docker images so ran but i still couldn’t able to search at localhost:8080 , where im missing and I have also changed config under DBDefs.pm file.
The search server could not fulfill your request due to an internal error. This is usually only temporary, so please retry your search again later.
Below is the error information. If you wish to file a bug report, you may do so at our bug tracker. The information below will help, so please be sure to include it!
Can’t connect to localhost:80 (Connection refused)
This container was supposed to be created and started using sudo docker-compose up -d. Your container is named codescending_hertz instead of musicbrainzdocker_search_1. It is likely it didn’t build correctly. Please try rebuilding it as follows:
Assuming search indexes have been built correctly, run sudo docker-compose up -d
To check search actually started, run sudo docker-compose ps
To check search actually works, visit http://localhost/ws/2/artist?query=artist:queen
(Please note that the port 8080 is not exposed directly to your host, it is exposed to other linked containers, thus it is not possible to check by visiting localhost:8080 directly from your host.)
If that failed again, it should not, please read/show the output of sudo docker-compose -t logs musicbrainz search.
Ok, so XML WS/2 works fine, JSON WS/2 probably too, and your search indexes and containers are up.
It looks like a potential bug or configuration issue in MusicBrainz Server to me. Maybe more info can be found in the output of sudo docker-compose -t logs musicbrainz