Stand alone Harvester with any plot will lose connection to Farmer

Chia Farming & Harvesting
1

I am using a setup allowing Farming on multiple machines. It was working for long time, but stopped working recently.
But I don’t know what triggered the problem, it might be a windows update, or a Chia upgrade.
Here is the problem: If any plot is added to the harvester, the connection to Farmer is lost.

If no plot is added to the harvester, the harvester will show up in the Farmer’s “Your Harvester Network”

Capture
Capture1154×623 67.9 KB

Windows is restored to initial state, but it didn’t help to resolve the problem. Another network cable connecting to a working Harvester was borrowed, no Help!

It was a old PC, but had been working for more than 1 year. If no solution found, I will migrate everything to some new PC, which will a lot of work.

Here is log: (Connection to Farmer is closed 10 minutes after the start of Harvester, I had changed plots_refresh_parameter: interval_seconds: to 3600 )

2023-11-22T11:44:01.283 harvester chia.harvester.harvester: INFO Using plots_refresh_parameter: {‘batch_size’: 300, ‘batch_sleep_milliseconds’: 1, ‘interval_seconds’: 3600, ‘retry_invalid_seconds’: 1200}
2023-11-22T11:44:01.299 harvester harvester : INFO Starting service harvester …
2023-11-22T11:44:01.299 harvester harvester : INFO chia-blockchain version: 2.1.1
2023-11-22T11:44:01.299 harvester harvester_server : INFO Service capabilities: [(1, ‘1’), (2, ‘1’), (3, ‘1’)]
2023-11-22T11:44:01.315 harvester filelock : DEBUG Attempting to acquire lock 1832115449920 on C:\Users\admin.chia\mainnet\run\harvester.lock
2023-11-22T11:44:01.330 harvester filelock : DEBUG Lock 1832115449920 acquired on C:\Users\admin.chia\mainnet\run\harvester.lock
2023-11-22T11:44:01.330 harvester harvester : INFO Started harvester service on network_id: mainnet at port 8448
2023-11-22T11:44:01.346 harvester harvester : INFO Add resolved PeerInfo(_ip=IPv4Address(‘192.168.1.30’), _port=8447)
2023-11-22T11:44:01.346 harvester harvester_server : DEBUG Connecting: wss://192.168.1.30:8447/ws, Peer info: PeerInfo(_ip=IPv4Address(‘192.168.1.30’), _port=8447)
2023-11-22T11:44:01.378 harvester harvester_server : DEBUG → handshake to peer 192.168.1.30 3ed5???1d29
2023-11-22T11:44:01.394 daemon chia.daemon.server : DEBUG Received message: WSMessage(type=<WSMsgType.TEXT: 1>, data=‘{“ack”: false, “command”: “register_service”, “data”: {“service”: “chia_harvester”}, “destination”: “daemon”, “origin”: “chia_harvester”, “request_id”: “9e???8a”}’, extra=‘’)
2023-11-22T11:44:01.394 harvester harvester_server : INFO Connected with farmer PeerInfo(_ip=IPv4Address(‘192.168.1.30’), _port=8447)
2023-11-22T11:44:01.394 daemon chia.daemon.server : INFO Register service {‘service’: ‘chia_harvester’}
2023-11-22T11:44:01.409 harvester harvester_server : DEBUG ← harvester_handshake from peer 3ed550b4a667???1d29 192.168.1.30
2023-11-22T11:44:01.409 daemon chia.daemon.server : INFO registered for service chia_harvester
2023-11-22T11:44:01.409 harvester chia.plotting.cache : DEBUG Cache C:\Users\admin.chia\mainnet\cache\plot_manager_v2.dat not found
2023-11-22T11:44:01.425 daemon chia.daemon.server : INFO {‘success’: True}
2023-11-22T11:44:01.425 harvester harvester_server : DEBUG Time taken to process harvester_handshake from 3ed550b4a66???a961d29 is 0.015624523162841797 seconds
2023-11-22T11:44:01.425 harvester filelock : DEBUG Attempting to acquire lock 1832115577296 on C:\Users\admin.chia\mainnet\config\config.yaml.lock
2023-11-22T11:44:01.441 harvester chia.rpc.rpc_server : DEBUG Rpc call ← register_service
2023-11-22T11:44:01.441 harvester filelock : DEBUG Lock 1832115577296 acquired on C:\Users\admin.chia\mainnet\config\config.yaml.lock
2023-11-22T11:44:01.599 harvester filelock : DEBUG Attempting to release lock 1832115577296 on C:\Users\admin.chia\mainnet\config\config.yaml.lock
2023-11-22T11:44:01.599 harvester filelock : DEBUG Lock 1832115577296 released on C:\Users\admin.chia\mainnet\config\config.yaml.lock
2023-11-22T11:44:01.614 harvester chia.plotting.util : DEBUG get_filenames: 73 files found in D:\Farmer2_ChiaPlot10, recursive: False
2023-11-22T11:44:01.630 harvester chia.harvester.harvester: INFO _plot_refresh_callback: event started, loaded 0, removed 0, processed 0, remaining 73, duration: 0.00 seconds, total plots: 0
2023-11-22T11:44:01.630 harvester chia.plot_sync.sender : DEBUG sync_start sync_id 0, next_message_id 0, messages 0: count 73, initial True
2023-11-22T11:44:01.630 harvester chia.plot_sync.sender : DEBUG sync_start 1700671441
2023-11-22T11:44:01.646 harvester chia.plotting.manager : DEBUG refresh_batch: 73 files in directories {WindowsPath(‘D:/Farmer2_ChiaPlot10’)}
2023-11-22T11:44:01.661 harvester chia.plotting.manager : DEBUG process_file D:\Farmer2_ChiaPlot10\plot-k32-2022-05-16-02-17-12a491fcc8???176693065c.plot
2023-11-22T11:44:01.661 harvester chia.plot_sync.sender : DEBUG _send_next_message send plot_sync_start: PlotSyncStart: identifier {‘message_id’: 0, ‘sync_id’: 1700671441, ‘timestamp’: 1700671441}, initial True, last_sync_id 0, plot_file_count 73, harvesting_mode 1
2023-11-22T11:44:01.677 harvester harvester_server : DEBUG → plot_sync_start to peer 192.168.1.30 3ed???61d29
2023-11-22T11:44:01.661 harvester chia.plotting.manager : DEBUG process_file D:\Farmer2_ChiaPlot10\plot-k32-2022-05-16-13-16-42ef5de2554???850a44fd2.plot
2023-11-22T11:44:01.694 harvester harvester_server : DEBUG ← plot_sync_response from peer 3ed550b???>0a961d29 192.168.1.30
2023-11-22T11:44:01.740 harvester chia.plot_sync.sender : DEBUG set_response valid PlotSyncResponse: identifier {‘message_id’: 0, ‘sync_id’: 1700671441, ‘timestamp’: 1700671441}, message_type 78, error None
2023-11-22T11:44:31.440 daemon chia.daemon.server : DEBUG About to ping: chia_harvester
2023-11-22T11:45:06.665 daemon chia.daemon.server : DEBUG Received message: WSMessage(type=<WSMsgType.CLOSED: 257>, data=None, extra=None)
2023-11-22T11:45:06.665 daemon chia.daemon.server : INFO Connection closed. Closing websocket with [‘chia_harvester’].

