The farmer sometimes sees that the node seems to be synchronized and starts building a plot

Support Incentivized Testnet
, ,
1

Is it normal that the farmer sometimes sees that the node seems to be synchronized and starts building a plot?

System Information

CPU: Intel Core i5-8600K
RAM: 16 GB DDR4 2400
Drives: Samsung SSD 860 EVO M.2 500GB
OS: Win 11

Release

subspace-farmer-windows-x86_64-skylake-gemini-3f-2023-sep-05.exe
subspace-node-windows-x86_64-skylake-gemini-3f-2023-sep-05.exe

Logs

←[2m2023-09-11 17:19:56←[0m [Consensus] ⏳ Pending (3 peers), best: #51405 (0xb320…92be), finalized #0 (0x92e9…5095), ⬇ 428.2kiB/s ⬆ 0.4kiB/s
←[2m2023-09-11 17:20:01←[0m [Consensus] ⚙️  Syncing  5.0 bps, target=#381586 (5 peers), best: #51430 (0x3818…f555), finalized #0 (0x92e9…5095), ⬇ 142.6kiB/s ⬆ 0.5kiB/s
←[2m2023-09-11 17:20:06←[0m [Consensus] ⚙️  Syncing  5.7 bps, target=#381586 (4 peers), best: #51459 (0x90cc…02b5), finalized #0 (0x92e9…5095), ⬇ 2.7kiB/s ⬆ 1.8kiB/s
←[2m2023-09-11 17:20:11←[0m [Consensus] ⏳ Pending (3 peers), best: #51495 (0xd559…f4b1), finalized #0 (0x92e9…5095), ⬇ 112.6kiB/s ⬆ 0.5kiB/s
←[2m2023-09-11 17:20:16←[0m [Consensus] ⏳ Pending (3 peers), best: #51528 (0x1607…b5fe), finalized #0 (0x92e9…5095), ⬇ 0.2kiB/s ⬆ 0.2kiB/s
←[2m2023-09-11 17:20:21←[0m [Consensus] ⚙️  Syncing  5.9 bps, target=#381589 (4 peers), best: #51558 (0x9fef…224a), finalized #0 (0x92e9…5095), ⬇ 123.0kiB/s ⬆ 0.5kiB/s
←[2m2023-09-11 17:20:26←[0m [Consensus] ⚙️  Syncing  5.6 bps, target=#381590 (8 peers), best: #51586 (0x1cf1…bb3b), finalized #0 (0x92e9…5095), ⬇ 2.3kiB/s ⬆ 0.8kiB/s
←[2m2023-09-11 17:20:31←[0m [Consensus] ⏳ Pending (2 peers), best: #51626 (0xaa68…5731), finalized #0 (0x92e9…5095), ⬇ 2.6kiB/s ⬆ 0.3kiB/s
←[2m2023-09-11 17:20:32←[0m [Consensus] Ignoring request to disconnect reserved peer 12D3KooW9s8grscXvT537xw96YNdpUGaB9nuEBwcyTFrDvGN3ydP from SetId(3).
←[2m2023-09-11 17:20:36←[0m [Consensus] ⏳ Pending (2 peers), best: #51659 (0xb1f3…2c63), finalized #0 (0x92e9…5095), ⬇ 1.2kiB/s ⬆ 0.6kiB/s
←[2m2023-09-11 17:20:41←[0m [Consensus] ⚙️  Syncing  5.5 bps, target=#375189 (2 peers), best: #51687 (0xedbc…789d), finalized #0 (0x92e9…5095), ⬇ 0.3kiB/s ⬆ 0.3kiB/s

←[2m2023-09-11T14:16:18.506844Z←[0m ←[32m INFO←[0m ←[1msingle_disk_farm←[0m←[1m{←[0m←[3mdisk_farm_index←[0m←[2m=←[0m0←[1m}←[0m←[2m:←[0m ←[2msubspace_farmer::single_disk_farm::plotting←[0m←[2m:←[0m Sector plotted successfully (6.42%) ←[3msector_index←[0m←[2m=←[0m11
←[2m2023-09-11T14:17:16.672425Z←[0m ←[32m INFO←[0m ←[1msingle_disk_farm←[0m←[1m{←[0m←[3mdisk_farm_index←[0m←[2m=←[0m0←[1m}←[0m←[2m:←[0m ←[2msubspace_farmer::single_disk_farm::plotting←[0m←[2m:←[0m Node is synced, resuming plotting
←[2m2023-09-11T14:17:20.677461Z←[0m ←[32m INFO←[0m ←[1msingle_disk_farm←[0m←[1m{←[0m←[3mdisk_farm_index←[0m←[2m=←[0m0←[1m}←[0m←[2m:←[0m ←[2msubspace_farmer::single_disk_farm::plotting←[0m←[2m:←[0m Node is not synced yet, pausing plotting until sync status changes
←[2m2023-09-11T14:19:25.855702Z←[0m ←[32m INFO←[0m ←[1msingle_disk_farm←[0m←[1m{←[0m←[3mdisk_farm_index←[0m←[2m=←[0m0←[1m}←[0m←[2m:←[0m ←[2msubspace_farmer::single_disk_farm::plotting←[0m←[2m:←[0m Node is synced, resuming plotting
←[2m2023-09-11T14:19:31.862405Z←[0m ←[32m INFO←[0m ←[1msingle_disk_farm←[0m←[1m{←[0m←[3mdisk_farm_index←[0m←[2m=←[0m0←[1m}←[0m←[2m:←[0m ←[2msubspace_farmer::single_disk_farm::plotting←[0m←[2m:←[0m Node is not synced yet, pausing plotting until sync status changes
←[2m2023-09-11T14:19:56.954492Z←[0m ←[32m INFO←[0m ←[1msingle_disk_farm←[0m←[1m{←[0m←[3mdisk_farm_index←[0m←[2m=←[0m0←[1m}←[0m←[2m:←[0m ←[2msubspace_farmer::single_disk_farm::plotting←[0m←[2m:←[0m Sector plotted successfully (6.95%) ←[3msector_index←[0m←[2m=←[0m12
1 Like
2

In this case it can be seen that node is having number of peers close to 0, meaning it is likely that in beween two node log messages the number of peers was zero for some amount of time.

If number of peers is zero, there is nowhere to sync to and for farmer it would appear as it is time to plot already.

The solution here is to figure out why you have so few peers and fix that.

3

After switching to the release gemini-3f-2023-sep-11, the number of peers increased, now it works fine.
Wouldn’t it be a problem that part of the plot has already been built, but the node has not yet been completely synchronized?

4

Not really. I mean part of the plot will end up being already expired by the time node sync is over and will have to be re-plotted immediately, but other than that it’ll work fine.

1 Like