Hi all,
currently we have a problem with Kibana: After deleting the default index pattern in Kibana, we are not able to create this default pattern again. Our default pattern is called "packets-", if we try to create it again our Kibana shows only "blank" sites in Discover, Visualize, Dashboards, Management and Dev-Tools. If we try to create the index named "packets-2016-" or "packets-2017-*" it will works fine. Our migration from Kibana 4.6 to 5.0 is already a few months ago and worked without problems.
With the default index pattern "packets-*" we receive only "blank" sites with the following error message in browser debugger:
Error: Request to Elasticsearch failed: "Bad Request"
KbnError@http://127.0.0.1:5601/bundles/commons.bundle.js?v=14438:63:26224
errors.RequestFailure@http://127.0.0.1:5601/bundles/commons.bundle.js?v=14438:63:27413
exports.default/</<@http://127.0.0.1:5601/bundles/kibana.bundle.js?v=14438:26:14736
processQueue@http://127.0.0.1:5601/bundles/commons.bundle.js?v=14438:38:23621
scheduleProcessQueue/<@http://127.0.0.1:5601/bundles/commons.bundle.js?v=14438:38:23888
$RootScopeProvider/this.$get</Scope.prototype.$eval@http://127.0.0.1:5601/bundles/commons.bundle.js?v=14438:39:4607
$RootScopeProvider/this.$get</Scope.prototype.$digest@http://127.0.0.1:5601/bundles/commons.bundle.js?v=14438:39:2343
$RootScopeProvider/this.$get</Scope.prototype.$apply@http://127.0.0.1:5601/bundles/commons.bundle.js?v=14438:39:5026
done@http://127.0.0.1:5601/bundles/commons.bundle.js?v=14438:37:25016
completeRequest@http://127.0.0.1:5601/bundles/commons.bundle.js?v=14438:37:28702
createHttpBackend/</xhr.onload@http://127.0.0.1:5601/bundles/commons.bundle.js?v=14438:37:29634
1 commons.bundle.js:38:11454
consoleLog/< http://127.0.0.1:5601/bundles/commons.bundle.js:38:11454
$ExceptionHandlerProvider/this.$get</< http://127.0.0.1:5601/bundles/commons.bundle.js:37:17828
processQueue http://127.0.0.1:5601/bundles/commons.bundle.js:38:23742
scheduleProcessQueue/< http://127.0.0.1:5601/bundles/commons.bundle.js:38:23888
$RootScopeProvider/this.$get</Scope.prototype.$eval http://127.0.0.1:5601/bundles/commons.bundle.js:39:4607
$RootScopeProvider/this.$get</Scope.prototype.$digest http://127.0.0.1:5601/bundles/commons.bundle.js:39:2343
$RootScopeProvider/this.$get</Scope.prototype.$apply http://127.0.0.1:5601/bundles/commons.bundle.js:39:5026
done http://127.0.0.1:5601/bundles/commons.bundle.js:37:25016
completeRequest http://127.0.0.1:5601/bundles/commons.bundle.js:37:28702
createHttpBackend/</xhr.onload http://127.0.0.1:5601/bundles/commons.bundle.js:37:29634
It seems that this problem is related to this two Issues:
Some additional information:
- Kibana version: 5.0.0
- Elasticsearch version: 5.0.0
- Server OS version: Ubuntu 16.04.1 LTS x64
- Browser version: Chrome Version 54.0.2840.100 (64-bit)
- Browser OS version: Mac OS
- Original install method (e.g. download page, yum, from source, etc.): kibana-5.0.0-linux-x86_64.tar.gz
Seems to be a new bug... any idea how to rebuild our default index pattern in Kibana? We tried to delete the whole ".kibana" index manually but without success.
Many thanks!
Regards,
Manuel