Hi, I've a puppet module running which ensures the puppet service is not running and not starting on boot. A few times a few different nodes have become stuck, apparently always thinking that the service is running when it is not. The following below excerpt just goes round and round run after run until I commented out the ensure and enable for the puppet service. It then completes and the node works as expected after this when the #'s are removed again.
info: Applying configuration version '1309852902' debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: Service[puppet](provider=redhat): Executing '/sbin/service puppet status' debug: Puppet::Type::Service::ProviderRedhat: Executing '/sbin/chkconfig puppet' debug: Service[puppet](provider=redhat): Executing '/sbin/service puppet stop' notice: Caught TERM; calling stop [root@gibsvlin-erp2dst ~]# /etc/init.d/puppet status puppetd is stopped [root@gibsvlin-erp2dst ~]# /sbin/chkconfig puppet [root@gibsvlin-erp2dst ~]# echo $? 1 [root@gibsvlin-erp2dst ~]# ps -ef | grep puppet root 5548 4886 0 09:24 pts/0 00:00:00 grep puppet Everything is returning the right exit codes and such, so why after being very clearly told that puppet is NOT running does it stop it anyway, and terminate? 2.6.7 btw, eagerly awaiting 2.6.9 rpms in the yum repo. Thanks Chris -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
