Issue #12202 has been updated by Daniel Pittman.
Hrm. Normally, Linux should allow forking, but maybe you have a more strict overcommit mode turned on or something. You might want to try running Puppet from cron, rather than our daemon. While we work hard to avoid it, Ruby has a history of nasty memory leaks that bite us in daemon mode, and it looks like you might have hit one. (Very recent versions of Puppet have support for forking before the agent run, in daemon mode, but that is a bit less robust than just using cron.) If that solves the problem, I think we are going to call this closed. ---------------------------------------- Bug #12202: Could not run Puppet configuration client: Could not retrieve local facts: Cannot allocate memory - which lsdev 2>/dev/null https://projects.puppetlabs.com/issues/12202 Author: Banio Carpenter Status: Needs More Information Priority: High Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: Puppet agent functioning on multiple clients with this error in /var/log/messages: puppet-agent[602]: Could not run Puppet configuration client: Could not retrieve local facts: Cannot allocate memory - which lsdev 2>/dev/null service puppet status returns: puppetd (pid xxxx) is running... But no updates were being applied. After restarting the puppet service it works again. centos 5.7 puppet 2.7.5 facter 1.6.2 Let me know if you need more info. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
