On 24/05/13 11:43, Paul Tötterman wrote:
Did something change in the way Puppet outputs messages? Until this
morning we used the following to run Puppet from Cron on all our nodes:
But as of 3.2.1 this produces output on every Puppet agent run and that
output is mailed out, resulting in hundreds of messages which contain
nothing of importance (see below). This had worked fine for almost two
years now, with output only generated on errors and problems (such as
DNS not available).
I'm having the same issue. I couldn't find a bug report about this.
There is --verbose and --debug, but not --silent or --quiet. Should we
maybe use --logdest? Anyway the behaviour has changed from 3.1.1
We have always been using "--logdest syslog", it is only with 3.2.1 that
log messages now seem to go not only to syslog but also to stdout, which
is why Cron generates annoying mail messages.
Even more interesting: before 3.2.1 /var/log/syslog would only show the
"finished catalog run" message when running Puppet from Cron with
"puppet agent -o --no-daemonize --logdest syslog":
May 21 09:30:01 node01 CRON[14018]: (root) CMD (/usr/bin/puppet agent
--onetime --no-daemonize --logdest syslog)
May 21 09:30:38 node01 crontab[15379]: (root) LIST (root)
May 21 09:30:38 node01 puppet-agent[14019]: Finished catalog run in
17.33 seconds
Now it shows everything in /var/log/syslog:
May 24 07:15:01 node01 CRON[23182]: (root) CMD (/usr/bin/puppet agent
--onetime --no-daemonize --logdest syslog > /dev/null 2>&1)
May 24 07:15:02 node01 puppet-agent[23183]: Retrieving plugin
May 24 07:15:03 node01 puppet-agent[23183]: Loading facts in
/var/lib/puppet/lib/facter/postgres_default_version.rb
May 24 07:15:03 node01 puppet-agent[23183]: Loading facts in
/var/lib/puppet/lib/facter/corosync_mcastaddr.rb
May 24 07:15:03 node01 puppet-agent[23183]: Loading facts in
/var/lib/puppet/lib/facter/pe_version.rb
May 24 07:15:03 node01 puppet-agent[23183]: Loading facts in
/var/lib/puppet/lib/facter/concat_basedir.rb
May 24 07:15:03 node01 puppet-agent[23183]: Loading facts in
/var/lib/puppet/lib/facter/root_home.rb
May 24 07:15:03 node01 puppet-agent[23183]: Loading facts in
/var/lib/puppet/lib/facter/lvm_disk_usage.rb
May 24 07:15:03 node01 puppet-agent[23183]: Loading facts in
/var/lib/puppet/lib/facter/corosync_mcastport.rb
May 24 07:15:03 node01 puppet-agent[23183]: Loading facts in
/var/lib/puppet/lib/facter/libvirt_guests.rb
May 24 07:15:03 node01 puppet-agent[23183]: Loading facts in
/var/lib/puppet/lib/facter/libvirt_used_memory.rb
May 24 07:15:03 node01 puppet-agent[23183]: Loading facts in
/var/lib/puppet/lib/facter/puppet_vardir.rb
May 24 07:15:03 node01 puppet-agent[23183]: Loading facts in
/var/lib/puppet/lib/facter/has_libvirtd.rb
May 24 07:15:03 node01 puppet-agent[23183]: Loading facts in
/var/lib/puppet/lib/facter/has_group_libvirtd.rb
May 24 07:15:22 node01 puppet-agent[23183]: Caching catalog for
dbb01.db01.prod.rz01.riseops.at
May 24 07:15:24 node01 puppet-agent[23183]: Applying configuration
version '1369362429'
May 24 07:15:43 node01 crontab[24545]: (root) LIST (root)
May 24 07:15:43 node01 puppet-agent[23183]: Finished catalog run in
20.11 seconds
So, I am asking the Puppet devs: is this behaviour intended or a bug?
Should I open a bug report?
Andreas
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
