【ELK报错】Alias [.kibana] has more than one indices associated with it [[.kibana_1, .kibana_2]]
错误复现
搭建1套新的ELK环境,将之前旧的ES的索引文件data/nodes/0/indices/
全部复制到新的ES中。期间不要停止ES。然后kibana就无法访问了,重启kibana报错如下:
log [02:59:35.875] [info][status][plugin:maps@6.7.2] Status changed from yellow to green - Readyerror [02:59:35.890] [warning][stats-collection] [illegal_argument_exception] Alias [.kibana] has more than one indices associated with it [[.kibana_1, .kibana_2]], can't execute a single index op :: {"path":"/.kibana/doc/kql-telemetry%3Akql-telemetry","query":{},"statusCode":400,"response":"{\"error\":{\"root_cause\":[{\"type\":\"illegal_argument_exception\",\"reason\":\"Alias [.kibana] has more than one indices associated with it [[.kibana_1, .kibana_2]], can't execute a single index op\"}],\"type\":\"illegal_argument_exception\",\"reason\":\"Alias [.kibana] has more than one indices associated with it [[.kibana_1, .kibana_2]], can't execute a single index op\"},\"status\":400}"}at respond (/usr/local/elk/kibana-6.7.2-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:308:15)at checkRespForFailure (/usr/local/elk/kibana-6.7.2-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:267:7)at HttpConnector.<anonymous> (/usr/local/elk/kibana-6.7.2-linux-x86_64/node_modules/elasticsearch/src/lib/connectors/http.js:166:7)at IncomingMessage.wrapper (/usr/local/elk/kibana-6.7.2-linux-x86_64/node_modules/elasticsearch/node_modules/lodash/lodash.js:4935:19)at IncomingMessage.emit (events.js:194:15)at endReadableNT (_stream_readable.js:1103:12)at process._tickCallback (internal/process/next_tick.js:63:19)log [02:59:35.891] [warning][stats-collection] Unable to fetch data from kql collectorlog [02:59:35.923] [info][license][xpack] Imported license information from Elasticsearch for the [monitoring] cluster: mode: basic | status: activelog [02:59:36.407] [warning][browser-driver][reporting] Enabling the Chromium sandbox provides an additional layer of protection.log [02:59:36.409] [warning][reporting] Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.ymllog [02:59:36.446] [info][status][plugin:reporting@6.7.2] Status changed from uninitialized to green - Readylog [02:59:36.526] [warning][reporting] The Reporting plugin encountered issues launching Chromium in a self-test. You may have trouble generating reports: [object Object]log [02:59:36.526] [warning][reporting] See Chromium's log output at "/usr/local/elk/kibana-6.7.2-linux-x86_64/data/headless_shell-linux/chrome_debug.log"log [02:59:36.545] [info][listening] Server running at http://0.0.0.0:5601log [02:59:36.558] [error][status][plugin:spaces@6.7.2] Status changed from yellow to red - Alias [.kibana] has more than one indices associated with it [[.kibana_1, .kibana_2]], can't execute a single index op: [illegal_argument_exception] Alias [.kibana] has more than one indices associated with it [[.kibana_1, .kibana_2]], can't execute a single index op
查看ES健康状态
[root@soft-pro-elk ~]# curl -X GET localhost:9200/_cat/health?v
epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
1573095571 02:59:31 es-old-pro yellow 1 1 1661 1661 0 0 1635 0 - 50.4%
yellow是因为存在unsigned的shards,不用管
查看索引状态
[root@soft-pro-elk ~]# curl -X GET localhost:9200/_cat/indices?v | grep kibana% Total % Received % Xferd Average Speed Time Time Time CurrentDload Upload Total Spent Left Speed
100 44958 100 44958 0 0 54879 0 --:--:-- --:--:-- --:--:-- 54826
green open .monitoring-kibana-6-2019.10.30 BVi4K_GSTB6syaxHpMqmaQ 1 0 8639 0 2mb 2mb
green open .monitoring-kibana-6-2019.11.03 Aw13TiCbS9i_wipZkCay9w 1 0 8640 0 2mb 2mb
green open .monitoring-kibana-6-2019.11.07 di9f23TkRWeXDePkeTJ2UQ 1 0 1099 0 415.4kb 415.4kb
green open .monitoring-kibana-6-2019.11.05 lbend3h8TfyKg3s93HvB2g 1 0 6272 0 1.6mb 1.6mb
green open .kibana_task_manager SKEmdDhpT2-30BGQKT-iJQ 1 0 2 0 24.4kb 24.4kb
green open .monitoring-kibana-6-2019.11.01 tpFS8b31TFOyfb93AYtMmA 1 0 8639 0 2mb 2mb
green open .kibana_1 04KkU18bTYCMWqA2hQ9hbQ 1 0 5 0 22.6kb 22.6kb
green open .kibana_2 Pcin-zDAR-W0e_5QhYASog 1 0 8 3 33.3kb 33.3kb
green open .monitoring-kibana-6-2019.11.02 6-o5Q-K1TESggwdP9Qwi5A 1 0 8639 0 2mb 2mb
green open .monitoring-kibana-6-2019.10.31 dGif3lPVTr6A_aFRnK4f7Q 1 0 8640 0 2mb 2mb
green open .monitoring-kibana-6-2019.11.04 xvnGubofTTySFMpMdGaufg 1 0 3294 0 715.8kb 715.8kb
green open .monitoring-kibana-6-2019.11.06 yYv8bGQITp2KDLFjuNCS9g 1 0 5230 0 1.2mb 1.2mb
可以看到有一个.kibana_1 和 .kibana_2。直接将这两个索引删除就行了
删除索引
[root@soft-pro-elk ~]# curl -X DELETE localhost:9200/.kibana_1
{"acknowledged":true}
[root@soft-pro-elk ~]# curl -X DELETE localhost:9200/.kibana_2
{"acknowledged":true}
删完以后,再查看一下索引,确认下是否已删除,确认删除以后,再重启kibana就好了
【ELK报错】Alias [.kibana] has more than one indices associated with it [[.kibana_1, .kibana_2]]相关推荐
- ELK报错expected block end, but found BlockMappingStart
在配置文件中vim /etc/elasticsearch/elasticsearch.yml中. 每个配置行前需要有空格 每个':'两边需要有空格 数组中间加空格 还有注释掉的参数不能在#后边加空格不 ...
- ELK报错no handler found for uri原因postman的原因
- ELK报错hese locations are not writable or multiple nodes were started without inc
后台已经有一个elasticsearch进程了 当然是杀掉进程重启 看端口:netstat -alnp | grep 9200 或进程:ps -ef | grep elasticsearch #强杀 ...
- node-sass报错问题
转发 Cannot find module 'node-sass' https://my.oschina.net/dawd/blog/3004693 npm install npm@6.14.15 - ...
- es启动报错:could not find java in JAVA_HOME at /elk/es/elasticsearch-7.11.1/jdk/bin/java
es启动报错 错误排查 检查java环境变量是否配置 es启动要使用非root账户 es账户是否授权 如图:我的es账户未授权 通过执行命令解决: chown -R elk:elk /elk/* do ...
- kibana 报错 server is not ready yet 可能的原因
目录 问题1:KB.ES版本不一致 问题2:kibana.yml中配置有问题 问题3:系统防火墙造成的问题 问题1:KB.ES版本不一致 解决方法:把KB和ES版本调整为统一版本 实例1:docker ...
- 【Kibana】es 报错 all shards failed: [search_phase_execution_exception] all shards failed
1.背景 访问kibana报错,all shards failed {"message":"all shards failed: [search_phase_execut ...
- Kibana查询ES报错:[circuit_breaking_exception] [parent] Data too large
一.kibana浏览器报错 {"statusCode":429,"error":"Too Many Requests","mess ...
- kibana报错:No default index pattern. You must select or create one to continue.
报错信息 : 1.No default index pattern. You must select or create one to continue. 2.Timelion: Error: in ...
最新文章
- 博士Nature发文:研究生阶段,4点经验助你学术“独立”!
- rocketmq怎么保证消息一致性_从入门到入土(三)RocketMQ 怎么保证的消息不丢失?...
- mysql 平均响应时间_Percona-Server/MySQL响应时间统计
- 一个多版本IE共存软件 IETester(支持IE5.5,6,7,8Beta1)
- 如何使用BorgBackup,Rclone和Wasabi云存储推出自己的备份解决方案
- oracle手注,oracle手注
- oracle load data infile
- 人工智能python3+tensorflow人脸识别_Tensorflow+opencv2实现人脸识别
- 2021Java面试总结!平安银行java开发面试
- WPS Office 2019 v11.8.2专业增强版
- python螺旋输出矩阵_Python实现打印螺旋矩阵功能的方法
- Ethernet和802.3的区别
- Android开发常见问题汇总
- Gromacs基础教程一:入门建议
- 地方征信平台第2讲:河北省征信
- get 传值 是params
- nagios 的安装
- textpad:工具中没有编译
- 深度学习在推荐算法上的应用进展
- JS 两数相除取百分比%并保留两位小数