Search results

Yes, that's correct when you create a listener from the web console. For listener configured via Apache httpd.conf only one process is assigned, you need to override that by explicitly creating a listener from web console.

The URI used for a rewrite rule in .htaccess is different from the rewrite rule configured at vhost level. Basically, the rewrite base will be removed from the URI before matches the URI with a rewrite rules in .htaccess. You need to change the rewrite rule according like what Timothy...

Yes, it is always a good idea to avoid using .htaccess.

I am little puzzled by the back trace. maybe the libstc++ library linked into the binary has compatibility problem? We need to set up a test VM to give it a try. Can you tell me more about your server? FreeBSD version? 32bit or 64bit? Also you can try our latest 3.3.11 build your server, just...

We use on disk buffer mainly for buffering the large request body for those site dealing with large media files, let a 600MB media file fill up the memory is not a good idea, and there could be 20 upload sessions at the same time. Let's see what we can do about it. At least we can set the...

You can remove files under /tmp, just do not touch /tmp/lshttpd.

Linux packages only though.

Please download and try 3.3.11 release package by change the version number in the download link.

I think probably know what is going on. LSWS use on-disk buffer to store the body of large post requests. this will cause high I/O wait. The solution is to change the swapping directory to use /dev/shm instead of /tmp/lshttpd/swap...

It is caused by one your cron job that remove everything under /tmp on the 45 minutes every hour. when /tmp/lshttpd directory is removed, LSWS will have to restart itself, normally it is not a problem, the server will start fine. But for whatever reason, maybe the LSWS was killed in the middle...

If you are using enterprise edition, please switch to the debug build of the lshttpd. http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:howto:bug_report

try change <enableCoreDump> to 1 in lsws/admin/conf/admin_config.xml, there is an option in freebsd kernel to control core dump I believe.

Looks like crashed, is there a core file under /tmp/lshttpd? Can you inspect the core file with GDB? we need the stack backtrace to find out what is wrong.

debug log controled by both "Log Level" and "Debug Level", "kill -USR2" toggles "Debug Level".

If that is happen, please use command kill -USR2 <pid_of_a_child_lshttpd> to turn on debug logging and let it run for a while then send the log file to us. Run to kill command again to turn off the debug logging. Make sure to set server "Log Level" to "DEBUG" and server "Debug Level" to "NONE".

I/O Buffer is only for PHP request/response, won't affect media files, unless the media files were sent through PHP. Does it work better with larger I/O buffer today?

should be post_max_size

You can install a memcached if wordpress can take advantage of it. LiteSpeed does not need that much memory, at least for your current traffic volume.

If you stream media file through PHP, it may have this problem. should use internal redirect instead. You can try increasing the max io buffer size. http://www.litespeedtech.com/docs/webserver/config/general/#inMemBufSize

It is a PHP error, has nothing to do with LSWS. There is a "max_post_size" configuration may affect this. Please check your php configuration with a phpinfo() page.