-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
Error in log: "Nonce not matching. That should never happen." #1468
Comments
Are you still seeing it? |
It looks like a peer is spamming you. This PR throttles the warnings: #1469 |
I've been running for a while every day with --maxConnections=300 to gauge the size of the network, so I'm more likely to see a single peer out of the network misbehaving than someone with max 12 connections. I'll leave it up longer today to see if I get it again. Maybe it should log the peer address to make it easier to track them down? |
Added the peer node address to the log. |
Logging merged in #1469 |
Got some more of them. I put in the peer logging but not the suppression, so I got to see that it happens in a burst, but from all different peers:
|
It takes a couple days of continuous running to see it again. I got two more batches so far; I include one below. All different addresses, all within a few seconds of each other.
|
Getting this error regularly in the log running haveno-reto current (1.0.14)
The text was updated successfully, but these errors were encountered: