總結遇到的elasticsearch啟動失敗的幾種情況及解決

阿新 • • 發佈：2018-06-03

elasticsearch

1、使用root用戶啟動失敗

在有一次搭建elasticsearch的時候，使用systemctl啟動elasticsearch失敗，然後在bin目錄下面去使用啟動腳本啟動，發現報錯不能用root用戶啟動，報“Caused by: java.lang.RuntimeException: can not run elasticsearch as root”：

[root@localhost bin]# ./elasticsearch
[2017-12-20T17:01:47,922][WARN ][o.e.b.ElasticsearchUncaughtExceptionHandler] [node-1] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: java.lang.RuntimeException: can not run elasticsearch as root
    at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:125) ~[elasticsearch-6.1.1.jar:6.1.1]
    at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:112) ~[elasticsearch-6.1.1.jar:6.1.1]
    at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-6.1.1.jar:6.1.1]
    at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) ~[elasticsearch-cli-6.1.1.jar:6.1.1]
    at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-6.1.1.jar:6.1.1]
    at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) ~[elasticsearch-6.1.1.jar:6.1.1]
    at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:85) ~[elasticsearch-6.1.1.jar:6.1.1]
Caused by: java.lang.RuntimeException: can not run elasticsearch as root
    at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:104) ~[elasticsearch-6.1.1.jar:6.1.1]
    at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:171) ~[elasticsearch-6.1.1.jar:6.1.1]
    at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:322) ~[elasticsearch-6.1.1.jar:6.1.1]
    at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:121) ~[elasticsearch-6.1.1.jar:6.1.1]
    ... 6 more
[root@localhost bin]# cd ..

解決：

創建一個獨立的用戶，比如elk來啟動elasticsearch，不用root用戶啟動

2、elasticsearch安裝目錄權限不對

遇到啟動elasticsearch失敗，使用的是專門的用戶elk來啟動的，啟動日誌提示不能加載配置文件：

[elk@docker bin]$ ./elasticsearch
Exception in thread "main" 2018-06-03 17:36:23,881 main ERROR No log4j2 configuration file found. Using default configuration: logging only errors to the console. Set system property ‘log4j2.debug‘ to show Log4j2 internal initialization logging.
2018-06-03 17:36:24,113 main ERROR Could not register mbeans java.security.AccessControlException: access denied ("javax.management.MBeanTrustPermission" "register")
        at java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
        at java.lang.SecurityManager.checkPermission(SecurityManager.java:585)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.checkMBeanTrustPermission(DefaultMBeanServerInterceptor.java:1848)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:322)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
        at org.apache.logging.log4j.core.jmx.Server.register(Server.java:389)
        at org.apache.logging.log4j.core.jmx.Server.reregisterMBeansAfterReconfigure(Server.java:167)
        at org.apache.logging.log4j.core.jmx.Server.reregisterMBeansAfterReconfigure(Server.java:140)
        at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:556)
        at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:617)
        at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634)
        at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229)
        at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:242)
        at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
        at org.apache.logging.log4j.LogManager.getContext(LogManager.java:174)
        at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:618)
        at org.elasticsearch.common.logging.ESLoggerFactory.getLogger(ESLoggerFactory.java:54)
        at org.elasticsearch.common.logging.ESLoggerFactory.getLogger(ESLoggerFactory.java:62)
        at org.elasticsearch.common.logging.Loggers.getLogger(Loggers.java:101)
        at org.elasticsearch.ExceptionsHelper.<clinit>(ExceptionsHelper.java:42)
        at org.elasticsearch.ElasticsearchException.toString(ElasticsearchException.java:663)
        at java.lang.String.valueOf(String.java:2994)
        at java.io.PrintStream.println(PrintStream.java:821)
        at java.lang.Throwable$WrappedPrintStream.println(Throwable.java:748)
        at java.lang.Throwable.printStackTrace(Throwable.java:655)
        at java.lang.Throwable.printStackTrace(Throwable.java:643)
        at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1061)
        at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1052)
        at java.lang.Thread.dispatchUncaughtException(Thread.java:1959)

SettingsException[Failed to load settings from /usr/local/elasticsearch-5.6.0/config/elasticsearch.yml]; nested: AccessDeniedException[/usr/local/elasticsearch-5.6.0/config/elasticsearch.yml];
        at org.elasticsearch.node.InternalSettingsPreparer.prepareEnvironment(InternalSettingsPreparer.java:102)
        at org.elasticsearch.cli.EnvironmentAwareCommand.createEnv(EnvironmentAwareCommand.java:72)
        at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:67)
        at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:134)
        at org.elasticsearch.cli.Command.main(Command.java:90)
        at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:91)
        at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:84)
