Found 0 proofs!?!

I have 15 k32 plots with expected time to win: 1 year (why does it keep going up?!) so maybe this shouldn’t come as a surprise but I thought that each plot was supposed to find proofs and then the best proof was supposed to create the new block. Is something wrong with my farming setup if it’s always ‘Found 0 proofs’? Does my wallet need to finish syncing before I can farm successfully (it seems like syncing the wallet is going to take forever… currently only at height 10480)? I thought a local wallet instance wasn’t needed for farming.

0 proofs. Time: 0.47498 s. Total 15 plots
2021-05-07T04:04:22.161 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming de9acddd9f... Found 0 proofs. Time: 0.22937 s. Total 15 plots
2021-05-07T04:08:59.670 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming de9acddd9f... Found 0 proofs. Time: 3.09855 s. Total 15 plots
2021-05-07T04:12:25.460 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming 2f1dd57f14... Found 0 proofs. Time: 0.32372 s. Total 15 plots
2021-05-07T04:47:03.589 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming 7f7f0f32d2... Found 0 proofs. Time: 1.34546 s. Total 15 plots
2021-05-07T04:49:23.797 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming 7f7f0f32d2... Found 0 proofs. Time: 1.41917 s. Total 15 plots
2021-05-07T04:49:32.712 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming db09dea5e1... Found 0 proofs. Time: 1.76537 s. Total 15 plots
2021-05-07T04:50:08.995 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming db09dea5e1... Found 0 proofs. Time: 2.52196 s. Total 15 plots
2021-05-07T04:50:48.457 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming db09dea5e1... Found 0 proofs. Time: 0.73629 s. Total 15 plots
2021-05-07T04:51:13.906 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming db09dea5e1... Found 0 proofs. Time: 0.29567 s. Total 15 plots
2021-05-07T04:52:45.337 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming db09dea5e1... Found 0 proofs. Time: 1.49542 s. Total 15 plots
2021-05-07T04:58:00.017 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming db09dea5e1... Found 0 proofs. Time: 1.87423 s. Total 15 plots
2021-05-07T05:02:41.172 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming 0809ab8629... Found 0 proofs. Time: 1.76905 s. Total 15 plots
2021-05-07T05:32:19.456 harvester chia.harvester.harvester: INFO     2 plots were eligible for farming 41258fb54b... Found 0 proofs. Time: 4.44604 s. Total 15 plots
2021-05-07T05:36:22.208 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming 41258fb54b... Found 0 proofs. Time: 1.73768 s. Total 15 plots
2021-05-07T05:48:49.457 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming d4bf7278d4... Found 0 proofs. Time: 2.23398 s. Total 15 plots
2021-05-07T05:50:10.460 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming 23e674d83d... Found 0 proofs. Time: 7.70011 s. Total 15 plots
2021-05-07T05:52:08.960 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming 23e674d83d... Found 0 proofs. Time: 2.96046 s. Total 15 plots
2021-05-07T06:00:42.458 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming 71b19597e0... Found 0 proofs. Time: 4.19589 s. Total 15 plots
2021-05-07T06:07:06.707 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming 71b19597e0... Found 0 proofs. Time: 2.20445 s. Total 15 plots
2021-05-07T06:09:29.983 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming fbd92a643e... Found 0 proofs. Time: 3.00030 s. Total 15 plots
2021-05-07T06:13:11.957 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming fbd92a643e... Found 0 proofs. Time: 2.21831 s. Total 15 plots
2021-05-07T06:20:54.209 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming af8bf0beb4... Found 0 proofs. Time: 2.50202 s. Total 15 plots
2021-05-07T06:21:55.461 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming af8bf0beb4... Found 0 proofs. Time: 1.21447 s. Total 15 plots
2021-05-07T06:40:10.707 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming 4fdc9735b5... Found 0 proofs. Time: 3.71568 s. Total 15 plots
2021-05-07T06:40:16.737 harvester chia.harvester.harvester: INFO     1 plots were eligible for farming 4fdc9735b5... Found 0 proofs. Time: 2.25604 s. Total 15 plots

Your log looks fine, assuming you are only showing challenges where one plot passed the filter. Your Time: parameter is a bit slow, but as long as it’s under 10 seconds it’ll work. Just make sure it doesn’t go higher.

If you find a proof, you’ll most likely win a 2XCH reward. “Found 0 proofs.” is normal, even for people with over 10,000 plots. It will only show “Found 1 proof” if you find a proof that is smaller than a threshold based on the difficulty level, which is growing every day as the netspace grows.

4 Likes

Also it doesn’t matter that your wallet isn’t synced yet. You’re farming. That’s all you need to do to have a chance at winning XCH.

