greetings, I'm using a Dockerfile for setting up a few regtest nodes. I face a dns issue inside the container which I can hack my way around but it feels dirty, let me explain. Part of the monerod flag I want to pass is --add-exclusive-node container_name:port . However I dont get where the dns resolution happens, monerod refuses to launch with the various container hostnames I provide, I get a E Exception in

main! Failed to initialize p2p server. So my hack is in the entrypoint script : I have to lookup for the container ip with dig +short container_name and pass that ip in the --add-exclusive-node flag instead and it's working fine. As I said it feels dirty and I thought I could pass hostnames instead of ips for that particular flag, but maybe I'm wrong on that : if you could shed some light that would be great,

thanks in advance

There is no DNS resolution IIRC.

For better err reporting, run with --log-level 1.

gives me this

2022-11-09 15:53:07.618 I Initializing p2p server...

2022-11-09T15:53:07.619462373Z 2022-11-09 15:53:07.619 I Resolving node address: host=monero_buyer_1:28080, port=18080

2022-11-09T15:53:07.619957288Z 2022-11-09 15:53:07.619 E Failed to resolve host name 'monero_buyer_1:28080': Host not found (authoritative):1

2022-11-09T15:53:07.619967670Z 2022-11-09 15:53:07.619 E Failed to parse or resolve address from string: monero_buyer_1:28080

2022-11-09T15:53:07.619974249Z 2022-11-09 15:53:07.619 E Failed to handle command line

2022-11-09T15:53:07.620093305Z 2022-11-09 15:53:07.620 I Deinitializing core...

mmm

think I got it

it's docker compose adding a _1 to the hostname it seems

ha nope sorry my hostname inside the container is monero_buyer_1 and dig +short monero_buyer_1 is successfully getting the ip

ok so given the log, I pass --add-exclusive-node monero_buyer_1:28080 and it seems like it tries Resolving node address: host=monero_buyer_1:28080, port=18080

so the host is the full string and the port is the default port, so I might be using an incorrect syntax for that flag

in essence it seems my issue is that --add-exclusive-node deals fine passing ip:port but treat hostname:port as the host and uses the default port, is there anything I can do on my side ?

Short of adding name resolution, I don't think so. It looks like the lower layer can do since "Failed to resolve host name" suggests it's trying to.

The remaining work would seem to be just command line parsing changes, if that proves correct.

should I open a bug report ?

If you don't want to do it, sure.

If you do, no need.

I'm afraid I'm more into python than c++, will try and see if I can though

"it" being the patch here.

I'm sorry I looked at the code, see where I think it's happening but it's been a while I havnt touched c++ and it would be a mess so I sent a (hopefully) detailed bug report :)

Hi! I use a "transfer" RPC method to create tx. How to choose proper "ring_size", "mixin" and "priority"?

Are you going to send old outputs (pre-ringct) ?

If not (likely), you can set all of them to 0.

btc falling.

but, imo, it seems normal, as btc generally falls around this time. i expect it to continue falling until mid 2023.

cvmn: wrong channel

apologies.

#monero-markets :)

<moneromoooo> "Are you going to send old..." <- I'm not sure what I'm going to send))... (full message at <libera.ems.host/_matrix/media/v3/do…2b68bbde6d9b4855498e243b98c1279ef7b>)

the new wallet rpc docs say " ring_size - unsigned int; Sets ringsize to n (mixin + 1). This field is completely ignored on mainnet." it is optional