No rewards for 9863 plots for about a month

is there any secret address or keys in the logs to open in public?

Then is there some how I can check if the 9149 plots eligible?

One thing you can do is run the chia plot check.

./chia plots check -n 30

This will check if the plots are good or not.

2 Likes

Thanks, what does the number 30 mean?

It’s the amount of proofs it will test each plot with. You can also set it lower to 5 to speed up the check, but 30 gives more accurate results (they say)

1 Like

Thanks, let me give it a go. :grinning:

Slightly different concept…
The plot check will generate -n amount of challenges.
And then will check against a plot how many of those challenges result in a Proof

The default value of -n is 30… and let’s say out of those 30 challenges, 25 Proof are generated…
This is considered good.
You can up the number of challenges to throw at the plot to get a more accurate reading…
maybe you were unlucky and only 5 Proofs were found from 30 challenges… but when you run 1000 challenges for example then 800 Proof may come back… giving it a 80% score of Proofs found

That’s why it’s important to use a high -n value to recheck a plot that came back with a low score with the default or low -n value.

Just remember, a challenge doesn’t have to be in a plot… but enough different challenges should result in a decent ratio of Proof found.

2021-06-26T00:17:04.158 chia.plotting.plot_tools : INFO Loaded a total of 9149 plots of size 905.6176038219819 TiB, in 245.24349427223206 seconds
2021-06-26T00:17:04.160 chia.plotting.check_plots : INFO
2021-06-26T00:17:04.160 chia.plotting.check_plots : INFO
2021-06-26T00:17:04.160 chia.plotting.check_plots : INFO Starting to test each plot with 30 challenges each

