Waiting for farmer to receive and acknowledge archived segment

Support
1

Many users are reporting this frequent error, which stalls the progress of the node sync Waiting for farmer to receive and acknowledge archived segment

2022-06-10 17:24:27 [PrimaryChain] Waiting for farmer to receive and acknowledge archived segment
2022-06-10 17:24:32 [PrimaryChain] Waiting for farmer to receive and acknowledge archived segment
2022-06-10 17:24:35 [PrimaryChain] :gear: Syncing 0.0 bps, target=#55270 (50 peers), best: #21470 (0x0f1e…c4bb), finalized #0 (0x9ee8…ccf0), :arrow_down: 11.2kiB/s :arrow_up: 871.6kiB/s
2022-06-10 17:24:37 [PrimaryChain] Waiting for farmer to receive and acknowledge archived segment
2022-06-10 17:24:40 [PrimaryChain] :gear: Syncing 0.0 bps, target=#55270 (50 peers), best: #21470 (0x0f1e…c4bb), finalized #0 (0x9ee8…ccf0), :arrow_down: 24.8kiB/s :arrow_up: 2.1MiB/s
2022-06-10 17:24:42 [PrimaryChain] Waiting for farmer to receive and acknowledge archived segment
2022-06-10 17:24:46 [PrimaryChain] :gear: Syncing 0.0 bps, target=#55270 (49 peers), best: #21470 (0x0f1e…c4bb), finalized #0 (0x9ee8…ccf0), :arrow_down: 10.5kiB/s :arrow_up: 53.8kiB/

2

The most common reasons is that your farmer client is either down or stuck. The simple solution is to restart your farmer client (remember when you started you had the node client and the farmer client). That should address 90% of the cases.

However, you might encounter a similar issue if you are trying to pledge a very large amount of storage, like 1 terabyte or more. You can follow the discussion linked below

3

I have a user that is having a similar issue, however the end result is just a stuck loop where the node is waiting for the farmer to “Receive and acknowledge archived segment.”

Restarting did not work, and I confirmed his initial start up commands and process he is following is the correct method based off of documentation
He is using Windows 10 Pro

User Logs:

image
image1280×358 66 KB

image
image1280×424 124 KB

image
image1280×113 61 KB

4

Did the user full wipe & purge when they restarted or just a restart of the program?

5

He did, Although we didnt solve this original problem, I had him switch the the GUI desktop app whiched worked, but I was never able to figure out how to get him past the feedback loop.

6

I would suggest they give our june-13 snapshot a try, it looks like the node is making connection with the network just cant seem to get a block synced.

what if they try it with the C: drive and not d:?

1 Like
7

Ill suggest this and see how it goes if he’s willing to switch back to the CLI, Thanks!

Update Edit: So far so good seems to be working for him, thanks!