Update windows fluent buffer configuration #299
Closed
Conversation
This file contains 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
buffer_path is a linux path on a Windows machine; removing it. buffer_type file is not used as well, given the invalid file path; removing it. buffer_chunk_limit of 512KB is breaking the Windows Event Log source. Resetting this back to 1M.
|
"2020-09-30 18:57:29 -0500 [info]: Worker 0 finished unexpectedly with signal SIGSEGV" is caused by the grpc not directly due to the buffer_chunk_limit. By changing it to Igor has a PR fixing the buffer_type file path: #282. Actually buffer path is used if you check your C:\var\log\google-fluentd\buffers folder, you shall find file there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
buffer_path is a linux path on a Windows machine; removing it.
buffer_type file is not used as well, given the invalid file path; removing it.
buffer_chunk_limit of 512KB is breaking the Windows Event Log source. Resetting this back to 1M.
For the record, the errors in the fluentd.log related to this issue are "2020-09-30 18:57:29 -0500 [info]: Worker 0 finished unexpectedly with signal SIGSEGV" and Windows logs never get sent up. For us, this is on Windows Server 2016 machines.