Closed brenzi closed 4 years ago
Hey @brenzi - try removing the space from the project name (make it encointer-testnet
). You will first have to clean your infrastructure otherwise the ssh keys will conflict on DigitalOcean.
This should work for now - I'll ensure that this is patched so as not to allow names with spaces in future.
didn't help. Still the same issue
In this case I might have patched something already which is allowing it to succeed on my latest version and not the release.
I'll ping you when we have a release ready to test - otherwise you will have to try the latest dev with a config file which looks like this (note the slight namespace changes):
{
"project": "encointer-testnet",
"binary": {
"repository": "https://github.com/encointer/encointer-node",
"name": "encointer-node"
},
"validators": {
"loggingFilter": "runtime=debug,txpool=debug",
"telemetry": true,
"nodes": [
{
"provider": "do",
"machineType": "s-2vcpu-4gb",
"count": 3,
"zone": "fra1",
"sshUser": "root"
}
]
}
}
The other way to get a crash report for me to look into would be to ssh into the machine which is failing and run:
journalctl --unit substrate.service --lines 500 -f
Then see if you can find the relevant lines which say why the substrate binary is not executing.
@brenzi are you still experiencing this issue with the latest release?
If so, please provide us with output from the node as mentioned by @morelazers above.
This issue occurs when Ansible cannot communicate with the deployed binary as the binary has crashed.
@brenzi do you still have this issue in the latest version? At the time of this comment the latest version is v0.6.6.
You can check both your cli + lib version at once with the cli (gantree-cli --version
)
$ gantree-cli --version
gantree-cli 0.8.4
⮡ gantree-lib 0.6.6
I'm trying to deploy https://github.com/encointer/encointer-node
with config
building works, but here it fails: