Check if you are baking

[concordium-cl]

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 GetNodeInfo

Try the following workaround:
Make sure that the generated keys file (baker-credentials.json) is located in your concordium-data directory on the machine where the node is running. It should be under ~/.local/share/concordium on *nix and %LOCALAPPDATA%\concordium on Windows. Do not rename the file. Then restart the node.

[fotslen1]

You just need to make sure that the baker-credentials.json file is there? He is there. Restarting didn't help.

[andrste]

You just need to make sure that the baker-credentials.json file is there? He is there. Restarting didn't help.

Let me be clear, have you indicated correctly <concordium-data-dir>?

If NOT I will give you steps which helped me.

If YES (Who will be reading this issue), just restart your node by running this command on your concordium client ./concordium-node-stop

What helped to me:

1. Added new account to Concordium ID app
2. Exported account file from Concordium ID to my Concordium node.
3. On Concordium client I removed that account from which I was baking
4. Imported new account to Concordium client
5. One of the important steps is add baker command see below.

Key thing is with command:

<concordium-data-dir> - must be replaced with directory:

• on Linux and MacOS: ~/.local/share/concordium
• on Windows: %LOCALAPPDATA%\\concordium

Example if you are using MacOS or Linux your command would look like this:

./concordium-client baker add generated_keys.json --sender YOURACC --stake 1000 --out ~/.local/share/concordium/baker-credentials.json

Example if you are using Windows your command would look like this:

./concordium-client baker add generated_keys.json --sender YOURACC --stake 1000 --out %LOCALAPPDATA%\\concordium\baker-credentials.json

5. Important step!!! Reboot your node just by running command: ./concordium-node-stop

I hope it will help!

[fotslen1]

Thank you, everything worked out.24.01.2021, 13:01, "andrste" <[email protected]>: You just need to make sure that the baker-credentials.json file is there? He is there. Restarting didn't help. Let me be clear, have you indicated correctly <concordium-data-dir>? If not I will give you steps which helped me. What helped to me: Added new account to Concordium ID app Exported account file from Concordium ID to my Concordium node. On Concordium client I removed that account from which I was baking Imported new account to Concordium client One of the important steps is add baker command see below. Key thing is with command: <concordium-data-dir> - must be replaced with directory: on Linux and MacOS: ~/.local/share/concordium on Windows: %LOCALAPPDATA%\\concordium Example if you are using MacOS or Linux your command would look like this: ./concordium-client baker add generated_keys.json --sender YOURACC --stake 1000 --out ~/.local/share/concordium/baker-credentials.json Example if you are using Windows your command would look like this: ./concordium-client baker add generated_keys.json --sender YOURACC --stake 1000 --out %LOCALAPPDATA%\\concordium\baker-credentials.json Important step!!! Reboot your node just by running command: ./concordium-node-stop I hope it will help! —You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.