Closed swapnil-jaiswal closed 6 years ago
Hi @swapnil-jaiswal,
hmmm, upstart should be used as per the fix in 2.36.0.
Any chance you could replicate the issue on a clean Amazon Linux instance and document the steps to replicate the issue?
Thanks in advance! David
Hey @djoos The above issue was faced on a clean amazon image itself.
This error comes on simply invoking the recipe. newrelic::infrastructure_agent.
As stated earlier the newrelic infra got installed but on subsequent run the recipe gives error -- when it invokes restart of newrelic infra agent. Now it looks for init service & fails with error s
service[newrelic-infra]: No custom command for restart specified and unable to locate the init.d script!
Details have been shared above.
Since this was affecting our production we switched to alternate recipe as a quick fix : newrelic-infra from supermarket. This is working fine.
Fixed by @JCapriotti in #362
On checking the system i found out that the newrelic infra agent installation via yum results in creation of upstrart service. But this recipe looks for /etc/init.d/newrelic-infra or service newrelic-infra. Same is not found since the newrelic infra uses intctl instead.
initctl status newrelic-infra newrelic-infra start/running, process 10609
Please advice. I am using the latest cookbook version '2.36.0'
Summary of error
/newrelic/providers/agent_infrastructure.rb line 59) had an error: Chef::Exceptions::Service: service[newrelic-infra]: Service is not known to chkconfig.
Details of error logs