Closed brenzi closed 4 years ago
this happened 4 out of 5 times...
Thanks @brenzi, apologies from our end, and really appreciate your continued feedback on this issue :)
Given the numbers you've reported here it looks more like this might have been a side-effect of something we've recently changed. I'm going to prioritise finding a solution
hmm, I just realized that my telemetry option doesn't specify a verbosity level. might cause trouble at startup....
yeah, guess that was it. Would be good to forward node log to the user for quicker debug....
nope, was just good luck. the same still happens
I've just pushed a new version of gantree-cli@0.8.5.
This now checks for the RPC port to be ready before considering the substrate service to have been started. I'm not able to reproduce the issue currently so I wasn't able to confirm that this change had an effect, but if it is indeed a race condition on the RPC port becoming available I suspect this will fix it
Marking this resolved due to inactivity.
@brenzi please let us know if this is still occuring and we'll reopen this issue.
on second try it worked