Support

mistwang · #11 12-26-2005, 07:23 PM

Have you tried ealier release or just 2.1.8?

matt · #12 12-26-2005, 07:46 PM

I can downgrade if you want me to try that.

mistwang · #13 12-26-2005, 08:05 PM

Yes, please.

I will try to reproduce it in our lab tomorrow, is there any special context defined for that vhost? It will be great if you can send us the xml configuration for that vhost, and the .htaccess .

I also wonder if it has anything to do with the traffic volume?

matt · #14 12-26-2005, 09:12 PM

Possibly on the traffic, we're on the front page of Digg right now and a ton of blogs.

I downgraded to 2.1.7 and still having a prob, next earliest I have is 2.1.5 which I remember having a prob with hanging PHP procs.

matt · #15 12-27-2005, 12:42 PM

I emailed all my conf files and .htaccess to your support email, let me know if anything else is needed.

mistwang · #16 12-27-2005, 01:24 PM

Is that possible that there is some process keep recreating the .htaccess, even thoug the content of .htaccess does not change? Maybe not that specific file, but other .htaccess file along the path.

As lshttpd cache the .htaccess for 10 seconds, then check for changes, reload it if the modified time was changed, if the .htaccess file is being recreated when lshttpd reload the .htaccess, lshttpd may see an incomplete .htaccess without rewrite rules, and that will be cached for about 10 seconds as well.

That's just my guess based on the symtom of the 404 errors, as when 404 errors occur, it will last about a couple seconds then back to normal and all requests to the forum will return 404. You can confirm that with the timestamp of those missing file errors in the error log.

If .htaccess do get recreated once for a while, please make sure to create a temp file and move the temp file to .htaccess, not to overwrite it directly.

I am still trying to reproduce the problem. :-)

mistwang · #17 12-27-2005, 02:15 PM

Another quick question, is there a .htacess file under "support/" folder? If yes, what is the content and does it change frequently?

mistwang · #18 12-27-2005, 03:42 PM

Hi Matt,

Please download and install http://www.litespeedtech.com/package...6-linux.tar.gz, I had added some log messages to help identify the source of the problem. I think the problem is that, for some reason, lshttpd failed to open the .htaccess file, either run out of file descriptor or the file is being updated.

Anyway, please follow our howto to increase the file descriptor limit
http://www.litespeedtech.com/docs/Ho....html#qa_incfd

You can check how many file descriptors has been used with command "lsof -p <pid_of_lshttpd>".

then upgrade to 2.1.9, please watch out log messages containing "[HTAccess]" tag in the error.log. Normally, you should only see such messages at server start up or .htaccess has been changed.

matt · #19 12-27-2005, 04:12 PM

The root .htaccess is the only one, it changes pretty rarely, really only when I'm working on the site.

WordPress.org is on standard, not enterprise, though I can purchase one if needed. Will that file you pointed to still work?

matt · #20 12-27-2005, 04:19 PM

The lshttpd had 170 open files according to lsof. There are about 1500 open total on the system.

ulimit -a returns this:

Code:

two&#58;~# ulimit -a
core file size        &#40;blocks, -c&#41; 0
data seg size         &#40;kbytes, -d&#41; unlimited
file size             &#40;blocks, -f&#41; unlimited
max locked memory     &#40;kbytes, -l&#41; unlimited
max memory size       &#40;kbytes, -m&#41; unlimited
open files                    &#40;-n&#41; 1024
pipe size          &#40;512 bytes, -p&#41; 8
stack size            &#40;kbytes, -s&#41; 8192
cpu time             &#40;seconds, -t&#41; unlimited
max user processes            &#40;-u&#41; unlimited
virtual memory        &#40;kbytes, -v&#41; unlimited

This seemed okay:

Code:

two&#58;~# more /proc/sys/fs/file-max
64000

Anything else I can provide?