1 Like

The wallet doesn’t need to be synced, but the node does.

Expected time to win keeps going up because other people are plotting too :wink: and the estimate doesn’t (and can’t) take that into account. It’s also not a progress indicator - you could win in 5 minutes or 5 years from now or never - it’s just a statistical average.

3 Likes

Thanks for your answers! I guess there’s nothing to be worried about…

Is it also normal that there are many lines for a single attempt, e.g. farming db09dea5e1?

Yes, this is also normal.

Hello,
From my Log file, I dont see :

harvester chia.harvester.harvester: INFO     1 plots were eligible for farming d4bf7278d4... Found 0 proofs. Time: 2.23398 s. Total 15 plots

Someone can explain why ?

Thak you in advance

In the chia config.yaml file you can update the logging from DEBUG to INFO to get this additional logging.

Yes I did it…
And I see all INFO row…
But there are no “plots were eligible for farming d4bf7278d4… Found 0 proofs.”

2021-05-10T19:46:13.794 harvester harvester_server        : INFO     Connected with farmer {'host': '127.0.0.1', 'port': 8447}
2021-05-10T19:46:13.816 harvester chia.plotting.plot_tools: INFO     Searching directories ['D:\\', 'E:\\']
2021-05-10T19:46:13.816 harvester chia.plotting.plot_tools: INFO     Not checking subdirectory D:\$RECYCLE.BIN, subdirectories not added by default
2021-05-10T19:46:13.816 harvester chia.plotting.plot_tools: INFO     Not checking subdirectory D:\System Volume Information, subdirectories not added by default
2021-05-10T19:46:13.824 harvester chia.plotting.plot_tools: INFO     Not checking subdirectory E:\$RECYCLE.BIN, subdirectories not added by default
2021-05-10T19:46:13.826 harvester chia.plotting.plot_tools: INFO     Not checking subdirectory E:\System Volume Information, subdirectories not added by default
2021-05-10T19:46:13.896 harvester chia.plotting.plot_tools: INFO     Loaded a total of 101 plots of size 9.997358936146156 TiB, in 0.11048579216003418 seconds
2021-05-10T19:46:13.896 harvester harvester_server        : INFO     Connection closed: 127.0.0.1, node id: 5800b7c4469b6c0cce346af270106dea18bd19fc5c683a15edc0e03cc8fd7560
2021-05-10T19:46:13.904 harvester chia.harvester.harvester: INFO     peer disconnected {'host': '127.0.0.1', 'port': 8447}
2021-05-10T19:46:13.585 full_node chia.full_node.full_node: INFO     peer disconnected {'host': '127.0.0.1', 'port': 8449}
2021-05-10T19:46:14.600 full_node full_node_server        : ERROR    Exception:  <class 'concurrent.futures._base.CancelledError'>, closing connection {'host': '127.0.0.1', 'port': 8449}. Traceback (most recent call last):
  File "chia\server\server.py", line 531, in api_call
  File "asyncio\tasks.py", line 435, in wait_for
