-
Notifications
You must be signed in to change notification settings - Fork 525
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
Starting APM Server with -environment container fails #3576
Labels
Comments
simitt
added a commit
to simitt/apm-server
that referenced
this issue
Mar 30, 2020
Ensure logging overwrites do not fail startup when passing in -environment option fixes elastic#3576
simitt
added a commit
that referenced
this issue
Mar 31, 2020
Ensure logging overwrites do not fail startup when passing in -environment option fixes #3576
simitt
added a commit
to simitt/apm-server
that referenced
this issue
Mar 31, 2020
Ensure logging overwrites do not fail startup when passing in -environment option fixes elastic#3576
simitt
added a commit
to simitt/apm-server
that referenced
this issue
Mar 31, 2020
Ensure logging overwrites do not fail startup when passing in -environment option fixes elastic#3576
simitt
added a commit
that referenced
this issue
Mar 31, 2020
simitt
added a commit
that referenced
this issue
Mar 31, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version:
>= 7.7
branchWith introducing CLI flag -environment a new default value for logging to stdout/stderr was introduced. The new defaultToStderrConfig fails on decoding because the
Files.FileConfig.MaxSize
defaults to the zero value of0
, which conflicts with the required minimum value of1
.This only concerns the APM Server as we overwrite
logging
defaults, leading to encodinglogging.file
to the zero value.cc @kuisathaverat
How to reproduce:
apm-server -environment container
The text was updated successfully, but these errors were encountered: