Recent Node Updates (Docker Hub API v2)

Hello. I’m running the latest blink script, but my nodes keep saying no on latest version since today. How often does the blink script updates the dockers? Or do I need to manually update them?

1 Like

I’m experiencing the same, latest blink script, but node monitor says not latest version

my pNode is also on 2.0.1, but monitor says that chain version is out of date too.
Screen Shot 2022-10-04 at 20.08.38

Screen Shot 2022-10-04 at 20.09.20

Also, when checking the github page, I actually don’t see that release listed anywhere.
b83c74d4d


The most recent one shown is
65a8235
from 2 weeks ago, and I recall seeing that version on my nodes around that time.

Was there another version that was pushed out and then recalled?

Hi,
65a8235 is the latest tag for the community node. There is a bug in auto update script that get another tag. Luckily, that tag will not affect your node operation.

I’ve just fixed the auto update script.
Please update the fix by running this command:

sudo bash -c “rm -f blink.sh && curl -LO https://raw.githubusercontent.com/incognitochain/incognito-chain/production/bin/blink.sh && chmod +x blink.sh && ./blink.sh -y2”

2 Likes

Thank you I noticed the 22.10 v when I double checked my download.
vnode now showing green.

Is there a manual fix for pNode too?

There will be soon.

@Rocky, all my nodes are showing “Not latest version” but when I try to run this script I get the following:

-f: line 1: "rm: command not found

If you run Rocky’s script and choose option 2, it should fix everything for you.

sudo bash -c “apt install curl -y && curl -LO https://raw.githubusercontent.com/incognitochain/incognito-chain/production/bin/blink.sh && chmod +x blink.sh && ./blink.sh”

Look under:
How to setup your own node in a blink of an eye (Now support multi-nodes per host)
“How to update the IncognitoUpdater service if I already install an older version of it?”

I ran that script but it pulled an old image 20220921_1 and after 30 minutes all my vnodes are still offline. How do I force update that image?

The new Blink.sh should be on version 22.10.

Look at line 2 in Blink.sh (in /home directory) and make sure it says 22.10.
image

I have the same issue and its version 22.10. It’s still pulling through 20220921_1.

Also if its a new image we should be pulling through - why didn’t the team make an official post?

1 Like

It is not mandatory release. In fact, it changes nothing for the shard validators. Only one line of change for the beacon producers. It only made enabling the new features quicker. Probably the reason is this.

https://github.com/incognitochain/incognito-chain/compare/production…hotfix/increase-trigger-limit#diff-c4cc080e565e84611e2d2f9994587b9a040b2093bfed32f29ba1a3a525df8d4b

3 Likes

Thank you for the explanation :slight_smile:

2 Likes

@Support, any idea on how to get this updated? It’s still showing 20220921_1.

image

Hey @JG20, @SPAddict25, @sn0w

Now, I’ll correct myself. 20220921_1 is the latest version for us, ordinary shard validators in the mainnet. So this versioning (00221004_1) is also OK. It seems that the first decimal has a meaning. My guess: 2 for ordinary shard validators, 1 for shard validators using beta versions, 0 for beacon validators. This also verifies my explanation below:

So how come some validators were updated with 00221004_1? Since blink.sh has a minor bug. The buggy version had echo ${tags[*]} | sort -rn instead of sort -nr <<< "${tags[*]}". So the validator with the latest blink.sh won’t be updated.

Reverse engineering at its finest :joy:

2 Likes

Excellent. Thank you for the detailed explanation in plain language.

1 Like

There’s a fix for blink.sh already please follow this to get yours up to date @JG20
https://we.incognito.org/t/recent-node-updates-docker-hub-api-v2/17533/10

@Rocky - I tried to run that before but it returns:

-f: line 1: "rm: command not found

What am I doing wrong?