Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exit if failed to start pool #17

Merged
merged 1 commit into from May 4, 2018

Conversation

Projects
None yet
2 participants
@funkypenguin
Copy link

commented May 3, 2018

New PR (old one was a mistake)

When bringing up the entire mining pool stack under Docker Swarm, the TurtleCoind daemon starts at the same time as all the other elements. However, TurtleCoind takes some time to be ready (syncing with the blockchain, etc), and if pool starts before daemon is ready (quite likely), it'll log an error about being unable to start, but will then just hang around being useless. I discovered this under my swarm when pool wouln't listen on its ports (i.e., 3333 etc) on first deploy, but if I killed and recreated it, it'd start listening as expected.

This change just forces the pool thread to exit (rather than return) if it's logged an error about failing to start, so that a replacement can be spawned.

@RocksteadyTC RocksteadyTC merged commit 7ebac75 into turtlecoin:master May 4, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.