bootstrap.memory_lock: true导致Elasticsearch启动失败问题

elasticsearch官网建议生产环境需要设置bootstrap.memory_lock: true

重新启动elasticsearch,报错信息如下:

[[email protected] /home/baoshan/elk/elasticsearch-5.3.0]
$bin/elasticsearch
[2017-04-20T21:45:36,741][WARN ][o.e.b.JNANatives ] Unable to lock JVM Memory: error=12, reason=无法分配内存
[2017-04-20T21:45:36,746][WARN ][o.e.b.JNANatives ] This can result in part of the JVM being swapped out.
[2017-04-20T21:45:36,746][WARN ][o.e.b.JNANatives ] Increase RLIMIT_MEMLOCK, soft limit: 65536, hard limit: 65536
[2017-04-20T21:45:36,747][WARN ][o.e.b.JNANatives ] These can be adjusted by modifying /etc/security/limits.conf, for example: 
# allow user ‘baoshan‘ mlockall
baoshan soft memlock unlimited
baoshan hard memlock unlimited
[2017-04-20T21:45:36,747][WARN ][o.e.b.JNANatives ] If you are logged in interactively, you will have to re-login for the new limits to take effect.
[2017-04-20T21:45:37,057][INFO ][o.e.n.Node ] [node-43] initializing ...
[2017-04-20T21:45:37,584][INFO ][o.e.e.NodeEnvironment ] [node-43] using [1] data paths, mounts [[/ (/dev/mapper/vg_root-lv_root)]], net usable_space [39.6gb], net total_space [44.7gb], spins? [possibly], types [ext4]
[2017-04-20T21:45:37,585][INFO ][o.e.e.NodeEnvironment ] [node-43] heap size [1.9gb], compressed ordinary object pointers [unknown]
[2017-04-20T21:45:37,587][INFO ][o.e.n.Node ] [node-43] node name [node-43], node ID [oUSfip81Sc-SGtZP9GCydg]
[2017-04-20T21:45:37,588][INFO ][o.e.n.Node ] [node-43] version[5.3.0], pid[5150], build[3adb13b/2017-03-23T03:31:50.652Z], OS[Linux/2.6.32-504.el6.x86_64/i386], JVM[Oracle Corporation/Java HotSpot(TM) Server VM/1.8.0_121/25.121-b13]
[2017-04-20T21:45:39,914][INFO ][o.e.p.PluginsService ] [node-43] loaded module [aggs-matrix-stats]
[2017-04-20T21:45:39,915][INFO ][o.e.p.PluginsService ] [node-43] loaded module [ingest-common]
[2017-04-20T21:45:39,916][INFO ][o.e.p.PluginsService ] [node-43] loaded module [lang-expression]
[2017-04-20T21:45:39,916][INFO ][o.e.p.PluginsService ] [node-43] loaded module [lang-groovy]
[2017-04-20T21:45:39,916][INFO ][o.e.p.PluginsService ] [node-43] loaded module [lang-mustache]
[2017-04-20T21:45:39,916][INFO ][o.e.p.PluginsService ] [node-43] loaded module [lang-painless]
[2017-04-20T21:45:39,917][INFO ][o.e.p.PluginsService ] [node-43] loaded module [percolator]
[2017-04-20T21:45:39,917][INFO ][o.e.p.PluginsService ] [node-43] loaded module [reindex]
[2017-04-20T21:45:39,917][INFO ][o.e.p.PluginsService ] [node-43] loaded module [transport-netty3]
[2017-04-20T21:45:39,917][INFO ][o.e.p.PluginsService ] [node-43] loaded module [transport-netty4]
[2017-04-20T21:45:39,919][INFO ][o.e.p.PluginsService ] [node-43] no plugins loaded
[2017-04-20T21:45:42,143][INFO ][o.e.n.Node ] [node-43] initialized
[2017-04-20T21:45:42,150][INFO ][o.e.n.Node ] [node-43] starting ...
[2017-04-20T21:45:42,282][WARN ][i.n.u.i.MacAddressUtil ] Failed to find a usable hardware address from the network interfaces; using random bytes: 5b:5f:0c:d6:78:e5:0b:ec
[2017-04-20T21:45:42,381][INFO ][o.e.t.TransportService ] [node-43] publish_address {10.88.128.88:9300}, bound_addresses {10.88.128.88:9300}
[2017-04-20T21:45:42,395][INFO ][o.e.b.BootstrapChecks ] [node-43] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
ERROR: bootstrap checks failed
memory locking requested for elasticsearch process but memory is not locked
[2017-04-20T21:45:42,430][INFO ][o.e.n.Node ] [node-43] stopping ...
[2017-04-20T21:45:42,500][INFO ][o.e.n.Node ] [node-43] stopped
[2017-04-20T21:45:42,500][INFO ][o.e.n.Node ] [node-43] closing ...
[2017-04-20T21:45:42,525][INFO ][o.e.n.Node ] [node-43] closed

