Wonder what may cause this when attempting to launch kibana 6.8.3 after patching up from kibana 5.6
{
"type": "log",
"@timestamp": "2019-10-08T10:35:57Z",
"tags": [
"fatal",
"root"
],
"pid": 17519,
"message": "TypeError: settings is not a function\n at /usr/share/kibana/src/legacy/core_plugins/elasticsearch/index.js:91:29\n at deprecation (/usr/share/kibana/src/deprecation/create_transform.js:36:7)\n at arrayEach (/usr/share/kibana/node_modules/lodash/index.js:1315:13)\n at /usr/share/kibana/node_modules/lodash/index.js:3393:13\n at /usr/share/kibana/src/deprecation/create_transform.js:35:25\n at getSettings (/usr/share/kibana/src/plugin_discovery/plugin_config/settings.js:31:10)"
}
Could you share your kibana config, the elasticsearch version you are using, the kibana logs and what are the kibana indexes your elasticsearch instance has ?
@tlagocosta sort of the same, the same error only not the same resolution. Used to utilize a local tribe elastic node to connect to two v.5.6 ES clusters. Both clusters are now upgraded to v.6.8 and one kibana v.6.8 instance now runs directly to one cluster holding the original kibana index.
Now I'm trying to run another kibana v.6.8 directly to the other ES cluster without the original kibana index, only I have copied the v.5.6 index and configured kibana to this in this ES cluster in order to try and preserve the parts of saved objects from this ES cluster. Only even with a direct local elastic node member of this single ES cluster this kibana instance still complains like initailly when using tribe nodes.
This kibana config (which is similar to the other working):
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.