2021-06-26T00:17:04.160 chia.plotting.check_plots : INFO Testing plot /storage_5/plot-k32-2021-06-01-00-28-1b4d22d6e98048e6c949.plot k=32
2021-06-26T00:17:04.160 chia.plotting.check_plots : INFO Pool public key: e679bab91111c3c131…
2021-06-26T00:17:04.175 chia.plotting.check_plots : INFO Farmer public key: b9944071…
2021-06-26T00:17:04.175 chia.plotting.check_plots : INFO Local sk:
2021-06-26T00:18:00.846 chia.plotting.check_plots : INFO Proofs 30 / 30, 1.0
2021-06-26T00:18:00.847 chia.plotting.check_plots : INFO Testing plot /storage_5/plot-k32-2021-06-06-14-13-d65d6da50ed7961f0155245c.plot k=32
2021-06-26T00:18:00.847 chia.plotting.check_plots : INFO Pool public key: e679bab91111c3c131…
2021-06-26T00:18:00.866 chia.plotting.check_plots : INFO Farmer public key: b9944071…
2021-06-26T00:18:00.866 chia.plotting.check_plots : INFO Local sk:
2021-06-26T00:18:52.509 chia.plotting.check_plots : INFO Proofs 27 / 30, 0.9
2021-06-26T00:18:52.510 chia.plotting.check_plots : INFO Testing plot /storage_5/plot-k32-2021-06-03-05-11-8311293a24534af6dda6af803c3d990.plot k=32
2021-06-26T00:18:52.510 chia.plotting.check_plots : INFO Pool public key: e679bab91111c3c131…
2021-06-26T00:18:52.530 chia.plotting.check_plots : INFO Farmer public key: b9944071…
2021-06-26T00:18:52.530 chia.plotting.check_plots : INFO Local sk:
2021-06-26T00:19:48.276 chia.plotting.check_plots : INFO Proofs 29 / 30, 0.9667
2021-06-26T00:19:48.277 chia.plotting.check_plots : INFO Testing plot /storage_5/plot-k32-2021-06-06-07-16-cdce20109eb9f388dfaf6e538b1.plot k=32
2021-06-26T00:19:48.277 chia.plotting.check_plots : INFO Pool public key: e679bab91111c3c131…
2021-06-26T00:19:48.295 chia.plotting.check_plots : INFO Farmer public key: b9944071…
2021-06-26T00:19:48.296 chia.plotting.check_plots : INFO Local sk:
2021-06-26T00:20:37.652 chia.plotting.check_plots : INFO Proofs 26 / 30, 0.8667
2021-06-26T00:20:37.653 chia.plotting.check_plots : INFO Testing plot /storage_5/plot-k32-2021-06-02-07-07-23e2770dfeba75a0a96cac1bc55027f55.plot k=32
2021-06-26T00:20:37.653 chia.plotting.check_plots : INFO Pool public key: e679bab91111c3c131…
2021-06-26T00:20:37.671 chia.plotting.check_plots : INFO Farmer public key: b9944071…
2021-06-26T00:20:37.671 chia.plotting.check_plots : INFO Local sk:
2021-06-26T00:21:59.479 chia.plotting.check_plots : INFO Proofs 35 / 30, 1.1667
2021-06-26T00:21:59.480 chia.plotting.check_plots : INFO Testing plot /storage_5/plot-k32-2021-06-04-12-13-3ba62c2c113a7169fda3a92f77d03.plot k=32
2021-06-26T00:21:59.480 chia.plotting.check_plots : INFO Pool public key: e679bab91111c3c131…
2021-06-26T00:21:59.499 chia.plotting.check_plots : INFO Farmer public key: b9944071…
2021-06-26T00:21:59.499 chia.plotting.check_plots : INFO Local sk:
2021-06-26T00:22:49.548 chia.plotting.check_plots : INFO Proofs 26 / 30, 0.8667
2021-06-26T00:22:49.549 chia.plotting.check_plots : INFO Testing plot /storage_5/plot-k32-2021-06-01-00-34-8113f32be3d7e99cce21063c56417e5f.plot k=32
2021-06-26T00:22:49.549 chia.plotting.check_plots : INFO Pool public key: e679bab91111c3c131…
2021-06-26T00:22:49.567 chia.plotting.check_plots : INFO Farmer public key: b9944071…
2021-06-26T00:22:49.568 chia.plotting.check_plots : INFO Local sk:
2021-06-26T00:23:35.743 chia.plotting.check_plots : INFO Proofs 24 / 30, 0.8
2021-06-26T00:23:35.745 chia.plotting.check_plots : INFO Testing plot /storage_5/plot-k32-2021-06-02-19-54-a3be5411494c6ee3fcf969efd27db81b.plot k=32
2021-06-26T00:23:35.745 chia.plotting.check_plots : INFO Pool public key: e679bab91111c3c131…
2021-06-26T00:23:35.764 chia.plotting.check_plots : INFO Farmer public key: b9944071…
2021-06-26T00:23:35.764 chia.plotting.check_plots : INFO Local sk:
2021-06-26T00:24:20.256 chia.plotting.check_plots : INFO Proofs 23 / 30, 0.7667
2021-06-26T00:24:20.257 chia.plotting.check_plots : INFO Testing plot /storage_5/plot-k32-2021-06-05-04-16-d8f71c5107afa4d24d687644652f2a7ee8.plot k=32
2021-06-26T00:24:20.257 chia.plotting.check_plots : INFO Pool public key: e679bab91111c3c131…
2021-06-26T00:24:20.276 chia.plotting.check_plots : INFO Farmer public key: b9944071…
2021-06-26T00:24:20.276 chia.plotting.check_plots : INFO Local sk:
2021-06-26T00:25:35.113 chia.plotting.check_plots : INFO Proofs 32 / 30, 1.0667
2021-06-26T00:25:35.128 chia.plotting.check_plots : INFO Testing plot /storage_5/plot-k32-2021-06-03-02-20-2b6b423d7e64cd862f8099104a1d01e.plot k=32
2021-06-26T00:25:35.129 chia.plotting.check_plots : INFO Pool public key: e679bab91111c3c131…
2021-06-26T00:25:35.147 chia.plotting.check_plots : INFO Farmer public key: b9944071…
2021-06-26T00:25:35.147 chia.plotting.check_plots : INFO Local sk: <>
2021-06-26T00:26:30.829 chia.plotting.check_plots : INFO Proofs 30 / 30, 1.0
2021-06-26T00:26:30.829 chia.plotting.check_plots : INFO Testing plot /storage_5/plot-k32-2021-06-07-05-41-e33ddf077bbb2612ecf7cec678fc2f00fd.plot k=32
2021-06-26T00:26:30.830 chia.plotting.check_plots : INFO Pool public key: e679bab91111c3c131…
2021-06-26T00:26:30.849 chia.plotting.check_plots : INFO Farmer public key: b9944071…
2021-06-26T00:26:30.849 chia.plotting.check_plots : INFO Local sk: <>

looks good.

any news on finding the “Found 1 Proof” in the logs?
to clarify this is not in the [chia plots check] output, but in the logs of the Farmer.

Nope, checking it by myself only shows proofs :expressionless:

is it different getting proofs via the self-checking like that? I mean if it is only for checking but not passing the steps?

[chia plots check] is just that… to see if the plots are ok and could in theory produce a Proof when the plot passes the plot filter + challenge is found + quality score is OK

I wonder If the commend, chia plots check -l or -n, makes the step of finding proofs passed. :face_with_monocle:

You have to open your log file (the one in the .chia/mainnet/log folder)
Press search (ctrl+f) and look for “Found 1 proof”

