You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by lacambre valentin <ro...@altern.org> on 1998/10/06 00:40:18 UTC
mod_rewrite/3147: apache sons eat all the cpu.
>Number: 3147
>Category: mod_rewrite
>Synopsis: apache sons eat all the cpu.
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Mon Oct 5 15:50:01 PDT 1998
>Last-Modified:
>Originator: root@altern.org
>Organization:
apache
>Release: 1.3.2
>Environment:
linux 2.0.33, apache 1.3.2, glibc6 (recent)
mod_rewrite intensive, free hosting high usage.
>Description:
Some apache process eat all cpu and no log nowhere, smells like bug#841
(mod_rewrite and 1.2.1).
apache 1.3.2 and 1.3.1 have it, 1.2.6 seems ok.
>How-To-Repeat:
dont know how to make it happen.
>Fix:
Cpu to 99 means endless loop, no log means before any logging (status dont get
it).
Tried to limit URI size but did not help (down to 200 bytes)
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig- ]
[nored unless you are responding to an explicit request ]
[from a developer. ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]