Search results

  1. M

    restart

    Please record the time when you have the problem. The log file shows only one restart after removing that site And the log file looks normal before the restart. If you need to restart the server in order to fix any thing, please keep a copy of the access log file under...
  2. M

    restart

    The php.ini try to load some PHP5 modules, has that been fixed, has /usr/local/apache/logs/stderr.log stopped complaining about missing modules? Please remember that our free support service is just for trouble shooting assistance, not going to take care of everything for you. Our dedicate...
  3. M

    restart

    Please answer my question. Has the php.ini issue has been addressed or not?
  4. M

    mod_limitipconn throttling

    The difficulty is that the VHost information is only available after receiving the "Host" header in the request. Right now, LSWS only need to look at the source IP of the socket connection. If the limit exceed, LSWS will close the connection immediately without any response.
  5. M

    performances issue with x86_64 and cpu cores

    3WARE raid card with 2.6 kernel should work better. Go with either RAID0 or RAID10 or RAID1, depends on what level of data protection do you need. 32bit or 64bit should not matter much, if you need to serve file larger than 2GB, you have to use 64bit.
  6. M

    restart

    Has another PHP problem been addressed yet?
  7. M

    performances issue with x86_64 and cpu cores

    I don't know how good is the 64bit support in 2.4 kernel, hope it is good enough. I think the high I/O wait may related to the RAID card driver. Hope you can get good support for the RAID card in latest 2.6 kernel. Not sure what kind RAID is used. RAID0 should be the best, then RAID10, RAID5, etc.
  8. M

    restart

    Looks like your site cannot move to another server. looks like it is a wordpress blog, the default wordpress installation does not have this problem, you may want to check which WP plugin causing the problem? Update it to the latest release, etc. Trouble shooting this kind of problem is beyond...
  9. M

    3.3.16 and Header directive

    http://httpd.apache.org/docs/1.3/mod/mod_headers.html#header
  10. M

    restart

    You should implement what I have suggested already. I can only take another look after those have been addressed.
  11. M

    cache function ?

    It will take a while, however, the cache function should be pretty stable, 4.0 in beta mainly because the SSI implement need more time to test.
  12. M

    LSWS 3.3.16 has been released

    LiteSpeed Web Server 3.3.16 has been released This release is mainly to address a few minor bugs. Download LiteSpeed Web Server View Version History
  13. M

    restart

    It is a good idea to move it to another server. At least it won't affect this main server. I don't know how to fix it as it is likely either bad PHP code or PHP internal bug. reduce "max_execution_time" in php.ini may make the PHP process recover more quickly. That's the best I can do about it.
  14. M

    restart

    See my previous post for the result of the investigation.
  15. M

    restart

    Have spent some time checking the server. found the following PHP issues: php.ini does match PHP version, php.ini is for php5, but PHP4 is actually used, got many error messages in /usr/local/apache/logs/stderr.log, should be fixed. Some features of your site may depends on those PHP modules...
  16. M

    restart

    which version of mysql server is used? phpinfo shows that mysql client lib 4.1.22 is used, you should build PHP with 5.0.x client if mysql server 5.0 is used. I will try to login to the server and take a look today, please make sure to have the ssh and LSWS web console access available to us.
  17. M

    405 Error response when processing POST requests to page cached Rails resources

    The rails context implicitly creates the "/dispatch.lsapi" LSAPI context. but you are free to configure everything manually.
  18. M

    performances issue with x86_64 and cpu cores

    You can create the listener manually with IP:Port and assign the binding. LSWS will use it together with configuration from httpd.conf. Using multiple CPU to handle I/O intensive task is important. epoll may have some impact as well, but should not be as significant.
  19. M

    restart

    Just make sure mysql persistent connection is turned off in php.ini
  20. M

    restart

    Looks like a PHP-MySQL problem if /index.php need to pull data from MySQL, Please try turn off PHP-MySQL persistent connection if it is enabled. If you use mmcache, need to investigate mmcached connection as well.
Top