This repository has been archived by the owner on Dec 27, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 359
Upstart changes not working on Ubuntu 12.04 #19
Comments
Can you please post the contents of your `/etc/init/logstash_agent.conf"? |
Shouldnt it be enough to specify something like:
Unfortunately, I dont have this file available right now since we reverted to an older version of the logstash agent since we need it running at the moment |
The following line should give you that automatically: https://github.com/lusis/chef-logstash/blob/master/recipes/agent.rb#L60 |
I believe this is a bug with the current Chef 10.14.0 release candidate and likely previously released betas as well. It should be fixed here: |
@arminbauer can you confirm this is still an issue? |
This is definitely working now. |
Closing out due to inactivity. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It seems that start_command is missing:
Error executing action
start
on resource 'service[logstash_agent]'Chef::Exceptions::Service
Chef::Provider::Service::Upstart:0x00000003c3e260 requires that start_command be set
Resource Declaration:
In /var/cache/chef-client/cookbooks/logstash/recipes/agent.rb
58: end
59: service "logstash_agent" do
60: provider Chef::Provider::Service::Upstart
61: action [ :enable, :start ]
62: end
63: else
Compiled Resource:
Declared in /var/cache/chef-client/cookbooks/logstash/recipes/agent.rb:59:in `from_file'
service("logstash_agent") do
provider Chef::Provider::Service::Upstart
action [:enable, :start]
supports {:restart=>false, :reload=>false, :status=>false}
retries 0
retry_delay 2
service_name "logstash_agent"
pattern "logstash_agent"
startup_type :automatic
cookbook_name "logstash"
recipe_name "agent"
end
Cheers,
Armin
The text was updated successfully, but these errors were encountered: