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
Daemon recurring error message #9314
Comments
If it only shows up once in a while you can ignore it. I sometimes see it on my nodes too. The transaction will still end up getting propagated in the Dandelion++ fluff phase. @vtnerd can you explain in detail what could cause this? |
This should only happen when you don't have any outbound connections. If you have outbound connections, then there is a bug somewhere in the D++ logic. |
I can confirm I do have outbound connections |
Sorry, I didn't mean to close this |
Did you check for outbound connections when the errors appeared or later? We still don't have confirmation of a bug unfortunately. |
I check the status frequently, and I recieved confirmation of inbound and outbound connections before and after the errors appeared. It hasn't appeared again since filing this issue. |
@vtnerd what happens when the randomly selected peer in the stem phase disconnects? could this cause the message? |
The Dandelion++ code should select a replacement peer, if available. |
This error continues to appear when monerod is running:
I run a node with port 18080 open. Does anyone know what this means, or how it can be resolved?
The text was updated successfully, but these errors were encountered: