Issue Report Environment Operating System: Ubuntu 24.04 (Linux Mint 22) Space Acres/Advanced CLI/Docker: ACLI Problem I run two (non-cluster)machines on the Taurus network, with a separate machine running a node. They are each plotting to 6 SATA SSD and farming. Randomly, the creating of sector…

Fix was shipped in Release taurus-2024-nov-01 · autonomys/subspace · GitHub

I’m seeing this as well. No errors or warnings on either the farmer or the plotter. It’s like the farmer just stops requesting sectors from the plotter. Restarting the farmer fixes the problem, at least temporarily. I’m running a cluster, and it happens with all my farmers, whether they have a local…

Similarly to Plotting Stops after Error (taurus-oct-2024) - #6 by nazar-pc there are two things I’d like to request. First to start farmer with RUST_LOG=info,subspace_farmer=trace, which will generate a lot more logs, but should also help with debugging, there could be gigabytes of logs potentially…

Now that you say it, I do see a couple of those lines in my plotter logs: 2024-10-31T00:54:18.924935Z WARN subspace_farmer::cluster::nats_client: Acknowledgement wait timed out response_subject=stream-response.01JBG0ZK51ME4XGG3M5AW26MGT expected_index=6 request_type=subspace_farmer::cluster::plott…

I’ve started both farmers back up with the RUST_LOG variable you asked. Will keep an eye out and see what it looks like if it stops plotting again. I’ll set up the gbd output shortly. Do you want me to just run that randomly or does it need to be done after the farmer stops plotting? Is there a …

No I don’t have any error messages in the log relating to this issue. I’m not on a cluster so I have no NATS server etc, just one node and two separate farmers running simple ACLI startup commands.

Gdb only needs to be connected after plotting has stopped, just to see what farmer is waiting for to understand why it stopped plotting. You can upload to pastebin.com or gist.github.com or anything similar and drop the link to it here.

Apologies but I have little idea what I’m doing here. Before including RUST_LOG in my command, I could easily see that the farmer had stopped producing sectors because (as shown in my log extracts in the OP) the log would show a stream of "Plotting sector (xx.xx% complete)) every 5-10 seconds with …

My previous message has been hidden pending review but I’ve managed to do the gdb trace and the results are here (I think): <script src="https://gist.github.com/Badfish1/e22eba20c59622eefd126baacafe8393.js"></script> I can’t upload the farmer log, it keeps giving me an error that it timed out so I…

I was unable to install gdb in the docker farmer container. I got the following: # apt-get install --no-install-recommends gdb Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package gdb I’m adding the RUST_LOG variable to my com…

Plotting stops, rewards continue, no errors - non-cluster ACLI

Support

Jim-Autonomys October 30, 2024, 11:54pm 3

Can you check your plotter logs please? Do you see the same as in this post? Plotting Stops after Error (taurus-oct-2024)

Topic		Replies	Views
Cluster Farm plotter/farmer panic Support	50	784	June 15, 2024
Plotting Stops after Error (taurus-oct-2024) Support	10	241	November 1, 2024
Farmer jun 11 stop farming after replot start sometimes Support	33	496	June 19, 2024
Abnormal plotting progress in farmer cluster Support	21	384	June 27, 2024
Farmer 15-feb stop plotting, farming keep on Support	11	287	March 11, 2024

Plotting stops, rewards continue, no errors - non-cluster ACLI

Related topics