I have 40 Ubuntu 12.04 servers. These servers are managed with puppet.
Sometimes I have problem with puppet agent.
puppet agent spawn child process (sh) and this process fails. Sh is zombie process. Puppet doesn't work, I must restart puppet agent to make it works.
I use puppet to manage files, packages and services. Problematic agent didn't make any change before fails, server is up to date.
On our puppet box ( under the puppet/modules folder ) , I have added a module for installing a package. I then added the classes needed for the resources into the init.pp ( and other derived class files ) into the manifests folder.
After upgrading a node to Puppet 3.0.0 from the Puppet Labs YUM repository, the node that gets upgraded throws a munging error: [ashinn@dis1 ~]$ sudo puppet agent --test --trace
Error: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: Parameter path failed on File[/var/lib/puppet/state/graphs]: Munging failed for value "/var/lib/puppet/state/
*Using VSphere Client 5.1 Ubuntu precise VM's with Puppet Enterprise 3.3.1 and PostgreSQL 9.3.1
I am utilizing the same postgresql database to manage a new puppet master and I know that the licenses are tied to the number of ssl certificates used, but what I am unsure about is if the data associated with keeping track of the number of ssl certificates generated and managed is handled in the postg