flux-perilog-run: improve usefulness of logging when prolog/epilog fails #4054
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.
When attempting to set up prolog/epilog support on a system, it was discovered that errors from remote prolog/epilog execution were being copied to the logs without an identifying rank or hostname, which made diagnosis of errors unnecessarily difficult.
This PR improves the logging of the
flux perilog-run
script when used to execute per-rankprolog
andepilog
by including the rank and hostname in any lines of stderr generated by these scripts, along with other small improvements.