How to register a puppet and a host

Puppet writes default entries to syslog. Why is this? Most software is written to a separate log file. I checked the documentation, and there is a mention of what you can write to the log file, but it was mentioned that "this is usually not used." It is a bad idea?

What is a typical setup for puppet management? Using grep in / var / log / messages?

+7
source share
2 answers

For this purpose we use a puppet. This will give you a good overview of the environment, what does not work and what works. And which servers stopped checking.

Its easy to set up, check out http://puppetlabs.com/puppet/related-projects/dashboard/

If you want to enter another file, you can use the syslogfacility configuration option in the puppet ( http://docs.puppetlabs.com/references/stable/configuration.html#syslogfacility ) and configure syslog to enter another file.

+3
source

From your mentioned syslog , I assume you were talking about Debian-like Linux.

There is really no need to write your own journal. Setting up /etc/default/puppet enough.

 # Startup options DAEMON_OPTS="--logdest /var/log/puppet/puppet.log" 

/etc/default/puppet is /etc/init.d/puppet , so the parameters you add here will be executed when the puppet service starts.

Documents on --logdest options: https://docs.puppetlabs.com/references/3.3.1/man/apply.html#OPTIONS

BTW, the deb deb doll provides that Debian (or Ubuntu) even includes a logrotate configuration file for /var/log/puppet , I don’t know why this option is not standard.

 /var/log/puppet/*log { missingok sharedscripts create 0644 puppet puppet compress rotate 4 postrotate pkill -USR2 -u puppet -f 'puppet master' || true [ -e /etc/init.d/puppet ] && /etc/init.d/puppet reload > /dev/null 2>&1 || true endscript } 
+6
source

All Articles