-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Fluent Bit encountering errors after detecting log files in FSx file shares on Windows Server 2019 (v2.0.9) #7220
Comments
@leonardo-albertovich @cosmo0920 this is an issue reported at KubeCon, can you take a loop pls ? cc: @afishler |
It seems like we might have a problem in I'll try to reproduce it with a UNC path in my local network and go from there. |
Great, I did notice that I was incorrect and logs are being sent to our end point despite the errors. So this is more so an annoyance with the errors vs not working entirely it seems. |
@leonardo-albertovich @edsiper Any chance of an update here? The errors do flood our logs quite a bit. |
Sorry @evolart, I've been swamped and haven't been able to put any time on this so far and can't foresee anyone from the team being able to dedicate time to it in within this week either. I have this one on my queue and intend to give it closure but I'd be lying if I offered an ETA. |
Hi @leonardo-albertovich any chance of update on ETA. We have the same problem with the logs flooded with the error messages but the logs successfully streaming. Thanks!! |
I'm wrapping up a set of changes that could potentially fix this as a side effect, I'll send an update by the end of the week with a link to the PR and would really appreciate it if tested it and helped with feedback so we can include that fix in the PR (if it doesn't address it). |
As promised, this is the PR with the new file access abstraction layer #7564 Keep in mind that even though the code is complete and it was internally tested there is still a discussion and we might make changes so it would be good if you managed to test it and give us some feedback. I have just started the test container creation process so if everything works as expected (and I can't see any reasons for it not to) there should be container images container images here ghcr.io/fluent/fluent-bit/test/leonardo-master-filesystem-access-abstraction-layer Although I haven't ever used windows containers so I have no idea of how that works so you might be better off getting the build artifacts from appveyor or building fluent-bit yourself. |
Thank you @leonardo-albertovich will check on this pr and see if we can find a way to build a windows version. |
@leonardo-albertovich tried to generate windows build on this branch but failed on "C:\fluent-bit\include\fluent-bit/flb_hmac.h(22): fatal error C1083: Cannot open include file: 'openssl/err.h': No such file or directory" . Any ideas? |
You need to specify the place for installed/compiled OpenSSL directory. We use OpenSSL installer from chocotaley. Also, you can install it from https://slproweb.com/products/Win32OpenSSL.html. And then, specifying the place with fluent-bit/.github/workflows/call-build-windows.yaml Lines 113 to 143 in 9ecb8b6
Also, if you want to create the installers, you have to install WiX toolset or NSIS. |
Hi @leonardo-albertovich @cosmo0920 I Just tested the branch and found the results to be same as before.
config file:
STDOUT:
|
Thanks for reporting your results, we will take a look as soon as possible. One thing that confuses me in your log though is that the error message reports the source line as 1513 whereas in the code line 1513 is not a |
Hi @leonardo-albertovich I pulled the branch again and tested. Looks like the earlier test I did probably is against master branch. Here are the results :
Log:
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the |
hey guys |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the |
This issue was closed because it has been stalled for 5 days with no activity. |
Hi All, Just wondering if previous issue has been resolved. [2024/07/03 22:42:17] [debug] [input:tail:tail.0] 1 new files found on path 'Z:\My Docs\Log_7_4_2024.txt' |
This is a continuation from #7185. Original file paths and other environment details/metadata has been stripped.
Problem:
After resolving the issue of Fluent Bit not detecting log files in FSx file shares on Windows Server 2019, we are now encountering errors when adding log files to bulk ingestion. It's worth noting that the message lines with "adding log to the bulk" show the file path with the backslashes escaped out. We had to remove the backslash escaping from our INPUT stanza to get Fluent Bit to detect the log files in the first place.
Environment:
\\fsx-example-host.example.net\share\staging\if\dir\example-server\Logs
Steps to Reproduce:
Configure Fluent Bit with the following input stanza:
Start Fluent Bit with trace log level.
Create or modify log files in the specified FSx file share path.
Observe that Fluent Bit does detect log files but begins throwing errors:
Expected Behavior
Fluent Bit should detect and send logs to output without errors.
Actual Behavior
Fluent Bit does detect file changes in FSx file shares on Windows Server 2019 but throws many errors.
Additional Context
We have validated that the FSx file share path is accessible from the Windows Server 2019 system, and we are able to read the content of the files without any issues.
Please let me know if you need any further information or if there are any workarounds or solutions to this issue.
The text was updated successfully, but these errors were encountered: