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 | 394 | 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 | 388 | 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 | 449 | 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 | 416 | 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 | 256 | 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 | 245 | 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 | 265 | May 17, 2021 |
|
Discussions and issues pertaining to running a node
|
|
1 | 263 | May 17, 2021 |
|
Sudden drop in rewards
|
|
8 | 61 | March 16, 2023 |
|
Concordium GRPCv2 API Upgrading Issues
|
|
5 | 49 | March 9, 2023 |
|
Using a mainnet node on a server that already has a testnet
|
|
2 | 38 | February 28, 2023 |
|
Module name in GRPCv2?
|
|
3 | 33 | February 12, 2023 |
|
Starting node on the main network
|
|
12 | 73 | February 11, 2023 |
|
Node Setup on Mac Studio
|
|
1 | 29 | January 23, 2023 |
|
Can we use the ID layer from private chain?
|
|
5 | 57 | January 19, 2023 |
|
Transaction logging does not work for now?
|
|
3 | 54 | January 17, 2023 |
|
Backup and Availability
|
|
2 | 50 | January 15, 2023 |
|
Node falling behind with extensive querying
|
|
8 | 75 | January 10, 2023 |
|
How start a distributed systems as Concordium from scratch?
|
|
6 | 65 | January 4, 2023 |
|
Impact of load on baker performance
|
|
5 | 84 | December 24, 2022 |
|
Docker node does not finish loading the blocks
|
|
2 | 54 | November 28, 2022 |
|
How to change default data directory of rpc node
|
|
2 | 61 | November 22, 2022 |
|
Multiple nodes for same baker
|
|
3 | 86 | November 15, 2022 |
|
Nodejs sdk, company identity and client infos
|
|
26 | 416 | October 18, 2022 |
|
Baker commissions
|
|
4 | 140 | October 10, 2022 |
|
I cannot see the Node's name on the network dashboard
|
|
8 | 143 | September 28, 2022 |
|
BlockTooEarly/InvalidResult Testnet node stuck
|
|
4 | 120 | September 26, 2022 |
|
Node isn't running properly
|
|
8 | 110 | September 13, 2022 |
|
Node stops after powerfailure
|
|
1 | 112 | August 29, 2022 |
|
Moving node to another system
|
|
1 | 113 | August 23, 2022 |