----- Original Message ----- > From: "Josh" <j...@chickenmonkey.co.uk> > To: puppet-users@googlegroups.com > Sent: Friday, April 12, 2013 5:07:48 PM > Subject: Re: [Puppet Users] MCollective and Puppet with periodic runs disabled > > On Friday, April 12, 2013 4:41:24 PM UTC+1, R.I. Pienaar wrote: > > > so it works now? > > > > if not - first make sure 'mco rpc rpcutil ping -I your.node' works > > when that works the rest will also work. > > > > No, still not working, and the ping (and everything else for that matter > just as inventory) works fine. > > I am begging to suspect that there is some internal timeout in the mco > plugin and the puppet agent is taking some time to fire up and hence > triggering the timeout. This is all on virtual machines without a great > deal of resources but it still seems to run puppet quickly enough when i > run it manually > > I will have a think about it over the weekend, maybe I will have a flash of > inspiration. > > Many thanks for all your time today, I'll post back if I get some progress
ok - you could set direct_addressing=0 in your client.cfg, that I'd guess would make it work. else turn on debug level logs and put those on pastebins cos that will enable me to really figure out, thus far I've just been quessing at common causes This thread is probably best on the mcollective-users list also on google groups. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
