Reg: Kibana build from source in Linux/RHEL environment

Hi,

I am trying to build Kibana 4.5 from source in Linux/RHEL environment following the steps given here:

I am facing below issue when I execute the command 'npm start' :

./bin/kibana --dev

sh: ./bin/kibana: Permission denied

npm ERR! Linux 3.10.0-327.el7.x86_64
npm ERR! argv "/home/ec2-user/.nvm/versions/node/v4.4.7/bin/node" "/home/ec2-user/.nvm/versions/node/v4.4.7/bin/npm" "start"
npm ERR! node v4.4.7
npm ERR! npm v2.15.8
npm ERR! code ELIFECYCLE
npm ERR! kibana@4.5.2-snapshot start: ./bin/kibana --dev
npm ERR! Exit status 126
npm ERR!
npm ERR! Failed at the kibana@4.5.2-snapshot start script './bin/kibana --dev'.
npm ERR! This is most likely a problem with the kibana package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! ./bin/kibana --dev
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs kibana
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls kibana
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /home/ec2-user/Kibana-src/kibana-4.5/npm-debug.log

It would be really great, if you help me resolve this issue.

Request your kind support.

Thanks,
V.Vasanth

It seems you're trying to run the environment on a Amazon AWS Linux instance (judging based on the file path containing ec2-user). Do you have a way of running the server/creating a build on a local machine such as a Linux VM?

Regardless, an error like that would indicate that maybe the script file lost the executable permissions.

Hi Tim,

Thanks for your response!!!

We have set our environment in Amazon AWS, so would like to set it up in AWS.

FYI, I am able to build Kibana 4.4 successfully in the same environment. Getting the permission denied error, only with the version 4.5.

Could you let me know how to set right the executable permissions?

Thanks,
V.Vasanth

Sure. The file needs 0755 permission and the owner must be the user ID of the user that will run the process.

So if you do ls -l on the file, you should see something like:

ls -l bin/kibana
-rwxr-xr-x 1 tsullivan  staff  598 Jul  5 06:36 bin/kibana

If you need to fix the permissions, you can use chmod 755 bin/kibana. But the file permissions are correct in the git repository, so I'm unsure why you would be running into this error if you followed all the steps from the Contributing guide. If you keep getting stuck, you might want to try re-cloning, and be sure to use the same user for all the steps.