_Luke
April 27, 2023, 9:01pm
1
Issue Report
Environment
Operating System: Ubuntu 20
CPU Architecture: intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz
RAM: 4GB
Storage: 100GB
Plot Size: 50GB
Subspace Deployment Method: Download the binaries and run as a service
Problem
Steps to reproduce
Sync the node - Works fine but takes time
Start farmer once is node is synced
Farmer doesnt really output much - Until a restart or something similar
Been speaking to Justin to test things out but not much has progressed
Expected result
What happens instead
Below error and sometimes nothing on the screen session for when the Farmer Runs
2023-04-27T21:00:56.926527Z ERROR single_disk_plot{disk_farm_index=0}: subspace_networking::utils::piece_provider: Couldn't get a piece from DSN. No retries left. piece_index=1171152 current_attempt=3 max_retries=3
2023-04-27T21:00:56.926554Z INFO single_disk_plot{disk_farm_index=0}: subspace_farmer_components::segment_reconstruction: Recovering missing piece... missing_piece_index=1171152
2023-04-27T21:00:56.926953Z ERROR single_disk_plot{disk_farm_index=0}: subspace_networking::utils::piece_provider: Couldn't get a piece from DSN. No retries left. piece_index=1405831 current_attempt=3 max_retries=3
2023-04-27T21:00:56.926980Z INFO single_disk_plot{disk_farm_index=0}: subspace_farmer_components::segment_reconstruction: Recovering missing piece... missing_piece_index=1405831
2023-04-27T21:01:48.627156Z ERROR single_disk_plot{disk_farm_index=0}: subspace_farmer_components::segment_reconstruction: Recovering missing piece failed. missing_piece_index=1987088
2023-04-27T21:01:48.668129Z ERROR single_disk_plot{disk_farm_index=0}: subspace_farmer_components::segment_reconstruction: Recovering missing piece failed. missing_piece_index=2968673
1 Like
@ivan-subspace @ozgun this user is running multiple farmers and has still not received any rewards. Any ideas?
We had a bit more lengthy discussion in discord here:
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
ozgun
April 28, 2023, 6:09am
3
First of all, welcome @_Luke !
The problem seems to be DSN.
IIRC, this problem should have been resolved with the newer versions.
This is probably originating at monorepo or SDK level.
Please share the version you are using, and then we can find the reason
1 Like
_Luke
April 28, 2023, 9:28am
4
Looks like I am using April 18th Version:
This command was similar but another users. This is my install command:
wget -O /usr/bin/subspace-farmer https://github.com/subspace/subspace/releases/download/gemini-3d-2023-apr-18/subspace-farmer-ubuntu-x86_64-v3-gemini-3d-2023-apr-18 && chmod +x /usr/bin/subspace-farmer
This is my run command:
/usr/bin/subspace-farmer farm --disable-private-ips --reward-address st8zm9neA8U75wPidi22psJ1qBkoQ2Gr8agG3AbEcigYsaGBt --plot-size 50G
ozgun
April 28, 2023, 10:07am
5
This may be outdated. There are newer releases. I think there is good chance to succeed if you use newer releases.
By the way, you are using the substrate cli (monorepo), not subspace-cli. So, @ImmaZoni , maybe tagging Shamil or Nazar will be more accurate if the issue persists after update.
1 Like
_Luke
April 28, 2023, 11:04am
6
Updated to latest, wiped the farm and then re ran it at 10GB instead of 50GB to see if we can see what is happening quicker. Any idea what should be outputted to the screen session ? What do I need to be looking for ? Thanks
_Luke
May 1, 2023, 10:58pm
7
Still 0 Rewards after 3 Days farming with 15 nodes:
subspaceliquify01 - 0.1.0 Emeryville 12D3KooWP… 41 16 - #481 ,279 0x25f3baf1d5a33… 6.001s 4ms 4d
Apologies luke, this notification slipped past me.
I’ve spoken with the development team regarding this and other farming issues and it looks like this one is related to this error here: Farming not working on gemini-3d - #19 by nazar-pc
One of our core devs Nazar mentioned the following
Farmers can get stuck at a particular sector and be unable to plot further, this is caused by networking issues preventing farmer from finding some of the pieces of history it needs. We are working on fixing that, but it will take some time.
Unfortunately for the time being it seems we don’t have a fix beyond what we have tried so far, our team is working diligently on another version which we hope to have out in the coming weeks
1 Like