Issue #20900 has been updated by Charlie Sharpsteen.
We have an issue in 3.2.x where the agent daemon is logging startup messages to
the console. Cron can catch these and send them out as mail. Does the issue go
away if you add the following options and redirects to your agent runs?
--logdest syslog >/dev/null 2>&1
----------------------------------------
Bug #20900: tagmail triggers in --onetime mode without changes after upgrade
from 3.1.1 to 3.2.1
https://projects.puppetlabs.com/issues/20900#change-91546
* Author: Bernhard Schmidt
* Status: Unreviewed
* Priority: Normal
* Assignee:
* Category:
* Target version:
* Affected Puppet version: 3.2.1
* Keywords:
* Branch:
----------------------------------------
I run a Puppetmaster on Debian Wheezy with the Puppetlabs APT repository. A
couple of clients, mostly Debian as well, are connected to it. My clients
usually run "puppet agent --onetime" from crontab.
I have the following tagmail.conf to get a mail on changes:
all: [email protected]
With 3.1.1 this did not generate a mail unless there were changes. After
upgrading to 3.2.1 (both server and some clients), I start to get tagmail
notifications from _some_ 3.2.1 clients. 3.1.1 clients are quiet.
May 24 19:38:07 puppet-kom puppet-master[5814]: Not sending tagmail report;
no changes
May 24 19:38:07 puppet-kom puppet-master[5814]: (//isatap-w.xxx.de/Puppet)
Caught TERM; calling stop
Pretty much the same manifest on a 3.2.1 client
May 24 19:03:09 puppet-kom puppet-master[891]: (//isatap-g.xxx.de/Puppet)
Caught TERM; calling stop
May 24 19:03:09 puppet-kom postfix/pickup[25864]: B2E0A113C4B: uid=106
from=<puppet>
The mail looks like this
2013-05-24 19:41:02 +0200 Puppet (info): Retrieving plugin
2013-05-24 19:41:02 +0200 Puppet (info): Loading facts in
/etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
2013-05-24 19:41:02 +0200 Puppet (info): Loading facts in
/etc/puppet/modules/stdlib/lib/facter/pe_version.rb
2013-05-24 19:41:02 +0200 Puppet (info): Loading facts in
/etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
2013-05-24 19:41:02 +0200 Puppet (info): Loading facts in
/etc/puppet/modules/stdlib/lib/facter/root_home.rb
2013-05-24 19:41:02 +0200 Puppet (info): Loading facts in
/var/lib/puppet/lib/facter/ipmi.rb
2013-05-24 19:41:02 +0200 Puppet (info): Loading facts in
/var/lib/puppet/lib/facter/has_mptsas.rb
2013-05-24 19:41:02 +0200 Puppet (info): Loading facts in
/var/lib/puppet/lib/facter/facter_dot_d.rb
2013-05-24 19:41:02 +0200 Puppet (info): Loading facts in
/var/lib/puppet/lib/facter/has_aacraid.rb
2013-05-24 19:41:02 +0200 Puppet (info): Loading facts in
/var/lib/puppet/lib/facter/root_home.rb
2013-05-24 19:41:02 +0200 Puppet (info): Loading facts in
/var/lib/puppet/lib/facter/puppet_vardir.rb
2013-05-24 19:41:02 +0200 Puppet (info): Loading facts in
/var/lib/puppet/lib/facter/pe_version.rb
2013-05-24 19:41:02 +0200 Puppet (info): Loading facts in
/var/lib/puppet/lib/facter/lldp.rb
2013-05-24 19:41:02 +0200 Puppet (info): Loading facts in
/var/lib/puppet/lib/facter/has_megaraid_sas.rb
2013-05-24 19:41:03 +0200 Puppet (info): Caching catalog for
puppet-kom.xxx.de
2013-05-24 19:41:03 +0200 Puppet (info): Applying configuration version
'1369416785'
2013-05-24 19:41:04 +0200 Puppet (notice): Caught TERM; calling stop
I _think_ this is related to running with --onetime as a daemon. When I add
--no-daemonize or --test, I cannot trigger it.
Somehow every major Puppet release tagmail seems to be broken :-(
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" 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-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
