I moved our stake pool LOXE to 1.35.3 (git rev 80b5637a5520648d50b0763d7677ddbe374cd598) on August 20th and it was producing blocks regularly. I noticed yesterday that our block producer was up as a slot leader, but the block was not adopted by the chain. Only later did I realize that our pool was stuck in Alonzo at the last block of epoch 364 (7791698).
I stopped the nodes and deleted some recent files from the db, fo force replaying of blocks on restart with no difference.
I complied cardano-node and cardano-cli - this time from commit ea6d78c7 - transferred the binaries and configs to my nodes and compiled the libsodium on the nodes as well. I changed the topology on the relays to just connect to the IOHK servers for the moment to try and just sync up, but I’m still getting nowhere with it.
Attached is a view from my journalctl from the relay in question.
cardano-node: decodeTelescope: invalid telescope length
CallStack (from HasCallStack):
error, called at src/Ouroboros/Consensus/HardFork/Combinator/Serialisation/Common.hs:443:27 in ouroboros-consensus-0.1.0.0-6Kpqbym2b1s1arV4kigRIW:Ouroboros.Consensus.HardFork.Combinator.Serialisation.Common[
Since IO’s shipped binaries (80b5637a5520648d50b0763d7677ddbe374cd598) ceased to work, I’m compiling the binaries on my kvm host machine and pull it via scp into my kvm clients, so there’s no rust build machinery there, thus a .cargo directory would be absent. Of course, I had to install some build tools on the kvm clients after all for the shared libraries (libsodium namely).
I downloaded the snapshot, but after running into the telescope length error, I’ve removed files that fall within the last few days (epoch 365). My nodes are still replaying the blocks.