-
Notifications
You must be signed in to change notification settings - Fork 18
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
startup: preserve the database #203
Comments
hannesm
added a commit
that referenced
this issue
Feb 4, 2025
reynir
added a commit
that referenced
this issue
Feb 5, 2025
albatrossd: on startup, back up state file, fixes #203
hannesm
added a commit
to hannesm/opam-repository
that referenced
this issue
Feb 5, 2025
CHANGES: * albatross-daemon: on startup backup the state file (robur-coop/albatross#206 @hannesm, fixes robur-coop/albatross#203) * Add block size to info command, adapt types slightly (robur-coop/albatross#195 @hannesm) * Allow the arguments in restart to be changed (robur-coop/albatross#195 @hannesm) * Update to ocaml-solo5-elftool 0.4.0 - bump OCaml lower bound to 4.14 (robur-coop/albatross#207 @reynir, robur-coop/albatross#208) * BUGFIX: restart command kills the unikernel first (robur-coop/albatross#205 @reynir) * Print manifest on mismatch (robur-coop/albatross#196 @reynir) * Albatross-console: use physical equality for file descriptors (robur-coop/albatross#200 @reynir) * Albatross-console: allow multiple subscribers (robur-coop/albatross#194 @reynir)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There can be arbitrary complexity / stuff broken when starting albatross daemon:
This leads to albatross starting, but all unikernels failing to start --> sigabort or some other issue with solo5-hvt dumping core. A fix of the system is good, but won't bring us back the unikernels <--> manual intervention needed.
It would be great to first copy the "albatross.state" to a "albatross.state.started" backup file, so we can recover (manually) from such failures, without needing to deal with each unikernel individually.
The text was updated successfully, but these errors were encountered: