Issue #12202 has been updated by Banio Carpenter.

I happened again.  /var/log/messages:


Jan 31 12:42:42 ip-10-196-147-4 puppet-agent[22728]: Could not run Puppet 
configuration client: Could not retrieve local facts: Cannot allocate memory - 
which lsdev 2>/dev/null
Jan 31 13:12:42 ip-10-196-147-4 puppet-agent[22728]: Could not run Puppet 
configuration client: Could not retrieve local facts: Cannot allocate memory - 
which lsdev 2>/dev/null
Jan 31 13:42:43 ip-10-196-147-4 puppet-agent[22728]: Could not run Puppet 
configuration client: Could not retrieve local facts: Cannot allocate memory - 
which lsdev 2>/dev/null
Jan 31 14:12:43 ip-10-196-147-4 puppet-agent[22728]: Could not run Puppet 
configuration client: Could not retrieve local facts: Cannot allocate memory - 
which lsdev 2>/dev/null


The server started swapping again, and it appears that it's puppet using all 
the memory (1.2GB of memory?):

# ps afux | grep puppet
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root     22728  2.4 70.7 1279716 1259932 ?     Ssl  Jan23 285:52 /usr/bin/ruby 
/usr/sbin/puppetd



# free -m
             total       used       free     shared    buffers     cached
Mem:          1740       1680         59          0         17        267
-/+ buffers/cache:       1396        344
Swap:          895        448        447

----------------------------------------
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.

Reply via email to