SQ Upgrade 6.7 - 7.9 after 2 hrs got IllegalArgumentException: Unable to create shared memory

I am performing an upgrade from 6.7 community Ed to 7.9 Community Ed, When I upgrading the db ( https://myserver/setup) after 2 hrs I am getting the following error message, then the UI shows (SonarQube is Offline).

Any ideas?
My server params:
vm.max_map_count = 262144

sonarqube_app.1.kclfnjapm5r1@my_server    | 2020.04.30 15:11:14 INFO  web[][o.s.s.p.d.m.s.MassUpdate] 1212409 files processed (3495 items/sec)
sonarqube_app.1.kclfnjapm5r1@my_server    | 2020.04.30 15:12:11 WARN  web[][o.s.p.ProcessEntryPoint] Fail to start web
sonarqube_app.1.kclfnjapm5r1@my_server    | java.lang.IllegalArgumentException: Unable to create shared memory : 
sonarqube_app.1.kclfnjapm5r1@my_server    | 	at org.sonar.process.sharedmemoryfile.AllProcessesCommands.<init>(AllProcessesCommands.java:103)
sonarqube_app.1.kclfnjapm5r1@my_server    | 	at org.sonar.process.sharedmemoryfile.DefaultProcessCommands.<init>(DefaultProcessCommands.java:34)
sonarqube_app.1.kclfnjapm5r1@my_server    | 	at org.sonar.process.sharedmemoryfile.DefaultProcessCommands.secondary(DefaultProcessCommands.java:52)
sonarqube_app.1.kclfnjapm5r1@my_server    | 	at org.sonar.server.app.WebServer.isOperational(WebServer.java:69)
sonarqube_app.1.kclfnjapm5r1@my_server    | 	at org.sonar.server.app.WebServer.getStatus(WebServer.java:61)
sonarqube_app.1.kclfnjapm5r1@my_server    | 	at org.sonar.process.ProcessEntryPoint.waitForStatus(ProcessEntryPoint.java:121)
sonarqube_app.1.kclfnjapm5r1@my_server    | 	at org.sonar.process.ProcessEntryPoint.launch(ProcessEntryPoint.java:104)
sonarqube_app.1.kclfnjapm5r1@my_server    | 	at org.sonar.process.ProcessEntryPoint.launch(ProcessEntryPoint.java:81)
sonarqube_app.1.kclfnjapm5r1@my_server    | 	at org.sonar.server.app.WebServer.main(WebServer.java:99)
sonarqube_app.1.kclfnjapm5r1@my_server    | Caused by: java.io.FileNotFoundException: /opt/sonarqube/temp/sharedmemory (Too many open files in system)

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
  • what are you trying to achieve
  • what have you tried so far to achieve this


To be clear, during the DB upgrade process, you get this?

Off-hand it looks like you’re somehow exceeding the number of open file handles your OS is configured to allow. Some OS spelunking to verify what process(es) hold these open file handles might be helpful. Additionally, you can probably tune the number of allowed open files & try again. The DB upgrade should be fully re-entrant.


Yes, it was during DB upgrade process. htts://server/setup . thank for your support, I will try to tune the number of allowed files.