When you need to submit a bug report you need to provide as much information as you can. Including
Your Server
OS (Linux/FreeBSD/Solaris/MacOSX)
CPU/Processor family (32bit/64bit)
If you think LSWS does not work properly with certain feature, you should provide as detail information as possible for us to reproduce the problem in our lab.
If lshttpd crashed, LSWS Enterprise user should switch to the debug build of lshttpd, then submit the debug report generated and core file if possible.
The GDB stack backtrace and core file generated with a debug build of lshttpd is the most useful information for fixing the bug. there are two version of lshttpd binary shipped in LSWS Enterprise package. One is release build, another is debug-build version. In the distribution package, they are:
lsws-<version>/bin/lshttpd
lsws-<version>/bin/lshttpd.dbg
by default, the release version is used, install to the target directory as “lshttpd.<version>”, the debug build is install to the target directory as “lshttpd.dbg.<version>”, but not being used. In order to get most useful bug report, you need to switch to the debug build manually. Following steps should be taken:
cd /opt/lsws/bin
ln -sf lshttpd.dbg lshttpd
./lswsctrl restart
Then try to reproduce your problem and submit a bug report.
By default, core dump is disabled for LiteSpeed PHP, to enable it, you need to add environment variable to lsphp5 external application configuration
LSAPI_ALLOW_CORE_DUMP=1
In addition, you need to enable core dump at server wide. How to enable core dump for Linux
