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 | 297 | 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 | 281 | 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 | 369 | 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 | 285 | 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 | 193 | 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 | 173 | 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 | 213 | May 17, 2021 |
|
Discussions and issues pertaining to running a node
|
|
1 | 196 | May 17, 2021 |
|
Issue finding node on dashboard after update
|
|
16 | 51 | August 17, 2022 |
|
Determine baker for next epoch
|
|
7 | 50 | July 28, 2022 |
|
4.2.1 node (docker) consistently runs behind roughly 70 blocks
|
|
6 | 49 | July 26, 2022 |
|
Cannot restart mainnet docker node
|
|
10 | 90 | July 11, 2022 |
|
Instructions for node uninstall
|
|
3 | 57 | July 1, 2022 |
|
Concordium-testnet-node.service: Failed with result 'exit-code'
|
|
1 | 45 | June 18, 2022 |
|
Getting this error > yarn build , -while trying SDK
|
|
2 | 66 | June 16, 2022 |
|
Place for database
|
|
1 | 70 | June 6, 2022 |
|
Please provider public a testnet rpc and mainnetrpc for developer
|
|
2 | 115 | June 6, 2022 |
|
Running multiple nodes with the same baker credentials
|
|
1 | 70 | May 16, 2022 |
|
Reason not to bake on initial account.?
|
|
2 | 77 | May 9, 2022 |
|
Unable to synchronize nodes
|
|
1 | 68 | May 8, 2022 |
|
Namespace spawning fails (Debian package)
|
|
0 | 91 | May 3, 2022 |
|
Instrumentation in concordium node 3.0.1 Debian package
|
|
2 | 81 | April 18, 2022 |
|
Failed to launch CCD node
|
|
4 | 131 | April 11, 2022 |
|
How to calculate bakingRewards from tx_logging db entry?
|
|
3 | 114 | April 11, 2022 |
|
Delegation reporting in concordium-client and node
|
|
1 | 88 | March 31, 2022 |
|
Accounts as 32-byte arrays
|
|
1 | 174 | March 22, 2022 |
|
About how the parameters of calling the contract function are passed
|
|
3 | 89 | March 21, 2022 |
|
Transaction logging check?
|
|
3 | 133 | March 21, 2022 |
|
No Baking Rewards since 9 Days but others with less power get rewards every 2nd day
|
|
11 | 205 | March 20, 2022 |
|
Copy node db from up to date node to fresh node
|
|
2 | 83 | April 11, 2022 |