Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
litespeed_wiki:howto:bug_report [2015/02/26 14:32] Jackson Zhang |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== How to submit a bug report ====== | ||
| - | To submit a useful 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 a certain feature, you should provide as detailed information as possible on the feature and how you use it, so we can reproduce the problem in our lab. | ||
| - | * If lshttpd crashed, LSWS Enterprise users should switch to the debug build of lshttpd, then submit the debug report generated and a core file if possible. | ||
| - | |||
| - | ===== How to switch to the debug build of LSWS Enterprise ===== | ||
| - | There are two versions of the lshttpd binary shipped in the LSWS Enterprise package. One is the release build. The other is the debug build. The debug build is not normally used when you run LSWS, but, when debugging, the GDB stack backtrace and core file generated by the debug build are the most useful information you can provide for fixing the bug. | ||
| - | |||
| - | These two builds are shipped in the distribution package as: | ||
| - | |||
| - | lsws-<version>/bin/lshttpd | ||
| - | lsws-<version>/bin/lshttpd.dbg | ||
| - | |||
| - | The release version is installed as "lshttpd.<version>", while the debug build is installed as "lshttpd.dbg.<version>". In order to use the debug build (and produce the data that will allow us to more effectively debug your issue), you need to switch to the debug build manually: | ||
| - | |||
| - | cd /opt/lsws/bin | ||
| - | ln -sf lshttpd.dbg lshttpd | ||
| - | ./lswsctrl restart | ||
| - | |||
| - | Once you have switched, reproduce your problem and submit a bug report. | ||
| - | |||
| - | ===== How to download debug build of LSWS Enterprise ===== | ||
| - | If there is no debug build of lshttpd binary in your current installation, you can download the related version and arch of debug build from our website. For example: | ||
| - | |||
| - | wget http://www.litespeedtech.com/packages/dbg/lsws-<version>-ent-x86_64-linux-dbg.tar.gz | ||
| - | tar xvfz lsws-<version>-ent-x86_64-linux-dbg.tar.gz | ||
| - | cd lsws-<version> | ||
| - | ./install.sh | ||
| - | |||
| - | then just hit enter till the end. | ||
| - | |||
| - | Once you have debug version installed, reproduce your problem and submit a bug report. | ||
| - | |||
| - | ===== How to enable a core dump ===== | ||
| - | |||
| - | ==== For PHP ==== | ||
| - | By default, core dumping is disabled in LSAPI PHP external applications. To enable it, you need to add an environment variable to your LSPHP external application configuration (WebAdmin console > Configuration > External App > your external application > Environment): | ||
| - | |||
| - | LSAPI_ALLOW_CORE_DUMP=1 | ||
| - | |||
| - | ==== Server-wide ==== | ||
| - | Core dumping is generally disabled by default on Linux. The following guide will lead you through the steps necessary to enable it: [[http://en.linuxreviews.org/HOWTO_enable_core-dumps|How to enable core dump for Linux]] | ||
| - | |||
| - | |||
| - | ===== Where to send the bug report ===== | ||
| - | Bug reports can be sent to our [[bug@litespeedtech.com|bug report email]]. | ||
| - | |||
| - | We recommend that Enterprise customers use our ticket system (accessible from [[https://store.litespeedtech.com/store/clientarea.php|the client area]]) for their bug reports. | ||