Search results

This is specifically for Litespeed processing GeoIP into the HTTP request headers. Depending on how your website it setup, the IP header being used by Litespeed for GeoIP isn't necessarily the client IP header. In our case, it is often a proxy IP (CDN middleman) with the client IP being...

I know 100% for sure it is calling the lsapi. The lsapi is presently configured to invoke strace on lsphp-5.2, so if .php weren't associated with this lsapi then strace wouldn't be getting called. That file also does not exist.

Hi there, LSAPI App lsphp-5.2 uds://$SERVER_ROOT/tmp/lsphp-5.2.sock $SERVER_ROOT/fcgi-bin/lsphp-5.2 stat /usr/lsws/fcgi-bin/lsphp-5.2 File: `/usr/lsws/fcgi-bin/lsphp-5.2' -> `/usr/lsws/fcgi-bin/lsphp-5.2.17' The referenced file in /proc doesn't exist.

ZendGuard is not enabled. Running lsphp-5.2 -i works without error. Executing fcgi-bin/lsphp-5.2 /home/www/htdocs/php.php executed successfully. Executing it over lsws fails.

Hi there, I have setup a small VM with a Litespeed enterprise license on it. The VM runs Fedora 15 x86_64. PHP and Lsws compiled and installed properly. When I call PHP, however, I get no response at all. Running the lsapi process thru strace ends in: It references libgcc_s.so.1...

Okay, something in how Litespeed acted between 4.0 and 4.1 changed which made the permissions on my shared config folder no longer valid. The folder is owned by lsws and only had read access to members of its UID/GID. While looking into this I came across another issue that your opinion could...

Sorry for this large delay in my response. This issue is pretty low on the priority list as it doesn't affect service. The link you provided does not appear to apply. admin_php is running as lsadm on the server. /usr/lsws/conf/httpd_config.xml is owned by lsadm:lsadm and is, by default...

Hi there, I just noticed that all of my Litespeed 4.1.3 web servers are giving generally the same error when I try to do anything requiring it to access httpd_config.xml except on the General page. /usr/lsws/conf/httpd_config.xml is a symbolic link on all of our web servers. The file is...

Our load balancer is session aware, but if you're logged into the ACP of a product that session might not be removed after you've left the ACP. That's why we're looking to go this alternate route.

Hi there, Not sure if this would be considered a bug or a feature request, but to offer the benefit of the doubt we'll go with feature request :) In the mod_rewrite documentation for Apache 2.2 there is support for setting cookies using rewrite rules. [see...

Makes sense, webizen. Also, so far so good. No errors with the 4.1 box 17 hours later.

Okay, I've ran the force reinstall. If the issue happens again I will reply again. Until later, good night! Fyi - it still thinks 4.0.20 is newer than 4.1.

Hi there, As you may know, I run a CentOS-based web cluster utilizing Litespeed on all of our backend nodes. A couple weeks ago I upgraded all of our Litespeed servers from 4.0.19 to 4.1. First, the minor issue - 4.1 keeps informing me that a new version is available (4.0.20). Next, the...

Aha, I see. Yes, this appears to have done the trick. All of the sudden feature implemented. Thank you :)

As I stated in my original post, I am using 4.1.

A slightly modified combined format - %{X-Client-IP}i - %h %l %u %t "%r" %s %b "%{Referer}i" "%{User-agent}i"

I set the server-level logFormat and it was not inherited by any of the VHs. Any idea why that may be?

Set it on the web server side? Litespeed is the web server. Our load balancer uses a header other than X-Forwarded-For making the Client IP Header feature useless. We can't change that. Mind you, we don't use LSLB. Aside from this one example of different client IP headers, being able to...

Except X-Forwarded-For is not the header presented making that not so helpful.

Hi there! I am running Litespeed 4.1 Gold in a load balanced environment. While the load balancer supplies the remote client IP address in its own header, Litespeed logs using the default Remote Host header which is that of the load balancer. This makes the standard combined format logs...