Search results

monitor the performance by real-time stats admin console->Actions->Real-Time Stats, particularly "EAProc WaitQ" column for your concern.

Prince, your attachment is too small to view clearly. it looks you set Max Connections=200 PHP_LSAPI_CHILDREN=210 this is wrong, the 2 figures should be equal. you can revert both to the default 35.

yes, please try lower lsphp5 external app max connections and PHP_LSAPI_CHILDREN from 35 to 10. looks like memory is the bottle-neck of this vps + php application, so have to reduce memory usage in various ways to avoid swap or increase vps memory to 2G, or move mysqld out of the VPS etc.

let's go ahead step by step. php suExec must be enabled for PHPRC to take effect. admin console->Configuration->Server-> Using Apache Configuration File->PHP suEXEC:Yes since this warning you can comment lines which start with suPHP_ConfigPath in suphp.conf litespeed's...

need check the error.log(or error_log) and/or stderr.log why it restart every hour. if your website only serve static content, it's not likely to restart often. I managed a few high traffic websites, one is images only, another one has simple php, both of them don't restart for months/weeks...

here's my suggestion if I read right: using PHPRC: PHPRC=$VH_ROOT/myphp.ini then in $VH_ROOT(for example /home/user2), create symbol link: ln -s /home/ini/user2/php.ini /home/user2/myphp.ini

adjust "Graceful Restart Timeout (secs)" Server->General->Graceful Restart Timeout (secs):-1 "During graceful restart, the new server instance is up, while the old instance will continue to handle existing requests. This timeout defines how long the previous instance shall wait before exit...

regarding 2, in addition to admin console's Real-time stats, lsws will support apache's mod_status, may be what you're familiar with. please refer http://www.litespeedtech.com/support/forum/showthread.php?t=4601 for status: "it's on the roadmap of our official 4.1 release..." regarding 3, the...

1. for apache modules: mod_limitipconn mod_cband mod_bw mod_evasive litespeed has better (in general) anti-ddos features built-in. it can be configured through admin console->server->security 2.admin console->click on "Actions" ( on the right of "Home") 5.we're working on full...

this is ok, ignore the warning. when lsws read apache's httpd.conf to define all listeners and virtual hosts, no natively defined listener(s), this warning can be ignored without any problem.

then probably the configuration of listeners in /usr/local/apache/conf/httpd.conf has some conflicts. if you switch back to apache, maybe same problem exist.

please paste the screenshot here: admin console-->Configuration-->Listeners

not sure if it was a combination or not if previous lsphp5 binary is saved, can take a quick test by point /usr/local/lsws/fcgi-bin/lsphp5 symbol link to old binary and restart lsws.

any difference from phpinfo()? I think ok to build php from litespeed admin console. It just have an additional lsphp5 binary for try, won't overwrite existing ones(however best to backup them first)

just that place. can you paste the screen shot here ? "Memory Soft/Hard Limit" is just above "Process Soft/Hard Limit"

"Memory Soft Limit" is not "Process Soft Limit" "Memory Hard Limit" is not "Process Hard Limit"

you can try increasing gradually. for example, start from Memory Soft Limit: 500M Memory Hard Limit: 550M then increase 50M or 100M each time, until the error disappear. yes, you can use 1000M or 1G, they are same, but 1000 is too small.

I think I've fixed the top problem -- php not working at all. further discussion into PM

should be 1000M ? not 1000.

couple of problems found at your server: 1)many IPs are banned by iptables #iptables -nL 2)can't run phpinfo() /home/tehXXXX/public_html>/usr/local/lsws/fcgi-bin/lsphp5 p.php Warning: phpinfo() has been disabled for security reasons in /home/tehXXXX/public_html/p.php on line 2 3)tons of error...