Puppet; pushing manifests to nodes without restarting puppetmasterd

puppetpuppetmaster

After I update a manifest for a node; does puppetmaster automatically send the configuration to the node? If it does what is the interval and how do I change it? Where can I find more information about this?

I assume it's the runinterval for puppet.conf? The default setting is 1800 seconds; however I have yet to notice any configuration change since puppetmaster started.

Best Answer

The master doesn't send the file to the node; the node checks in with the master on the run interval.

And yeah, no need to restart the master service to serve the new updates.

Related Solutions

Puppetmaster don’t notice changes to site.pp

I've found the problem. I've been writing the manifests with notepad++, with EOL set to Windows, NOT Unix. So there was there problem :/

Converting from one puppetmaster to another

I don't want to detract from anyone's possible answers - perhaps there is a cleaner way to achieve my goals.

Here is what I did: I removed everything in /var/lib/puppet:

cd /var/lib/puppet
rm -rf *

Since I was using a package manager, I looked for files owned by any package in that directory - and there were none. For Debian and dpkg, that is done this way:

dpkg -S * */* */*/*

Since no packages were found that owned these files, this suggested that the files were created on the fly, and since /var/lib/puppet was owned by a package (puppet-common) I left the empty directory in place.

Then I ran puppetmaster (actually a mistake since passenger is to be used) and the appropriate files were all recreated. After stopping puppetmaster, configuring passenger, and configuring /etc/default/puppetmaster and "restarting" puppetmaster (which failed quietly) - everything seemed to be good again.

Running puppet agent against the server pulled down the appropriate certs and made everything nice.

Best Answer

Related Solutions

Puppetmaster don’t notice changes to site.pp

Converting from one puppetmaster to another

Related Topic