Bug #2654
closed
Loads of cf-execd leads to OOM killer
Description
I have a virtual machine with Rudder server 2.4.
After some time running (a couple of hours), the VM is full of cf-execd (tens of them), eventually leading to really hight CPU consumption and even OOM Killer going wild.
Files
Updated by Nicolas PERRON over 12 years ago
- File OOM_Kill_Rudder2.5.png OOM_Kill_Rudder2.5.png added
Images are better than words
Updated by Nicolas PERRON over 12 years ago
- Target version changed from 2.4.0~beta2 to 2.4.0~beta3
2.4.0~beta2 has been released. This ticket must be moved to 2.4.0~beta3.
Updated by Jonathan CLARKE over 12 years ago
- Assignee deleted (
Jonathan CLARKE) - Priority changed from 3 to 1 (highest)
This has been "worked around" by adding a promise in the Rudder common Technique to kill cf-execd automatically when too many instances are running. This is not a fix, but will avoid most of the main issues encountered. See #2661.
Updated by Nicolas CHARLES over 12 years ago
For some reason, the Vagrant VM holds bad promises, editing the /var/spool/cron/crontabs/root
It is unclear where this promises come from, and when we mount the VM Vagrant, it overrides the promises located on the host machine on /var/rudder/cfengine/inputs
Regenerating promises correct the promises on the Vagrant VM
Updated by Nicolas PERRON over 12 years ago
- Status changed from New to Discussion
- Target version changed from 2.4.0~beta3 to 2.4.0~beta4
Nicolas CHARLES wrote:
For some reason, the Vagrant VM holds bad promises, editing the /var/spool/cron/crontabs/root
It is unclear where this promises come from, and when we mount the VM Vagrant, it overrides the promises located on the host machine on /var/rudder/cfengine/inputs
Regenerating promises correct the promises on the Vagrant VM
If I understand, this is due to the configuration of a Vagrant VM for dev, which use a specific /var/rudder/cfengine/inputs shared by the host machine.
Whatever, this issue should be moved to the next run
Updated by Jonathan CLARKE about 12 years ago
- Target version changed from 2.4.0~beta4 to 24
Updated by Jonathan CLARKE almost 12 years ago
- Status changed from Discussion to Pending technical review
- Target version changed from 24 to 2.4.0~beta3
This is fixed thanks to #2661
Updated by Jonathan CLARKE almost 12 years ago
- Status changed from Pending technical review to Released