-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I was not able to generate blocks #1359
Comments
It's normal on my private net too. |
Any clue? I was following the flow, and I don't know why it spend this time in |
Are you using |
Yes. |
You can see in the video that the block is not received in protocol {
"ProtocolConfiguration": {
"Magic": 5195086,
"MillisecondsPerBlock": 1000,
"StandbyValidators": [
"032887e2f9ac0081d0ec622d42285afb10134990e7b193e596690630d43ebe806e"
],
"SeedList": [ ]
}
} |
I found the issue, but now i need to understand why :S |
With empty seeds, it takes the default seeds. And it starting throwing errors in dns, and AKKA's messages was lagged Without seeds, ( And I am able to generate blocks |
@Tommo-L The question is why non working dns can alter the AKKA messages? neo/src/neo/Network/P2P/LocalNode.cs Line 89 in e913403
My error
|
Maybe DNS queries can consume a lot of time? We should set a timeout. |
With only one CN and Memory store, I never received the Block in LocalNode
I was able to ensure that the block was relayed here
But in
LocalNode
I never receive the blocks hereCould @superboyiii tell me if you have any problem with this?
The text was updated successfully, but these errors were encountered: