Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
litespeed_wiki:config:bug-reporting [2019/04/02 15:13]
Jackson Zhang
litespeed_wiki:config:bug-reporting [2019/04/02 16:10]
Jackson Zhang
Line 1: Line 1:
 ====== How to submit a bug report ====== ====== How to submit a bug report ======
-There are two cases you can log a bug report. 
-One case when the server crashed and core files were generated at /​tmp/​lshttpd/​bak_core/,​ you can submit a server crash report. 
-The other case is server doesn'​t crash at all, but LSWS doesn'​t work as expected, especially it works with apache but doesn'​t work with LSWS in the control panel environment. In this situation, you can turn on debug logging when reproducing the issue, then send the detailed debug log for us to investigate. ​ 
- 
-We will discuss the proper bug report processes for both cases in the following. 
- 
-===== Submit a server crash report =====  
- 
 ==== Always upgrade to the latest version of Latest build before submitting a report ==== ==== Always upgrade to the latest version of Latest build before submitting a report ====
  
-New version/new build of web server may hit the bug, crash and generate core files at /​tmp/​lshttpd/​bak_core/​core.*. Normally you will receive some email alert on this situation. You are welcome to sumbit such server crash report ​to us, either forwarding the alert email to us or forwarding core files to bug@litespeedtech.com.+There are two cases you can log a bug report. ​
  
-Before you log such server crash bug report to us, it is always a good practice to check which release ​versio ​and which BUILD caused such crash.+One case when the server crashed and core files were generated at /​tmp/​lshttpd/​bak_core/,​ you can submit a server crash report. 
 +The other case is server doesn'​t crash at all, but LSWS doesn'​t work as expected, especially it works with apache but doesn'​t work with LSWS in the control panel environment. In this situation, you can turn on debug logging when reproducing the issue, then send the detailed debug log for us to investigate.  
 + 
 +Before you log such server crash bug report to us, it is always a good practice to check which release ​version ​and which BUILD caused such crash.
   cat /​usr/​local/​lsws/​VERSION   cat /​usr/​local/​lsws/​VERSION
   cat /​usr/​local/​lsws/​BUILD   cat /​usr/​local/​lsws/​BUILD
  
-If it is still an old version or old build, please ​alway run the force upgrade command so that you are using the latest build of the latest version. This action alone may fix your problem.+If it is still an old version or old build, please ​always ​run the force upgrade command so that you are using the latest build of the latest version. This action alone may fix your problem.
  
   /​usr/​local/​lsws/​admin/​misc/​lsup.sh -f -v <​latest_version_number>​   /​usr/​local/​lsws/​admin/​misc/​lsup.sh -f -v <​latest_version_number>​
  
 then monitor your server to see if it happens again or not. If yes, please take the following steps to log the server crash report. then monitor your server to see if it happens again or not. If yes, please take the following steps to log the server crash report.
 +
 +
 +===== Submit a server crash report ===== 
 +
 +New version/new build of web server may hit the bug, crash and generate core files at /​tmp/​lshttpd/​bak_core/​core.*. Normally you will receive some email alert on this situation. You are welcome to sumbit such server crash report to us, either forwarding the alert email to us or forwarding core files to bug@litespeedtech.com.
  
 ==== Email alert received with debug info ==== ==== Email alert received with debug info ====
  • Admin
  • Last modified: 2020/01/03 17:52
  • by George Wang