Windows Server 2012 R2 Discover (5.1.1)

Tried to use Kibana on Windows Server 2012R2, but Discover and Dashboard does not work. Is this a known problem? Using 5.1.1.

What is the error you're getting?

I am not getting any error. It just does not give any information.
Visualize, Timelion, Dev Tools and Management does work fine.

Which browser are you using? Have you checked the server console to see if anything is reported there?

I have tried latest version of IE, Chrome and Firefox. All without any result. I do not know what you mean with server console. How can I check that?

First of all, have you checked the developer console for errors? In Chrome, you can open this by clicking on the menu, then "More Tools", then "Developer Tools".

Ok, I am not able to check now. I will check developer console tomorrow. I'll let you know. Thanks!

Chrome console gives following error:

PUT http://localhost:5601/elasticsearch/.kibana/_mapping/search 400 (Bad Request)
(anonymous) @ commons.bundle.js?v=14588:37
sendReq @ commons.bundle.js?v=14588:37
serverRequest @ commons.bundle.js?v=14588:37
processQueue @ commons.bundle.js?v=14588:38
(anonymous) @ commons.bundle.js?v=14588:38
$eval @ commons.bundle.js?v=14588:39
$digest @ commons.bundle.js?v=14588:39
(anonymous) @ commons.bundle.js?v=14588:39
completeOutstandingRequest @ commons.bundle.js?v=14588:36
(anonymous) @ commons.bundle.js?v=14588:36
commons.bundle.js?v=14588:38 Error: [illegal_argument_exception] mapper [version] cannot be changed from type [long] to [integer]
at respond (kibana.bundle.js?v=14588:14)
at checkRespForFailure (kibana.bundle.js?v=14588:14)
at kibana.bundle.js?v=14588:1
at processQueue (commons.bundle.js?v=14588:38)
at commons.bundle.js?v=14588:38
at Scope.$eval (commons.bundle.js?v=14588:39)
at Scope.$digest (commons.bundle.js?v=14588:39)
at Scope.$apply (commons.bundle.js?v=14588:39)
at done (commons.bundle.js?v=14588:37)
at completeRequest (commons.bundle.js?v=14588:37)

The [string] field is deprecated, please use [text] or [keyword] instead on [title], The [string] field is deprecated, please use [text] or [keyword] instead on [description], The [string] field is deprecated, please use [text] or [keyword] instead on [panelsJSON], The [string] field is deprecated, please use [text] or [keyword] instead on [optionsJSON], The [string] field is deprecated, please use [text] or [keyword] instead on [uiStateJSON], The [string] field is deprecated, please use [text] or [keyword] instead on [timeTo], The [string] field is deprecated, please use [text] or [keyword] instead on [timeFrom], The [string] field is deprecated, please use [text] or [keyword] instead on [display], The [string] field is deprecated, please use [text] or [keyword] instead on [searchSourceJSON]

Hi Lukas, is this a known error or am I doing something wrong? Best regards, Mario

Which version of Elasticsearch are you using, and are you able to provide your mapping? Thanks!

Version is 5.1.1.
I am not an Elasticsearch specialist, but what do you mean with mapping?

Are you getting this error when you first visit Kibana without having set up any index patterns or anything?

No, I am able to setup index patterns. I am also able to use Visualize/Tile map or Visualize/Vertical bar chart. When clicking on Discover or Dashboard though, nothing happens. But creates an error log in the console. This is the case with the latest versions of IE, Chrome and Firefox.
I have to mention also that Windows 2012R2 is running in an Azure environment.

Hmm, this is really weird. Are you getting any errors in the terminal in which you're running Kibana (the actual file you're executing, outside of the context of the browser).

Kibana console
Windows PowerShell
Copyright (C) 2014 Microsoft Corporation. All rights reserved.

PS C:\Users\Vitagion> e:
PS E:> cd .\kibana-5.1.1-windows-x86
PS E:\kibana-5.1.1-windows-x86> .\bin\kibana.bat
log [10:15:02.943] [info][status][plugin:kibana@5.1.1] Status changed from uninitialized to green - Ready
log [10:15:03.071] [info][status][plugin:elasticsearch@5.1.1] Status changed from uninitialized to yellow - Waiting
for Elasticsearch
log [10:15:03.102] [info][status][plugin:console@5.1.1] Status changed from uninitialized to green - Ready
log [10:15:05.163] [info][status][plugin:timelion@5.1.1] Status changed from uninitialized to green - Ready
log [10:15:05.179] [info][listening] Server running at http://localhost:5601
log [10:15:05.179] [info][status][ui settings] Status changed from uninitialized to yellow - Elasticsearch plugin is
yellow
log [10:15:05.194] [info][status][plugin:elasticsearch@5.1.1] Status changed from yellow to green - Kibana index rea
dy
log [10:15:05.194] [info][status][ui settings] Status changed from yellow to green - Ready

