On Apr 5, 6:43 am, ankush grover <ankushcen...@gmail.com> wrote: > Hi Friends, > > I have configured Puppet 2.7.12-1 on Centos 6 as server and various clients > running on Redhat/Centos/Ubuntu etc.. The issue I am facing is that > somehow Puppet is not able to start the ossec service on the client. > > If the service is stopped on the client then puppet is not able to start > the service. Below are the logs of the Puppet client running on the Centos > 5 machine.
>From the log, it does not appear that Puppet is unable to start the service, but rather that it thinks it doesn't needs to do. The log shows it checking the service's current status > debug: Service[ossec](provider=redhat): Executing '/sbin/service ossec > status' and whether the service is enabled > debug: Puppet::Type::Service::ProviderRedhat: Executing '/sbin/chkconfig > ossec' but not any attempt to start the service. There are two main possibilities: 1) Your manifest doesn't declare that the service should be running, or 2) the service's initscript does not follow LSB convention for the return value of the 'status' command. Puppet relies on the return value, not the text output. See, for example, http://refspecs.linux-foundation.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html. My bet would be that the initscript's 'status' command is always returning 0, regardless of the actual status. Instead, it ought to return 1, 2, or 3 when the service is not running, depending on whether there is a leftover pid file, lock file, or neither. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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.
