Jormungandr: Stability with/without listen_addr + public_addr

[voidovic]

When is in node config defined listen and public addr, then will node stuck in 5-60 minutes.

If these directives are commented, then are nodes (passive/active, boths) active without stucking.

[laplasz]

which version are you using? v0.8.6 should be better now

[ofakem-banock]

I have the same problem. Running v0.8.6, one of my node node is up 22hours now without getting stuck when my node config doesn't have listen and public addr defined. When I put them in my node config, my max uptime is 15min then I get stuck

[dmindfuse]

I have the same problem. Running v0.8.6, one of my node node is up 22hours now without getting stuck when my node config doesn't have listen and public addr defined. When I put them in my node config, my max uptime is 15min then I get stuck

Interesting, I also have the addresses configured and have a long bootstrapping phase (>10minutes) followed by up to 50-60mins of uptime, then stuck/desync.

Are you stating that running without the addresses defined in the config you're getting more stable performance? You are actually seeing your blockHeight increase in this case, not just the node humming while doing nothing?

I haven't tried this, as I thought it was considered bad practice...? There's the following thread about an aspect of this as well: #1537

[ofakem-banock]

@dmindfuse Yes I am now synced for about 2 days now without the addresses configured. And the blockheight is increasing and it is in sync with pooltool.io and the shelleyexplorer.

I know it is bad practice but it is the only solution I have at the moment to not get stuck. I run a passive node with the addresses configured and it can't stay synced for more than 1hr. I hope they will look into it and solve this issue

[dmindfuse]

@ofakem-banock Glad to hear that’s working for you. I may try that, because the 1hr is spot on the issue I’m seeing as well. Cheers.