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

gluon-quickfix: don't reboot on missing dropbear or respondd #27

Open
rubo77 opened this issue Jul 25, 2017 · 1 comment
Open

gluon-quickfix: don't reboot on missing dropbear or respondd #27

rubo77 opened this issue Jul 25, 2017 · 1 comment

Comments

@rubo77
Copy link
Collaborator

rubo77 commented Jul 25, 2017

adorfer:

If for example respondd or dropbear is not present, i do not want an instant reboot.
for example if somebody is just restarting dropbear or respondd just that very moment during the check, the node would then reboot instantly.

this is already fixed in

https://github.com/eulenfunk/packages/blob/v2016.2.x/gluon-quickfix/files/lib/gluon/quickfix/quickfix.sh#L52

but still a reboot is not needed then, a restart or restart/stop&start would be enough

@Adorfer
Copy link
Member

Adorfer commented Oct 19, 2017

a non running respondd or dropbear is something that is a clear indicator for a stumbling node. The service does not end itself out of clear sky. if this happens, a reboot is the safest exit road.

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

No branches or pull requests

2 participants