@aatonnomicc FYI here’s an odd one. I saw this earlier but this is on a clean setup using my tweaked scripts. As you can see it has started a couple of hundred nodes with version 0.4.4 and then seems to think it needs to upgrade to 0.4.4. From then the log appears to stop, although it does continue starting new nodes
...
antnode0211,12D3KooWFhDvSrVacSBrivLeQrb1RzumGeZWsw3e8BW6pXHUQJCJ,0.4.4,RUNNING
**************************************
* *
* Installing antnode *
* *
**************************************
Installing antnode for x86_64-unknown-linux-musl at /home/ant/.local/bin...
Installing antnode version 0.4.4...
antnode 0.4.4 is now available at /home/ant/.local/bin/antnode
upgradeing ant node binary with antup node --version 0.4.4
Have any anm runners seen this and is it a problem?
it has an attempt at an auto upgrade which will work if you remove the
--version 0.4.4```
from the config file it is hard wired by default as there was some strange behaviour where antup node would get a lower version in the past.
when it tries to do an upgrade it will delete the old log file to start a fresh log.
if you check the config file there is something about an upgrade hour and minute I bet the time that happened corresponds to that time.
anm works in strange ways it was supposed to be a few lines in a script to start nodes that ended up continually growing arms and legs over the beta period
It’s happy so I’m not touching anything for now. I want to see how many nodes it starts until it levels off.
I haven’t bothered with NTracking though, which might explain the remaining cron emails but they aren’t many so I’ll leave it for now, or just shut them off with 2>&1 /dev/null
yes if you set ““ it removes the version flag so it will upgrade to latest at the upgrade hour and minute time which is set just above in the config file
When watching discord now it seems some nodes might have trouble restarting after Bootstrap cache changes, some seems to timeout. I am starting to consider delaying node upgrade.
The NodeRestartV version, is that if they fail to start?
I’ve started a bunch of homes nodes again. These should just be quality ones, not overprovisioning whatsoever. Just straight up trying to contribute to the decentralization.
I got to say, I’ve been messing around with launchpad and antctl but the entry barrier in my opinion is still quite high for a regular user.
After the suggestion from Southside to use Formicaio from @bochaco I figured I’d give it a go. But this is really showing me the power of what a community can accomplish. This is so much easier to understand and user-friendly than antctl already, kudos! Now I think we could improve on this even further when it comes to UI/UX and I’m more than happy to assist here. But I also noticed there are some other community made tools out there already. Perhaps this is something we should all combine forces on to make running a home node as easy as can possibly be. It’s really such an important aspect to getting more decentralized, in multiple ways.
Talk to @aatonnomicc about anm ( a subfolder of NTracking on Github) which does not use antctl either upfront or in the background.
There is certainly some room for improvement on the Formicaio UX but if I have not submitted an issue to @bochaco’s Github then I should not moan. Instead, I’ll congratulat @bochaco on an excellent tool that is the best noderunner by a long way IMHO.
