Announcement: Antnode Upgrade 0.3.1

Development Updates
1

:loudspeaker: Announcement: Antnode Upgrade 0.3.1 :loudspeaker:

Please follow these instructions to upgrade your nodes to the newest version to ensure the best performance and stability for everyone! We have seen improvements in reducing resource spikes with this upgrade. Although you don’t need to upgrade to continue earning attos, I encourage you to do so.

For Node Launchpad Users:

  1. Open Node Launchpad v0.5.1 if you are not already on that version
  2. Press O to access the Options screen.
  3. Then, press Ctrl + U, and hit Enter. This will upgrade your nodes. Upgrading can take several minutes for each node. Please don’t close the app or stop your nodes during this process.
  4. Your nodes will now stop
  5. Press Ctrl + S to start your nodes again

For CLI Tool Users:

  1. If you’re using the CLI tool, please update and upgrade. Run the update first: antup update
  2. Then run the upgrade: antctl upgrade --interval 60000

For ALL Users:

  • Please start your nodes gradually — especially if you plan on running multiple nodes.
  • Be conservative with CPU allocation to maintain stability

Binary Versions:

  • antnode: v0.3.1
  • antctld: v0.11.5
  • antctl: v0.11.5
  • ant: v0.3.1
  • nat-detection: v0.2.13
  • node-launchpad: v0.5.1
8 Likes
2

@rusty.spork I didn’t have to hit ctrl-S, the three nodes I run, ‘Updated’ and just started by themselves. Is this correct?

image
image1101×707 58.3 KB

3 Likes
3

Yes, you should be good.

3 Likes
4

I did this a few days ago but going to check they were up to date just now, I find 5/5 nodes on my slightly more powerful VPS are stopped and have earned nothing.

While on my really cheap VPS 5/5 are running and have bee earning since I updated them :man_shrugging:

I probably killed them off accidentally by running other stuff on the VPS, but this is a warning to folks that nodes can die for unexpected reasons.

So I think we need a way to ensure they keep running (or get restarted) without having to be tended by hand on a regular basis.

1 Like
5

I have also found some peculiar stopped nodes. Seems error writing to disk is killing nodes too not only cpu.

4 Likes
6

Iv seen that write to HD error on several systems but peculuary it was only antnode001 on each of the systems

1 Like
7

If we’re running Node Launchpad 0.5.0 and the antnode versions are already 0.3.1, should we take any action?

8 
Retrieving latest version for safenode...
Latest version of safenode is 0.3.1
There is no previous installation for the safenode component.
No update will be performed.

Retrieving latest version for safenode-manager...
Latest version of safenode-manager is 0.11.5
Current version of safenode-manager is 0.11.4
Updating safenode-manager to 0.11.5...
Installing antctl for x86_64-unknown-linux-musl at /root/.local/bin...
Installing safenode-manager version 0.11.5...

Since we changed terminology from safenode to antnode, etc., here I can still see some old words during the update process.

2 Likes
9

A while ago I pointed out to Chriso that he was saying nodes will update in place and restart themselves while the instructions say to restart them manually.

Guess you showed Chriso was correct

10

Months ago I saw this where 50 out of 100 nodes died and one left its logs with this error. (Before the CPU test was implemented)

Plenty of disk space available and no other issue I could identify.

Then the problem went away after a couple of days. Weird

Oh make sure your wastebin is being emptied. Resets can delete all the chunks and they end up in the wastebin chewing up disk space. (not my problem above though LOL)

2 Likes
11

I upgraded my nodes on the 21st Dec to 0.3.1

Just checking if this is another upgrade to the same version number or indeed the same one released some 5 or 6 days ago.

3 Likes
12

It’s all a custom setup I use and I know old chunks were cleared out.

It was several machines node 001 and only 001 had shut down only a few machines but not all of them.

I’m keeping an eye on it if I see it in next upgrade ill dig in further with it

1 Like