You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Andrew Zeon <an...@au1.ibm.com> on 2005/05/16 07:00:00 UTC
[users@httpd] mod_rewrite: failed to lock file descriptor
Hi,
I have Apache 1.3.26 running on Windows 2000. I am getting the following
in my error.log:
[Mon May 16 13:44:04 2005] [error] Server ran out of threads to serve
requests. Consider raising the ThreadsPerChild setting
[Mon May 16 13:44:09 2005] [error] [client 10.207.14.115] (36)Resource
deadlock avoided: mod_rewrite: failed to lock file descriptor
[Mon May 16 13:44:09 2005] [error] [client 10.120.122.148] (13)Permission
denied: mod_rewrite: failed to unlock file descriptor
The "ran out of threads" bit I can understand... we are planning on
increasing this value. However, I'm trying to understand why I am getting
the next two lines. FYI, there is a problem with one of our rewrite rules
and hence is consistenly throwing this error:
[Mon May 16 13:44:00 2005] [error] [client 10.56.3.45] File does not
exist: e:/apps/ibmhttpserver/htdocs/en_us/callhome
I get about 10 of these per second in error.log. Could it be that the
threads are trying to write to the log files so fast that it's having
locking issues?
Thanks.
Andrew
Re: [users@httpd] mod_rewrite: failed to lock file descriptor
Posted by Nick Kew <ni...@webthing.com>.
Andrew Zeon wrote:
> Hi,
>
> I have Apache 1.3.26 running on Windows 2000.
How perverse. Without getting into why-use-windows-at-all,
Apache 1.x is a server designed for unix-family boxes, and
not well-suited to windows. One of the changes in Apache2
is the true cross-platform architecture.
> I am getting the following
> in my error.log:
>
> [Mon May 16 13:44:04 2005] [error] Server ran out of threads to serve
> requests. Consider raising the ThreadsPerChild setting
> [Mon May 16 13:44:09 2005] [error] [client 10.207.14.115] (36)Resource
> deadlock avoided: mod_rewrite: failed to lock file descriptor
> [Mon May 16 13:44:09 2005] [error] [client 10.120.122.148] (13)Permission
> denied: mod_rewrite: failed to unlock file descriptor
Well, that could either be due to poor performance (see above),
or perhaps a set of rewrites spiralling recursively out of control.
> FYI, there is a problem with one of our rewrite rules
> I get about 10 of these per second in error.log.
That looks like a self-inflicted wound. Fix the rewriterules.
Or, failing that, drop them.
--
Nick Kew
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] mod_rewrite: failed to lock file descriptor
Posted by Andrew Zeon <an...@au1.ibm.com>.
I forgot to mention that after "failed to unlock file descriptor " it
always crashes.
Andrew Zeon/Australia/IBM@IBMAU
16/05/2005 03:00 PM
Please respond to
users
To
users@httpd.apache.org
cc
Subject
[users@httpd] mod_rewrite: failed to lock file descriptor
Hi,
I have Apache 1.3.26 running on Windows 2000. I am getting the following
in my error.log:
[Mon May 16 13:44:04 2005] [error] Server ran out of threads to serve
requests. Consider raising the ThreadsPerChild setting
[Mon May 16 13:44:09 2005] [error] [client 10.207.14.115] (36)Resource
deadlock avoided: mod_rewrite: failed to lock file descriptor
[Mon May 16 13:44:09 2005] [error] [client 10.120.122.148] (13)Permission
denied: mod_rewrite: failed to unlock file descriptor
The "ran out of threads" bit I can understand... we are planning on
increasing this value. However, I'm trying to understand why I am getting
the next two lines. FYI, there is a problem with one of our rewrite rules
and hence is consistenly throwing this error:
[Mon May 16 13:44:00 2005] [error] [client 10.56.3.45] File does not
exist: e:/apps/ibmhttpserver/htdocs/en_us/callhome
I get about 10 of these per second in error.log. Could it be that the
threads are trying to write to the log files so fast that it's having
locking issues?
Thanks.
Andrew