Logstash console
Windows PowerShell
Copyright (C) 2014 Microsoft Corporation. All rights reserved.

PS C:\Users\Vitagion> e:
PS E:> cd .\logstash-5.1.1
PS E:\logstash-5.1.1> .\bin\logstash -f sonicwall.conf
Could not find log4j2 configuration at path /logstash-5.1.1/config/log4j2.properties. Using default config which logs to
console
13:32:12.098 [Ruby-0-Thread-10: E:/logstash-5.1.1/vendor/bundle/jruby/1.9/gems/logstash-input-syslog-3.2.0/lib/logstash/
inputs/syslog.rb:101] INFO logstash.inputs.syslog - Starting syslog udp listener {:address=>"0.0.0.0:514"}
13:32:12.106 [Ruby-0-Thread-11: E:/logstash-5.1.1/vendor/bundle/jruby/1.9/gems/logstash-input-syslog-3.2.0/lib/logstash/
inputs/syslog.rb:105] INFO logstash.inputs.syslog - Starting syslog tcp listener {:address=>"0.0.0.0:514"}
13:32:14.076 [[main]-pipeline-manager] INFO logstash.outputs.elasticsearch - Elasticsearch pool URLs updated {:changes=

{:removed=>[], :added=>["http://localhost:9200"]}}
13:32:14.077 [[main]-pipeline-manager] INFO logstash.outputs.elasticsearch - Running health check to see if an Elastics
earch connection is working {:url=>#<URI::HTTP:0x482ea011 URL:http://localhost:9200>, :healthcheck_path=>"/"}
13:32:14.757 [[main]-pipeline-manager] WARN logstash.outputs.elasticsearch - Restored connection to ES instance {:url=>
#<URI::HTTP:0x482ea011 URL:http://localhost:9200>}
13:32:14.759 [[main]-pipeline-manager] INFO logstash.outputs.elasticsearch - Using mapping template from {:path=>nil}
13:32:14.964 [[main]-pipeline-manager] INFO logstash.outputs.elasticsearch - Attempting to install template {:manage_te
mplate=>{"template"=>"logstash-", "version"=>50001, "settings"=>{"index.refresh_interval"=>"5s"}, "mappings"=>{"defaul
t
"=>{"_all"=>{"enabled"=>true, "norms"=>false}, "dynamic_templates"=>[{"message_field"=>{"path_match"=>"message", "matc
h_mapping_type"=>"string", "mapping"=>{"type"=>"text", "norms"=>false}}}, {"string_fields"=>{"match"=>"
", "match_mappin
g_type"=>"string", "mapping"=>{"type"=>"text", "norms"=>false, "fields"=>{"keyword"=>{"type"=>"keyword"}}}}}], "properti
es"=>{"@timestamp"=>{"type"=>"date", "include_in_all"=>false}, "@version"=>{"type"=>"keyword", "include_in_all"=>false},
"geoip"=>{"dynamic"=>true, "properties"=>{"ip"=>{"type"=>"ip"}, "location"=>{"type"=>"geo_point"}, "latitude"=>{"type"=
"half_float"}, "longitude"=>{"type"=>"half_float"}}}}}}}}
13:32:14.981 [[main]-pipeline-manager] INFO logstash.outputs.elasticsearch - New Elasticsearch output {:class=>"LogStas
h::Outputs::ElasticSearch", :hosts=>["localhost"]}
13:32:15.052 [[main]-pipeline-manager] INFO logstash.filters.geoip - Using geoip database {:path=>"/E:/GL/Geolite2-City
.mmdb"}
13:32:15.371 [[main]-pipeline-manager] INFO logstash.pipeline - Starting pipeline {"id"=>"main", "pipeline.workers"=>2,
"pipeline.batch.size"=>125, "pipeline.batch.delay"=>5, "pipeline.max_inflight"=>250}
13:32:15.404 [[main]-pipeline-manager] INFO logstash.pipeline - Pipeline main started
13:32:15.455 [Api Webserver] INFO logstash.agent - Successfully started Logstash API endpoint {:port=>9600}

Could you try wiping your .kibana index? I'm thinking maybe it still has old mappings or something.

I tried this several times but does not solve the problem.

5.1.2 has been released, are you able to upgrade and try that instead?

I already tried that. Same results.

Sorry for all the back and forth, and thanks for being patient.

Could you visit the Console app and make the following requests, and copy/paste the responses here?

GET .kibana/search/_mapping

GET .kibana/search/_search

You can get to the Console app by clicking on the wrench icon in the left nav of the application:

Thanks!