# Dicover tab is defunt when loading visualizations using CURL at command line **URL:** \ **Category:** Kibana\ **Created:** [May 18, 2017, 3:08pm UTC](https://discuss.elastic.co/t/dicover-tab-is-defunt-when-loading-visualizations-using-curl-at-command-line/86290 "2017-05-18T15:08:29Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![raazeev64](https://avatars.discourse-cdn.com/v4/letter/r/7feea3/32.png) [@raazeev64](https://discuss.elastic.co/u/raazeev64)\ **Post date:** [May 18, 2017, 3:08pm UTC](https://discuss.elastic.co/t/dicover-tab-is-defunt-when-loading-visualizations-using-curl-at-command-line/86290/1 "2017-05-18T15:08:29Z")
I have been trying to achieve one click delpoyment of ELK(with some sample dashboard) using some shell scripts. Things work out fine except for glitches at the end. The discover tab does not load anything at all. It appears to be defunct. Got to see this bad request in the logs for Kibana - > {"type":"response","@timestamp":"2017-05-18T14:49:59Z","tags":,"pid":12961,"method":"put","statusCode":400,"req":{"url":"/es\_admin/.kibana/\_mapping/search","method":"put","headers":{"host":"localhost:5601","connection":"keep-alive","content-length":"271","accept":"application/json, text/plain, _/_","origin":"[http://localhost:5601](http://localhost:5601)","kbn-version":"5.3.0","user-agent":"Mozilla/5.0 (X11; Fedora; Linux x86\_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36","content-type":"application/json","referer":"[http://localhost:5601/app/kibana","accept-encoding":"gzip](http://localhost:5601/app/kibana%22,%22accept-encoding%22:%22gzip), deflate, sdch, br","accept-language":"en-US,en;q=0.8"},"remoteAddress":"127.0.0.1","userAgent":"127.0.0.1","referer":"[http://localhost:5601/app/kibana"},"res":{"statusCode":400,"responseTime":249,"contentLength":9},"message":"PUT](http://localhost:5601/app/kibana%22%7D,%22res%22:%7B%22statusCode%22:400,%22responseTime%22:249,%22contentLength%22:9%7D,%22message%22:%22PUT) /es\_admin/.kibana/\_mapping/search 400 249ms - 9.0B"} Had dumped the visualizations/dashboards using the following script - ``` curl -XPUT localhost:9200/.kibana/visualization/example4?pretty -d@example4.json curl -XPUT localhost:9200/.kibana/dashboard/example?pretty -d@dashboard.json ``` Had imported these JSONs earlier from a running stack. ---
**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\ **Post date:** [May 18, 2017, 3:22pm UTC](https://discuss.elastic.co/t/dicover-tab-is-defunt-when-loading-visualizations-using-curl-at-command-line/86290/2 "2017-05-18T15:22:56Z")
Hi @raazeev64, it looks like Kibana fails to update the mapping for the `.kibana` index. When importing the JSON upon deployment, make sure to dump and import the mapping beforehand. Otherwise the dynamic mapping algorithm of Elasticsearch might incorrectly guess some types which leads to mapping conflicts later. ---
**Author:** ![raazeev64](https://avatars.discourse-cdn.com/v4/letter/r/7feea3/32.png) [@raazeev64](https://discuss.elastic.co/u/raazeev64)\ **Post date:** [May 19, 2017, 6:47am UTC](https://discuss.elastic.co/t/dicover-tab-is-defunt-when-loading-visualizations-using-curl-at-command-line/86290/3 "2017-05-19T06:47:03Z")
I tried updating the mapping beforehand. `curl -XPUT localhost:9200/.kibana/_mapping/config -d@kibanamapping.json` But the error persists. Getting the same for timeliontab too. Can we get to see the kibana server logs somewhere? ---
**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\ **Post date:** [May 19, 2017, 9:31am UTC](https://discuss.elastic.co/t/dicover-tab-is-defunt-when-loading-visualizations-using-curl-at-command-line/86290/4 "2017-05-19T09:31:21Z")
The error message from your initial post indicates that the mapping for the `search` type causes that failure. Try dumping the mapping for all types, not just the `config` type. How you access the Kibana server log depends on the way you deploy it. ---
**Author:** ![raazeev64](https://avatars.discourse-cdn.com/v4/letter/r/7feea3/32.png) [@raazeev64](https://discuss.elastic.co/u/raazeev64)\ **Post date:** [May 20, 2017, 1:58pm UTC](https://discuss.elastic.co/t/dicover-tab-is-defunt-when-loading-visualizations-using-curl-at-command-line/86290/5 "2017-05-20T13:58:53Z")
Thanks @weltenwort. I got it working. Dumped the mapping for all types. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 17, 2017, 1:59pm UTC](https://discuss.elastic.co/t/dicover-tab-is-defunt-when-loading-visualizations-using-curl-at-command-line/86290/6 "2017-06-17T13:59:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.