User Tools

Site Tools


poolinfo:dashboard:harvesters

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
poolinfo:dashboard:harvesters [2022/12/09 23:49] vleesbanaanpoolinfo:dashboard:harvesters [2023/01/07 10:33] (current) – added info regarding the harvester Partials (time) panels vleesbanaan
Line 1: Line 1:
-==== Dashboard - Harvesters ====+===== Dashboard - Harvesters =====
  
 In the Harvesters tab, you can find useful information on your individual harvesters' performance in order to help you improve your farm. Specifically, it shows  In the Harvesters tab, you can find useful information on your individual harvesters' performance in order to help you improve your farm. Specifically, it shows 
Line 9: Line 9:
  
 You can set the name for your harvesters in the [[poolinfo/dashboard/personalize|settings page]]. You can set the name for your harvesters in the [[poolinfo/dashboard/personalize|settings page]].
 +
 +{{ :poolinfo:dashboard:dashboard_-_harvestersv2.png?800 |}}
 +
 +If you select Partials (time) from the dropdown, you can see the time taken of your partials per harvester. By clicking a partial, you can even see from what plot the partial originated. There's no better way to monitor and improve your farm than this! 
 +{{:poolinfo:dashboard:dashboard_-_harvestersv2_partials.png|}}
  
 If you are using docker or machinaris, your harester ID will by default reset on every start up.To prevent this:  If you are using docker or machinaris, your harester ID will by default reset on every start up.To prevent this: 
  
-=== Official Docker ===+==== Official Docker ===
 +**Step 1:** On the first run of a harvester, launch of the container with the following  environment variables 
 +    * ''keys'' set to ''copy'' 
 +    * ''ca'' mapping a copy of the ''.chia/mainnet/config/ssl/ca'' directory of the **farmer node** 
 +This will create what's needed for the harvester to be authenticated with the farmer node with a ''chia init -c "ca"''
  
-  -  On the first run of a harvester, launch of the container with the following  environment variables +**Step 2:** If the communication between the harvester and the farmer is properly established, stop the container, and set ''keys'' to ''persistent''.
-  ''keys'' set to ''copy'' +
-  ''ca'' mapping a copy of the ''.chia/mainnet/config/ssl/ca'' directory of the **farmer node** +
-This will create what's needed (?) for the harvester to be authenticated with the farmer node with a ''chia init -c "ca"'' +
-  - If the communication between the harvester and the farmer is properly established, stop the container, and set ''keys'' to ''persistent''.+
 The harvester ID is now persistent, and will be perserved even when the container is upgraded. The harvester ID is now persistent, and will be perserved even when the container is upgraded.
  
-=== Machinaris ===+==== Machinaris ====
   - Follow the instructions to run a remote harvester, machinaris automates the step 1 above   - Follow the instructions to run a remote harvester, machinaris automates the step 1 above
   - Stop the container, edit the ''docker-compose.yml'' and add ''- keys=persistent'' in the environment section. Rebuild the container (''docker compose up -d --force-recreate machinaris''), and you're done as above.    - Stop the container, edit the ''docker-compose.yml'' and add ''- keys=persistent'' in the environment section. Rebuild the container (''docker compose up -d --force-recreate machinaris''), and you're done as above. 
  
  
poolinfo/dashboard/harvesters.1670629796.txt.gz · Last modified: 2022/12/09 23:49 by vleesbanaan

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki