Hi, np, Thanks for replying. We are using mcollective from long time. I was unable to provide you required details to you.
I am debugging issue, will find the root cause and provide the details. Apologies for wasting your time. Thanks and Regards, Pradeep. On Thursday, 9 February 2017 09:16:46 UTC+1, R.I.Pienaar wrote: > > > > On Wed, Feb 8, 2017, at 19:41, pradeep reddy wrote: > > 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. > > No sorry, it appears you do not know even how your mcollective is run or > what commands are used or what the outputs are, it's impossible to help > without that > -- --- 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.
