Starting in version 2.3.0, you can restart Puppet Server by sending a hangup signal, also known as a HUP signal or SIGHUP, to the running Puppet Server process. The HUP signal stops Puppet Server and reloads it gracefully, without terminating the JVM process. This is generally much faster than completely stopping and restarting the process. This allows you to quickly load changes to your Puppet Server master, including configuration changes.
There are several ways to send a HUP signal to the Puppet Server process, but the most straightforward is to run the following kill
command:
kill -HUP `pgrep -f puppet-server`
There are three ways to trigger your Puppet Server environment to refresh and pick up changes you’ve made. A request to the HTTP Admin API to flush the JRuby pool is the quickest, but picks up only certain types of changes. A HUP signal restart is also quick, and applies additional changes. Other changes require a full Puppet Server restart.
Note: Changes to Puppet Server’s logging configuration in
logback.xml
don’t require a server reload or restart. Puppet Server recognizes and applies them automatically, though it can take a minute or so for this to happen.
hiera.yaml
file to change your Hiera configuration.puppetserver gem
.puppet cert clean
conf.d
directory.puppet cert clean
/etc/sysconfig/puppetserver
or /etc/default/puppetserver
file.ca.cfg
to enable or disable Puppet Server’s certificate authority (CA) service.For these types of changes, you must restart the process by using the operating system’s service framework, for example, by using the systemctl
or service
commands.