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

Fix restart_indy_node under supervisord #1585

Conversation

smithbk
Copy link

@smithbk smithbk commented Feb 18, 2020

After the indy_node_control process downloads a new version of software, it invokes /usr/local/bin/restart_indy_node which then invoked supervisorctl restart indy-node-control. Unfortunately this command is not atomic and is equivalent to supervisorctl stop indy-node-control followed by supervisorctl start indy-node-control, which results in NOT restarting indy-node-control because it has just stopped itself.

The fix is for indy-node-control to simply commit suicide so that supervisord will automatically restart the process; that is, from a supervisorctl perspective, we do not change the state of the indy-node-control service.

Signed-off-by: Keith Smith bksmith@us.ibm.com

…ervisord, we must kill the process. Restarting indy_node_control from a script started by indy_node_control itself causes a hang.

Signed-off-by: Keith Smith <bksmith@us.ibm.com>
@sovbot
Copy link

sovbot commented Feb 18, 2020

Can one of the admins verify this patch?

@ashcherbakov
Copy link
Contributor

(ci) test this please

@ashcherbakov ashcherbakov merged commit 0063d46 into hyperledger:master Mar 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants