capture sendmail output#923
Open
jnweiger wants to merge 1 commit into
Open
Conversation
and encode it into the Exception message.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Seen with checkmk 2.4.0p24 in appliance 1.7.17
When there is an error with sending an email, the return code of sendmail is captured, but no further diagnostics.
In my example, a reporting background job failed (due to a postfix missconfiguration) with this terse message in the logs and in the gui:
Scheduling report in background failed:With nothing after the colon.
Expected behaviour: Error messages from sendmail should propagate into logs and gui.
As one part of the fix, I suggest to capture stderr and stdout of sendmail.
This enables other parts of the code to pick up error messages and show them appropriately.