Search results

It means that the file is opened with file handle #38, still being accessed by clients. It is not MMAPed. web server need to keep the file open in order to send the file back to clients. The css is a file used during performing the update. web server keep the file open when a file is accessed...

The crash is inside sqlite, you can let php dump a core file by add environment LSAPI_ALLOW_CORE_DUMP to lsphp5 ext app. once find the cause of the crash, submit bug report to corresponding party.

could be a rewrite rule rewrite the custom 403 page ? You can enable rewrite logging along with debug logging.

looks like the file was uploaded in wrong way, the original file does not have "^M".

you also need to add "LSAPI_MAX_PROCESS_TIME" env to lsphp5 external app. http://www.litespeedtech.com/php-litespeed-sapi.html

Unless it is from Igor@CL, I wont take this comment seriously. Whenever LVE return an error, it will be logged into stderr log like You can check /usr/local/apache/logs/stderr.log Your 503 error is likely due to PHP crash for some reason. It is not hard to figure out with strace and gdb if...

that's due to process limit of LVE being reached, not CPU limit. that is still pending due to the way Litespeed communicates with CL LVE. If you can reliably reproduce this issue, you can try to strace the PHP process processing the request, since it run for a while, it is not difficult to...

It depends, maybe a little bit.

You need to add those MIME types in configuration. http://www.litespeedtech.com/docs/webserver/config/general/#mime

Yes, that's the way how PHP/APC works. That's the reason why we introduce suEXEC daemon mode.

CL LVE should not cause 503 error when CPU limit is reached. However, PHP itself may terminate the request if "max_execution_time" is reached. http://www.php.net/manual/en/info.configuration.php#ini.max-execution-time

you can ignore signal 15, only signal 11 is crash. yes, those which logs looks suspicious.

trial key has been used on that IP before. Please contact sales@litespeed... to have your IP cleared if you need more time to evaluate it.

Please check stderr.log see if you get some entries like: signal 11 is segfault, means PHP crashed with memory related problem. add LSAPI_ALLOW_CORE_DUMP env to lsphp5 extapp see if core dump can be created, "core dump: 1" will be logged. you can try to figure it out with core dump or submit...

LiteSpeed uses MMAP to optimize static file delivery. but in this case, MMAP has to be avoided. You need to change server configuration under tuning tab: Max MMAP File Size (bytes): 0 Total MMAP Cache Size (bytes): 0 Use Asynchronized disk I/O (AIO): Yes (Do not use "Keep file mapped")

You need to check /opt/lsws/conf/httpd_config.xml, maybe the main configuration file is corrupted. May need a complete reinstall.

add "--disable-pdo" option to PHP build configuration.

You can ignore that message as LSWS use Apache configuration file. that's normal.

This issue should have been addressed in latest 4.2.4 update, just ask your host provider to do a force reinstall of 4.2.4 .

Sorry about that, try to address a drupal user_dir issue affected this. Please force reinstall, should be fixed now.