Skip to content

Latest commit doesn't start the nodes #10

@stormeye2000

Description

@stormeye2000

Running on a EC2 Ubuntu instance and in a Docker Debian image
Running against node release-1.5.6

The current main branch builds and compiles ok
But the nodes are all showing exited when viewing the status
Also errors in the error log:

Screenshot 2024-04-11 at 21 41 07

The error shown is:

Error: decoding from TOML error: data did not match any variant of untagged enum ActivationPoint for key protocol.activation_point at line 316 column 1

Caused by:
data did not match any variant of untagged enum ActivationPoint for key protocol.activation_point at line 316 column 1
Error: "/home/ubuntu/cctl-local-build/cctl/assets/nodes/node-1/bin/1_0_0/casper-node" "validator" "/home/ubuntu/cctl-local-build/cctl/assets/nodes/node-1/config/1_0_0/config.toml" exited with error

When I reset the CCTL git branch locally and rebuild it works as expected:
git reset --hard ac3a941b3d6170027fd175d39fb708ce9c794369

Screenshot 2024-04-12 at 10 08 17

SHA ac3a941 is from Feb 22 and is the commit I built CCTL Docker images for the Terminus tests

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions