Skip to content
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

Don't close stderr under --quiet #49431

Merged

Conversation

pugnascotia
Copy link
Contributor

Backport of #47208.

Closes #46900. When running ES with --quiet, if ES then exits abnormally, a
user has to go hunting in the logs for the error. Instead, never close
System.err, and print more information to it if ES encounters a fatal error
e.g. config validation, or some fatal runtime exception. This is useful when
running under e.g. systemd, since the error will go into the journal.

Note that stderr is still closed in daemon (-d) mode.

Closes elastic#46900. When running ES with `--quiet`, if ES then exits abnormally, a
user has to go hunting in the logs for the error. Instead, never close
System.err, and print more information to it if ES encounters a fatal error
e.g. config validation, or some fatal runtime exception. This is useful when
running under e.g. systemd, since the error will go into the journal.

Note that stderr is still closed in daemon (`-d`) mode.
@pugnascotia pugnascotia added :Core/Infra/Core Core issues without another label backport v7.6.0 labels Nov 21, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (:Core/Infra/Core)

@pugnascotia pugnascotia changed the title Don't close stderr under --quiet Don't close stderr under --quiet Nov 22, 2019
@pugnascotia pugnascotia merged commit 4fae2bb into elastic:7.x Nov 22, 2019
@pugnascotia pugnascotia deleted the 46900-stderr-open-print-logs-location-7x branch November 22, 2019 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport :Core/Infra/Core Core issues without another label v7.6.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants