Skip to content
This repository has been archived by the owner on Mar 20, 2021. It is now read-only.

/sbin/start kibana fails #95

Open
jensskott opened this issue Oct 26, 2016 · 5 comments
Open

/sbin/start kibana fails #95

jensskott opened this issue Oct 26, 2016 · 5 comments

Comments

@jensskott
Copy link

seems the template becomes wrong for the upstart script in /etc/init/kibana.conf

Running ubuntu 14.04 chef 12 kibana 4.6.2 with install package it sets the exec path to
current/bin/kibana, wtich makes the upstart fail.

@jensskott
Copy link
Author

adding
node.default['kibana']['service']['bin_path'] = 'bin/'
makes kibana start

found it in syslog kernel: [ 3504.357099] init: Failed to spawn kibana main process: unable to execute: No such file or directory

@drenalin23
Copy link
Collaborator

@jensskott - in my test kitchen setup it works as expected for me. Are you doing a source install? or using the OS package?
kitchen verify kibana4-nginx-ubuntu-1404
works for me (other than an issue where it isn't seeing nginx listening on 8080 correctly)

@drenalin23
Copy link
Collaborator

What does your run_list look like?

@jensskott
Copy link
Author

jensskott commented Oct 27, 2016

Im using the package install.
The source and release fails due to checksum errors.
They get checksum errors since elastic only presents sha1 checksum and ark wants sha256
so I cant update the checksum to match the downloaded file.

Run List: role[kibana]
Roles: kibana, default
Recipes: accedo-datadog, accedo-datadog::default, accedo-chef, accedo-chef::default, accedo-users, accedo-users::default, accedo-kibana, accedo-kibana::default, datadog::dd-agent, datadog::_install-linux, datadog::repository, apt::default, datadog::integrations, datadog::dd-handler, chef_handler::default, chef-client::default, chef-client::service, chef-client::init_service, ec2-tags-ohai-plugin::default, sudo::default, kibana::default, kibana::kibana4, kibana::_service, kibana::nginx, chef_nginx::default, chef_nginx::package, chef_nginx::ohai_plugin, chef_nginx::commons, chef_nginx::commons_dir, chef_nginx::commons_script, chef_nginx::commons_conf

Overlook the accedo ones =)

@drenalin23
Copy link
Collaborator

@jensskott
I think that #97 should resolve the issue in the upstream cookbook for you. Let me know if it looks like it to you.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants