Daemon recurring error message about monero

[houseofleaf]

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

[houseofleaf]

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.

[selsta]

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?

[vtnerd]

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.

[houseofleaf]

Sorry, I didn't mean to close this

[vtnerd]

Did you check for outbound connections when the errors appeared or later? We still don't have confirmation of a bug unfortunately.

[selsta]

@vtnerd what happens when the randomly selected peer in the stem phase disconnects? could this cause the message?

[vtnerd]

The Dandelion++ code should select a replacement peer, if available.

[toncho6501]

fake monero