Gregor Zupan
2013-Oct-30 06:42 UTC
[Puppet Users] Puppet agent fails when executed via mcollective
I have configured that my puppet agents are executed twice a night. For urgent updates I have mcollective and I can run them manually (or at least I thought so). I am experiencing problems when puppet agent is executed via mcollective: mco puppet runonce -I XXXXXXXXXXXXXXX.com * [ ============================================================> ] 1 / 1 Finished processing 1 / 1 hosts in 3198.59 ms In puppet dashboard execution is marked as an error with the following text: *notice Caught TERM; calling stop Puppet 2013-10-30 07:28 CET* and in a syslog on puppet agent: *Oct 30 07:28:11 sc4-008 puppet-agent[23043]: Reopening log files * *Oct 30 07:28:38 sc4-008 puppet-agent[23043]: Caught TERM; calling stop* If I execute puppet agent manually everything is ok: *puppet agent --test* *Info: Retrieving plugin* *Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb* *Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb* *Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb* *Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb* *Info: Caching catalog for XXXXXXXXXXXXXX.com* *Info: Applying configuration version ''69M''* *Notice: /Stage[post]/Patch_all_force/Exec[patchScanner_ALL_force]/returns: executed successfully* *Notice: Finished catalog run in 13.06 seconds* -- 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 puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5a80abea-4fa4-4a86-beb3-811b27ff2b95%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Konstantin Shcherban
2013-Nov-15 07:28 UTC
[Puppet Users] Re: Puppet agent fails when executed via mcollective
Can confirm i have pretty same issue. Puppet 2.7.19 Mcollective 2.2.2 Centos 6.4 среда, 30 октября 2013 г., 10:42:00 UTC+4 пользователь Gregor Zupan написал:> > I have configured that my puppet agents are executed twice a night. For > urgent updates I have mcollective and I can run them manually (or at least > I thought so). > > I am experiencing problems when puppet agent is executed via mcollective: > > mco puppet runonce -I XXXXXXXXXXXXXXX.com > > * [ ============================================================> ] 1 / 1 > > Finished processing 1 / 1 hosts in 3198.59 ms > > > In puppet dashboard execution is marked as an error with the following > text: > > *notice Caught TERM; calling stop Puppet 2013-10-30 07:28 CET* > > > and in a syslog on puppet agent: > > > *Oct 30 07:28:11 sc4-008 puppet-agent[23043]: Reopening log files* > *Oct 30 07:28:38 sc4-008 puppet-agent[23043]: Caught TERM; calling stop* > > > If I execute puppet agent manually everything is ok: > > *puppet agent --test* > *Info: Retrieving plugin* > *Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb* > *Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb* > *Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb* > *Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb* > *Info: Caching catalog for XXXXXXXXXXXXXX.com* > *Info: Applying configuration version ''69M''* > *Notice: > /Stage[post]/Patch_all_force/Exec[patchScanner_ALL_force]/returns: executed > successfully* > *Notice: Finished catalog run in 13.06 seconds* > > >-- 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 puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/acd751b5-c164-4439-ba79-d4e8091f0c1f%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.