How to Resolve SonarQube Server cannot be reached Error?
Pre-requisites:
refer this page for pre-requisites to install SonarQube
Resolution:
Make sure EC2 instance or server where you are installing SonarQube has enough virtual memory and open file limits for Linux OS.
How to change default value for vm.max_map_count temporarily
sudo sysctl vm.max_map_count=262144
sudo sysctl fs.file-max=65536
The above command will load the max_map_count values and open file limits till the next system restart.
How to update vm.max_map_count directly in sysctl.conf permanently
Login to instance where you will be installing SonarQube, perform the below command to configure virtual memory permanently for SonarQube to function:
sudo vi /etc/sysctl.conf
Add the following lines to the bottom of that file:
vm.max_map_count=262144
fs.file-max=65536
To make sure changes are getting into effect:
sudo sysctl -p
Make sure SonarQube is up and running by checking the logs
sudo docker-compose logs --follow
Once you see the message, that's it. SonarQube have been configured successfully. press control C and enter.
Watch Steps in YouTube channel:
No comments:
Post a Comment