Re: [users@httpd] mod_rewrite: failed to lock file descriptor

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




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@xxxxxxxxxxxxxxxx
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


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux