doc: add example error message when creating DB after starting systemd service #485
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.
Problem
The flux-accounting service depends on the creation of the flux-accounting DB before starting since it needs to establish a connection to the DB in order to run
flux account
commands. If this is done out of order, confusing behavior can result from running the commands, such as anattempt to write to a readonly database
error.This PR just adds a note to the flux-accounting guide about making sure the flux-accounting DB has been created before starting the flux-accounting service and gives an example of the error message that can potentially occur.