Red Hat Bugzilla – Bug 102931
mod_throttle does not work
Last modified: 2007-04-18 12:57:04 EDT
Description of problem:
mod throttle does not throttle bandwidth for user accounts on a stock 7.3
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.install a 7.3 system plus updates, including apache and mod_throttle rpms
2.make a simple throttle configuration file for one user with a low throttle for
# mod_throttle configurations
ThrottleIndicator green 50
ThrottleIndicator yellow 80
ThrottleIndicator red 95
Allow from all
Allow from internal.webquarry.com ns.webquarry.com
ThrottleUser useracct Volume 10M 30d
3.include throttle.conf in httpd.conf make sure httpd.conf loads the throttle
modules as verified by server-info
4.populate the public_html directory of useracct's account with some sample html
5.send some traffic to http://yourserver/~useracct
6.observe their throttles at http://yourserver/throttle-status and
Actual results:once the user's traffic goes over hte throttle limits set in
throttle.conf, throttle should stop honoring requests for users files, it keeps
on serving files even though the throttle-status clearly shows that the user is
over quota. Interestingly enough, mod_throttle will stop serving requests for
the throttle-me file when the user is over quota, but not any other file. This
is exactly backwards of its intended operation, its supposed to stop serving all
files but the throttle-me file so that the user can see when they are over quota
Expected results: see above
I have some new info.
I downloaded and built apache, mod_ssl, php and mod_throttle from scratch and it works fine. I
built everything as closely to how redhat does as possible. I tore apart their rpm spec files and did
the layout exactly how they have it.
The key difference is this:
There are a bunch of patches that redhat does to the apache source according to the spec file-
I'm not a programmer and have no idea what these do but it will compile without them. I have a
feeling that something in one of these patches is what is causing mod_throttle to operate
backwards. Most of the patches appear to be for prior versions of apache and don't get applied as
far as I can tell.
The ones that do apply appear to be:
The "ndbm" Perl links with (the dbmmanage script is written in Perl) is actually
Berkeley DB, so force DBM to be Berkeley DB for httpd, too.
*I strongly suspect this patch is the culprit*
No description but appears to patch the following files
Red Hat apologizes that these issues have not been resolved yet. We do want to
make sure that no important bugs slip through the cracks.
Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc.
They are maintained by the Fedora Legacy project (http://www.fedoralegacy.org/)
for security updates only. If this is a security issue, please reassign to the
'Fedora Legacy' product in bugzilla. Please note that Legacy security update
support for these products will stop on December 31st, 2006.
If this is not a security issue, please check if this issue is still present
in a current Fedora Core release. If so, please change the product and version
to match, and check the box indicating that the requested information has been
If you are currently still running Red Hat Linux 7.3 or 9, please note that
Fedora Legacy security update support for these products will stop on December
31st, 2006. You are strongly advised to upgrade to a current Fedora Core release
or Red Hat Enterprise Linux or comparable. Some information on which option may
be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/.
Any bug still open against Red Hat Linux 7.3 or 9 at the end of 2006 will be
closed 'CANTFIX'. Again, if this bug still exists in a current release, or is a
security issue, please change the product as necessary. We thank you for your
help, and apologize again that we haven't handled these issues to this point.
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still
running Red Hat Linux, you are strongly advised to upgrade to a
current Fedora Core release or Red Hat Enterprise Linux or comparable.
Some information on which option may be right for you is available at
Closing as CANTFIX.