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:
PassengerMaxInstancesPerApp is not honored in passenger version 4.0.18 (Satellite 6.0.7)
Version-Release number of selected component (if applicable):
6.0.7
Passenger Version : 4.0.18
How reproducible:
Always
Steps to Reproduce:
1. Adjust PassengerMaxInstancesPerApp in /etc/httpd/conf.d/passenger.conf
2. Use apache bench to generate a number of requests against foreman
3. View number of processes foreman scales to above PassengerMaxInstancesPerApp
Actual results:
# of processes scales greater than PassengerMaxInstancesPerApp
Expected results:
# of processes to be limited by PassengerMaxInstancesPerApp
Additional info:
We have no means to control whether foreman or puppet will starve one or the other in a scaled environment.
Comment 1RHEL Program Management
2015-01-19 21:43:46 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
This bug is fixed in 4.0.28:
Release 4.0.28
--------------
* Introduced a workaround for a GCC 4.6 bug. This bug could cause Phusion
Passsenger to crash during startup. Affected operating systems include
Ubuntu 12.04 and Amazon Linux 2013.09.01, though not every machine with
this OS installed exhibits the problem. See issue #902.
* Improved Node.js support: the Sails framework is now supported.
* Improved Node.js support: the streams2 API is now supported.
* Introduced support for hooks, allowing users to easily extend Phusion
Passenger's behavior.
* Fixed a bug in the `passenger start -R` option. It was broken because of a
change introduced in 4.0.25.
* Fixed a bug in PassengerMaxInstancesPerApp. Fixes issue #1016.
...
https://code.google.com/archive/p/phusion-passenger/issues/1016
Hi - Do we have plan to use updated version of passenger? In satellite 6.2.12, PassengerMaxInstancesPerApp option does not work. It is fixed in 4.0.28, however we are using 4.0.8
Installed Packages
mod_passenger.x86_64 4.0.18-22.el7sat @rhel-7-server-satellite-6.2-rpms
rubygem-passenger.x86_64 4.0.18-22.el7sat @rhel-7-server-satellite-6.2-rpms
rubygem-passenger-native.x86_64 4.0.18-22.el7sat @rhel-7-server-satellite-6.2-rpms
rubygem-passenger-native-libs.x86_64 4.0.18-22.el7sat @rhel-7-server-satellite-6.2-rpms
PassengerMaxInstancesPerApp - I will help to assign equal number of max processes to foreman and puppet app.
One of the customer's satellite is having high puppet request and puppet is consuming all the process from pool size. Only 1 is assign to foreman. If above option can be used, we can assign equally assign max processes for both app. Thanks.
I am closing this current release. This issue is found on the Puppet Server which is deployed in Passenger. With the introduction of 6.3, puppet 4 can be used which is a Java application and therefore avoids this bug. With 6.4, the puppet version will be 5 which is still Java based.
So, moving to puppet4+ avoids this issue which is currently delivered.