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:
mod_file_cache Is not available in httpd on RHEL 9.
I am aware of the RHEL 6 change in which that module, and a few others, were no longer supported [0]. If I had to guess, it would be that the module was dropped because it was labeled as experimental.
However, as was indicated in httpd-2.2:
> As of Apache HTTP server version 2.2 mod_cache and mod_file_cache are no longer
> marked experimental and are considered suitable for production use. These caching
> architectures provide a powerful means to accelerate HTTP handling, both as an
> origin webserver and as a proxy.
I would very much like to take advantage of this powerful means to accelerate my HTTP handling. I see that mod_cache has been enabled, what is blocking mod_file_cache?
Version-Release number of selected component (if applicable):
> [root@certs2 httpd]# rpm -q httpd
> httpd-2.4.53-7.el9_1.1.x86_64
>
> [root@certs2 httpd]# cat /etc/redhat-release
> Red Hat Enterprise Linux release 9.1 (Plow)
How reproducible:
Always
Steps to Reproduce:
1. Add
> LoadModule file_cache_module modules/mod_file_cache.so
Into an httpd config file, restart the service
Actual results:
> httpd: Syntax error on line 61 of /etc/httpd/conf/httpd.conf: Syntax error on line
> 1 of /etc/httpd/conf.modules.d/1337-file_cache.conf: Cannot load
> modules/mod_file_cache.so into server: /etc/httpd/modules/mod_file_cache.so:
> cannot open shared object file: No such file or directory
Additionally, I verified that the file_cache module is not in /usr/lib64/httpd/modules or anywhere else in the package.
Expected results:
mod_file_cache is loaded and serves content cached using the MMapFile directive.
Additional info:
[0] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/migration_planning_guide/sect-migration_guide-networking-apache#doc-wrapper
[1] https://httpd.apache.org/docs/2.2/caching.html
I'm not aware that mod_file_cache has any measurable performance benefit on Linux systems, IIRC it was developed for Windows where caching file handles does help, and possibly was useful on something like AIX in the past too. On Linux files will be delivered via mmap() or sendfile() as appropriate anyway.
A convincing benchmark where mod_file_cache is shown to improve system performance could lead us to reconsider this, but in the absence of that it looks like additional complexity to support with no functional advantage for users. AFAIK we have had no customer requests for this module.