Search results

Yes, I noticed the 404 errors as well, pretty strange. Can you turn on the debug logging for a little while, it will help us analyzing the problem. It will generate tons of log messages for a heavily traffic web site, be careful. You can use the toggle debug logging feature to turn it on...

Does the .htaccess file got updated frequently or the modified time of the file keeps changing?

Looks like something wrong with the rewrite rules in .htaccess, rewrite rules has not been executed, Can you please try the rewrite rules at the vhost level, see if the problem dissapear. Please make sure that the full URL is used in the vhost level rewrite rule. Only custom error pages set...

Looks like a problem with the rewrite engine, not the problem I mentioned. Can you please turn on the rewrite logging under the "Rewrite" tab? And send me the log messages for a request that results in 404 code (with the file not found error), grep with the client ip address can be used to...

What rewrite rule is used? Is [/home/wporg/public_html/support/topic/52511] a directory or a file? If it happens randomly, I think it might be a problem like "running out of file descriptors".

Are you sure it is /etc/passwd out side the jail, not the /chroot/etc/passwd? If it is, then it is a bug means that the CGI has not been chroot properly. As some application need to read /etc/passwd to work properly, so I don't recommend making it not world readable, you can fake a passwd...

If you install lsws to /opt/lsws, then you can only chroot lsws to /opt or /opt/lsws, as the lsws must be installed inside the jail. when you specify the server root path, full path including the jail must be given. :-)

I think it is a unix account security issue. A private group should be created for each user, the root directory of each user should be owned by the user and the private group, perission should be 0750 or 0770. then only this user can read his own directory. The user that web server...

Sorry, we don't have a document regarding the syntax of the configuration file. The xml configuration file should be easy to understand, try changing configurations form the web interface, then reference the configuration file, you should be able to get familiar with it. :-)

I think you can start to test 2.1.8 on your test machine. Send me the debug log if you can reproduce the upload problem. :-)

The latest 2.1.8 package should have this addressed. This bug does not related to the upload problem though.

Please tell me which version/edition of LSWS is used, I tried the core files with different binaries, does not work. If there is any back trace information in the email you received, please forward. I think you upload problem probably is related to the /tmp directory, as PHP store uploaded...

I guess the hundreds of core files you got is before you set the admin email, don't you? It should be ok to enabled core dump once the admin email is set, as long as your /tmp has enough space left for maximum 10 core files. If you do mind, please enable core dump, maybe temporarily, we...

Hi Marcus, Sorry about that. When admin email is set, lshttpd should only keep the latest 10 core files, we will reduce it to 5. Sometime the core file is just too big to be sent in a email. changing the core file directory is a good idea. If you don't mind please send us the core files...

Does that mean that the problem can be reproduced on your test server with large files? Sometimes it work, sometimes it does not. If so, can you please turn on debug logging on the test server, then send the error.log to bug @ litespeedtech.com. debug logging is not recommended for production...

Is that with LSAPI PHP? Are you sure it is 404 error? 404 is file not found. Is there any thing special for the URL for the upload request, like special context, rewritten url etc? Can you please give 2.1.8 a try, just download the new release by changing the version number. Thanks...

Thanks! Thomas. :-) There are some changes in dynamic response body handling to avoid closing the persistent connection to backend application when there is no response body, like a HEAD request or 304 response, hope the change does not break anything. :-)

Thomas, You can give 2.1.8 a try if you are available before our official announcement. Thanks, George

I think you are pretty close to figure out the missing libraries. When you straced the lsperld.fpl, you actually traced the cgi-fcgi or whatever the fcgi spawner you used, not the lsperld.fpl itself. You should either let strace to trace children process by adding an command line option, or...

It is because of a bug introduced by 2.1.7, will be fixed in 2.1.8.