alpha
1
Hi:
I m new to this, I m currently follow your toturial , I met a problem after type:
./bin/epoch check_config epoch.yaml
I got the error as followed:
Configuration error ({yamerl_exception,
[{yamerl_parsing_error,error,
"Block mapping value not allowed here",13,13,
block_mapping_value_not_allowed,undefined,[]}]})
I double checked the epoch.yaml I created , all the content I wrote seemed correct.
Any ideas?
I m running on Ubuntu 18.04
THANKS
alpha
2
Can someone post one correct format yaml template ? so I can make sure no problems of content
Hey @alpha,
We’ve forwarded your question to the dev team and they’ll get back to you as soon as possible.
Regards,
Albena
Hi @alpha,
which release are you using? 0.25.0?
alpha
5
Yes , I m using the 0.25 release
Here is the example of config yaml (see aeternity/installation.md at master · aeternity/aeternity · GitHub):
sync:
port: 3115
external_port: 3015
keys:
dir: keys
peer_password: "secret"
http:
external:
port: 3013
internal:
port: 3113
websocket:
channel:
port: 3014
mining:
beneficiary: "beneficiary_pubkey_to_be_replaced"
autostart: true
chain:
persist: true
db_path: ./my_db
Once you replace "beneficiary_pubkey_to_be_replaced"
with the public key that you have generated for your account, the yaml validation should give OK.
2 Likes
alpha
7
Thanks ! That works, I have one more question
after I queried my reward , it shows {“reason”:“Account not found”} that means I have 0 in my count ? or it’s an error ?
jay
8
It’s the expected behavior if your account is never do any transaction on the chain before
3 Likes
Sure!
Regarding the config file, check this document with detailed info on the config parameters.
2 Likes
alpha
10
Thanks for helping me out !
1 Like