Skip to content
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

[BUG] ntpsync error first seen? #430

Open
minsulee2 opened this issue Jun 4, 2021 · 1 comment
Open

[BUG] ntpsync error first seen? #430

minsulee2 opened this issue Jun 4, 2021 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@minsulee2
Copy link
Member

Got firstly the below message during data compatibility test. (Env: four of data version 1.0.0 and one of data version 2.0.0)

[CONSENSUS] ntpsync error: Error: Operation timed out Error: Operation timed out

The error message came up in the node version 2.0.0. This error didn't stop the entire network though, reported this for the future accident prevention.

@minsulee2 minsulee2 added the bug Something isn't working label Jun 4, 2021
@liayoo
Copy link
Contributor

liayoo commented Jun 7, 2021

This is actually a known issue, and I thought I mentioned & left comments about the issue but apparently not...
If you see here, ntpsync doesn't allow "concurrent NTP requests or chains of NTP requests", so the error is seen occasionally if you run multiple nodes on one machine (e.g. local hosting env). I left it as it is because 1) it doesn't really affect the nodes nor the tests, 2) it doesn't seem to happen very often, and 3) we don't run multiple nodes in a GCP instance for the testnet. But if we decide to avoid the error message, I could simply add a hosting env check before the ntpsync call. Let me know your thoughts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants