-
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
[Windows] fluent-bit keep deleted files #2133
Comments
I have the same issue. |
@farcop Hmm. I spent some time this evening trying to reproduce your AFAICT when we remove a file on NTFS, Windows actually moves the file In fact, I could perform "delete & create" operation to a file being
... That being said, while I'm unable to reproduce the issue myself, This adds an explicit check for DeletePending to I'd appreciate if you could test this patch and see if it solves your problem. |
@fujimotos patched files from this build https://ci.appveyor.com/project/fluent/fluent-bit-2e87g/build/job/y2vhal6w4lwsdddi/artifacts Fluent-bit was started and works for a while
del events.log
echo aiueo > events.log
Thank you so much! |
fixed in #2141 |
Hello, i'm with the same error when fluent-bit 2.1.2 is in different server, reading *.json files from an network share, on Windows. |
Environment:
Windows Server 2016 Stardard
Fluent Bit v1.4.2 started with winsw wrapper
Input configuration:
As is:
If we'll try to delete file D:\temp\events.log for example with Powershell
Remove-Item -Force -LiteralPath D:\temp\events.log
or with Shift+Del hotkeys, then file marked DeletePending: True, but file does not actually get removed from the file system.
Anybody that tries to open the file after that gets an Access denied error.
Fluent-bit continues to query information about file and nothing writes to log.
After Fluent-bit stops file D:\temp\events.log deletes from file system.
As expected:
After file was marked DeletePending: True, fluent-bit release it and give a chance to delete file from file system.
The text was updated successfully, but these errors were encountered: