Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Without this wait, the rmm process fails to start on y291ga with the "Disabled cloud" option enabled. Fixes #670.
This feels more like a workaround rather than a fix though.
For some reasons, rmm fails to start if started without the wait.
Here you can find the output of rmm when started manually after the boot (after having disabled the WD's reboot) and the failed one when starting it within
system.sh
(without the wait).rmm_fail.txt
rmm_success.txt
I do not see anything obvious missing (for example, all the mounts are up), however
ps
shows that twosystem.sh
are running (captured just before the./rmm
command, without the wait):Is it expected?