[SOLVED] SonarQube Max virtual memory areas vm max_map_count 65530 is too low, increase to at least [262144]

[SOLVED] SonarQube Max virtual memory areas vm max_map_count 65530 is too low, increase to at least [262144]
Photo by Stefan Widua on Unsplash
Share this post and Earn Free Points!

SonarQube" is the tool which allows developers to keep the clean code in their repositories. [ SonarQube" Max virtual memory areas vm max_map_count 65530 ] It do automatic check every time when new code is pushed to the repository. If you haven’t started using this tool yet, then start! It will pay you back in the future.

[SOLVED] SonarQube Max virtual memory areas vm max_map_count 65530 is too low, increase to at least [262144]


This error message indicates that the maximum number of virtual memory areas (vm.max_map_count) allowed by your system is too low for SonarQube" to run properly. SonarQube" requires a minimum value of 262144 for this setting, but the current value on your system is 65530.

Max Virtual Memory

The maximum virtual memory (also known as virtual address space) refers to the maximum amount of memory that a process can access on a computer. Virtual memory is used to supplement the physical memory (RAM) on a computer, allowing a process to access more memory than is physically available.

Virtual memory is implemented using a combination of physical memory and space on the hard drive, which is used as an “overflow” area for data that does not fit in physical memory. When a process accesses data that is stored in virtual memory, it is temporarily moved from the hard drive to physical memory, allowing the process to access it more quickly.

The maximum virtual memory is limited by the operating system and the hardware of the computer. On most systems, the maximum virtual memory is equal to the total amount of physical memory plus the size of the hard drive.

If a process tries to access more virtual memory than is allowed by the maximum virtual memory setting, it will typically result in an “out of memory” error. This can occur if the process is trying to use more memory than is physically available on the system, or if the maximum virtual memory setting is set too low. In such cases, you may need to increase the maximum virtual memory setting or optimize the process to use less memory.

Problem -> SonarQube Max virtual memory areas vm max_map_count 65530

The system isn’t allowed to get the requested virtual memory amount.

In computing, virtual memory, or virtual storage[b] is a memory management technique that provides an “idealized abstraction of the storage resources that are actually available on a given machine”[3"] which “creates the illusion to users of a very large (main) memory”



To fix this issue, you can increase the value of vm.max_map_count by following these steps:

  1. Open" a terminal and enter the following command to view the current value of vm.max_map_count: sysctl vm.max_map_count
  2. If the current value is lower than 262144, you can increase it by running the following command: sysctl -w vm.max_map_count=262144
  3. To make the change permanent, you will need to edit the sysctl.conf file. On most systems, this file is located at /etc/sysctl.conf. Open" the file using a text editor, such as nano or vim, and add the following line at the end: vm.max_map_count=262144
  4. Save the changes to the sysctl.conf file and exit the text editor.
  5. Reload the sysctl configuration by running the following command: sysctl -p

After making these changes, you should be able to start SonarQube" without encountering the “vm.max_map_count” error.

Keep in mind that you may need to restart your system or log out and log back in for the changes to take effect.

Run the following command before attempting to start Sonar or issuing your docker-compose command:

# Set vm.max_map_count=262144

sudo sysctl -w vm.max_map_count=262144

SonarQube Documentation

A self-managed, automated code review tool called SonarQube" systematically aids in the production of Clean Code. SonarQube", a key component of our Sonar product, works with your current workflow to spot errors in your code and aids in your ongoing code inspection of your projects. To make sure your code complies with high standards, the tool analyzes 30+ different programming languages and interfaces with your CI pipeline and DevOps" platform.

Writing Clean Code

A healthy codebase must be maintained by writing Clean Code. We refer to code that adheres to a stated standard as “Clean Code,” which includes being dependable, secure, manageable, legible, and modular in addition to other crucial characteristics. This is true for all types of code, including scripts, Infrastructure as Code, glue code, and source code.

Many of the difficulties that result from evaluating code at a late stage in the development process are eliminated by Sonar’s Clean as You Code methodology.

The Clean as You Code methodology leverages your Quality Gate to notify you when there is New Code (code that has been added or altered) that needs to be fixed or reviewed, allowing you to maintain high standards and concentrate on code quality.

SonarQube" notifies your team that there are problems to fix using its UI, emails, and decorations on pull or merge requests (in commercial versions). When operating in Connected Mode, SonarLint may also provide feedback in IDEs that it supports.

For developers of all levels of expertise, SonarQube" also offers in-depth help on the issues, explaining why each issue is a problem and how to remedy it. Code is only promoted when it passes the Quality Gate and is clean, so that developers may resolve problems in an efficient manner.

Could You Please Share This Post? 
I appreciate It And Thank YOU! :)
Have A Nice Day!

How useful was this post?

Click on a star to rate it!

Average rating 4.8 / 5. Vote count: 1385

No votes so far! Be the first to rate this post.

As you found this post useful...

Follow us on social media!

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?