[ Core 23.0 Regtest ] Debug logs spammed with "Selected address from new"

nc50lc

legendary

Activity: 2394

Merit: 5531

Self-proclaimed Genius

Quote from: cmdcode on May 13, 2022, 12:44:06 AM

Quote from: nc50lc on May 11, 2022, 02:19:29 AM

-snip-

Thank you for taking the time to test that! I do have "debug=addrman" enabled. The output is not interfering with anything, but it does seem quite spammy so I was wondering if maybe it was a bug.

I've searched for related Pull Requests after v22.0 and found this: https://github.com/bitcoin/bitcoin/pull/22839/files
Apparently, it's added as an improvement to "Address Manager" logging.

cmdcode

newbie

Activity: 3

Merit: 2

Quote from: nc50lc on May 11, 2022, 02:19:29 AM

Quote from: cmdcode on May 10, 2022, 03:30:08 PM

I have two regtest nodes, one connected to the other through the "addnode" RPC command. Both nodes are using Tor.
-snip-
unless I add "connect=0" to the config.

I didn't have this experience with Core version 22.0. Is this normal behavior for the node, or is this a bug?

Have you enabled debugging?
I have tested it and it shows in v23.0 with either -debug or -debug=addrman active but it's not showing in v22.0.
So it might be something new that's added in the latest version.

Also, by adding "connect=0", you have disabled "automatic connections" so it might have something to do with it.

Thank you for taking the time to test that! I do have "debug=addrman" enabled. The output is not interfering with anything, but it does seem quite spammy so I was wondering if maybe it was a bug.

nc50lc

legendary

Activity: 2394

Merit: 5531

Self-proclaimed Genius

Quote from: cmdcode on May 10, 2022, 03:30:08 PM

I have two regtest nodes, one connected to the other through the "addnode" RPC command. Both nodes are using Tor.
-snip-
unless I add "connect=0" to the config.

I didn't have this experience with Core version 22.0. Is this normal behavior for the node, or is this a bug?

Have you enabled debugging?
I have tested it and it shows in v23.0 with either -debug or -debug=addrman active but it's not showing in v22.0.
So it might be something new that's added in the latest version.

Also, by adding "connect=0", you have disabled "automatic connections" so it might have something to do with it.

vv181

legendary

Activity: 1932

Merit: 1273

Quote from: BitMaxz on May 10, 2022, 07:18:41 PM

That is misconfiguration if you use only the onion address on "addnode" it should be the Ip address: Port

Code:

192.168.1.1:8777

Addnode configuration can be used with its own respective network type(IPv4, CJDNS, onion, etc).

Quote from: cmdcode on May 10, 2022, 07:47:13 PM

Is it possible for it to be misconfigured yet the nodes still connect over tor?

I don't think that is where the problem relies on, though I'm also not sure about the OP problem. I don't particularly have an experience with regtest, maybe you can wait for someone else or try to set up a more log level might help. You can use debug=net on the bitcoin.conf.

cmdcode

newbie

Activity: 3

Merit: 2

Quote from: BitMaxz on May 10, 2022, 07:18:41 PM

That is misconfiguration if you use only the onion address on "addnode" it should be the Ip address: Port
Your Bitcoin core is trying to connect on that set up it's rejected which is why it keeps spamming repeatedly.

Sample of IP address: Port

Code:

192.168.1.1:8777

Can you read this maybe this guide below will help you to set up your config?

- https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md

Thank you for the reply. I am surprised that it is a misconfiguration, because the status of the peer is connected and I receive transactions / blocks between the nodes.

Is it possible for it to be misconfigured yet the nodes still connect over tor?

I will try adding the port designation. I did not add it previously because bitcoind is a little weird with regards to how it handles incoming tor connections (moving between 18445-18444 on regtest).

Edit: When I add the port designation, the peer connection no longer works.

BitMaxz

legendary

Activity: 3304

Merit: 3037

BTC price road to $80k

That is misconfiguration if you use only the onion address on "addnode" it should be the Ip address: Port
Your Bitcoin core is trying to connect on that set up it's rejected which is why it keeps spamming repeatedly.

Sample of IP address: Port

Code:

192.168.1.1:8777

Can you read this maybe this guide below will help you to set up your config?

- https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md

cmdcode

newbie

Activity: 3

Merit: 2

Hello. Not sure if this is a bug or standard procedure.

I have two regtest nodes, one connected to the other through the "addnode" RPC command. Both nodes are using Tor.

When reading the debug logs for the connecting node, it will spam repeatedly this line, about twice a second:

"{date string} Selected {onion address} from new" I have redacted the date and onion address.

The debug logs for the node being connected to will show something similar, unless I add "connect=0" to the config.

I didn't have this experience with Core version 22.0. Is this normal behavior for the node, or is this a bug?

Thank you for reading!

Topic: [ Core 23.0 Regtest ] Debug logs spammed with "Selected address from new" (Read 122 times)