Description of problem: Today our vhost templates reference a variable that is only available when using mod-rewrite. Therefore the servername for an application is not properly logged. To manually fix this you can edit the following files: /var/lib/openshift/.httpd.d/frontend-vhost-https-template.erb /var/lib/openshift/.httpd.d/frontend-vhost-http-template.erb From there you will need to save, delete and restore the frontends. This will create an outage on a node so it should be done with care. See https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/2/html-single/Administration_Guide/#Changing_Front-end_HTTP_Server_Plug-in_Configuration for full documentation. For someone already using the vhost plugin the steps would be as follows: # oo-frontend-plugin-modify --save > filename # oo-frontend-plugin-modify --delete # oo-frontend-plugin-modify --restore < filename
And the reason we care, I believe, is because this is the log that's used by the idler to determine whether and app has been accessed recently or is a candidate for idling.
BTW please upstream this change... right?
Upstream change is in https://github.com/openshift/origin-server/pull/4604
Sorry, forgot to include the upstream commit: commit 1229d591abd961c740f32bbeb94016ad77e8ab43 Author: Andy Goldstein <andy.goldstein> Date: Tue Jan 28 11:04:58 2014 -0500 Fix the Apache vhost plugin Fix bug in the Apache vhost plugin that prevented it from functioning. Change V_MATCH_HOST to %v in custom access log format so the server name is included in the log (V_MATCH_HOST is only available when using the mod rewrite plugin). Bug 1058849
verified with puddle-2014-01-30
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. http://rhn.redhat.com/errata/RHBA-2014-0209.html