ReleaseEngineering/How To/Check for Slaves Stuck on Puppet
< ReleaseEngineering | How To
We often see puppet clients pointing to the wrong master, and until we get bug 627126 fixed, the only way we'll notice is to see that the slave is not doing anything, or to look in the logfiles.
On each of the four puppet masters, run
grep Allowing /var/log/messages | less
any slaves that cannot connect will be trying every minute, so you shouldn't have to look back too far from the end. Note that qm-maddon01 hits production-puppet quite a lot, but is out of our control. It's not a big deal. Any other slaves should be investigated and fixed.