My [master] has :
report = true
reports = http, store, xmpp
pluginsync = true
The [agent] includes:
report = true
listen = true
pluginsync = true
The second agent I tested with also has the same configuration as the
above [agent]
Correct, the xmpp.yaml has all that information. What I was asking
about the remote client not having mail.yaml is I enabled pluginsync
on the remove client to see if the results would differ and it failed
stating the mail.yaml was missing (locally on the client). But if the
repots = xmpp is only defined for [master] then should I not include
"pluginsync = true" on the clients?
Thanks
- Trey
On Jun 7, 7:32 pm, James Turnbull <ja...@puppetlabs.com> wrote:
> treydock wrote:
> > Ok I restarted puppetmaster daemon and then broke a module to create a
> > failed puppet run on the same host as the master...and here's /var/log/
> > messages from that
>
> Can I confirm you have:
>
> [master]
> report = true
> reports = xmpp
>
> [agent]
> report = true
>
> In your puppet.conf on the master and the [agent] block on the client?
>
> You mentioned an issue with the xmpp.yaml file? That should have you
> Jabber jid, password, target etc and be located in /etc/puppet on the
> master - not sync'ed with the module.
>
> Regards
>
> James Turnbull
>
> --
> James Turnbull
> Puppet Labs
> 1-503-734-8571
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