Caused by: java.nio.file.AccessDeniedException: /usr/local/elasticsearch-5.6.0/config/elasticsearch.yml
        at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
        at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
        at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
        at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
        at java.nio.file.Files.newByteChannel(Files.java:361)
        at java.nio.file.Files.newByteChannel(Files.java:407)
        at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384)
        at java.nio.file.Files.newInputStream(Files.java:152)
        at org.elasticsearch.common.settings.Settings$Builder.loadFromPath(Settings.java:1032)
        at org.elasticsearch.node.InternalSettingsPreparer.prepareEnvironment(InternalSettingsPreparer.java:100)
        ... 6 more
[elk@docker bin]$

解決：

看到“Caused by: java.nio.file.AccessDeniedException: /usr/local/elasticsearch-5.6.0/config/elasticsearch.yml”的提示，就去檢查目錄的權限，果然是root:root權限，使用elk用戶去啟動，就報錯了。
將目錄的權限改成elk:elk就好了。

[root@docker ~]# ll /usr/local/
drwxr-xr-x  7 root root       123 9月   7 2017 elasticsearch-5.6.0

[root@docker local]#  chown  -R elk:elk elasticsearch-5.6.0
[root@docker local]# ll
drwxr-xr-x  7 elk  elk        123 9月   7 2017 elasticsearch-5.6.0

3、日誌和數據目錄權限異常，啟動失敗

在一次啟動elasticsearch的時候啟動失敗，日誌有提示“main ERROR Unable to create file /home/elk/logs/my-application_index_indexing_slowlog.log java.io.IOException: 權限不夠”和“Caused by: java.nio.file.AccessDeniedException: /home/elk/data/nodes”。關鍵日誌信息如下（下面兩段日誌是節選的，日誌信息太多了，有很多重復的）：

[elk@docker bin]$ ./elasticsearch
2018-06-04 01:15:07,609 main ERROR Unable to create file /home/elk/logs/my-application.log java.io.IOException: 權限不夠
        at java.io.UnixFileSystem.createFileExclusively(Native Method)
        at java.io.File.createNewFile(File.java:1012)

後面還有一段：

 Caused by: java.lang.IllegalStateException: Failed to create node environment
        at org.elasticsearch.node.Node.<init>(Node.java:268) ~[elasticsearch-5.6.0.jar:5.6.0]
        at org.elasticsearch.node.Node.<init>(Node.java:245) ~[elasticsearch-5.6.0.jar:5.6.0]
        at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:233) ~[elasticsearch-5.6.0.jar:5.6.0]
        at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:233) ~[elasticsearch-5.6.0.jar:5.6.0]
        at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:342) ~[elasticsearch-5.6.0.jar:5.6.0]
        at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:132) ~[elasticsearch-5.6.0.jar:5.6.0]
        ... 6 more
Caused by: java.nio.file.AccessDeniedException: /home/elk/data/nodes
        at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) ~[?:?]

日誌報的“/home/elk/data/”和“/home/elk/logs/”目錄都是在elasticsearch.yml配置文件裏面配置的兩個目錄，查看權限果然不對，權限是elk的目錄權限是elk，但是下面的data目錄和logs目錄權限還是root，因此引起了啟動失敗：

[root@docker home]# ll 
drwx------  5 elk    elk         125 6月   3 17:35 elk       #elk目錄權限正常
[root@docker home]# cd elk/
[root@docker elk]# ll
總用量 0
drwxr-xr-x 2 root root 6 6月   3 17:34 data      #下面的data和logs目錄還是root
drwxr-xr-x 2 root root 6 6月   3 17:34 logs

將目錄權限修改成elk之後，啟動就OK了

[root@docker elk]# chown elk:elk -R ./*
[root@docker elk]# ll
總用量 0
drwxr-xr-x 2 elk elk 6 6月   3 17:34 data
drwxr-xr-x 2 elk elk 6 6月   3 17:34 logs
[root@docker elk]#

4、內存不夠，啟動失敗

在一次使用虛擬機做實驗的過程中啟動elasticsearch遇到了這樣的報錯：

