On Wed, Nov 28, 2012 at 5:42 AM, Med75 <[email protected]> wrote: > The problem disappeared after a reboot of the client. I saw your answer too > late so I haven't had the chance to run the agent with --debug and > --trace... I'll update this thread once it will be back again. > > meanwhile, and after a couple of agent run, I'm now getting a different > message, here is the full stack trace: http://pastebin.com/yLdBhcyN > I don't know if this is related or not, and if it would be better to create > a new thread.
How much memory does the machine have, and how much memory free? It looks like the system is running dry: Cannot allocate memory - fork FYI, In Puppet 3 we're now using fork when doing catalog runs, which may increase memory utilization relative to previous versions of Puppet. -Jeff -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
