Differences

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

--- guides:farming:debug_log [2021/09/07 07:20] – [Debugging using Powershell] spacefarmer01
+++ guides:farming:debug_log [2021/10/29 12:10] (current) – vleesbanaan
@@ Line 1: / Line 1: @@
 ===== Debugging =====
-FIXME <this page is under construction>
 Before you start debugging, we advise you to use our [[resources:tools:logtool|Harvest Inspector]]. If the inspector finds many errors, follow the steps in this guide to improve your farming.
@@ Line 6: / Line 5: @@
 ==== How to enable your Chia debug log? ====
-  - Navigate to the config.yaml file in your .chia folder. For Windows the default path is ''C:\Users\<username>\.chia\mainnet\config'', for Linux ''~/.chia/mainnet/log/config'', and for Mac ''/Users/<username>/.chia/mainnet/config''
+  - Navigate to the config.yaml file in your .chia folder.
-  - Open the file called "config"
+     * For Windows: ''C:\Users\<username>\.chia\mainnet\config''
+     * For Linux: ''~/.chia/mainnet/log/config''
+     * For Mac: ''/Users/<username>/.chia/mainnet/config''
+  - Open the file called "config.yaml"
   - Find a line called "log_level: WARNING" and change this to "log_level: INFO" and hit save
-  - Restart Chia for the change to take effect
+  - Restart Chia for the change to take effect.
 Now you can see detailed information in your Chia debug log, which is found in the chia folder.
-  * For Windows users the default path is ''C:\Users\<username>\.chia\mainnet\log\debug.log''
+  * For Windows: the default path is ''C:\Users\<username>\.chia\mainnet\log\debug.log''
-  * For Linux users the default path is ''~/.chia/mainnet/log/debug.log''
+  * For Linux:  the default path is ''~/.chia/mainnet/log/debug.log''
-  * For Mac users the default path is ''/Users/<username>/.chia/mainnet/log/debug.log''
+  * For Mac: the default path is ''/Users/<username>/.chia/mainnet/log/debug.log''
 ==== What to look for in the logs? ====
@@ Line 22: / Line 24: @@
-==== Debugging using Powershell ====
+==== Debugging using PowerShell ====
-Scanning your debug log with ''tail | grep'' in Powershell is perhaps the easiest way to aggregate the information you are looking for.
+Scanning your debug log with ''tail | grep'' in PowerShell is perhaps the easiest way to aggregate the information you are looking for.
+For monitoring your harvester timing, for example, use
-For monitoring your harvester times for example, use
 '' Get-Content -Path "~\.chia\mainnet\log\debug.log" -Wait | Select-String -Pattern "found"''
 And for finding errors, use
 ''Get-Content -Path "~\.chia\mainnet\log\debug.log" | Select-String -Pattern "error"''