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-local-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屋！