Seems like we’re hung attempting to vote off nodes, and so never accepting new joins just now.
Okay, going to bring this down.
If you’re lucky atm, you can put a chunk or two. But I can see we’ve stalled voting. Seemingly as we have bad elders, but that sees to be as we have had no node aging at all. I do not see a single RelocateStart
log for example.
So a few compounding factors there.
All good stuff though! And plenty of logs to sift through to see if we can see why things are not happening!
Thanks everyone who participated here!
Can you or somebody else look what happened to the --public-addr
parameter? Why it cannot be set? My ISP has specific NAT setup and without this parameter I cannot run nodes. In previous testnets, where could manually enter public and private address my nodes worked fine.
@bzee can update you on what’s afoot there. (thanks @bzee )
(in short, it should not be needed now… but I’m not up on the ins and outs there)
The public_addr
was not used in the actual code anymore. Therefore we removed it, it should not make a difference to how a node runs.
What exactly did your ISP need that required you to set the public_addr
?
They give me public IP (176.62.229.135), but in the form of 1:1 NAT so the real public IP is somewhere in the ISP network and on my router I have 10.x.y.z as WAN and 192.168.x.y LAN.
When I set --public-addr 176.62.229.135 --local-addr 192.168.x.x everything works fine, without it the autodetection tries to use the 10.x.y.z address as public.
What do you mean by autodetection?
When I do safe node join --network-name feb2
without the additional parameters.
Interesting to see this was brought down two or three hours ago. My node is still running, storing 9.6GB and still receiving chunks so I thought wow, this is good!
What does it say if you safe networks sections
I think that there is a lot of confusion in the community on how this works (see also NAT thread)
It would be great to have clarifications on how the IP is detected, how to understand whether a node is reachable, etc. For example, in this feb2 testnet, I think my node joined (and got chunks), but couldn’t see my node in the list when executing safe networks sections
.
Maybe in the next weekly update?
@aatonnomicc did your nodes end up in the elders list? As I understand, you’re using Oracle cloud as well…today I had a look at the instance configutation and got lost in VNCs, subnets, gateways etc…we should exchange notes…
So, if @joshuef brought down their nodes, does it mean that the remaining nodes are from community?
I’m about to board a plane right now but I’ll have a look at my set up in oracle and put some tips together.
If you working at it now remember to contigure the fire wall in Ubuntu as it blocks everything except ssh on port 22 by default.
Will developers search for why “… Did not receive sufficient ACK messages … expected: 7, received 0” errors were happening?
I can’t find clear answer about this problem in this discussion.
Thanks mate, I’m off to bed soon, but I remember fixing that thanks to an old post of yours, here for reference:
Still I think there’s more to it, as per this link:
Say wut? 2GB max , old chunks?
No, it started empty.
I’ve deleted it all though so can’t check.
Hopefully there will be a new test up soon with the fixes.
AIUI safe networks sections only shows the Elders so its unsurprising that on a short-lived network your IP would not be shown.
@joshuef how many total nodes did you start with?