Bug #12105

service always thinks service is down

Added by François Beausoleil 4 months ago. Updated 4 months ago.

Status:Closed Start date:01/24/2012
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
Affected Puppet version:2.6.4 Branch:
Keywords:service
Votes: 0

Description

I wrote the following puppet service description, running on Ubuntu 11.04:

class mysql::service{ service{‘mysql’:

ensure     => running,
enable     => true,
hasrestart => true,
hasstatus  => true,
require    => Class['mysql::install'],

} }

Everytime I apply the manifest, the service is reenabled: puppet doesn’t notice MySQL is already running. I’ve attached as much information as I could to help debug this. The “new” way to detect if a service is running is through “/usr/bin/service SERVICE_NAME status”.

I changed my service description to use a status parameter, which should prevent starting the service every time puppet runs.

puppet.log (6.6 kB) François Beausoleil, 01/24/2012 05:39 am

History

Updated by François Beausoleil 4 months ago

I’m using 2.6 because that’s what’s packaged with Ubuntu.

Updated by Nan Liu 4 months ago

I’m not sure when upstart got included into Puppet, try adding provider => upstart.

Updated by François Beausoleil 4 months ago

  • Status changed from Unreviewed to Closed

Yeah, I noticed I have Puppet 2.6 on that 11.04 host. I’m using the packaged Puppet. I think the bug should be closed invalid, since I’m on an old version.

Thanks for replying.

Also available in: Atom PDF