Search results

I think it is a issue with the disk system of the host server, the disk I/O wait is too high on that server. you got bad neighbors that keep the disk too busy. If static files wont load fast, it should be the case. when you do strace use "-T -tt" option to print timestamps.

It is likely a permission problem with your perl interpreter. check ls -l /usr/bin/perl

Can it be reliably reproduced? If yes, we can take a closer look at it.

That looks like a MySQL DB connection, you should investigate why. Maybe try different version of MySQL driver and socket type (TCP/Domain).

let truss print out timestamps, and the amount of time each system call. I can do that with strace, not sure about truss. Then, send a request that show the stall problem. from truss output, you can catch some pauses matching the stall period, log in that period is what you should pay...

Try strace/truss/ktrace the lsphp5 process, it should show what stall PHP. Sometimes, it is a issue with DNS.

It should be a issue with PHP, check if PHP has all required modules. check error log and stderr.log for errors.

if you can execute "/usr/local/lsws/bin/lshttpd -v" from PHP or command line, it will tell you which version of LSWS is installed.

The easiest way is to let PHP dump core files. set LSAPI_ALLOW_CORE_DUMP http://www.litespeedtech.com/php-litespeed-sapi.html for lsphp5 external app, then run "ulimit -a" from PHP script, make sure core limit is high enough. Make sure the directory holding the script has the correct...

Please try a rebuild of PHP, there is a bug in LSAPI 5.4 being addressed today. The default location of LSWS installation should be /usr/local/lsws, maybe /root/litespeed-version/ is the expanded LSWS package, you can remove it after installation.

Sorry about that. It is usually the case when people cannot start LSWS. Please send your external IP to sales@... for verification.

Then, you have tried the NULLed LSWS, and got black listed.

PHP crashed when serving that request. You can try load ionCube from php.ini instead of loading dynamically. check stderr.log as well, see if there is any related error message. you can also try to enable PHP core dump with LSAPI_ALLOW_CORE_DUMP env...

There is a size limit of single rewrite rule. The limit has been increased in 4.0.16 build, you can download it by changing the version number in the download link.

Are you using a trial key? maybe this IP has used trial a while ago, so it is not allowed, have to be cleared in our trial tracking DB. Please contact sales.

try to execute "/usr/local/lsws/fcgi-bin/lsphp5 -i" from command line, see if you get any error and fix it.

When upload the 300MB file, have you noticed that LSWS storing the request body in the swap directory? If you do, it means LSWS accepts and receives the request. You can turn on debug logging and check if LSWS send the request body to PHP successfully or not. There might be a problem on PHP side...

Just create a symbolic link from bash to /bin/sh, it is not about account shell login configuration in /etc/passwd.

Likely a problem with shell interpret coming with Solaris 10. Can you install bash, and make it default shell?

your need to install curl-devel rpm in order to compile PHP with curl.