Kibana: Error "Cannot find module 'babel-runtime/core-js/object/keys'" when starting Kibana-4.2.0

Created on 5 Nov 2015 · 7Comments · Source: elastic/kibana

I'm trying to start vanilla Kibana-4.2.0-linux-x64 downloaded from the homepage, but run into the following.

The machine in question is an Ubuntu 14.04.1 and has some other node-js processes running which are installed via Ubuntu packages, is there some cross-dependency to other versions of required packages?

Tried searching for other occurrences of this error, but Google did not show any instances of such problems...

~/kibana-4.2.0-linux-x64$ bin/kibana

Error: Cannot find module 'babel-runtime/core-js/object/keys'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Module._compile (module.js:460:26)
    at normalLoader (/home/labuser/kibana-4.2.0-linux-x64/node_modules/babel-core/lib/api/register/node.js:199:5)
    at Object.require.extensions.(anonymous function) [as .js] (/home/labuser/kibana-4.2.0-linux-x64/node_modules/babel-core/lib/api/register/node.js:216:7)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/home/labuser/kibana-4.2.0-linux-x64/node_modules/request/request.js:3:12)
    at Module._compile (module.js:460:26)
    at Module._extensions..js (module.js:478:10)
    at Object.require.extensions.(anonymous function) [as .js] (/home/labuser/kibana-4.2.0-linux-x64/node_modules/babel-core/lib/api/register/node.js:214:7)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)

Source

centic9

Most helpful comment

I ran into the exact same error when running the babel transpiled grunt tasks from inside Intellij. The root problem seemed to be that when loading Intellij's own grunt tasks, it was looking for the babel libs in my global node_modules instead of the one in my local project. I fixed it by installing babel-runtime and babel-core globally. It's a shot in the dark, but you might try to see if that fixes it. It's not a real solution, but it would at least tell us if this is a path problem.

Bargs on 5 Nov 2015

👍6

All 7 comments

FYI, there is a similar discussion at https://discuss.elastic.co/t/kibana-4-2-0-does-not-start-could-not-find-files-for-the-given-pattern-s/33840

centic9 on 5 Nov 2015

Bargs on 5 Nov 2015

👍6

Thanks for the tip!

Installing the modules globally did not change the error message. If I install the module locally in the kibana directory, I got some error from a tool running on the same machine, but after fixing that kibana starts. So it seems that the bundled babel is not working sometimes?

centic9 on 6 Nov 2015

It seems most of this was caused by a local tool interfering with node-js processes, after stopping it and restarting the installation it did work for me.

centic9 on 6 Nov 2015

👍2

@centic9 Glad you got it to work! Are there any details you could provide on the tool you were using? I'm interested in why conflicts might be occurring since other users seem to be having similar problems.

Bargs on 6 Nov 2015

Hi, sure, I was testing a pre-release of the Ruxit Node-JS Agent, a performance monitoring tool, it seems it interfered with loading of node-js modules in a bad way.

centic9 on 7 Nov 2015

Gotcha, thanks for the extra info!

Bargs on 9 Nov 2015

Was this page helpful?

0 / 5 - 0 ratings