Kibana version: 7.2.0-1
Elasticsearch version: 7.2.0
Server OS version: CentOS release 6.9 (Final)
Original install method (e.g. download page, yum, from source, etc.):
Tried both rpm manually and yum
Describe the bug:
Kibana is not starting after upgrade to 7.2.0-1
Steps to reproduce:
Expected behavior:
Kibana starts
Provide logs and/or server output (if relevant):
/var/log/kibana/kibana.stderr
FATAL Error: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /usr/share/kibana/node_modules/@elastic/nodegit/build/Release/nodegit.node)
/var/log/kibana/kibana.stdout
{
"type": "log",
"@timestamp": "2019-07-05T05:56:18Z",
"tags": ["fatal", "root"],
"pid": 12563,
"message": "Error: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /usr/share/kibana/node_modules/@elastic/nodegit/build/Release/nodegit.node)\n at Object.Module._extensions..node (internal/modules/cjs/loader.js:718:18)\n at Module.load (internal/modules/cjs/loader.js:599:32)\n at tryModuleLoad (internal/modules/cjs/loader.js:538:12)\n at Function.Module._load (internal/modules/cjs/loader.js:530:3)\n at Module.require (internal/modules/cjs/loader.js:637:17)\n at require (internal/modules/cjs/helpers.js:22:18)\n at Object.(/usr/share/kibana/node_modules/@elastic/nodegit/dist/nodegit.js:12:12)\n at Module._compile (internal/modules/cjs/loader.js:689:30)\n at Module._compile (/usr/share/kibana/node_modules/pirates/lib/index.js:99:24)\n at Module._extensions..js (internal/modules/cjs/loader.js:700:10)\n at Object.newLoader [as .js] (/usr/share/kibana/node_modules/pirates/lib/index.js:104:7)\n at Module.load (internal/modules/cjs/loader.js:599:32)\n at tryModuleLoad (internal/modules/cjs/loader.js:538:12)\n at Function.Module._load (internal/modules/cjs/loader.js:530:3)\n at Module.require (internal/modules/cjs/loader.js:637:17)\n at require (internal/modules/cjs/helpers.js:22:18)\n at Object.require (/usr/share/kibana/x-pack/plugins/code/server/git_operations.js:10:19)\n at Module._compile (internal/modules/cjs/loader.js:689:30)\n at Module._compile (/usr/share/kibana/node_modules/pirates/lib/index.js:99:24)\n at Module._extensions..js (internal/modules/cjs/loader.js:700:10)\n at Object.newLoader [as .js] (/usr/share/kibana/node_modules/pirates/lib/index.js:104:7)\n at Module.load (internal/modules/cjs/loader.js:599:32)"
}
Additional Info:
This is a new issue introduced in Kibana 7.2.0-1, Kibana starts without any issues upto 7.1.1-1
Pinging @elastic/kibana-operations
Pinging @elastic/code
it's already fixed and will be released in 7.2.1
Is there a workaround for this until release of 7.2.1?
@markniel
Waiting for 7.2.1 is the best option. However, if you are blocked by this issue, try the following steps, which will involve some changes in the code.
in <kibana-folder>/x-pack/plugins/code/index.js file, comment out line 11:
const init_1 = require("./server/init"); ===> // const init_1 = require("./server/init");
and comment line 83:
init: init_1.init, ===> // init: init_1.init,
Then the kibana should be able to start normally.
Commenting out those two lines and starting kibana has me unblocked.
Thanks so much!
Commenting out those two lines and starting kibana has me unblocked.
Thanks so much!
Glad to know the blocker has been removed @markniel. But again, I would suggest upgrading Kibana to 7.2.1 in the coming release to resolve this problem.
Most helpful comment
@markniel
Waiting for 7.2.1 is the best option. However, if you are blocked by this issue, try the following steps, which will involve some changes in the code.
in
<kibana-folder>/x-pack/plugins/code/index.jsfile, comment out line 11:const init_1 = require("./server/init");===>// const init_1 = require("./server/init");and comment line 83:
init: init_1.init,===>// init: init_1.init,Then the kibana should be able to start normally.