On 10/06/2010 03:24 PM, Felix Frank wrote:
In any case, by /more/ selective commenting I've deduced that it's the
recurse => true in http://paste.lisp.org/display/115229 that triggers
this. If I leave it out (or change it to false), puppet applies the
catalog as expected.
Haven't I hinted at y
On 10/06/2010 03:18 PM, Peter Meier wrote:
In any case, by /more/ selective commenting I've deduced that it's the
recurse => true in http://paste.lisp.org/display/115229 that triggers
this. If I leave it out (or change it to false), puppet applies the
catalog as expected.
Can someone figure out
On 10/06/2010 02:41 PM, Trevor Vaughan wrote:
I've had that same issue with things hanging and having no idea whet
they're hanging on.
Try popping open your YAML catalog in a text editor and see what comes
right after the entry that's listed last.
Hmm, this sounds like good advice, but is the
On 10/06/2010 12:17 AM, Patrick wrote:
This is huge. Are you serving a lot of big files or templates?
Not at all.
Aggelos
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
On 10/05/2010 06:58 PM, Trevor Vaughan wrote:
You might want to try running the client with --evaltrace for
additional information.
Thanks. This didn't help much, as it's only printing out the information
after the resource evaluation, so I still have no idea what it's doing
when it gets st
Hello all,
I'm playing with a new puppet setup (2.6.1 on debian stable with ruby
1.8) and I've run into a problem with puppetd consuming ridiculous
amounts of memory.
My setup isn't that complex (apache2 configuration and a few other
packages/services), but puppetd will force the machine int
