ElasticSearch本人启动报错总结

1.报错关键代码如下:

Exception in thread "main" 2019-04-28 03:53:04,339 main ERROR No log4j2 configuration file found.

SettingsException[Failed to load settings from [elasticsearch.yml]]; nested: ParsingException[Failed to parse object: expecting token of type [START_OBJECT] but found [VALUE_STRING]];

Caused by: ParsingException[Failed to parse object: expecting token of type [START_OBJECT] but found [VALUE_STRING]]

  报错原因:是你的elasticsearch.yml文件中的key/value值写错了,重新检查或者将其他可以正常启动的机器中的文件发送到报错机器,并修改节点名、ip等即可

2.报错关键代码如下:

failed to send join request to master

 nested: IllegalArgumentException[can‘t add node 

found existing node

  报错原因:这是启动从节点时报错,可以看出提示报错找到存在节点,原因是本人先安装了ES的单节点模式,然后将主节点的ES目录发送到了从节点,导致ES目录下的data目录中存储的数据是主节点的,所以删除dasa目录下的nodes文件集,重启从节点即可。

原文地址:https://www.cnblogs.com/HelloBigTable/p/10780224.html

时间: 2025-01-09 16:47:29

ElasticSearch本人启动报错总结的相关文章

elk中elasticsearch安装启动报错

elasticsearch安装之后.启动报错.elasticsearch版本为5.4.1 下载安装: wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-5.4.1.tar.gz tar zxf elasticsearch-5.4.1.tar.gz mv elasticsearch-5.4.1 /usr/local/elasticsearch cd /usr/local/elasticsearch/ ./

logstash启动报错 Exception in thread ">output" org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]

部署ELK时候,logstash启动报错 Sending logstash logs to /var/log/logstash.log.Exception in thread ">output" org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]    at org.elasticsearch.action.support.master.TransportMasterNodeOper

sonar6.7启动报错: can not run elasticsearch as root

最近玩一下sonar, centos上启动报错: can not run elasticsearch as root,log如下: sonar.log 2017.11.20 21:16:48 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running2017.11.20 21:16:49 INFO app[][o.e.p.PluginsService] no modules loaded2017.1

Linux安装ElasticSearch启动报错的解决方法

Linux安装ElasticSearch后,ElasticSearch是不能用root用户启动的,以root用户启动会报错Refer to the log for complete error details,出现这种情况该如何解决呢?下面小编就为大家带来Linux安装ElasticSearch启动报错的解决方法,一起去看看吧 今天就出现的异常问题专门解决一下.你安装好ElasticSearch以后,在启动的时候需要注意的问题是,ElasticSearch是不能用root用户启动的(这是根据el

【elaseticsearch】elaseticsearch启动报错Caused by: org.elasticsearch.transport.BindTransportException: Failed to bind to [9300-9400]

elaseticsearch启动报错 [es1] uncaught exception in thread [main] org.elasticsearch.bootstrap.StartupException: BindTransportException[Failed to bind to [9300-9400]]; nested: BindException[Cannot assign requested address]; at org.elasticsearch.bootstrap.E

MySql启动报错,无法更新PID文件

MySql启动报错 Starting MySQL.. ERROR! The server quit without updating PID file (/var/lib/mysql..) 1,查看错误日志 2017-08-10 19:38:14 31865 [Note] InnoDB: Initializing buffer pool, size = 50.0M InnoDB: mmap(53657600 bytes) failed; errno 12 2017-08-10 19:38:14

VM虚拟机启动报错Reason Failed to lock the file怎么办

VMware启动报错Reason: Failed to lock the file的解决方法 症状:  启动VMware虚拟机的时候出现了Cannot open the disk '*.vmdk' or one of the snapshot disks it depends on.Reason: Failed to lock the file.的错误. 解决办法一: 1.在VMware该虚拟机路径下的所有.lck文件和文件夹下删除或迁移至其它目录,一般就可以解决了. 2.如果再次启动VMwar

mysql无法启动问题的解决方案:mysql.sock重启不自动生成,mysqld_safe启动报错

mysql无法启动问题的解决方案:mysql.sock重启不自动生成,mysqld_safe启动报错 - superlucky 时间 2013-08-03 11:55:00 博客园-原创精华区 原文  http://www.cnblogs.com/super-lucky/p/superlucky.html 主题 MySQL 本人还是个菜鸟,下面是我的经验之谈,能解决一些问题,有不对的地方,敬请斧正. 我的是CentOS6.3+MySQL5.1.57. 重启了一次服务器后, 使用> mysql -

kibana 启动报错

kibana4.1 启动报错 {"name":"Kibana","hostname":"linux-node1.example.com","pid":3941,"level":60,"err":{"message":"unknown error","name":"Error","