SonarQube进程已退出，退出值为[es]：137 [英] SonarQube Process exited with exit value [es]: 137
问题描述
我想在我的vps（Linux x86_64 debian 9）上安装声纳，但是当我执行此cdm：./ sonar.sh控制台时，我有以下日志：
I want to install sonar on my vps (linux x86_64 debian 9) but when i exec this cdm : ./sonar.sh console i have this following log :
Running SonarQube...
wrapper | --> Wrapper Started as Console wrapper | Launching a JVM...
jvm 1 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
jvm 1 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
jvm 1 |
jvm 1 | 2017.12.14 18:45:28 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /etc/sonarqube/temp
jvm 1 | 2017.12.14 18:45:28 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
jvm 1 | 2017.12.14 18:45:29 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/etc/sonarqube/elasticsearch]: /etc/sonarqube/elasticsearch/bin/elasticsearch -Epath.conf=/etc/sonarqube/temp/conf/es
jvm 1 | 2017.12.14 18:45:29 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
jvm 1 | 2017.12.14 18:45:29 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 137
jvm 1 | 2017.12.14 18:45:29 INFO app[][o.s.a.SchedulerImpl] Process [es] is stopped
jvm 1 | 2017.12.14 18:45:29 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
jvm 1 | 2017.12.14 18:45:29 INFO app[][o.e.p.PluginsService] no modules loaded
jvm 1 | 2017.12.14 18:45:29 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
jvm 1 | 2017.12.14 18:45:30 WARN app[][i.n.u.i.MacAddressUtil] Failed to find a usable hardware address from the network interfaces; using random bytes: 05:2b:7f:2f:de:90:ca:4a
wrapper | <-- Wrapper Stopped
为什么立即关闭服务器？我搜索了[es]：137，但没有找到任何东西：（
An idea why the server is shut down immediately? I searched for [es]: 137 but I found nothing :(
推荐答案
这是内存问题。我们遇到了这类问题当我们将Sonar容器作为容器运行时，我们尝试将Sonar容器的最大可用内存限制在2GB或RAM以下。
it is memory problem. We experienced that kind of problems when we run Sonar as container and we try to limit maximum memory available for Sonar container below 2GB or RAM.
Sonar在Elasticsearch的引擎盖下运行，这需要大量内存因此，在这种情况下，我建议为Sonar分配更多的2GB。
The Sonar runs under the hood Elasticsearch which requires a lot of memory so in this case I suggest to assign more that 2GB for Sonar.
您还可以尝试通过ES_JAVA_OPTS将内存限制为2GB以下（如果您的内存服务器有限），但是当我尝试过使用该选项，但Sonar成功启动，但过了一段时间，又出现了一些交通问题，并且集装箱停了下来。
You could also try to limit memory by ES_JAVA_OPTS below 2GB (if you have limited memory server) but when I've tried to play with this option Sonar started sucessfully but after some time and with some traffic problem returns and container stopped.
因此，上面提到的机票上的描述这是正确的内存问题： https://github.com/10up/wp-因此，II认为在这种情况下，最简单的方法是处理docker / issues / 6
So the desciption on the ticket mentioned above that this is memory issue is correct: https://github.com/10up/wp-local-docker/issues/6
问题-只需增加Sonar服务器（容器）的内存即可。
So I I think in this situation the easiest way to deal with the problem - just increase the memory for your Sonar server (container).
这篇关于SonarQube进程已退出，退出值为[es]：137的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
