将Elasticsearch 2.1.1升级到2.2.0 -缺少身份验证令牌？
我决定尝试将当前集群从ES2.1.1升级到ES2.2.0。一面镜子。集群在AWS中运行，所以我使用cloud-aws插件进行通信。
我成功地升级了第一个节点，它已经成为主节点，但是在升级第二个节点时遇到了一个奇怪的通信/身份验证问题。
我注意到了指南这里，但我似乎仍在经历一个奇怪的问题。
从第二个节点上的主群集日志：
[2016-02-03 12:29:41,241][INFO ][discovery.ec2 ] [Sharon Ventura] failed to send join request to master [{Space Phantom}{NzN7b7ZHT8uPu6oXJAORMg}{10.60.164.147}{10.60.164.147:9300}], reason [RemoteTransportException[[Space Phantom][10.60.164.147:9300][internal:discovery/zen/join]]; nested: IllegalStateException[failure when sending a validation request to node]; nested: RemoteTransportException[[Sharon Ventura][10.60.163.74:9300][internal:discovery/zen/join/validate]]; nested: ElasticsearchSecurityException[missing authentication token for action [internal:discovery/zen/join/validate]]; ]
[2016-02-03 12:29:42,455][DEBUG][action.admin.cluster.health] [Sharon Ventura] no known master node, scheduling a retry
[2016-02-03 12:29:44,255][INFO ][discovery.ec2 ] [Sharon Ventura] failed to send join request to master [{Space Phantom}{NzN7b7ZHT8uPu6oXJAORMg}{10.60.164.147}{10.60.164.147:9300}], reason [RemoteTransportException[[Space Phantom][10.60.164.147:9300][internal:discovery/zen/join]]; nested: IllegalStateException[failure when sending a validation request to node]; nested: RemoteTransportException[[Sharon Ventura][10.60.163.74:9300][internal:discovery/zen/join/validate]]; nested: ElasticsearchSecurityException[missing authentication token for action [internal:discovery/zen/join/validate]]; ]
[2016-02-03 12:29:47,269][INFO ][discovery.ec2 ] [Sharon Ventura] failed to send join request to master [{Space Phantom}{NzN7b7ZHT8uPu6oXJAORMg}{10.60.164.147}{10.60.164.147:9300}], reason [RemoteTransportException[[Space Phantom][10.60.164.147:9300][internal:discovery/zen/join]]; nested: IllegalStateException[failure when sending a validation request to node]; nested: RemoteTransportException[[Sharon Ventura][10.60.163.74:9300][internal:discovery/zen/join/validate]]; nested: ElasticsearchSecurityException[missing authentication token for action [internal:discovery/zen/join/validate]]; ]
[2016-02-03 12:29:49,472][DEBUG][action.admin.cluster.state] [Sharon Ventura] timed out while retrying [cluster:monitor/state] after failure (timeout [30s])
[2016-02-03 12:29:49,473][INFO ][rest.suppressed ] /_cluster/settings Params: {}
MasterNotDiscoveredException[null]
at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$5.onTimeout(TransportMasterNodeAction.java:205)
at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:239)
at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:794)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[2016-02-03 12:29:50,283][INFO ][discovery.ec2 ] [Sharon Ventura] failed to send join request to master [{Space Phantom}{NzN7b7ZHT8uPu6oXJAORMg}{10.60.164.147}{10.60.164.147:9300}], reason [RemoteTransportException[[Space Phantom][10.60.164.147:9300][internal:discovery/zen/join]]; nested: IllegalStateException[failure when sending a validation request to node]; nested: RemoteTransportException[[Sharon Ventura][10.60.163.74:9300][internal:discovery/zen/join/validate]]; nested: ElasticsearchSecurityException[missing authentication token for action [internal:discovery/zen/join/validate]]; ]我的elasticsearch.yml文件：
cluster.name: cluster01
http.cors.enabled: true
network.host: 0.0.0.0
discovery.type: ec2
discovery.ec2.tag.project_code_info: "cluster01"
cloud.aws.region: eu-central-1我可以从日志中看到，它检测到了第一个节点：[Space Phantom][10.60.164.147:9300] --它在没有任何干预的情况下检测到了它，但是它显然无法进行身份验证。
我怀疑这可能与安装的Shield插件有关，但正确和相同的权限设置与以前相同。其他的一切都没有改变。
我在屏蔽中使用用户名和密码，没有配置SSL。
有人能帮忙吗？
回答 1
Stack Overflow用户
发布于 2016-02-29 16:16:22
按照@ figure 3458016的请求，我设法想出了答案。
我设法解决了这个问题，通过(所有节点上的)重置所有设置和配置，删除插件license、shield，删除所有用户并像以前一样重新添加它们。这些配置一开始是相同的，所以这很奇怪。
首先，停止对所有节点的elasticsearch。如果在本地运行，就停止基班纳。
如果您有任何自定义角色()，请在/etc/elasticsearch/shield/roles.yml中检查此角色的配置，如果可能，请从单个记录的配置中刷新此配置。
删除插件：
/usr/share/elasticsearch/bin/plugin remove elasticsearch/license/latest /usr/share/elasticsearch/bin/plugin remove elasticsearch/shield/latest
删除用户：
/usr/share/elasticsearch/bin/shield/esusers userdel admin /usr/share/elasticsearch/bin/shield/esusers userdel logstash
重新添加插件：
/usr/share/elasticsearch/bin/plugin install elasticsearch/license/latest -b /usr/share/elasticsearch/bin/plugin install elasticsearch/shield/latest -b
重新添加用户：
/usr/share/elasticsearch/bin/shield/esusers useradd admin -p adminuserpw -r admin /usr/share/elasticsearch/bin/shield/esusers useradd logstash -p logstashuserpw -r logstash
--如果您有任何自定义角色，请在/etc/elasticsearch/shield/roles.yml中重复检查该角色的配置，以验证配置没有被修改或重写。
在第一个节点上启动elasticsearch。如果在本地运行，请启动kibana。
检查索引已正确出现，验证主节点状态。
在所有其他节点上执行上述所有步骤.
启动剩余节点的elasticsearch，每次一个。在启动下一个节点之前验证正常的群集复制。
我希望有人发现这有用。
https://stackoverflow.com/questions/35182574
复制相似问题
腾讯云开发者