[elk@docker bin]$ ./elasticsearch
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000085330000, 2060255232, 0) failed; error=‘Cannot allocate memory‘ (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 2060255232 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /usr/local/elasticsearch-5.6.0/bin/hs_err_pid2819.log

解決：

原因：
查看了 /usr/local/elasticsearch-5.6.0/bin/hs_err_pid1027.log日誌文件，出現這樣的報錯，有兩種可能：
1、系統進程數達到上限了，部屬的時候/etc/security/limits.conf文件修改沒有生效。
2、確實物理內存不夠

解決：
通過命令查看系統限制：ulimit -a查看open files不夠大，如果不夠大，就嘗試通過設大該值：

[root@docker ~]# ulimit -n
1024

果然是部屬的時候修改的/etc/security/limits.conf文件沒有生效。於是將機器reboot了一下，在查看就生效了：

[root@docker ~]# ulimit -n
65536

但是在啟動的時候還是報同樣的錯，查看了一下內存，這個虛擬機的內存只有1G，那應該就是物理內存不夠了。目前還剩下這麽多：

[root@docker ~]# free -h
              total        used        free      shared  buff/cache   available
Mem:           974M        119M         79M        7.7M        775M        680M
Swap:          819M          0B        819M

手動清理了一下內存：

[root@docker ~]# echo 3 > /proc/sys/vm/drop_caches  
[root@docker ~]# free -h
              total        used        free      shared  buff/cache   available
Mem:           974M        114M        789M        7.7M         69M        739M
Swap:          819M          0B        819M
[root@docker ~]#

但是在啟動報錯依舊。
於是增加物理內存到2G：

[root@docker elk]# free -h
              total        used        free      shared  buff/cache   available
Mem:           1.8G        1.6G         77M          4K         72M         29M
Swap:          819M        691M        128M

然後切換到elk用戶去啟動服務，就OK了：

[elk@docker bin]$ ./elasticsearch     #為了看啟動日誌就前臺啟動的，ctrl+c 進程就會over掉

檢查端口，起來了

[root@docker elk]# netstat -tlunp|grep 9200
tcp6       0      0 10.0.0.16:9200          :::*                    LISTEN      9628/java           
[root@docker elk]#

然後關掉進程重新後臺啟動：

[elk@docker bin]$ nohup ./elasticsearch >/dev/null 2>&1 &     #後臺啟動
[2] 9808
[elk@docker bin]$ ps -ef|grep elasticsearch   #檢查進程
elk        9808   4115 10 01:29 pts/0    00:00:23 /usr/local/jdk1.8.0_151/bin/java -Xms2g -Xmx2g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+AlwaysPreTouch -server -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -Djdk.io.permissionsUseCanonicalPath=true -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j.skipJansi=true -XX:+HeapDumpOnOutOfMemoryError -Des.path.home=/usr/local/elasticsearch-5.6.0 -cp /usr/local/elasticsearch-5.6.0/lib/* org.elasticsearch.bootstrap.Elasticsearch
elk        9890   4115  0 01:32 pts/0    00:00:00 grep --color=auto elasticsearch
[elk@docker bin]$ 
[root@docker elk]# netstat -tlunp|grep 9200    #用root用戶檢查端口
tcp6       0      0 10.0.0.16:9200          :::*                    LISTEN      9808/java           
[root@docker elk]#

總結遇到的elasticsearch啟動失敗的幾種情況及解決

elasticsearch1、使用root用戶啟動失敗在有一次搭建elasticsearch的時候，使用systemctl啟動elasticsearch失敗，然後在bin目錄下面去使用啟動腳本啟動，發現報錯不能用root用戶啟動，報“Caused by: java.lang.RuntimeException

總結遇到的elasticsearch啟動失敗的幾種情況及解決

解決：

2、elasticsearch安裝目錄權限不對

解決：

3、日誌和數據目錄權限異常，啟動失敗

4、內存不夠，啟動失敗

解決：

總結遇到的elasticsearch啟動失敗的幾種情況及解決

Error LNK2001 無法解析的外部符號的幾種情況及解決

大規模WebGL應用引發瀏覽器崩潰的幾種情況及解決辦法

VC++ Error LNK2001無法解析的外部符號的幾種情況及解決辦法

總結影響z-index的幾種情況

MYSQL建立外來鍵失敗幾種情況記錄Can't create table不能建立表

Pagehelper 不分頁幾種情況的解決方法

關於listview的自定義adapter不執行getview（）方法的幾種情況和解決辦法

oracle ORA 00936 missing expression 報錯的幾種情況和解決方法

Oracle物化檢視失效的幾種情況及測試

RMI總結及可能產生的幾種異常及解決

thinkphp模板變數輸出的幾種情況及注意點

Oracle EBS診斷方面幾種情況的解決方法（診斷選單隱藏、個性化功能報錯、關於此頁的顯示）

轉:Tomcat內存溢出的三種情況及解決辦法分析

高併發快取處理之——快取穿透的幾種形式及解決方案

Jfinal開發時，404常見幾種問題及解決辦法

Tensorflow由於版本問題出現的幾種錯誤及解決辦法

Tomcat記憶體溢位的三種情況及解決辦法分析

Java中OutOfMemoryError(記憶體溢位)的三種情況及解決辦法

詳談表單重複提交的三種情況及解決方法

總結遇到的elasticsearch啟動失敗的幾種情況及解決

解決：

2、elasticsearch安裝目錄權限不對

解決：

3、日誌和數據目錄權限異常，啟動失敗

4、內存不夠，啟動失敗

解決：

相關推薦