Replies: 2 comments
-
|
actually I just got this fixed I think what happened was i blew out all my containers on my harvester nodes and deleted all the /root/.machinaris* folders this works for all containers except for chia, btcgreen and shibgreen - these harvesters would not report any plots to the main node. For my chia node all I did was recopy my CA keys from the main node and ran "chia init -c /myCAfolder.. and all was good on btcgreen and shibgreen.. i did the same as above but it still did not work. So for some reason when deploying a new harvester for these three blockchain the CA key and the farmer IP are no longer being setup properly when deploying a new harvester. just wanted every to know the fix |
Beta Was this translation helpful? Give feedback.
-
|
some more info... it is possible that for SHIBGreen and BTCGreen the farmer IP was not set in the config file.. but the CA init was ok for Chia it was only the CA init not having the right keys in the new container |
Beta Was this translation helpful? Give feedback.
-
currently on Machinaris I run Chia and 12 forks
I have one full node and 2 harvester only nodes
all of the harvester nodes use the exact same plot directories for all 13 harvester dockers (1 nodes has 13 harvester containers)
On both nodes BTCGreen, Chia and SHIBGreen harvesters refuse to check in and report to the full node (see image) and this is from both harvester nodes?? very strange
but on the full node all Blockchains and wallets are all synced..
all harvester workers on the full node are showing up and green with logs that look clear.
on the Chia harvester node i did notice that the when i do a "chia plots check"
all the plots a complaining about a famer and\or public key being not in the list -- but for some reason i think that's ok on harvester only nodes.
anyone have any thoughts where to check?
Beta Was this translation helpful? Give feedback.
All reactions