2

If you did a Chia upgrade, you should have upgraded the farmer and the harvesters to be on the same level. Start the farmer then the harvesters. On your windows boxes you can disable the auto windows update, so your in control. Add the updates when needed.
.
.
And if it was working for a year no need to upgrade to a newer PC.

3

Both Farmer and Harvester are at the same level of Chia upgrade 2.1.1
I did disabled the access of internet for the Harvester to disable the windows update, but for a short period I did opened the access. However, it doesn’t looks like the windows update is the issue because I had restored the windows to intial state, which didn’t help. Mean while, it also not likely caused by Chia upgrade. The same Chia version, another Harvester is working ok with the Farmer. That’s why I am lost.
The only difference between the working Harvester and non-working Harvester is the hardware. Working one is at better performance

4

When you said you disabled the machine from updates what did you do?
.
.
.Also what are the specs of both harvesters, cpu. video memory etc.

5

The Harvester is disabled of access of internet in my Gateway router, still allowing it accessing internal network.
The non-working Harvester is an old PC, AMD Athlon Dual Core. But it has been working for more than 1 year and I am not using any compressed plots.

6

How much system memory do you have on the harvester and how much free space is on your C: drive???

7

6GM RAM, C drive still has 113GB free. CPU utilization is also low

8

Ca cert renewed? (20 chrs )

9

Yes, renewed used Farmer/Main Node’s cert

10

Do you have plots mounted in NTFS folders as mount points ? Do you have recursive plot scanning enabled ?

I have found on a few versions of Chia that if one of the NTFS mount points is unavailable, chia just gives up/crashes and see zero plots on that entire machine.

1 Like
11

No plot on NTFS. Even with only one plot on local drive, the connecti to Farmer dropped

12

I found one thing: chia.exe will crash if I run Chia plots check in cmd

13

If you only have a total of 6GB of system memory your wasting your effort.

1 Like
14

Increased RAM to 8GB, no difference. This PC is only used as Harvester. Does it really need high spec hardware?

15

Last question, which version of Windows are you running and do you have a system page file setup since you still lack system memory. And where are your plots located?

16

Did you copy the farmers \ca files to a temp directory and run something like this?
C:\Program Files\Chia\resources\app.asar.unpacked\daemon .\chia.exe init -c c:\files\ca\ each box has to have it’s own certs, or you will have problems.

17

Yes. CA cert is regenerated based on Farmer’s ca.
Windows 10 pro. System page file is default. I don’t think 8G is the problem for a farmer. Plot is located locally on the Harvester.

18

My farner needed / needs 32 gb ram, 16 got to close to full.

19

Mine is Harvester, not Farmer. And the same setting had been running well is the past one year.

20

Looks like you have just 73 plots on that harvester ?

I have run a harvester on Windows 10 with 4GB RAM for a while with a similar number of plots with no issues, but that was an earlier version, so no sure it’s a RAM issue.

How are 192.168.1.25 and 192.168.1.30 connected ? I presume there is no router between the two ?

What’s with your config path “C:\Users\admin.chia\mainnet\config\” ? I would say it should be “C:\Users\admin\.chia\mainnet\config\” ?

[Edit] Ignore the above question, it seems it’s the forum parsing the log in an odd way and replacing the ‘slash dot’ characters with just a dot!! Edited to correct - but this is not the issue anyway.

And the path to your plots “D:\Farmer2_ChiaPlot10” I presume there are no security issues ? Is this an external HDD (USB) ? Sometimes Windows mounts them with weird permissions whereby Windows (and applications) can read folder contents but not actually read/open contents of files. Check that.