解决办法如下:

需要修改
/etc/security/limits.conf 
baoshan soft memlock unlimited
baoshan hard memlock unlimited

修改:
/etc/sysctl.conf 
vm.swappiness=0

之后重启机器

再次启动elasticsearch,成功,信息如下:

[[email protected] /home/baoshan/elk/elasticsearch-5.3.0]
$bin/elasticsearch
[2017-04-20T21:49:34,755][INFO ][o.e.n.Node ] [node-43] initializing ...
[2017-04-20T21:49:35,168][INFO ][o.e.e.NodeEnvironment ] [node-43] using [1] data paths, mounts [[/ (/dev/mapper/vg_root-lv_root)]], net usable_space [39.6gb], net total_space [44.7gb], spins? [possibly], types [ext4]
[2017-04-20T21:49:35,170][INFO ][o.e.e.NodeEnvironment ] [node-43] heap size [1.9gb], compressed ordinary object pointers [unknown]
[2017-04-20T21:49:35,176][INFO ][o.e.n.Node ] [node-43] node name [node-43], node ID [oUSfip81Sc-SGtZP9GCydg]
[2017-04-20T21:49:35,178][INFO ][o.e.n.Node ] [node-43] version[5.3.0], pid[1208], build[3adb13b/2017-03-23T03:31:50.652Z], OS[Linux/2.6.32-504.el6.x86_64/i386], JVM[Oracle Corporation/Java HotSpot(TM) Server VM/1.8.0_121/25.121-b13]
[2017-04-20T21:49:38,647][INFO ][o.e.p.PluginsService ] [node-43] loaded module [aggs-matrix-stats]
[2017-04-20T21:49:38,647][INFO ][o.e.p.PluginsService ] [node-43] loaded module [ingest-common]
[2017-04-20T21:49:38,647][INFO ][o.e.p.PluginsService ] [node-43] loaded module [lang-expression]
[2017-04-20T21:49:38,648][INFO ][o.e.p.PluginsService ] [node-43] loaded module [lang-groovy]
[2017-04-20T21:49:38,648][INFO ][o.e.p.PluginsService ] [node-43] loaded module [lang-mustache]
[2017-04-20T21:49:38,648][INFO ][o.e.p.PluginsService ] [node-43] loaded module [lang-painless]
[2017-04-20T21:49:38,649][INFO ][o.e.p.PluginsService ] [node-43] loaded module [percolator]
[2017-04-20T21:49:38,650][INFO ][o.e.p.PluginsService ] [node-43] loaded module [reindex]
[2017-04-20T21:49:38,650][INFO ][o.e.p.PluginsService ] [node-43] loaded module [transport-netty3]
[2017-04-20T21:49:38,650][INFO ][o.e.p.PluginsService ] [node-43] loaded module [transport-netty4]
[2017-04-20T21:49:38,652][INFO ][o.e.p.PluginsService ] [node-43] no plugins loaded
[2017-04-20T21:49:43,478][INFO ][o.e.n.Node ] [node-43] initialized
[2017-04-20T21:49:43,478][INFO ][o.e.n.Node ] [node-43] starting ...
[2017-04-20T21:49:43,650][WARN ][i.n.u.i.MacAddressUtil ] Failed to find a usable hardware address from the network interfaces; using random bytes: 5d:dc:90:e8:b1:e1:50:72
[2017-04-20T21:49:43,858][INFO ][o.e.t.TransportService ] [node-43] publish_address {10.88.128.88:9300}, bound_addresses {10.88.128.88:9300}
[2017-04-20T21:49:43,872][INFO ][o.e.b.BootstrapChecks ] [node-43] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
[2017-04-20T21:50:13,896][WARN ][o.e.n.Node ] [node-43] timed out while waiting for initial discovery state - timeout: 30s
[2017-04-20T21:50:13,935][INFO ][o.e.h.n.Netty4HttpServerTransport] [node-43] publish_address {10.88.128.88:9200}, bound_addresses {10.88.128.88:9200}
[2017-04-20T21:50:13,950][INFO ][o.e.n.Node ] [node-43] started

OK,搞定!

