-
Notifications
You must be signed in to change notification settings - Fork 4
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
Skaled should be started by skaleadmin first #942
Closed
kladkogex opened this issue
Apr 25, 2023
· 4 comments
· Fixed by skalenetwork/predeployed-generator#84, skalenetwork/marionette#380, skalenetwork/marionette#381, skalenetwork/etherbase#337 or skalenetwork/etherbase#338
Closed
Skaled should be started by skaleadmin first #942
kladkogex opened this issue
Apr 25, 2023
· 4 comments
· Fixed by skalenetwork/predeployed-generator#84, skalenetwork/marionette#380, skalenetwork/marionette#381, skalenetwork/etherbase#337 or skalenetwork/etherbase#338
Comments
Scope 2.2 for this ticket:
|
DmytroNazarenko
added
enhancement
New feature or request
and removed
bug
Something isn't working
labels
May 2, 2023
github-project-automation
bot
moved this from In Progress
to Ready For Release Candidate
in SKALE Engineering 🚀
Jun 13, 2023
This was referenced Jun 13, 2023
This was referenced Jun 13, 2023
badrogger
moved this from Ready For Release Candidate
to Code Review
in SKALE Engineering 🚀
Jun 19, 2023
Merged
DmytroNazarenko
moved this from Code Review
to Ready For Release Candidate
in SKALE Engineering 🚀
Jun 20, 2023
Merged
Merged
skale-manager: 1.9.4-beta.0 |
DmytroNazarenko
moved this from Ready For Release Candidate
to Merged To Release Candidate
in SKALE Engineering 🚀
Jun 21, 2023
Checked ✅
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Currently there are cases where failed DKG can prevent skaled from start.
Expected behavior
Skaled needs to run nomatter what happens to to DKG
One way to to do it is to handle skaled first when skaledadmin starts.
Cleaner way is to have a separate skaled restart agent (may be systemd or similar)
and have skale-admin talk to this agent
The text was updated successfully, but these errors were encountered: