On Saturday, 21 March 2015 22:08:34 UTC, Christopher Wood wrote:
>
> On Sat, Mar 21, 2015 at 12:08:07PM -0700, Robert Inder wrote:
>
:
:
> >This is not quite the behaviour I want.
> >
> >But how can I stop it?
>
> In your place I'd probably just purge stale sessions with a c
On Sat, Mar 21, 2015 at 12:08:07PM -0700, Robert Inder wrote:
>On Friday, 20 March 2015 08:18:15 UTC, jamese wrote:
>
> Try running puppet with "--debug" and "--evaltrace" to see where it's
> taking the time.
>
>Ah! As before, the evaltrace for the empty node definition lists a
On Friday, 20 March 2015 08:18:15 UTC, jamese wrote:
>
> Try running puppet with "--debug" and "--evaltrace" to see where it's
> taking the time.
>
Ah! As before, the evaltrace for the empty node definition lists a handful
of things
being evaluated in negligible times.
But that out put is b
On Fri, Mar 20, 2015 at 4:18 AM jamese 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
be
On Friday, March 20, 2015 at 3:18:15 AM UTC-5, jamese 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.
>
DNS issues can indeed cause long runtimes when requests time
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.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and
