Differences

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

--- litespeed_wiki:config:bug-reporting [2019/04/22 13:36]
Jackson Zhang [Email Alert Without Debug Info]
+++ litespeed_wiki:config:bug-reporting [2019/12/24 15:21]
George Wang [How to Toggle Debug Logging and Capture Output]
@@ Line 15: / Line 15: @@
   /usr/local/lsws/admin/misc/lsup.sh -f -v <latest_version_number>
-Monitor your server to see if the issue recurrs. If it does, please take the following steps, as appropriate, to log a report.
+Monitor your server to see if the issue reoccurs. If it does, please install the debug build:
+  /usr/local/lsws/admin/misc/lsup.sh -f -d -v <latest_version_number>
+Monitor your server to see if the issue reoccurs. If it does, please take the following steps, as appropriate, to log a report.
 ===== Submit a Server Crash Report =====
@@ Line 276: / Line 279: @@
   mv error_log error_log.debug
-The ''error_log.debug'' file could be very big if it is a busy shared production server, since there could be many domains servicing requests at the same time. It might be good to just focus on the IP of your location. (You can easily find your own IP by searching ''IP'' at google.com.)
+The ''error_log.debug'' file could be very big if it is a busy shared production server, since there could be many domains servicing requests at the same time. When forward the log file please compress it.
+If compressed log file is still too big, it might be good to just focus on the IP of your location. (You can easily find your own IP by searching ''IP'' at google.com.)
   grep your_IP error_log.debug > error_log.debug.ip
-(Substitute your actual IP address where it says ''your_IP''.)
+(Substitute your actual IP address where it says ''your_IP''.)  Some related debug log entries are not marked with your IP address, so we may miss some important information to diagnose the problem. The original log file should be kept just in case we need that. We recommend sending the full log.
 You can then forward ''error_log.debug.ip'' along with detailed steps to reproduce issue to ''bug@litespeedtech.com'' for investigation.