|Applies To||RSA Product Set: Security Analytics|
RSA Product/Service Type: Security Analytics UI, Health and Wellness
|Issue||In health and wellness the Puppet Agent Failure alarm is seen.|
|Cause||There can be several reasons for this alarm.|
Issuing the command below on the affected node will give more information on the error.
puppet agent -t
However, due to a known issue with a slow memory leak in the puppetmaster module, when puppet agent -t is run on the node then the following message may be seen:
Warning: Unable to fetch my node definition, but the agent run will continue:
|Workaround||The workaround for the puppetmaster memory leak is to schedule a cron job to restart puppetmaster on a regular basis. |
Edit the /etc/crontab file to add a weekly restart for the puppetmaster service on the Security Analytics Server.
Copy and past the following line at the bottom of the /etc/crontab file:
57 23 ? * SAT * service puppetmaster stop && service puppetmaster start
The above line restarts the puppetmaster service every Saturday at 23:57.
Write and exit from the vi editor.
Once back to the command prompt, execute the command below to reload the crond daemon and put the scheduled job into effect.
service crond restart