Search results

You should pay more attention to the packet before this one, containing request from the client. If tcpdump does not catch anything for your script, means that your script does not hit server, but hits another server, thus 404.

just use rsync to copy lsws directory and data. mysqldump to copy mysql DB. did a LSWS license migration. install rc script with /usr/local/lsws/admin/misc/rc-inst.sh

chmod go-x /usr/bin/perl

I believe it has been removed from latest eaccelerator, either use earlier version or use something else for that purpose.

That's because PHP crashes while processing the request, you need to check stderr.log, see if anything related. As the request url has been logged, you can give it a try see if you can reproduce the 503 error, if you can, you can trouble shoot it further with strace and core dumps.

You should continue play with the tcpdump parameter until you can capture the packet contain the request. you can try tcpdump -s0 -x -v port 80 first see if you can get something, then add more rules one by one.

Can you PM me a temp root access, we will take a look.

It is likely a issue with the certificate, not LiteSpeed. Please switch back to Apache, make sure the SSL certificate working properly, then switch to LiteSpeed. if still having problem, let us know.

You may have multiple NICs, and the traffic is going through another NIC, try tcpdump -i eth1 ....

You need to check the request sent by curl with tcpdump tcpdump -s0 -X port 80 and host <ip_of_the_curl_client> Please post or PM the tcpdump result containing the curl request if you believe it is a valid HTTP request.

You should look into "tc" + iptables, google for traffic shaping.

please check the owner of log files under that directory, if owned by root, change owner to "apache", make sure those log file grows when you access a web site hosted.

Please let us know the public IP of this server, we will check.

make sure you remove the serial.no if you use a trial key.

You need to undo the change to your PHP setup, upgrade/downgrade, opcode cache, etc. If you made changes to LSWS configuration, restore it. try a reinstall of LSWS to start from fresh.

check phpinfo() page under Litespeed, open_basedir is enforced, so id command cannot be executed successfully, suphp does not support open_basedir.

You must be forgetting doing step in the wiki http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:apache:da

You need to keep "httpd" service checked under WHM service manager.

LiteSpeed has similar resource usage as Nginx, if you use Apache backend, replace Nginx + Apache with LiteSpeed will reduce the resource usage. when 500 concurrent connections reach, it will stop accepting new connections until concurrent level drop below 500.