Skip to content
This repository has been archived by the owner on Jun 12, 2023. It is now read-only.

send_witness:234: failed to dial challenger #976

Closed
wolasss opened this issue Aug 11, 2021 · 0 comments
Closed

send_witness:234: failed to dial challenger #976

wolasss opened this issue Aug 11, 2021 · 0 comments

Comments

@wolasss
Copy link

wolasss commented Aug 11, 2021

I am getting a lot of 'failed to dial challenger' errors while sending witness proof with a direct p2p connection to the challenger. This causes a lot of beacons with 0 witnesses since the miners cannot connect to the challengers. Consider logs from my three miners:

https://pastebin.com/j2Q6XfPv - miner 1
https://pastebin.com/EAQYYxQA - miner 2
https://pastebin.com/Vzyuvdvy - miner 3

My networking setup is correct - ports are properly forwarded, no firewall is blocking the inbound/outbound traffic. I also run them behind a VPS with separate public IPs for each one of them because of helium/erlang-libp2p#44. This way it yields much more witnesses but there are still cases where direct p2p connection fails (timeouts) for an unknown reason.

I think these failures happen way too often to be an occasional issue with the other peer (challenger) it seems to me that this is related to the network itself.

Maybe there should be an additional logic if p2p connection timeouts so that the witness proof is relayed anyway.

@evanmcc evanmcc closed this as completed Sep 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants