On Fri, Mar 20, 2015 at 4:18 AM jamese <james.eckers...@gmail.com> wrote:
> Try running puppet with "--debug" and "--evaltrace" to see where it's > taking the time. > I'd be looking at DNS as that is often the culprit for unexplained things. > > -- > A tale I tell is where Puppet was taking three or more minutes to even begin to do anything. This was on an RHEL platform and it turned out my support guys has RHN configured to look for an RPM repository that was unreachable due to network restrictions. I removed the RHN plugin to yum and Puppet began to function normally. Just throwing that out there... -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAArvnv1nfPkQpWNA-by2ozYAWNAUGznpFdoAdsSgQyk0Oh0Rfw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
