# ES 5.0 new installation question **URL:** \ **Category:** Elasticsearch\ **Created:** [November 8, 2016, 8:40pm UTC](https://discuss.elastic.co/t/es-5-0-new-installation-question/65405 "2016-11-08T20:40:20Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Diggy](https://avatars.discourse-cdn.com/v4/letter/d/e99b99/32.png) [@Diggy](https://discuss.elastic.co/u/Diggy)\ **Post date:** [November 8, 2016, 8:40pm UTC](https://discuss.elastic.co/t/es-5-0-new-installation-question/65405/1 "2016-11-08T20:40:20Z")
After getting less-than-desired results trying to upgrade my ELK stack to version 5.0, I thought I'd start fresh, and create a brand new ELK 5.0 node. I have reused some config files (e.g. elasticsearch.yml, kibana.yml, logstash config files) from my older setup. So far, so good. ES, Logstash, and Kibana start OK, and I can access the Kibana Web UI. However, I can't configure an index pattern. For example, the pattern logstash-\* returns the dreaded "Unable to fetch mapping. ... ". When I look in /var/lib/elasticsearch/nodes/0/indices, I see idices with names like Lk8wl5UtRASVyldRHspZQg, instead of e.g. logstash-2016.11.08. When I go to [http://localhost:9200/\_cat/indices](http://localhost:9200/_cat/indices), I see the following: yellow open .monitoring-data-2 s147bGxoQ5WgDgsP4XlECA 1 1 4 0 13.5kb 13.5kb yellow open .monitoring-es-2-2016.11.08 PcZAvTv8TjmTJgZ6e-rm0Q 1 1 2900 40 2.4mb 2.4mb yellow open .monitoring-kibana-2-2016.11.08 m1MyHbtXRCiNPdeDr97aZA 1 1 550 0 335kb 335kb yellow open .kibana Lk8wl5UtRASVyldRHspZQg 1 1 1 0 3.2kb 3.2kb What happened to my logstash, filebeat, winlogbeat, and topbeat indices? Thanks ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 8, 2016, 8:53pm UTC](https://discuss.elastic.co/t/es-5-0-new-installation-question/65405/2 "2016-11-08T20:53:03Z")
Did you push data from beats etc into ES? That might sound obvious, but it doesn't look like you have. ---
**Author:** ![Diggy](https://avatars.discourse-cdn.com/v4/letter/d/e99b99/32.png) [@Diggy](https://discuss.elastic.co/u/Diggy)\ **Post date:** [November 8, 2016, 9:33pm UTC](https://discuss.elastic.co/t/es-5-0-new-installation-question/65405/3 "2016-11-08T21:33:43Z")
warkolm, I take it you mean from all of the hosts that are forwarding logs? I would think so. I'm using logstash as output. Here's my output configuration (30-elasticsearch-output.conf): > output { > if [@metadata][beat] { > elasticsearch { > hosts =\> ["[http://10.0.101.101:9200](http://10.0.101.101:9200)"] > manage\_template =\> false > index =\> "%{[@metadata][beat]}-%{+YYYY.MM.dd}" > document\_type =\> "%{[@metadata][type]}" > } > } else { > elasticsearch { hosts =\> ["10.0.101.101:9200"] } > stdout { codec =\> rubydebug } > } > } ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 8, 2016, 10:07pm UTC](https://discuss.elastic.co/t/es-5-0-new-installation-question/65405/4 "2016-11-08T22:07:35Z")
And do you _know_ that data is reaching the output? Do things show if you use a stdout? ---
**Author:** ![Diggy](https://avatars.discourse-cdn.com/v4/letter/d/e99b99/32.png) [@Diggy](https://discuss.elastic.co/u/Diggy)\ **Post date:** [November 9, 2016, 3:39pm UTC](https://discuss.elastic.co/t/es-5-0-new-installation-question/65405/5 "2016-11-09T15:39:54Z")
Actually, I don't know. If I've followed installation instructions to-the-letter, but used various config files from the old installation, maybe that's where the problem lies. I've posted the various configs on Pastebin ([http://pastebin.com/dcEbc32k](http://pastebin.com/dcEbc32k)). I would most appreciate it if someone could take a look. That way, either a misconfig will be uncovered, or it'll rule out that that's where the problem lies. With thanks. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 9, 2016, 3:51pm UTC](https://discuss.elastic.co/t/es-5-0-new-installation-question/65405/6 "2016-11-09T15:51:49Z")
You should add a stdout to check 🙂 ---
**Author:** ![Diggy](https://avatars.discourse-cdn.com/v4/letter/d/e99b99/32.png) [@Diggy](https://discuss.elastic.co/u/Diggy)\ **Post date:** [November 9, 2016, 4:19pm UTC](https://discuss.elastic.co/t/es-5-0-new-installation-question/65405/7 "2016-11-09T16:19:25Z")
OK. But, er (shuffling feet, looking sheepish), how do I do that? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 9, 2016, 10:24pm UTC](https://discuss.elastic.co/t/es-5-0-new-installation-question/65405/8 "2016-11-09T22:24:24Z")
It's totally ok to ask that 😃 ```auto output { stdout { codec => rubydebug } } ``` ---
**Author:** ![Diggy](https://avatars.discourse-cdn.com/v4/letter/d/e99b99/32.png) [@Diggy](https://discuss.elastic.co/u/Diggy)\ **Post date:** [November 9, 2016, 10:27pm UTC](https://discuss.elastic.co/t/es-5-0-new-installation-question/65405/9 "2016-11-09T22:27:22Z")
Thanks so much. I'm taking it I add this to my logstash output config? And I should access, or see, output where? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 9, 2016, 11:00pm UTC](https://discuss.elastic.co/t/es-5-0-new-installation-question/65405/10 "2016-11-09T23:00:51Z")
Yeah add it to your config, it'll show the output of your pipeline to the console, aka stdout. ---
**Author:** ![Diggy](https://avatars.discourse-cdn.com/v4/letter/d/e99b99/32.png) [@Diggy](https://discuss.elastic.co/u/Diggy)\ **Post date:** [November 10, 2016, 3:22pm UTC](https://discuss.elastic.co/t/es-5-0-new-installation-question/65405/11 "2016-11-10T15:22:43Z")
> [@warkolm](#): > > output { > stdout { > codec =\> rubydebug > } > } OK. Once added, and services restarted, am I supposed to see output flowing to stdout (I don't, as of now), or must I do something else? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 8, 2016, 3:23pm UTC](https://discuss.elastic.co/t/es-5-0-new-installation-question/65405/12 "2016-12-08T15:23:05Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.