Bug 973796 - PassengerPreStart points at root which logs errors
PassengerPreStart points at root which logs errors
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Brenton Leanhardt
libra bugs
Depends On:
  Show dependency treegraph
Reported: 2013-06-12 14:43 EDT by Luke Meyer
Modified: 2017-03-08 12 EST (History)
5 users (show)

See Also:
Fixed In Version: openshift-origin-broker-1.5.4-1
Doc Type: Bug Fix
Doc Text:
The broker application's default configuration directed Passenger to initialize two threads with two requests to the application root. However, the application root did not respond correctly, causing the preloading process to fail with errors logged to httpd's error_log. With this fix, the PassengerPreStart configuration in /var/www/openshift/broker/httpd/broker.conf has been updated to send the GET request to This is an API call that requires no authentication, allowing the Broker application to be properly preloaded.
Story Points: ---
Clone Of:
Last Closed: 2013-08-05 13:16:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Luke Meyer 2013-06-12 14:43:43 EDT
Description of problem:
When starting openshift-broker, get two errors in /var/log/openshift/broker/httpd/error_log like:

[error] [client] Attempt to serve directory: /var/www/openshift/broker/httpd/root/

Additional info:
This is caused by passenger self-testing at start which is based on the PassengerPreSpawn setting in /var/log/openshift/broker/httpd/error_log

This was fixed for online devenvs but somehow never made it into origin.
Comment 2 Luke Meyer 2013-06-12 14:50:08 EDT
Sorry, I meant PassengerPreStart; it should be:

Comment 5 Luke Meyer 2013-07-01 10:19:01 EDT
Sorry for the mistakes above.

The file that needs to be changed on the broker is /var/www/openshift/broker/httpd/broker.conf

The directive that needs to change is PassengerPreStart, which should be:

Comment 6 openshift-github-bot 2013-07-10 16:54:05 EDT
Commit pushed to master at https://github.com/openshift/origin-server

Bug 973796 - PassengerPreStart points at root which logs errors
Comment 7 Brenton Leanhardt 2013-07-11 07:59:30 EDT
This also pulls in the fix for the missing lsof depedency.  This was commit edb31c88eecc744626fbedbd9a73eff45db2f358 on Origin.

Comment 9 Gaoyun Pei 2013-07-16 02:23:23 EDT
Checked this on puddle http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise/1.2/2013-07-12.3/ 

The package version was right.
[root@broker ~]# rpm -qa|grep openshift-origin-broker

But PassengerPreStart address is still set in /var/www/openshift/broker/httpd/broker.conf 

Error still could be seen in /var/log/openshift/broker/httpd/error_log when openshift-broker started. So assign it back, thanks!
[Sun Jul 14 20:19:06 2013] [error] [client] Attempt to serve directory: /var/www/openshift/broker/httpd/root/
Comment 10 Brenton Leanhardt 2013-07-16 07:48:32 EDT
Looks like the SCL package has it's own configuration file and I failed to update that one.   I'm submitting another pull request.
Comment 11 openshift-github-bot 2013-07-16 09:00:18 EDT
Commit pushed to master at https://github.com/openshift/origin-server

Bug 973796 - PassengerPreStart points at root which logs errors
Comment 13 Gaoyun Pei 2013-07-18 01:12:57 EDT
Verify this on puddle http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise/1.2/2013-07-17.1/

When starting openshift-broker, no errors shown in /var/log/openshift/broker/httpd/error_log 

Checked the PassengerPreStart address in /var/www/openshift/broker/httpd/broker.conf
[root@broker ~]# grep PassengerPreStart /var/www/openshift/broker/httpd/broker.conf
Comment 16 errata-xmlrpc 2013-08-05 13:16:37 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.