# Kibana source installation error

**URL:** <https://discuss.elastic.co/t/kibana-source-installation-error/83986>\
**Category:** Kibana\
**Created:** [April 28, 2017, 9:08am UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986 "2017-04-28T09:08:44Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![sravya](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@sravya](https://discuss.elastic.co/u/sravya)\
**Post date:** [April 28, 2017, 9:08am UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986/1 "2017-04-28T09:08:45Z")

</div>

# git clone [https://github.com/root/kibana.git](https://github.com/root/kibana.git) kibana

Initialized empty Git repository in /opt/kibana/.git/  
error: Couldn't resolve host '[github.com](http://github.com)' while accessing [https://github.com/root/kibana.git/info/refs](https://github.com/root/kibana.git/info/refs)

fatal: HTTP request failed

-\> when i searched for this error, i got 2 solutions, 1 was to check git file permissions which didnot help me out and another one was to update my git version(current version 1.7.1)

- i have tried "git clone [https://github.com/git/git](https://github.com/git/git)" but even this didnot work out also yum,wget arent working in our box  
what else can i try to resolve this issue?

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [April 28, 2017, 7:48pm UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986/2 "2017-04-28T19:48:58Z")

</div>

Where did these instructions come from?

[https://github.com/root](https://github.com/root) is not the Elastic organization, that's just some random user on Github.

Download the products from here: [https://www.elastic.co/products](https://www.elastic.co/products)

---

<div class="post-metadata">

**Author:** ![sravya](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@sravya](https://discuss.elastic.co/u/sravya)\
**Post date:** [May 2, 2017, 11:43am UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986/3 "2017-05-02T11:43:35Z")

</div>

we are looking into installing Kibana through source , can you please provide any other or detailed links on it?

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [May 2, 2017, 11:01pm UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986/4 "2017-05-02T23:01:38Z")

</div>

Sure, you can just do:

```auto
git clone https://github.com/elastic/kibana.git kibana
cd kibana

```

You'll need to have your own distribution of NodeJS and you'll need to install all the NodeJS packages. The full instructions are here: [https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#setting-up-your-development-environment](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#setting-up-your-development-environment)

What is your reason for wanting to install Kibana through source? There are way more steps in that path versus downloading the distribution. Based on your initial comment, you seem to have some DNS problems (is the machine firewalled?), as well as issues grasping the basics of GitHub.

---

<div class="post-metadata">

**Author:** ![sravya](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@sravya](https://discuss.elastic.co/u/sravya)\
**Post date:** [May 16, 2017, 12:32pm UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986/5 "2017-05-16T12:32:37Z")

</div>

hi!  
i was able to go ahead with the steps:

1. Install git from yum
2. I installed Node.Js from [https://nodejs.org/download/release/latest/](https://nodejs.org/download/release/latest/)  
3.git clone [https://github.com/elastic/kibana.git](https://github.com/elastic/kibana.git) kibana
3. Installed NVM from curl -o- [https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh](https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh) | bash
4. nvm install "$(cat .node-version)"
5. npm install
6. npm run elasticsearch

and then i got npm errors

npm run elasticsearch  
npm ERR! Linux 3.10.0-327.el7.x86\_64  
npm ERR! argv "/root/.nvm/versions/node/v7.10.0/bin/node" "/root/.nvm/versions/node/v7.10.0/bin/npm" "run" "elasticsearch"  
npm ERR! node v7.10.0  
npm ERR! npm v4.2.0  
npm ERR! path /root/package.json  
npm ERR! code ENOENT  
npm ERR! errno -2  
npm ERR! syscall open

npm ERR! enoent ENOENT: no such file or directory, open '/root/package.json'  
npm ERR! enoent ENOENT: no such file or directory, open '/root/package.json'  
npm ERR! enoent This is most likely not a problem with npm itself  
npm ERR! enoent and is related to npm not being able to find a file.  
npm ERR! enoent

npm ERR! Please include the following file with any support request:  
npm ERR! /root/.npm/\_logs/2017-05-08T15\_10\_31\_611Z-debug.log

here is log file details:  
tail -f /root/kibana/KIBANA/npm-debug.log  
23 error If you do, this is most likely a problem with the kibana package,  
23 error not with npm itself.  
23 error Tell the author that this fails on your system:  
23 error grunt esvm:dev:keepalive  
23 error You can get information on how to open an issue for this project with:  
23 error npm bugs kibana  
23 error Or if that isn't available, you can get their info via:  
23 error npm owner ls kibana  
23 error There is likely additional logging output above.  
24 verbose exit [1, true]

could not get what to do

---

<div class="post-metadata">

**Author:** ![FareehaNaaz](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@FareehaNaaz](https://discuss.elastic.co/u/FareehaNaaz)\
**Post date:** [May 16, 2017, 12:41pm UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986/6 "2017-05-16T12:41:30Z")

</div>

hi!  
i was looking for the same and i get the same errors after going through all the dependecies and i havent found any solution for this, i have come up with 3 suggestion after searching nearly 20 different links, **1) deleting esvm dir 2) degarding node version and 3) running "npm install grunt -keep alive --save-dev**, but neither of these helped me!

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [May 16, 2017, 4:41pm UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986/7 "2017-05-16T16:41:08Z")

</div>

> [@sravya](#):
>
> npm run elasticsearch  
> npm ERR! Linux 3.10.0-327.el7.x86\_64  
> npm ERR! argv "/root/.nvm/versions/node/v7.10.0/bin/node" "/root/.nvm/versions/node/v7.10.0/bin/npm" "run" "elasticsearch"  
> npm ERR! node v7.10.0  
> npm ERR! npm v4.2.0  
> npm ERR! path /root/package.json  
> npm ERR! code ENOENT

Based on the command you used to clone, I presume the location to the package.json file is `/root/kibana`, and that's where you want to run `npm run elasticsearch` - the location that you clone it from.

> [@sravya](#):
>
> tail -f /root/kibana/KIBANA/npm-debug.log

Why are you not cloning the repo in a user home directory? The dev environment is meant for a user to develop with, not to run as a production environment or in a container.

If you need to make customizations to Kibana before running it in production, you should:

1. File an enhancement issue to see if the thing you need can be added into the core source code, but first search the current issues to see if there is something already open for it.
2. If you can't wait for the enhancement to go into core, or if you just need to build Kibana with your own NPM mirror, you should fork the repo in Github and clone your own fork

- Develop on this fork in an actual development environment, not a container
- Create a build in this environment. The documentation has instructions on how to do this.
- Deploy the build to your production environment.
- Use an actual build of (one that matches the version of Kibana) to run in your production environment. In the production environment, you won't want to use `npm run elasticsearch`, which uses a development module called ESVM.

---

<div class="post-metadata">

**Author:** ![sravya](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@sravya](https://discuss.elastic.co/u/sravya)\
**Post date:** [June 3, 2017, 8:54am UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986/8 "2017-06-03T08:54:09Z")

</div>

Hi! iwas trying to create kibana rpm package "npm run build -- --rpm", and ran into this issue.  
Fatal error: Path must be a string. Received true  
npm ERR! code ELIFECYCLE  
npm ERR! errno 1  
npm ERR! kibana@6.0.0-alpha2 build: grunt build "--rpm"  
npm ERR! Exit status 1  
npm ERR!  
npm ERR! Failed at the kibana@6.0.0-alpha2 build script.  
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:  
npm ERR! /home/farya/.npm/\_logs/2017-05-31T10\_36\_12\_445Z-debug.log

i did try upgarding my babel-core@6.10.4 but that agin didnt help me out.

$ npm run build -- --rpm

kibana@6.0.0-alpha2 build /home/farya/kibana  
grunt build "--rpm"  
Running "build" task

Running "clean:build" (clean) task

1 path cleaned.  
Running "clean:target" (clean) task

0 paths cleaned.  
Running "\_build:downloadNodeBuilds" task

Downloading darwin-x86\_64 and corresponding sha  
Downloading linux-x86\_64 and corresponding sha  
Downloading windows-x86\_64 and corresponding sha  
darwin-x86\_64 downloaded and verified  
linux-x86\_64 downloaded and verified  
windows-x86\_64 downloaded and verified  
Running "\_build:extractNodeBuilds" task

Running "copy:devSource" (copy) task  
Created 483 directories, copied 2032 files

Running "clean:devSourceForTestbed" (clean) task

1 path cleaned.  
Running "babel:build" (babel) task

Running "\_build:babelOptions" task

Running "\_build:plugins" task

Running "\_build:data" task

Running "i18nextract:default\_options" (i18nextract) task

Create file: build/i18n\_extract/en.json  
Statistics : empty: 47 (100%) / Updated: 0 / Deleted: 0 / New: 47

Running "\_build:check" task

Running "\_build:packageJson" task

Running "\_build:readme" task

Running "\_build:babelCache" task

Running "\_build:installNpmDeps" task

Running "\_build:notice" task  
Fatal error: Path must be a string. Received true  
npm ERR! code ELIFECYCLE  
npm ERR! errno 1  
npm ERR! kibana@6.0.0-alpha2 build: grunt build "--rpm"  
npm ERR! Exit status 1  
npm ERR!  
npm ERR! Failed at the kibana@6.0.0-alpha2 build script.  
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

# npm ERR! A complete log of this run can be found in: npm ERR! /home/farya/.npm/\_logs/2017-06-01T12\_59\_41\_662Z-debug.log

here is the log file o/p:  
0 info it worked if it ends with ok  
1 verbose cli [ '/home/farya/.nvm/versions/node/v6.10.2/bin/node',  
1 verbose cli '/home/farya/.nvm/versions/node/v6.10.2/bin/npm',  
1 verbose cli 'run',  
1 verbose cli 'build',  
1 verbose cli '--',  
1 verbose cli '--rpm' ]  
2 info using npm@4.6.1  
3 info using node@v6.10.2  
4 verbose run-script ['prebuild', 'build', 'postbuild']  
5 info lifecycle kibana@6.0.0-alpha2~prebuild: kibana@6.0.0-alpha2  
6 silly lifecycle kibana@6.0.0-alpha2~prebuild: no script for prebuild, continuing  
7 info lifecycle kibana@6.0.0-alpha2~build: kibana@6.0.0-alpha2  
8 verbose lifecycle kibana@6.0.0-alpha2~build: unsafe-perm in lifecycle true  
9 verbose lifecycle kibana@6.0.0-alpha2~build: PATH: /home/farya/.nvm/versions/node/v6.10.2/lib/node\_modules/npm/bin/node-gyp-bin:/home/farya/kibana/node\_modules/.bin:/home/farya/.nvm/versions/node/v6.10.2/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/farya/.local/bin:/home/farya/bin:/home/farya/.nvm/versions/node/v6.10.2/bin/grunt  
10 verbose lifecycle kibana@6.0.0-alpha2~build: CWD: /home/farya/kibana  
11 silly lifecycle kibana@6.0.0-alpha2~build: Args: ['-c', 'grunt build "--rpm"']  
12 silly lifecycle kibana@6.0.0-alpha2~build: Returned: code: 1 signal: null  
13 info lifecycle kibana@6.0.0-alpha2~build: Failed to exec build script  
14 verbose stack Error: kibana@6.0.0-alpha2 build: grunt build "--rpm"  
14 verbose stack Exit status 1  
i also tried to edit tasks/build/notice.js by adding console.log({ kibanaDir, noticePath }); after line 22 where noticePath is initialized and the ran npm run build -- --rpm but again i ran into same issue

---

<div class="post-metadata">

**Author:** ![FareehaNaaz](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@FareehaNaaz](https://discuss.elastic.co/u/FareehaNaaz)\
**Post date:** [June 6, 2017, 4:05am UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986/9 "2017-06-06T04:05:20Z")

</div>

Hi!  
i too face the same issue, can anyone guide us on this?

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [June 6, 2017, 4:24pm UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986/10 "2017-06-06T16:24:05Z")

</div>

> [@sravya](#):
>
> i did try upgarding my babel-core@6.10.4 but that agin didnt help me out.

Sounds like you might have some global NPM packages. If you do, those would conflict with the packages specified in the project.

You should not have any global NPM packages installed when developing with Kibana.

This topic has gotten hijacked from the original posting. Please open a new topic with your question if you have new questions to post. Thanks 🙂

---

<div class="post-metadata">

**Author:** ![FareehaNaaz](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@FareehaNaaz](https://discuss.elastic.co/u/FareehaNaaz)\
**Post date:** [June 7, 2017, 5:01am UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986/11 "2017-06-07T05:01:29Z")

</div>

i did try removing all the globally installed npm packages but then again i face the same issue.

---

<div class="post-metadata">

**Author:** ![sravya](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@sravya](https://discuss.elastic.co/u/sravya)\
**Post date:** [June 7, 2017, 10:19am UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986/12 "2017-06-07T10:19:43Z")

</div>

> [@Kibana Package creation issue](https://discuss.elastic.co/t/kibana-package-creation-issue/88149):
>
> Hi! iwas trying to create kibana rpm package "npm run build -- --rpm", and ran into this issue. Fatal error: Path must be a string. Received true npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! kibana@6.0.0-alpha2 build: grunt build "--rpm" npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the kibana@6.0.0-alpha2 build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm …

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [June 7, 2017, 4:20pm UTC](https://discuss.elastic.co/t/kibana-source-installation-error/83986/13 "2017-06-07T16:20:02Z")

</div>


