On Tuesday, November 13, 2012 7:40:08 AM UTC-6, Martin Alfke wrote: > > Hi Bret, > > On 13.11.2012, at 13:18, Bret Wortman wrote: > > I'm getting this problem on all the puppet client's I've been setting up > and it's got me both scratching my head (because I'm not seeing anything > obvious in any system logs) and pausing in my rollout until I get it solved: > > # puppet resource service puppet ensure=running enable=true > > > does the service script has a status option and does the status deliver > proper results? > > service puppet status > > Some service scripts do not check properly for the status or they deliver > wrong exit codes. > If this is the case you can set > hasstatus => false > > Or, better, fix the service script. Note that Puppet cares only about the exit code; it ignores the output and error streams. Be sure to check / fix the exit codes of *all* initscript actions, but especially "start", "stop", "status", and "restart" actions.
John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/s3DERbSNhD4J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
