2.1.19 broken?

#1
Hello,

I upgraded from 2.1.18 to 2.1.19 and now my webserver monitoring script is sending me SMSses for nothing. I have a script running on another machine that checks the webserver every minute by requesting /monitor.php and check if the response is 'Ok' (monitor.php = <?echo "Ok";?>).

Looking further into my monitor script it seems that litespeed sometimes accepts a connection and returns absolutely nothing.

I reverted back to 2.1.18 and the problem is gone. Possible bug?

Thanks for any help I can get here...
 
#2
After reading the sticky thread i can give you the folowing sys-info information. Anything else required to help resolve this problem?

1) Linux 2.6.17 (32 Bit)
2) Litespeed 2.1.9 ENT
3) LSAPI PHP 5.1.4
4) Nothing in error.log about this.
 
#3
and i also have a couple of crontab scripts which take a website from the webserver by downloading the page from it's URL and writing it to a .html file.
Some of those files are now 0bytes in size. Since i reverted back to 2.1.18 all these problems are gone away.

Can anyone confirm if this is either a bug or configuration error ?
 

xing

LiteSpeed Staff
#4
without knowing your site configuration and crontab/url get method, it would be hard to replicate this problem.

1) You can privately send us your /lswsinstall/conf/httpd.xml + the vhconf.xml file in the vhost directory to bug@litespeedtech.com.

2) Let us know what tool you are using within crontab to retrieve the html file (wget/curl/etc).

3) Did litespeed log any error/warning associated with the cronjob in error.log or stderr.log?
 
#5
well, the monitor is a PHP script which does a file_get_contents("http://blabla/monitor.php");

I don't know of any way to reproduce the problem because it's not always doing the same thing. Since 2.1.19 the monitor works most of the time, but it sometimes gets an empty page back from the webserver and then sends me an SMS telling there's something wrong with the webserver.

I tried the same thing with an empty configuration, new setup:

For testing you could just setup a website and add monitor.php in it : <?echo "Ok";?>

Then write a script that downloads monitor.php every minute: <? file_get_contents("http://server/monitor.php"); .. and check it's result ..?>

It returns "Ok" most of the time but sometimes it fails... And it doesn't happen with 2.1.18 and below.

Hope this helps in recovering this error...
 

xing

LiteSpeed Staff
#6
Here is our test script running every 1 second.

PHP:
<?
while(1) {
        $check = file_get_contents("http://localhost/monitor.php");
        if($check != "ok") {
                die("error...reproduced problem");
        }

        echo time() . ": good\n";

        sleep(1);
}
?>
Lsws 2.1.19
PHP 5.1.4 LSAPI
2.6.17.7

So far we cannot reproduce it but we will keep the test case running for a few hours on our live server.
 

xing

LiteSpeed Staff
#8
Akke,

Turns out our initial 2.1.19 release contained a small problem which has been patched just a few hours after release. It would explain why I am not able to reproduce this problem has it has been patched with the updated binaries.

If you are still having this issue, please re-download 2.1.19 from our site.
 
#9
Hi!

I have just installed the latest version and I already reproduced the problem, so it's not (yet) fixed...

I do have 1 vhost and 1 listener with '*' as the domain and don't know how to reproduce the problem but with my monitor-script running it happens like 1 or 2 times an hour (live webserver, maybe this bug is triggered depending on the current visitors, connection count or something..)

Any config option I should consider changing in order to help debug down the problem?

Thanks!
 

xing

LiteSpeed Staff
#10
We have yet to reproduce this problem with our script which test every second for 8 hours also on a live server with almost the exact specs as your server.

What we need to do is capture the entire transmission as it fails via a tool like lynx:

lynx -mime-header http://testurl/

The above command would connect to page and instead of rendering it, output the entire http header + body.

Please email your /conf/httpd.xml and /vhost/conf/vhost.xml files to bug@litespeedtech.com. We need check and test your config settings.

In addition, how much traffic/concurrent static/dynamic requests is your server handling?
 
Top