# Upgrade from 5.6.8 to 6.2.2 failing

**URL:** <https://discuss.elastic.co/t/upgrade-from-5-6-8-to-6-2-2-failing/122926>\
**Category:** Elasticsearch\
**Created:** [March 7, 2018, 4:36pm UTC](https://discuss.elastic.co/t/upgrade-from-5-6-8-to-6-2-2-failing/122926 "2018-03-07T16:36:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![blackey](https://avatars.discourse-cdn.com/v4/letter/b/958977/32.png) [@blackey](https://discuss.elastic.co/u/blackey)\
**Post date:** [March 7, 2018, 4:36pm UTC](https://discuss.elastic.co/t/upgrade-from-5-6-8-to-6-2-2-failing/122926/1 "2018-03-07T16:36:45Z")

</div>

I am in the process of working through a rolling update to my cluster an am not sure if its working correctly.

I fixed the issues the assistant had before starting.

After creating Certs and enabling TLS I upgraded the first node.

The first node I upgraded is complaining about authenticating my elasticsearch user.

curl -u elastic -XGET 'localhost:9200/\_cat/health?pretty'  
Enter host password for user 'elastic':  
{  
"error" : {  
"root\_cause" : [  
{  
"type" : "security\_exception",  
"reason" : "failed to authenticate user [elastic]",  
"header" : {  
"WWW-Authenticate" : "Basic realm="security" charset="UTF-8""  
}  
}  
],  
"type" : "security\_exception",  
"reason" : "failed to authenticate user [elastic]",  
"header" : {  
"WWW-Authenticate" : "Basic realm="security" charset="UTF-8""  
}  
},  
"status" : 401  
}

This is set to the default password.

Ideas?

---

<div class="post-metadata">

**Author:** ![blackey](https://avatars.discourse-cdn.com/v4/letter/b/958977/32.png) [@blackey](https://discuss.elastic.co/u/blackey)\
**Post date:** [March 7, 2018, 6:12pm UTC](https://discuss.elastic.co/t/upgrade-from-5-6-8-to-6-2-2-failing/122926/2 "2018-03-07T18:12:40Z")

</div>

I am seeing this in the log.

[2018-03-07T18:11:18,110][INFO][o.e.x.m.e.l.LocalExporter] waiting for elected master node [{pp-es-03}{QfWBnWYxTWyQFq6qgeto2Q}{q\_bsqgmoTKqO5gHi6LJk4w}{10.161.5.41}{10.161.5.41:9300}{ml.max\_open\_jobs=10, ml.enabled=true}] to setup local exporter [default\_local] (does it have x-pack installed?)

They all have x-x-pack installed.

---

<div class="post-metadata">

**Author:** ![blackey](https://avatars.discourse-cdn.com/v4/letter/b/958977/32.png) [@blackey](https://discuss.elastic.co/u/blackey)\
**Post date:** [March 7, 2018, 10:47pm UTC](https://discuss.elastic.co/t/upgrade-from-5-6-8-to-6-2-2-failing/122926/3 "2018-03-07T22:47:37Z")

</div>

After running the ./setup-passwords interactive for x-pack and setting it to the same original password that were used I can now run API commands on the new hosts.

They show up in this list..

curl -user elastic -XGET 'localhost:9200/\_cat/nodes?pretty'  
10.161.6.42 11 95 1 0.14 0.09 0.03 d - pp-es-04  
10.161.4.42 12 74 1 0.05 0.12 0.08 di - pp-es-05  
10.161.6.41 7 99 8 0.38 0.16 0.12 md - pp-es-01  
10.161.5.41 67 99 12 0.07 0.02 0.03 md \* pp-es-03  
10.161.4.41 8 82 20 0.12 0.11 0.23 md - pp-es-02  
10.161.5.42 10 98 0 0.14 0.08 0.09 di - pp-ek-01

But don't show up in Kibana Monitoring..

---

<div class="post-metadata">

**Author:** ![blackey](https://avatars.discourse-cdn.com/v4/letter/b/958977/32.png) [@blackey](https://discuss.elastic.co/u/blackey)\
**Post date:** [March 7, 2018, 11:52pm UTC](https://discuss.elastic.co/t/upgrade-from-5-6-8-to-6-2-2-failing/122926/4 "2018-03-07T23:52:11Z")

</div>

I solved this. I continued the upgrade and eventually they all shoed up on kibana dashboard.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 4, 2018, 11:52pm UTC](https://discuss.elastic.co/t/upgrade-from-5-6-8-to-6-2-2-failing/122926/5 "2018-04-04T23:52:14Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.