Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/tuning_red_hat_satellite/tuning#tuning_passenger_for_puppet_4_related_workloads

Section Number and Name: 
5.2.4. Tuning Passenger for Puppet 4-related workloads

Describe the issue: 
Puppet 4 does not run under Passenger, but as a standalone (Java) process and as such should be configured/tuned in /etc/sysconfig/puppetserver and /etc/puppetlabs/puppetserver/ and not /etc/httpd/conf.d/passenger.conf

Also, given it's Java, not Ruby, different tuning settings will apply.

Suggestions for improvement: 

Additional information:

(In reply to Evgeni Golov from comment #0)
> Document URL: 
> https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/
> tuning_red_hat_satellite/
> tuning#tuning_passenger_for_puppet_4_related_workloads
> 
> Section Number and Name: 
> 5.2.4. Tuning Passenger for Puppet 4-related workloads
> 
> Describe the issue: 
> Puppet 4 does not run under Passenger, but as a standalone (Java) process
> and as such should be configured/tuned in /etc/sysconfig/puppetserver and
> /etc/puppetlabs/puppetserver/ and not /etc/httpd/conf.d/passenger.conf
> 
> Also, given it's Java, not Ruby, different tuning settings will apply.
> 
> Suggestions for improvement: 
> 
> Additional information:

Hi Evgeni,

This tuning actually relates to Passenger when the workload is mostly Puppet 4 based and does not really cover any tunings that should be applied to Puppet itself.
Probably, we can title this section more inline with that purpose to reflect on that.