Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When we upgraded to 6.2 and we removed the firewall rule from blocking clients to 8140 this took down our satellite server as too many processing requests from puppet clients took down the apache/passenger/puppet service(s).
To fix the issue we've had to re-implement the firewall, stop puppet agent across all our servers, remove firewall rule, restart puppet in a delayed manner across the landscape.
A saner solution is to limit the number of connections Apache can service out of the window based upon Puppet facts for the server. Tuning the Apache server should happen as a part of the install as its a critical part to the ongoing operation of Puppet.
Version-Release number of selected component (if applicable):
6.2.8
How reproducible:
All the time (until mitigating the problem)
Steps to Reproduce:
1. Block ports for upgrade or any other reason
2. Open ports...
3. Flood of Puppet requests.
Actual results:
Takes down apache/passenger/puppet
Expected results:
apache/passenger/puppet stay up - back off client systems...
Additional info:
We ship since 6.2.7 I believe the adjusted Passenger settings that work in most large-ish environments. If your environment is significantly larger, then those settings need further increasing.
In 6.2.8, you can do this by editing /etc/foreman-installer/custom-hiera.yaml and doing:
---
apache::mod::passenger::passenger_max_pool_size: 12
apache::mod::passenger::passenger_max_instances_per_app: 6
apache::mod::passenger::passenger_max_request_queue_size: 250
apache::mod::passenger::passenger_stat_throttle_rate: 120
And changing whatever needs changing. Those become persistent across upgrades (unlike editing passenger_extra.conf).
Is there some other action we need to take on this bug? We can't make the default 24/12, it's too much for a smaller Satellite instance.