1 Like

at this point we’re past the chia plot check… your plots look good… let’s circle back to examining your Farmer logs and look for the “Found 1 Proof”

1 Like

Ok, let me check them.

Based on the log snips you gave, your plot eligibility is on par with what it should be. Personally, I’d work on decreasing your proof response time. Mine are almost all <1sec. The 3 proofs (and yes they are wins) here are all inside a month and I only have ~5K plots next to your nearly 10K.

674309 chances to win in your logs.
3 proofs found (these are wins, right?).
0.6483 Average time to check.
11.72267 Max time to check.

1 Like

As I know this checking performance must be running on the long term storage rather than SSD which is the short term storage. is that right?

I’ve no “Found 1 Proof”. But I’ve got something, Looking up qualities, you mentioned.
But they were before I checked plots by myself.

2021-06-25T23:42:58.023 harvester chia.harvester.harvester: WARNING Looking up qualities on /storage_6/plot-k32-2021-06-06-12-49-db16bde…5d73.plot took: 14.262152910232544. This should be below 5 seconds to minimize risk of losing rewards.
2021-06-25T23:42:58.024 harvester chia.harvester.harvester: WARNING Looking up qualities on /storage_6/plot-k32-2021-06-03-12-19-de885…f2b2.plot took: 14.263249397277832. This should be below 5 seconds to minimize risk of losing rewards.
2021-06-25T23:42:58.024 harvester chia.harvester.harvester: WARNING Looking up qualities on /storage_6/plot-k32-2021-06-04-21-53-4a0cc…059c.plot took: 14.263813018798828. This should be below 5 seconds to minimize risk of losing rewards.
2021-06-25T23:42:58.025 harvester chia.harvester.harvester: WARNING Looking up qualities on /storage_6/plot-k32-2021-06-06-15-16-3eebc…7e4ff32bd.plot took: 14.264305353164673. This should be below 5 seconds to minimize risk of losing rewards.
2021-06-25T23:42:58.025 harvester chia.harvester.harvester: WARNING Looking up qualities on /storage_6/plot-k32-2021-06-04-13-46-b4b27…4ac78.plot took: 14.264768123626709. This should be below 5 seconds to minimize risk of losing rewards.
2021-06-25T23:42:58.025 harvester chia.harvester.harvester: WARNING Looking up qualities on /storage_7/plot-k32-2021-06-10-10-33-54cc9…55b267.plot took: 14.264850854873657. This should be below 5 seconds to minimize risk of losing rewards.

Ok, this can be an issue… I’ll lay out in tech terms what the harvester does… then why the 14+ seconds is a lot… maybe not enough to disqualify you…

First… the role of the harvester:

“”"
The harvester receives a new signage point from the farmer, this happens at the start of each slot.
The harvester does a few things:
1. The harvester applies the plot filter for each of the plots, to select the proportion which are eligible
for this signage point and challenge.
2. The harvester gets the qualities for each plot. This is approximately 7 reads per plot which qualifies.
Note that each plot may have 0, 1, 2, etc qualities for that challenge: but on average it will have 1.
3. Checks the required_iters for each quality and the given signage point, to see which are eligible for
inclusion (required_iters < sp_interval_iters).
4. Looks up the full proof of space in the plot for each quality, approximately 64 reads per quality
5. Returns the proof of space to the farmer
“”"

So in previous messages we talked about the Farmer doing these things… but like you had before (with 25 harvesters) you can split off these tasks to harvesters that in turn communicate with the 1 Farmer who is connected to the blockchain.

The warning in the log tells us that step 2, checking the quality of a plot that passed the plot filter + challenge was found took 14+ seconds.

It still needs to perform extracting the Proof if quality is OK, and still needs to then send the Proof to the Farmer…
The Farmer then still needs to submit the Proof and if this Proof is not verified by the blockchain before the time window of 30 seconds after the challenge was issued… it cannot participate in winning the block (if it also conforms to difficulty requirement).

The quality lookup is not very read intensive… if this takes 14+seconds… you have an issue with read speed of the disks…

Are the disk in a RAID setup where there are slow disks in there that slow everything down?

Finally… 14+ seconds is too much and deserves a warning… but it could still perform the other steps and the farmer may receive the Proof in time… we don’t know at this point because:
checking the quality of the plot is just a step in generating a Proof… it could be none of these events actually generated a Proof, because the quality score was too low…

4 Likes

One thing just came to mind… can you check your systems clock (as in time) and the Farmers timestamps to make sure they are not lagging behind with real time?

If your system is creating Proofs right now that are from challenges in the past instead of the current challenge then those Proofs will be disqualified.