concurrent.futures._base.CancelledError
2021-05-10T19:46:14.600 full_node full_node_server        : INFO     -> new_peak_wallet to peer 127.0.0.1 62e35d739c42156408cfe9314a59a77bafabeb6412ebb633667561c26f9a006f
2021-05-10T19:46:14.600 wallet wallet_server              : INFO     <- new_peak_wallet from peer dd3262192a07f4eadb6cbec04242aa513acc672c218ed205bc7cefc8679d211d 127.0.0.1
2021-05-10T19:46:14.600 wallet wallet_server              : INFO     -> request_block_header to peer 127.0.0.1 dd3262192a07f4eadb6cbec04242aa513acc672c218ed205bc7cefc8679d211d
2021-05-10T19:46:14.618 wallet wallet                     : INFO     Reconnecting to peer {'host': '127.0.0.1', 'port': 8444}
2021-05-10T19:46:13.794 farmer farmer_server              : INFO     Connection closed: 127.0.0.1, node id: cc2e8d9b0e2b9ec0c69e1ac6884b1ad37824fcda56df56882c6de40a08dbc3d7
2021-05-10T19:46:14.799 farmer chia.farmer.farmer         : INFO     peer disconnected {'host': '127.0.0.1', 'port': 8448}
2021-05-10T19:46:14.801 farmer farmer_server              : INFO     -> harvester_handshake to peer 127.0.0.1 cc2e8d9b0e2b9ec0c69e1ac6884b1ad37824fcda56df56882c6de40a08dbc3d7
2021-05-10T19:46:14.801 harvester harvester_server        : INFO     <- harvester_handshake from peer 5800b7c4469b6c0cce346af270106dea18bd19fc5c683a15edc0e03cc8fd7560 127.0.0.1
2021-05-10T19:46:14.821 harvester chia.plotting.plot_tools: INFO     Searching directories ['D:\\', 'E:\\']
2021-05-10T19:46:14.829 harvester chia.plotting.plot_tools: INFO     Not checking subdirectory D:\$RECYCLE.BIN, subdirectories not added by default
2021-05-10T19:46:14.831 harvester chia.plotting.plot_tools: INFO     Not checking subdirectory D:\System Volume Information, subdirectories not added by default
2021-05-10T19:46:14.831 harvester chia.plotting.plot_tools: INFO     Not checking subdirectory E:\$RECYCLE.BIN, subdirectories not added by default
2021-05-10T19:46:14.831 harvester chia.plotting.plot_tools: INFO     Not checking subdirectory E:\System Volume Information, subdirectories not added by default
2021-05-10T19:46:14.921 harvester chia.plotting.plot_tools: INFO     Loaded a total of 101 plots of size 9.997358936146156 TiB, in 0.12052464485168457 seconds
2021-05-10T19:46:14.600 full_node full_node_server        : INFO     <- new_peak from peer 8a0cbc71c5b848f3a2586a3bc29a084fcf6017d8705df8254af1838cac3fc525 94.112.103.185
2021-05-10T19:46:15.625 full_node full_node_server        : INFO     <- new_peak from peer 0a3113f241f902f065e14eefe0d6bb6ad5cffa52321603457682065cab863fc8 69.247.220.33
2021-05-10T19:46:15.635 full_node full_node_server        : INFO     -> request_block to peer 94.112.103.185 8a0cbc71c5b848f3a2586a3bc29a084fcf6017d8705df8254af1838cac3fc525
2021-05-10T19:46:15.635 full_node full_node_server        : INFO     -> request_block to peer 69.247.220.33 0a3113f241f902f065e14eefe0d6bb6ad5cffa52321603457682065cab863fc8
2021-05-10T19:46:15.643 full_node full_node_server        : INFO     <- request_block_header from peer 62e35d739c42156408cfe9314a59a77bafabeb6412ebb633667561c26f9a006f 127.0.0.1
2021-05-10T19:46:15.655 full_node full_node_server        : INFO     <- new_signage_point_or_end_of_sub_slot from peer 8a0cbc71c5b848f3a2586a3bc29a084fcf6017d8705df8254af1838cac3fc525 94.112.103.185
2021-05-10T19:46:15.655 full_node full_node_server        : INFO     <- new_signage_point_or_end_of_sub_slot from peer 0a3113f241f902f065e14eefe0d6bb6ad5cffa52321603457682065cab863fc8 69.247.220.33
2021-05-10T19:46:15.655 full_node full_node_server        : INFO     <- new_signage_point_or_end_of_sub_slot from peer b277cede4042c72c972a6b83dee714760c47aeda0537ea3d5d6ab41b8a3bfbfc 168.119.89.171
2021-05-10T19:46:15.655 full_node full_node_server        : INFO     <- new_peak from peer b277cede4042c72c972a6b83dee714760c47aeda0537ea3d5d6ab41b8a3bfbfc 168.119.89.171
2021-05-10T19:46:15.655 full_node full_node_server        : INFO     <- new_signage_point_or_end_of_sub_slot from peer 50a9363d79143232d1db5ddd039c93b1d15936895bbd88336f248b7477e32179 58.122.145.29
2021-05-10T19:46:15.655 full_node full_node_server        : INFO     <- new_peak from peer 50a9363d79143232d1db5ddd039c93b1d15936895bbd88336f248b7477e32179 58.122.145.29
2021-05-10T19:46:15.663 full_node full_node_server        : INFO     <- new_peak from peer 8033c4961834502e373a9fd3e4d9cbd53a76a17253d26eecb7d114c3ea8c5e79 92.4.195.161
2021-05-10T19:46:15.663 full_node full_node_server        : INFO     <- new_signage_point_or_end_of_sub_slot from peer 8033c4961834502e373a9fd3e4d9cbd53a76a17253d26eecb7d114c3ea8c5e79 92.4.195.161
2021-05-10T19:46:15.665 full_node full_node_server        : INFO     <- new_peak from peer 8e3c2f54a58eb61df38652342f1691cae9fe573f286002063f7ee9b973c3ab21 101.100.164.51
2021-05-10T19:46:15.665 full_node full_node_server        : INFO     -> request_block to peer 168.119.89.171 b277cede4042c72c972a6b83dee714760c47aeda0537ea3d5d6ab41b8a3bfbfc
2021-05-10T19:46:15.665 full_node full_node_server        : INFO     -> request_block to peer 58.122.145.29 50a9363d79143232d1db5ddd039c93b1d15936895bbd88336f248b7477e32179
2021-05-10T19:46:15.665 full_node full_node_server        : INFO     -> request_block to peer 92.4.195.161 8033c4961834502e373a9fd3e4d9cbd53a76a17253d26eecb7d114c3ea8c5e79
2021-05-10T19:46:15.673 full_node full_node_server        : INFO     -> request_block to peer 101.100.164.51 8e3c2f54a58eb61df38652342f1691cae9fe573f286002063f7ee9b973c3ab21
2021-05-10T19:46:15.675 full_node full_node_server        : INFO     -> respond_block_header to peer 127.0.0.1 62e35d739c42156408cfe9314a59a77bafabeb6412ebb633667561c26f9a006f
2021-05-10T19:46:15.675 full_node full_node_server        : INFO     -> request_signage_point_or_end_of_sub_slot to peer 94.112.103.185 8a0cbc71c5b848f3a2586a3bc29a084fcf6017d8705df8254af1838cac3fc525
2021-05-10T19:46:15.675 full_node full_node_server        : INFO     -> request_signage_point_or_end_of_sub_slot to peer 69.247.220.33 0a3113f241f902f065e14eefe0d6bb6ad5cffa52321603457682065cab863fc8
2021-05-10T19:46:15.675 full_node full_node_server        : INFO     -> request_signage_point_or_end_of_sub_slot to peer 168.119.89.171 b277cede4042c72c972a6b83dee714760c47aeda0537ea3d5d6ab41b8a3bfbfc
2021-05-10T19:46:15.675 full_node full_node_server        : INFO     -> request_signage_point_or_end_of_sub_slot to peer 58.122.145.29 50a9363d79143232d1db5ddd039c93b1d15936895bbd88336f248b7477e32179
2021-05-10T19:46:15.675 full_node full_node_server        : INFO     -> request_signage_point_or_end_of_sub_slot to peer 92.4.195.161 8033c4961834502e373a9fd3e4d9cbd53a76a17253d26eecb7d114c3ea8c5e79
2021-05-10T19:46:15.683 wallet wallet_server              : INFO     -> handshake to peer 127.0.0.1 dd3262192a07f4eadb6cbec04242aa513acc672c218ed205bc7cefc8679d211d
2021-05-10T19:46:15.685 full_node full_node_server        : INFO     -> handshake to peer 127.0.0.1 62e35d739c42156408cfe9314a59a77bafabeb6412ebb633667561c26f9a006f
2021-05-10T19:46:15.685 wallet wallet_server              : INFO     Connected with full_node {'host': '127.0.0.1', 'port': 8444}

