Lost scheduled block

I am currently on 8.7.3 of the cardano binary, do I need to be 8.9 to mint blocks succesfully?

Was scheduled here but didn’t go through.

 SlotNo                          UTC Time              

 127102115                   2024-06-17 23:53:26 UTC

I think this is the latest version right?

Where can I download the binaries for this?

I believe the new binary is here?

https://github.com/IntersectMBO/cardano-node/releases/download/8.9.3/cardano-node-8.9.3-linux.tar.gz

I assume I need to update all my config files?

— UPDATE

So I had to do a lot of work to get this over to 8.9.3 but so far I think I might have it working, at least it launches now. For those that are interested, here is my docker file.

FROM ubuntu:20.04

# DEFINE THE PREFERRED STOP SIGNAL
STOPSIGNAL SIGINT

ENV DEBIAN_FRONTEND=noninteractive

# Install necessary packages in a single RUN command
RUN apt-get update && \
    apt-get install -y zip wget automake build-essential pkg-config libffi-dev libgmp-dev libssl-dev libtinfo-dev \
    libsystemd-dev zlib1g-dev make g++ tmux git jq curl libncursesw5 libtool autoconf llvm libnuma-dev tar gzip \
    netbase lsof bc python3-pip nodejs npm

# Set working directory
WORKDIR /home/cardano

# Download and extract cardano-node
RUN mkdir -p /home/cardano/bin && \
    wget -O cardano-node-8.9.3.tar.gz https://github.com/IntersectMBO/cardano-node/releases/download/8.9.3/cardano-node-8.9.3-linux.tar.gz && \
    tar -xvf cardano-node-8.9.3.tar.gz -C /home/cardano && \
    rm cardano-node-8.9.3.tar.gz && \
    chmod +x /home/cardano/bin/cardano-node /home/cardano/bin/cardano-cli

# Ensure cardano-node is in the PATH
ENV PATH="/home/cardano/bin:$PATH"

# Set up the working directory for the database
WORKDIR /home/cardano/tts-pool/db

# Set the start directory to the scripts location
WORKDIR /home/cardano/tts-pool/scripts

# Download gLiveView scripts
RUN wget https://raw.githubusercontent.com/cardano-community/guild-operators/master/scripts/cnode-helper-scripts/env && \
    wget https://raw.githubusercontent.com/cardano-community/guild-operators/master/scripts/cnode-helper-scripts/gLiveView.sh && \
    chmod +x env gLiveView.sh

# Copy the run.sh script
COPY /files/run.sh /home/cardano/tts-pool/scripts

# Healthcheck
HEALTHCHECK --interval=10s --timeout=60s --start-period=300s --retries=3 CMD sh /home/cardano/tts-pool/healthcheck.sh

# Set the default command
CMD ["/home/cardano/tts-pool/scripts/run.sh"]

I’m going to make a complete tutorial series how I did this so I can get your reviews later and to help other stake pool operators.

So my only question now is I noticed we have a new topology file, will my old one still work, I’m not going to paste it here for security reasons, but the only difference is the new one looks like this

{
  "bootstrapPeers": [
    {
      "address": "backbone.cardano.iog.io",
      "port": 3001
    },
    {
      "address": "backbone.mainnet.emurgornd.com",
      "port": 3001
    },
    {
      "address": "backbone.mainnet.cardanofoundation.org",
      "port": 3001
    }
  ],
  "localRoots": [
    {
      "accessPoints": [],
      "advertise": false,
      "trustable": false,
      "valency": 1
    }
  ],
  "publicRoots": [
    {
      "accessPoints": [],
      "advertise": false
    }
  ],
  "useLedgerAfterSlot": 116812831
}

It appears they added bootstrapPeers, what does this do and how is it different from the old method with publicRoots? I am going to assume it’s just a way to get the blocks starting out easier?

Good that you are doing the upgrade. It will be needed in a couple of weeks, anyway, but I really don’t think that that was the reason that you lost the block.

To see the reason, it’s probably more fruitful to look in the logs around the time the block was scheduled. Does the block producer show that it minted? Does it give a reason why it was discarded in favour of someone else’s block? Do your relays have incoming connections?

2 Likes

I think it might be the KES keys… I think I forgot to rotate them… insert curse words here haha, going to do that now… weird part is they didn’t expire technically until today though and the minted block to be was yesterday.

On a side note can I use an old version of cardano-cli on my air gap machine to sign the kes keys?

Anyhow just rotated the keys and booting up, takes forever, 2 hours for it to load up again (think validated chunk no.176 out of 5885…) and will let you know if it worked…