Chives Harvester Check How to check: Edit the Chives config.yaml, search for "WARNING", change it to "DEBUG", and restart both the farmer and the harvester service: chives start farmer -r chives start harvester -r Check both farmer and harvester log using a text editor of your choosing. The Chives farmer log will show it's farming from the harvester with the harvester's IP --->>> "<- farming_info from peer 430c1f9d4f87da550af452452fd6db0d3973593710eccb957cc450fde69908e7 10.0.0.2" 4) The harvester log will show it's farming to peer --->>> "-> farming_info to peer 10.0.0.1" Here are the Linux commands to check log whether the farmer and harvester node(s) are connected: tail -f ~/.chives/mainnet/log/debug.log tail -f ~/.chives/mainnet/log/debug.log | grep "<- farming_info from peer" Some of this information was gathered by personal experience and the other information was gathered from the Chives Official Discord from JohnD#8034 and 🈶TaijiMonster🉐#2350.

How to ensure your harvester is functioning correctly?

Zach_Dumas

Chives Harvester Check

How to check:

Edit the Chives config.yaml, search for "WARNING", change it to "DEBUG", and restart both the farmer and the harvester service:

chives start farmer -r

chives start harvester -r

Check both farmer and harvester log using a text editor of your choosing.
The Chives farmer log will show it's farming from the harvester with the harvester's IP --->>> "<- farming_info from peer 430c1f9d4f87da550af452452fd6db0d3973593710eccb957cc450fde69908e7 10.0.0.2"
4) The harvester log will show it's farming to peer --->>> "-> farming_info to peer 10.0.0.1"

Here are the Linux commands to check log whether the farmer and harvester node(s) are connected:

tail -f ~/.chives/mainnet/log/debug.log

tail -f ~/.chives/mainnet/log/debug.log | grep "<- farming_info from peer"

Some of this information was gathered by personal experience and the other information was gathered from the Chives Official Discord from JohnD#8034 and 🈶TaijiMonster🉐#2350.