SonarQube elastic search indices not writable or lock found in docker container

SonarQube Troubleshooting Steps

1. Check Docker Status:

Run docker ps -a to see the status of your Docker containers. Look for the SonarQube container and note its container ID.

docker ps -a
2. Restart Stopped Container:

If the SonarQube container is in a stopped state, try restarting it.

docker restart <container_id>
3. If Restart Fails: If restarting the container fails to resolve the issue, proceed with the following steps.
4. Stop and Start SonarQube Container:

   Navigate to the directory where your docker-compose.yml file is located (the SonarQube folder within the Docker Compose folder), then run:

   docker-compose down
docker-compose up -d
5. Check Logs:

   After restarting the container, check the logs for any errors related to Elasticsearch indices.

   docker logs <container_id>
6. Backup and Remove Elasticsearch Data:

   If you encounter errors related to Elasticsearch indices not writable or lock found, back up the current "es7" folder in the SonarQube data directory and then remove it.

   # Navigate to the directory where SonarQube data is stored
cd /path/to/sonarqube/data/directory

# Create a backup of the es7 folder
cp -r es7 es7_backup

# Remove the es7 folder
rm -rf es7
7. Restart Docker Compose:

   Once you've backed up and removed the Elasticsearch data, restart Docker Compose.

   docker-compose down
docker-compose up -d

After following these steps, monitor the logs to ensure that the SonarQube container starts up without any errors related to Elasticsearch indices. If you continue to encounter issues, you may need to delve deeper into the specific error messages and consult SonarQube's documentation or community forums for further assistance.