Signage point: "Don't have rc hash" / "Don't have signage point"

[adamsky-01]

When I'm searching the log file for string "signage point" I'm getting plenty of lines with:

"Don't have rc hash"
and
"Don't have signage point"

I've got a suggestion from the Chia support on Keybase to reduce the CPU load as I was also plotting on the same PC. I did it, I've restarted PC and I was running only the Chia farmer for a few hours, without any other programs running at the same time. The PC resources were barely used but I was still getting "Don't have rc hash" and "Don't have signage point" in new lines of the debug.log file.

My setup details:
Chia-blockchain ver. 1.1.7 (started from CLI, no Chia GUI used)
OS: Windows 10
CPU: Ryzen 5900X
RAM: 48GiB
LAN: Gigabit Ethernet, no WiFi cables only
Internet: 1Gb fibre broadband (fully tested: low latency and jitter, no packet loss)
Time: correct time zone, synchronized with windows server
Seek times: 100% below 5sec, 95% below 1sec
Sync status: I didn't notice any node or wallet syncing issue

Questions:

• Are these log lines indicating that the chance of winning Chia might be reduced?
• Is it possible (if yes how) to eliminate these lines with "Don't have rc hash" and "Don't have signage point"

2021-06-19T08:27:26.820 full_node chia.full_node.full_node: INFO       Finished signage point 62/64: CC: dcadc7d860f7d611172dc7feea718755aa100227586802c80677672f7055b32f RC: 44e3687c50d38d8a0a32556c66a15dd8f8b2c24f25f9587101f6d4761b4b9fcf
2021-06-19T08:27:36.946 full_node chia.full_node.full_node: INFO       Finished signage point 63/64: CC: 03aeb2a532058745a37cb7cfdb29796b2a603342c782d451ada541eb76312251 RC: f1155969052473634685d2f96ea5520d45aea97e867fbe481d304915505183b3
2021-06-19T08:27:52.936 full_node chia.full_node.full_node_store: INFO     Don't have rc hash 15ac438ee2672928502789f3829fa91f57b646b81c30bde5eecbe6f2464d0906. caching signage point 61.
2021-06-19T08:27:59.965 full_node chia.full_node.full_node: INFO       Finished signage point 1/64: CC: f34f31b8af254f3e49430b144a428713b58f9c9f386e5bc57ba4974ce8a675e3 RC: 9ec0194fcecbbc66305b0e3aa542c6920415163e09b7097c856dd7d99a7e77d0
2021-06-19T08:28:02.300 full_node chia.full_node.full_node_store: INFO     Don't have rc hash 15ac438ee2672928502789f3829fa91f57b646b81c30bde5eecbe6f2464d0906. caching signage point 62.
2021-06-19T08:28:09.228 full_node chia.full_node.full_node: INFO       Finished signage point 2/64: CC: 6f4341c808af5c1581fb4557b8c79c7a293935ff40076664f7aa474c2538e21a RC: a265b618406ebeff56037093ecb2d584de98f4305de25ad00eac8ac73674a698
2021-06-19T08:28:17.655 full_node chia.full_node.full_node_store: INFO     Don't have rc hash 171341bb09a7e04d2c05f43091b7bce12c3dde8534747836d5b3eb332117463d. caching signage point 63.
2021-06-19T08:28:19.578 full_node chia.full_node.full_node: INFO       Finished signage point 3/64: CC: c9aeeee579d1d39a7056c1a1497d739645b4a68e279c9885802c85ce99627fac RC: 534595824e42c8fab1479cc67be37ffb455bffcfe7186449237f9c162e8fb1ef
2021-06-19T08:28:28.337 full_node chia.full_node.full_node: INFO       Finished signage point 4/64: CC: 273ebb8434f6371d91e2bad35ac45ab4db581fc468e27c589d218008ce9f2ad4 RC: a8034a5223ad7c44f70ae007af77a7c1ef74b9618c6bd0b1a6b69dd5d42a682a


2021-06-19T08:31:52.351 full_node chia.full_node.full_node: INFO       Finished signage point 26/64: CC: 830db6e7eb2fcd31c066f354faeafeeea36cb19b5bdc95c7734f0520568244a5 RC: a935de6e1243c90e6bfee710310bb2f53ffd8f717ba02033515557f088d3fac5
2021-06-19T08:32:00.657 full_node chia.full_node.full_node: INFO       Finished signage point 27/64: CC: c0c890c4b70559f79ce683caae9700a3b85f4bb04941fba1a184f4d5940ccda1 RC: 87f47286d8261c382cde12768f19de67ef9d9aa8864f0fcd1407c3c7b85f8e0a
2021-06-19T08:32:01.628 full_node chia.full_node.full_node: INFO     Don't have signage point {'challenge_hash': '0xac6c1a2a65078576f1d09d38bae2e325dc4dfe45ab1eed9616168bf8f08c8a7c',
2021-06-19T08:32:01.630 full_node chia.full_node.full_node: INFO     Don't have signage point {'challenge_hash': '0xac6c1a2a65078576f1d09d38bae2e325dc4dfe45ab1eed9616168bf8f08c8a7c',
2021-06-19T08:32:09.290 full_node chia.full_node.full_node: INFO       Finished signage point 28/64: CC: 1f9f45bbf64899286b8f191744255ca0974c5924457143d37a207b12abf2a897 RC: e4f4b93a14392cd8717e6d7edfc8f0b037607372e4bcfdf9a38ddbef65b6f16d
2021-06-19T08:32:19.330 full_node chia.full_node.full_node: INFO       Finished signage point 29/64: CC: 5a904ccf95576384f5b1fa3226825c4734dc2bb8d3cbaa793c7155da6999bab1 RC: 00a2ab77d27a1ab6916c5ac30ac0da5ff8a34f0d178c1faa6ca3395100c50ea8

[loppefaaret]

the only way i see, is if you get connected to more peers - it would allow you to have more "strings" into the network, and eliminate the need for the blocks to pass through other peers before they get propagated to you - that being said, almost every instance of "rc hash" i've seen, are going on for ½ a second, before your node has gotten the signage point solved, and accepts it...
but it is all part of the "30 seconds" window - and judging from the rest of your story, it sounds like you a missing minimal amounts of farming opportunities

if you got consumer network gear on the path to internet, i wouldnt go far beyond 80 peer:
in config.yaml you find:

  target_outbound_peer_count: 10
  target_peer_count: 80

first line is how many your node seeks out to connect to, once this is reached, it stops creating connection attempts itself
the second line is how many it accepts coming in

[adamsky-01]

I'll test it and I'll share the result here.
Originally I had:

  target_outbound_peer_count: 8
  target_peer_count: 80

I've changed it to:

  target_outbound_peer_count: 20
  target_peer_count: 160

[adamsky-01]

UPDATE:
I've approx. 160 (157-159) FULL_NODE connections since a good few hours. Unfortunately it makes absolutely no difference on the frequency of occurrence lines with "Don't have rc hash" and "Don't have signage point". It has to be something else.

[BrandtH22]

@adamsky-01 , since this ticket was opened a number of years ago without further comments it seems this issue has been resolved.
We will be closing this ticket but if we have closed this ticket in error do not hesitate to reach out to us again with any followup questions or comments.

The best place to reach our support team is on Discord (https://discord.gg/chia) or by reopening this ticket.