The remote farmer cannot resume the connection to the node without restarting. (error=RestartNeeded)

Support
1

Issue Report

Environment

  • Operating System: Ubuntu 22.04.3 LTS on node+farmer server, Ubuntu 20.04.6 LTS on remote farmer.
  • Advanced CLI: gemini-3f-2023-sep-13-2

Problem

After restarting the node, the farmer on node’s local server can resume the connection as usual, while the remote farmer cannot resume the connection to the node without restarting.

Sep 15 07:52:38 lenovo7 subspace-farmer[93395]: 2023-09-15T04:52:38.620046Z ERROR single_disk_farm{disk_farm_index=6}: subspace_farmer::utils::piece_validator: Failed tor retrieve segment headers from node piece_index=1575 error=RestartNeeded("Networking or low-level protocol error: WebSocket connection error: connection closed")
Sep 15 07:52:38 lenovo7 subspace-farmer[93395]: 2023-09-15T04:52:38.702851Z ERROR single_disk_farm{disk_farm_index=12}: subspace_farmer::utils::piece_validator: Failed tor retrieve segment headers from node piece_index=1669 error=RestartNeeded("Networking or low-level protocol error: WebSocket connection error: connection closed")
Sep 15 07:52:39 lenovo7 subspace-farmer[93395]: 2023-09-15T04:52:39.303228Z ERROR single_disk_farm{disk_farm_index=10}: subspace_farmer::utils::piece_validator: Failed tor retrieve segment headers from node piece_index=3014 error=RestartNeeded("Networking or low-level protocol error: WebSocket connection error: connection closed")
Sep 15 07:52:39 lenovo7 subspace-farmer[93395]: 2023-09-15T04:52:39.420706Z ERROR single_disk_farm{disk_farm_index=3}: subspace_farmer::utils::piece_validator: Failed tor retrieve segment headers from node piece_index=2271 error=RestartNeeded("Networking or low-level protocol error: WebSocket connection error: connection closed")
2

There is zero difference between local and remote farmer, must be a coincidence and remove should also exit eventually.

Also judging by disk_farm_index=12 you either have a lot of disks or you sliced disk into multiple farms unnecessarily. If it is sliced disk it’ll be less efficient than one big farm.

3

Really? More rewards on smaller plots - #8 by nazar-pc
There are simply several relatively small plot files, like this:

path=/media/aorus-1/plot1,size=111679874151 \
path=/media/aorus-2/plot0,size=111679874151 \
path=/media/aorus-2/plot1,size=111679874151 \
path=/media/aorus-3/plot0,size=111679874151 \
path=/media/aorus-3/plot1,size=111679874151 \
path=/media/aorus-4/plot0,size=111679874151 \
path=/media/aorus-4/plot1,size=111679874151 \
path=/media/aorus-5/plot0,size=111679874151 \
path=/media/aorus-5/plot1,size=111679874151

I proceeded from the experience of colleagues. Should I now replot everything? :sob:

4

Things change quickly and we have already fixed underlying reasons for large plots that caused less rewards in Release gemini-3f-2023-sep-11 · subspace/subspace · GitHub. It is not necessary to replot, things will continue to work, but somewhat suboptimally, so no need to create small plots or recommend it to anyone. You’ll just spend more RAM and CPU for no reason.

1 Like