Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
The documentation for mod_log_debug (in httpd-manual package) contains four examples one of which is syntactically incorrect and prevents Apache from starting. It uses the following configuration:
<Location "/foo/">
LogMessage "subrequest to /foo/" hook=type_checker expr=%{IS_SUBREQ}
</Location>
This is how Apache reacts:
# systemctl start httpd
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
# journalctl -xe
...
httpd[2603]: AH00526: Syntax error on line 8 of /etc/httpd/conf.d/custom.conf:
httpd[2603]: Could not parse expression '%{IS_SUBREQ}': syntax error, unexpected $end
...
This is probably a documentation bug, one easily fixable by the following modification which I believe does the desired job (I am no expert at this matter, though):
LogMessage "subrequest to /foo/" hook=type_checker "expr=-T %{IS_SUBREQ}"
^ ^^^ ^
Version-Release number of selected component (if applicable):
httpd-manual-2.4.6-31.el7_1.1.x86_64
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.
https://rhn.redhat.com/errata/RHEA-2016-2534.html
Description of problem: The documentation for mod_log_debug (in httpd-manual package) contains four examples one of which is syntactically incorrect and prevents Apache from starting. It uses the following configuration: <Location "/foo/"> LogMessage "subrequest to /foo/" hook=type_checker expr=%{IS_SUBREQ} </Location> This is how Apache reacts: # systemctl start httpd Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. # journalctl -xe ... httpd[2603]: AH00526: Syntax error on line 8 of /etc/httpd/conf.d/custom.conf: httpd[2603]: Could not parse expression '%{IS_SUBREQ}': syntax error, unexpected $end ... This is probably a documentation bug, one easily fixable by the following modification which I believe does the desired job (I am no expert at this matter, though): LogMessage "subrequest to /foo/" hook=type_checker "expr=-T %{IS_SUBREQ}" ^ ^^^ ^ Version-Release number of selected component (if applicable): httpd-manual-2.4.6-31.el7_1.1.x86_64