原文地址:https://www.cnblogs.com/ExMan/p/11360302.html

时间: 2024-08-03 22:11:00

bootstrap.memory_lock: true导致Elasticsearch启动失败问题的相关文章

SPFILE导致数据库启动失败

服务器断电重启后,报数据库服务无法启动,在服务器上使用AS SYSDBA 登录后连接到空实例, 使用startup启动时报'ORA-24324: 未初始化服务句柄,ORA-01041: 内部错误, hostdef 扩展名不存在'错误. 分步启动startup nomount ,依然报以上错误,判断为spfile文件损坏造成.但本机没有使用pfile备份过spfile,而修改spfile要启动修改. 解决办法,手工创建pfile 文件INITSID.ORA,打开alert日志,找到数据库启动信息,

Windows 更新导致 VirtualBox 启动失败 VBoxDrvStub error

win8 导入virtualbox介质发生错误, NtCreateFile(\Device\VBoxDrvStub) failed: Unkown Status - 5600 (0xffffea20) (rcNt=0xe986ea20) VBoxDrvStub error: ntdll.dll: 7982 differences between 0x300c and 0x4fff in #1 (.text), first: 4c != 1f (rc=-5600) 尝试了各种办法,下载非最新版本v

总结遇到的elasticsearch启动失败的几种情况及解决

1.使用root用户启动失败 在有一次搭建elasticsearch的时候,使用systemctl启动elasticsearch失败,然后在bin目录下面去使用启动脚本启动,发现报错不能用root用户启动,报"Caused by: java.lang.RuntimeException: can not run elasticsearch as root": [[email protected] bin]# ./elasticsearch [2017-12-20T17:01:47,922

ORA-01078和LRM-00109问题导致ORACLE启动失败解决方法

操作环境 SuSE11 + ORACLE11gR2(11.2.0.3) 问题现象 新安装ORACLE启动失败,提示ORA-01078和LRM-00109错误.具体错误现象如下 SQL> startup ORA-01078: failure in processing system parameters LRM-00109: could not open parameter file '/home/oracle/base/dbs/initora11g.ora'  问题分析 根据错误分析是查找不到参

db_recovery_file_dest_size 满导致数据库启动失败

启动数据库时: [email protected]>startup ORACLE instance started. Total System Global Area 417546240 bytes Fixed Size 2213936 bytes Variable Size 327157712 bytes Database Buffers 83886080 bytes Redo Buffers 4288512 bytes Database mounted. ORA-03113: end-of-

Windows 更新导致 VirtualBox 启动失败

我的虚拟机版本是 4.3.20, Windows 版本是 Windows 8,但今天突然发现 VirtualBox 启动不了,报的错误如下: 为了搜索引擎能检索到此错误信息,我将错误信息的文本贴在下面: NtCreateFile(\Device\VBoxDrvStub) failed: Unkown Status - 5600 (0xffffea20) (rcNt=0xe986ea20) VBoxDrvStub error: ntdll.dll: 7982 differences between

ZooKeeper集群搭建中的Connection refused而导致的启动失败

1. 前言 每一次搭建集群环境都像一次战斗,作战中任何一个细节的出错都会导致严重的后果,所以搭建中所需要做的配置如系统配置.网络配置(防火墙记得关).用户权限.文件权限还有配置文件等等内容,都必须非常仔细,将失误扼杀在摇篮之中,避免因为粗心或者想要提高速度省下的一分钟,在后面付出几个小时的调试时间,因小失大实在不值,切记核对.核对再核对. 今天就来说说在搭建ZooKeeper集群遇到的一个常见的问题Connection refused,也就是网上很多朋友也会出现的问题,问题的表现也许是一样,但是

记一次Postgresql异常中断导致的启动失败

由于异常导致了测试服务器的Pg11宕机,启动时候报错 2019-06-11 14:20:08.121 CST [9980] 致命错误: 数据库系统启动中 2019-06-11 14:20:08.121 CST [9981] 致命错误: 数据库系统启动中 2019-06-11 14:20:08.121 CST [9964] 致命错误: 数据库系统启动中 2019-06-11 14:20:08.121 CST [9970] 致命错误: 数据库系统启动中 2019-06-11 14:20:08.121

hadoop 使用ip配置导致hdfs启动失败

dataNode 有守护进行,但hdfs web页面上显示没有live node. 错误日志: 2017-06-21 17:44:59,513 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: Initialization failed for Block pool BP-1394689615-10.85.123.43-1498038283287 (Datanode Uuid null) service to /10.85.123.43