Node
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
|
Multiple nodes on the same IP address
If you are running multiple nodes on the same external IP address you might have problems connecting. Such a situation can happen if you are running multiple nodes in the same apartment, office, or a similar local networ… |
|
2 | 168 | May 26, 2021 |
|
If you cannot see the bakerID on the network dashboard
If you cannot see your bakerID on the network dashboard, try the following. Query NodeInfo to check that you are indeed baking: Windows: concordium-client.exe raw GetNodeInfo *nix/macOS: ./concordium-client raw GetNo… |
|
2 | 145 | May 18, 2021 |
|
Node not appearing on network dashboard
It is possible that your node is running fine without appearing on the dashboard. Run consensus status and then compare the finalized height and the best block height to the ones on the dashboard. If they are the same,… |
|
2 | 194 | June 15, 2021 |
|
Docker error port already in use
The node may fail starting with the error Error starting {..} proxy: listen tcp 0.0.0.0:{PORT}: bind: address already in use which can be remedied by using a different {PORT} than the default used by the node. The por… |
|
2 | 97 | May 17, 2021 |
|
Node does not catch up with chain on Windows
On Windows, the Concordium node may fail to catch up with the chain when changing internet connections. It usually catches up with the chain again after few minutes. Otherwise, stop and restart the node. Failure to catc… |
|
2 | 108 | May 17, 2021 |
|
Appearance of high memory consumption of the node
The Concordium node may appear to use a lot of memory, and its memory consumption may grow over time. This happens because the node internally uses the LMDB database for block and transaction storage. LMDB manages the da… |
|
2 | 87 | May 17, 2021 |
|
Multiple nodes, bakers, and accounts
The current distribution does not support running more than one node on the same machine. When the concordium-node tool is run, while another node is already running, it will ask you if you want to stop the currently run… |
|
2 | 110 | May 17, 2021 |
|
Discussions and issues pertaining to running a node
|
|
1 | 106 | May 17, 2021 |
|
Configuration baker keys on ubuntu
|
|
3 | 32 | January 20, 2022 |
|
Nodes gets a new external IP, and then fails
|
|
9 | 60 | January 17, 2022 |
|
What to do if node has a block difference?
|
|
8 | 65 | January 15, 2022 |
|
Baking and Payment
|
|
3 | 77 | January 14, 2022 |
|
How to maintain the node that is currently the Baker?
|
|
2 | 200 | January 5, 2022 |
|
Are there any experiences with running a node on ARM?
|
|
1 | 37 | January 4, 2022 |
|
How to acquire GTU to start baking on Mainnet
|
|
5 | 165 | December 23, 2021 |
|
Incorrect block state hash for genesis blocks
|
|
1 | 57 | September 20, 2021 |
|
How to monitor Concordium blockchain and what events?
|
|
1 | 180 | August 10, 2021 |
|
Static IP Address for Baker Node?
|
|
2 | 108 | June 30, 2021 |
|
Node successfully set up - however never got the prompt to define a "Node Name"
|
|
3 | 184 | June 19, 2021 |
|
Optimal hardware to run a baker node
|
|
3 | 149 | June 14, 2021 |
|
How do I become a Baker?
|
|
3 | 154 | June 11, 2021 |
|
Debian package issue
|
|
1 | 132 | June 10, 2021 |