Has anyone else had issues with Litespeed failing to read .htaccess files randomly?
On one server, at random intervals, we see this in the...
I'll submit server details to a ticket so you can take a look as there's certainly something not quite right.
One of our servers appears to have upgraded itself to cPanel 11.38 and we're having trouble installing SSL certificates.
Thanks for the reply.
I don't think that's the case here, nothing else shows up in the logs and everything seems normal. The timestamp also...
I'm seeing a lot of the following in the stderr.log as well as a lot of random disconnects and freezing.
2013-03-03 23:54:51.081 [STDERR]...
We're using Litespeed with CloudLinux and are seeing the process lshttpd owned by 'nobody' using 100% CPU constantly.
Nothing obvious shows...
I echo pretty much everything QuantumNet has said.
I've tried various rules using different methods and nothing appears to be working.
Is your /tmp directory full?
Is it still true it doesn't support all rules and only a small selection?
Have there been any updates to this?
This is becoming a problem and as far as I can see it's just being overlooked. I've got a fair amount of...
I assume these instructions are outdated as the path /usr/local/lsws/lsphp5/bin no longer exists.
That still doesn't answer his question...
Thanks, I've checked that log and nothing seems to be getting logged for that site.
Has anyone else seen a rise in 503 errors on the latest version? (.20)
Here's an entry from the logs:
2011-03-21 21:19:44.552 [INFO]...
I've managed to resolve the issue by removing CloudLinux. Apparently this is fixed with 4.1 but I'll wait for it to become stable before booting back...
Has anyone had problems with the lshttpd process consuming 100% CPU on recent versions?
We're running a 4 core license on a 16 core server...
I don't quite get it either - I never had a problem building PHP without switching to Apache before.
Installed and tested and it seems to work perfectly, no longer an issue :)
It also affects 4.0.11,12 and 13 so it's not just a .14 thing.
I just had an email from George saying it's being looked in to and they'll post a fix later today if they're able to replicate it.
Separate names with a comma.