Not sure where they want this reported. I’m experiencing this inside the recent docker image with a hard node crash. (Around a random block) A restart “fixes” the issue but it’ll die on random blocks after a couple of minutes.
Ah I see that. Since this is in a docker container, it doesn’t seem to update properly:
root@685172a807f8:~/node# ./update.sh -d data
Current Version = 131083
Latest Version = 131088
New version found
Update Downloaded to /tmp/tmp.hOLqMDXk95/131088.tar.gz
Expanding update...
Validating update...
Starting the new update script to complete the installation...
... Resuming installation from the latest update script
Current Version = 131083
Stopping node...
... node not running
Backing up current binary files...
Backing up current data files from /root/node/data...
Installing new binary files...
Installing new data files into /root/node/data...
Copying genesis files locally
Checking for new ledger in /root/node/data
Updating genesis files for network testnet
Applying migration fixups...
Deleting existing log files in /root/node/data
Starting node in /root/node/data...
/tmp/tmp.hOLqMDXk95/a/bin/update.sh: line 393: systemd-escape: command not found
/tmp/tmp.hOLqMDXk95/a/bin/update.sh: line 393: sudo: command not found
Algorand node failed to start: node exited before we could contact it