Search results

You can rewrite the script in Perl. no problem. Call the original script should work fine was well. I prefer this as the wrapper script does not need to be updated even when cPanel script updated.

if the requests/second drops to very low number or zero occasionally, you probably need to optimize your SQL or MySQL, MySQL is blocking PHP. Adding more PHP process may not help the performance. "Running short of concurrent connections" means that you need to increase server maxConnections...

I think we will change the restartsrv_httpd script to able restart both Apache and lsws by test which web server is running. for testing LSWS, just use kill -0 /tmp/lshttpd/lshttpd.pid if [ $? -eq 0 ]; then service lsws restart fi kill -0 <apache httpd.pid> if [ $? -eq 0 ]; then Original...

did already. strace lsphp5 process to find out why, maybe the process crashed, or missing a required PHP module.

It does not really matter much.

seems 4.0b1 still has a bug with request rate throttling, do not use it in production yet.

Please try our ruby-lsapi 3.2 release which using non-blocking listener socket, ruby process will not be blocked at accept() call any more.

Yeah, 4.0 beta 1 package has been updated as well.

Your LSAPI configurations are over tuned. Try the following LSAPI maxconns=150, PHP_LSAPI_MAX_REQUESTS=2000, PHP_LSAPI_CHILDREN=150, persistConn=1, pcKeepAliveTimeout=N/A, backlog=100, instances=1 if the "WaitQ" for the lsphp external app in the real time status report is constantly non-zero...

I think this email is sent by lfd, 100 MB probably is a configuration for lfd script.

I'd rather not doing that, instead, change the restartsrv_httpd to use "lswsctrl restart" is a better solution to me.

Please update to the latest 3.3.10 release package uploaded today, there might be a problem with request rate throttling.

Memory soft/hard limit for lsphp5 external app. I am not sure it is limited by the system or not though. Also need to check why it use more than 100MB for a joomla site, allocate too much memory for opcode cache or something else.

enabled suEXEC, and strace lsphp5 process to find out why, maybe the process crashed, or missing a required PHP module.

It looks pretty nice, looks more powerful than awstats.

I think either way should work. You probably need to manually setup awstats instead of using integrated awstats solution in LSWS. You can try writing access log to the same location on your storage server from two web servers, it might work. we have never tried that before.

I guess you have been playing with the chroot option, it will not work properly with cPanel. Forget it.

Please PM me a temp root login, I will take a look when I get a chance.

rebuild lsphp binary on your server or change 'mysql_socket' configuration in your php.ini

http://www.postfix.org/faq.html#whoami change sendmail_path to /usr/sbin/sendmail -f user@domain -t -i should fix you problem.