Issue #7164 has been updated by James Turnbull. Category set to service Priority changed from Urgent to Normal Affected Puppet version set to 0.24.5
---------------------------------------- Bug #7164: Getting error when I am using provider upstart for ubuntu service in puppet client machine https://projects.puppetlabs.com/issues/7164 Author: Naga Babu Status: Needs More Information Priority: Normal Assignee: Category: service Target version: Affected Puppet version: 0.24.5 Keywords: Branch: I am getting below error message when I ran puppet on client machine. "err: //xxxxx::xxxxx/Service[xxxxx]/ensure: change from stopped to running failed: Could not start Service[xxxxx]: Execution of '/sbin/start xxxxx' returned 1: at xxxxxxxxxxxxxxxx:168" My service code in puppet recipe is like below: service { 'xxxxxx': provider => "upstart", ensure => running, hasstatus => true, hasrestart => true; } Service is running fine on the client machine but I am getting above error message every time puppet runs on the client machine. I think what happening here is every time puppet run on the client machine ensure=> running is trying to execute the "/sbin/start xxxx" command. for upstart scripts if process is already running and you are trying to start again it will give return code 1. puppetversion => 0.25.4 rubyversion => 1.8.7 I would like to getrid of that error message. I am using upstart script for this service. there is no init.d script available. Please provide solution. Thanks in advance. Naga. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
