Concordium / Concordium/concordium-node

Validator 9 - special case

Open
#1,291 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Haskell
Stars
108
Forks
24
Avg merge
2d 4h
Merged PRs (30d)
9

Description

**VM name:** [ubuntu@172.31.48.48](mailto:ubuntu@172.31.48.48)

- [ ] Set the node version 8.x up for Stagenet, enable debug logs.
- [ ] Setup Prometheus with `CONCORDIUM_NODE_PROMETHEUS_LISTEN_PORT=9090` and also I think `CONCORDIUM_NODE_PROMETHEUS_LISTEN_ADDRESS=0.0.0.0`
- [ ] Start the node and start to catch up
- [ ] Make sure that the node is still catching up while PU is going to be in effect
- [ ] **WAIT FOR PROTOCOL UPDATE**
- [ ] After protocol update verify:
- [ ] Node is still catching up
- [ ] No errors in the logs

Contributor guide

Open the contributing guide

Research direction

Use the listed VM and configure the node for Stagenet with debug logging and the two Prometheus environment variables. Start the node, observe catch-up through the protocol update, and review its logs afterward. Done means the node remains catching up and no errors appear after the update.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell, prometheus
Domain
blockchain, observability, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.