search for: thewortmans

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 Error: Could not start Service[puppet]: Execution of

I think I really hosed my certificates somehow this morning trying to get PuppetDB and Puppet talking again -- here''s where I stand. My Puppet master and PuppetDB are again talking, or at least, aren''t complaining about communication. From my puppet master, I can run "puppet agent -t", and it runs just fine. From any other node on which puppet had been running, I

I''m looking to implement a hiera backend for our Puppet installation, as we routinely deploy systems that are of varying hardware, OS, and which may have multiple roles they fill. I''ve figured out, I think, how to handle the OS question through facter, but implementing server roles isn''t quite so clear. I want to maintain that information on the server, not on the

Is there an easy way to convert a puppet client into being a puppet master? Here''s the scenario. I''m using puppet to configure all my systems, and would like it to be able to deploy a new puppet master as well. We have systems worldwide so having local puppet masters is very desirable for fault tolerance. So Kickstart (via cobbler) installs a puppet client during the initial