Symptoms:- Suspecious mcollective execution. (i.e automatic or manual) which resulted in puppet execution for all associated puppet nodes.
Description:- 1) We are using teamcity for puppet agent executions on remote servers. 2) By checking logs(i.e. mocllective.log, mcollective-audit.log) it looks like, there was an agent discovery triggered from teamcity. Which in essence let the mcollective to sync plugins from the master to this host. We are assuming this was triggering the puppet run. 3) We are suspecting the trigger is done by mcollective. And this trigger was received from root on Dev teamcity and 15 seconds later from production teamcity. We have checked mcollective.log, mcollective-audit.log and /var/log/messages of puppet master and mcollective server, but nothing is found. Could you please let us know if there are any system logs, audit logs to check. Please let me know, if you require any logs for analyzing the issue. Thanks and Regards, Pradeep. On Wednesday, 8 February 2017 18:11:28 UTC+1, R.I.Pienaar wrote: > > > > > On Wed, Feb 8, 2017, at 16:01, pradeep reddy wrote: > > > > Hi All, > > > > We are using a ruby script, which uses mcollective API for initiating the > > puppet run on multiple servers based on the group and track its status. > > > > It used to do the rolling deployment or in other words initiate puppet > > agent on the servers. > > > > We are using from three years same setup. But observed that, today we > > have > > mco automatic trigger issue. It effected, lot of servers. > > I don't really understand what you mean by "automatic trigger issue" can > you explain your symptoms, errors etc? > > > > > > Could someone please let us know, or guide us in finding the issue. > > > > Puppet Server Details:- > > ------------ > > puppet -V ----> 3.4.2 > > mcollective-service-client-3.1.2-1.noarch > > mcollective-client-2.4.0-1.el6.noarch > > mcollective-nettest-common-3.0.3-1.noarch > > mcollective-common-2.4.0-1.el6.noarch > > mcollective-iptables-client-3.0.1-1.noarch > > mcollective-puppet-agent-1.6.0-1.noarch > > mcollective-filemgr-client-1.0.1-1.noarch > > mcollective-puppet-client-1.6.0-1.noarch > > mcollective-package-client-4.2.1-1.el6.noarch > > mcollective-iptables-common-3.0.1-1.noarch > > mcollective-puppet-common-1.6.0-1.noarch > > mcollective-filemgr-common-1.0.1-1.noarch > > mcollective-iptables-agent-3.0.1-1.noarch > > mcollective-package-agent-4.2.1-1.el6.noarch > > mcollective-nettest-client-3.0.3-1.noarch > > mcollective-nettest-agent-3.0.3-1.noarch > > mcollective-package-common-4.2.1-1.el6.noarch > > mcollective-service-common-3.1.2-1.noarch > > mcollective-filemgr-agent-1.0.1-1.noarch > > mcollective-2.4.0-1.el6.noarch > > > > Puppet agent Details:- > > -------------- > > mcollective-puppet-common-1.9.3-1.el6.noarch > > mcollective-puppet-agent-1.9.3-1.el6.noarch > > puppet-3.7.4-1.el6.noarch > > > > > > Thanks and Regards, > > Pradeep. > > > > -- > > > > --- > > You received this message because you are subscribed to the Google Groups > > "mcollective-users" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > > > -- > R.I.Pienaar / www.devco.net / @ripienaar > > -- --- You received this message because you are subscribed to the Google Groups "mcollective-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
