The script does not produce an error neither in the error_log nor in Litespeed's log. It just fails by return "HTTP Error".
Here is some more information about my setup:
- lsphp 5.2.17 with configure flags:
- upload dir is /tmp which is mounted on tmpfs
- suexec is on
Did the force reinstall, the old issue was fixed but the problem with the uploads remains.
Actually, it will. 4.1.12 breaks randomly static file transfers (like images, css or js files) and corrupts them, leaving the client with...
Sadly no, these are the clues I have. Even strace'ing the process running the upload shows nothing (to my not that much trained eye).
I've been getting a strange error with every website running Wordpress ever since I recompiled PHP 5.2.17 with the LSAPI present on LSWS...
Did that in order to get my server to an operable state. With 4.1.11 I get no load issues.
I get extremely high loads on 4.1.12. The error log says:
2012-04-10 13:15:44.416 [WARN] Remove looping fd: 50, event: 1
+1 from me
Is this possible via .htaccess
or do I need to open debug logging throught LSWS's console?
I've been experiencing a very strange issue with a website that uses UTF-8 regular expressions in the rewrite rules:
This should be then a feature request then, since with suexec disabled PHP is pretty much useless in a shared environment.
FYI, nginx + php-fpm...
I've been experiencing cache clearing as well. I have configured Litespeed to let PHP/LSAPI to self-manage its instances:
No, no LSWS process is listening on IPv6 interfaces. The configuration files are autogenerated by Plesk and are valid:
In the interest of not opening a new topic on IPv6 support, I have recently upgraded to Plesk 10.3 and I am getting these errors on a...
In Plesk 10.2, I don't get the option to enable mod_php! It's just PHP fastcgi and that's it!
Parallels disables by default the mod_php engine through the dynamically generate server configuration file in...
It seems that LSWS 4.1 does not honor the PHP CGI clause that Plesk 10.2 uses to enable PHP support on a domain:
<Files ~ (\.php)>...
This feature would be useful outside of the normal LSWS vhost XML configuration (ie in an .htaccess or Apache-style .conf files), because even though...
Yes the piped logger is running "fine":
[root@server2:/root]> ps aux| grep [p]ipelog
root 3957 0.0 0.0 5376 1072 ? S 08:02 0:00...
Separate names with a comma.