Its Normal?
Can you understand why this error and why disconnetted and reconneting all the time?

Thank you

In that case you didn’t win the lottery those times. It’s normal and will be like that for weeks/months.

I don’t know, what did you find in a search?

You think that my log is correct?
Or there are something strange?

for example:

 harvester_server        : INFO     Connection closed: 127.0.0.1, node id: 5800b7c4469b6c0cce346af270106dea18bd19fc5c683a15edc0e03cc8fd7560
2021-05-10T19:46:13.904 harvester chia.harvester.harvester: INFO     peer disconnected {'host': '127.0.0.1', 'port': 8447}
2021-05-10T19:46:13.585 full_node chia.full_node.full_node: INFO     peer disconnected {'host': '127.0.0.1', 'port': 8449}
2021-05-10T19:46:14.600 full_node full_node_server        : ERROR    Exception:  <class 'concurrent.futures._base.CancelledError'>, closing connection {'host': '127.0.0.1', 'port': 8449}. Traceback (most recent call last):

thank you …

I really don’t know. Search :mag: is your friend and let us know what you find there! :+1:

Hi @e8s

How to see the log like that ? I changed level log to INFO, but no have any “proofs” and “time” word in debug log file.

Please help

In Linux CLI you can use the command grep proofs .chia/mainnet/log/debug.log

If there aren’t any, you probably aren’t actually farming. The most likely reason is that the full node is not finished syncing. If you are using the CLI, try running chia farm summary, which should confirm whether your farmer is active. I assume that this information is easy to find in the GUI but I don’t know where.

2 Likes

And this is normal?

how can we look to the this screen?

The peer disconnect messages are not normal. Is this a plain default setup using the default config file? If so, my first diagnostic step would be to try increasing the log level. I’m not sure what the next level after info is but debug or trace would be my first guesses. Maybe someone else will know. If you are not running the default config (maybe you have a distributed system) I’d double check the configuration first.

The problem is solved. The computer was 100% charged and crashed. Restart decided everything. Thanks for your attention. :+1:

1 Like