Search results

Ok i will see if it helps...thx

Hi, i have the Problem, that my site will load fast, or produce Error 503. The Error 503 will show up on every ~20 request The RealTime Stats show no wait Queue and my Settings are these: <tuning> <maxConnections>2000</maxConnections> <maxSSLConnections>200</maxSSLConnections>...

Same Problem I have reinstalled the whole server 3.3.4 is now running without problems PHP4 and PHP5 also And now FF wont show stylesheets. Changed admin/html/classes/ws/GUI.php line 10 "HTML 4.01" into "HTML 4.0" Now it worls in IE and FF So you definetly get FF problems when...

Hi, is the standard PHP setting used by LSWS good enough for high traffic websites? We use php 4 and 5 and do compile them ourself with litespeed sapi. Should we use the standard settings lsws came with or do you recommend different settings? We have ~80 virtual hosts on 25 listeners...

OMG, it is a total mess. I probably have to reinstall the whole server. Upgrading from 3.2.4 to any newer version leads into non working stylesheets and JS. Therefore, i can not downgrade anymore. Tried to compile new php 5.2.5 with lsws web interface. It worked almost. New php version became...

Iam upgrading one of our 6 servers to 3.3.4. It doesnt load the StyleSheets in FF, IE and Opera. Even Changing the DTD to 4.0 to enable Quirks mode doesnt help. What could i do to get the Stylesheets working?

Yes iam sure, i have 6 Litespeedservers running and all of them had the same effect. And for Gecko Quirks mode, 4.0 will use the mime type on the css link, 4.01 will overide the mime type by the server mime type wich is obviously set to text/html. If you would add mime.properties to admin...

Go to $SERVER_ROOT/admin/html/classes/ws and edit GUI.php Change around line ~10 HTML 4.01 in HTML 4.0 Styles will be loaded again... Marcus

done.... (is it tomorrow allready??? no, not yet, i am just to fast....)

ok, i will do that and report tomorrow

I just upgraded all 3 Servers to 2.1.9. We will see if i still get core dumps. I just tried to upload a 14 MB File which seems to work fine now...

Ok, whats next?

At [21/Dec/2005:19:38:04 +0100], web server with pid=20213 received unexpected signal=11, a core file is created. A new instance of web server will be started automatically! Please forward the following debug information to bug@litespeedtech.com. Environment: Server: LiteSpeed/2.1.6...

The version used is 2.1.6 ent dbg The /tmp was cleaned up when we encountered the error to be the fault of 2.1.7 I cant use any version beyond 2.1.6 until i can be sure the upload problem is solved in any way, Our developer Teams will just kick our butts to hell.

I have put sum core files here: http://www.mobile2day.de/core_dump/ These are from HOST WEB5 and i will add them always if i find new ones Marcus

I had hundreds of core dumps. i had to delete them all to get the server working and then i disabled the core dump. That means i dont have a dump right now. But i get Emails everey couple hours with this: At [21/Dec/2005:16:12:51 +0100], web server with pid=14825 received unexpected...

Hi, first of all, it took me 5 hours to find out that the error was based on zhe update to 2.1.7. I really checked every logfile i could find on the server to see whats happening - nothing - I saw the upload process with a grep on my local ip in the stderr but suddenly it just stopped, no...

iam getting off work right now, here in germany its already 8PM good night and if you need mor information, just email me, but i will look here again tommorrow anyways Marcus

It is with self compiled php 4.3.9 (http://www.mobile2day.de/info.php) running as lsphp (just replaced original one) The error is 404 because server does not respond to request in any way, so its the same error Firefox gets when not finding a server "Document contains no data" The error...

After upgrading to 2.1.7 enterprise, File uploads will result in 404 error even if file size is below php.ini settings or lsws tuning settings We allow file uploads up to 200M which are no problem with our settings. It takes some time but it works fine. After we got back to 2.1.6...