Search results

You have to clear the browser cache if you test it using browser.

Checked your sample configuration files. nothing that LiteSpeed cannot handle. You can give LSWS a try on anther port. Make sure to use "apache:apache" the installer ask for "user/group" that server run as.

It should be a APC issue. I have no clue. :)

A cron job added by root user is killing all processes running as nobody every minutes. the script is /root/sks.pl

Sure, we will update it in our next release. you can patch the code as well, at the beginning of lsws/admin/html/utility/buildPHPExecutable.php

It will be great if you could write a wiki entry on vB optimization, especially on tuning MySQL DB. :)

You need to find out which process want to kill lshttpd. PM me your server login, I can take a look if you want.

Our latest 3.3.10 build should be better. You can give it a try.

It is pretty strange. seems another user has the same problem, but I cannot reproduce it. If you rename the log file or remove it, LSWS will create a new one, what the ownership of the new file? I may need to take a look at your server if possible. OK. will address that later.

Please try a command line tool to download the script like lynx -mime_header URL wget URL LSWS should update its cache when a file has been changed. Sometimes browser caches it.

Max Connections: 200 PHP_LSAPI_MAX_REQUESTS=50000 PHP_LSAPI_CHILDREN=200 LSAPI_MAX_IDLE_CHILDREN=60 Instances: 1 start with above configuration. Either "Intances" and "PHP_LSAPI_CHILDREN" should match "Max connections". It is not recommended to use "Instances" and "PHP_LSAPI_CHIDLREN" together...

The I/O wait is too high in the first top output. You need to find out what causes it. Have the CPU utilization of mysqld ever been higher than 200%? I am not sure your MySQL takes advantage of all CPU available on your DB server. If the maximum CPU utilzation is around 100%, then it only uses...

I don't know why, the access_log and error_log should be created as www:www or www:user. created with group "user" because most time "user" need to get the read permission when umask is set to 027, it follows the vhost suexec group.

LiteSpeed's control panel integration is pretty generic, and it only interact with Apache httpd.conf, not directly with control panel, so LiteSpeed may work with interworx already. If you want you can try it on another port by following our wiki...

For you system, you need to find out the real bottle neck. It could be web server CPU bound, web server Disk I/O bound, web<-->DB server network I/O bound, DB server CPU bound, DB server disk I/O bound. From the information you provided, the web server is not CPU bound, so adding faster CPU...

That's probably our firewall blocking access from multiple PCs behind NAT.

It is up to what flexibilities you need.

Yes, we are using 4.0b1 now, the worst case is to switch back to 3.3.x release if anything goes wrong.

Yes, that's correct.

LSWS always rotate the log file to <log_file_name>.awstats before being feed to awstats.