-
Notifications
You must be signed in to change notification settings - Fork 487
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
Temporary Files Accumulating in /tmp Folder After Starting AppSec #3055
Comments
@TokuiNico: Thanks for opening an issue, it is currently awaiting triage. In the meantime, you can:
DetailsI am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository. |
Hello! I also stumbled on this issue and it's actually a "bug" in coraza. I reported it to them and it's fixed but will be released in version 3.2 corazawaf/coraza#922 (comment) My hotfix for this is to run a scheduled cron once a day to cleanup.
|
Thank you for your help. I will apply hotfix first. |
Coraza is now at v3.3.2 and this issue has been fixed with v3.2.0 👀 |
I'm still having this issue on the latest release of crowdsec. How do I update Coraza? |
That's because the issue is still "open" it means it not fixed within CrowdSec yet. We control a fork of Coraza that we need to update to latest as we merged our own fixes and then push them upstream. |
Makes sense, sorry for the misunderstanding. I'll apply the hotfix for now |
All good 👍🏻 we aim to bump the our own fork dependancy for |
Using v1.6.5-rc1 doesn't seem to fix this issue for me. Can someone confirm this? |
Looking at the release notes, the coraza dependency bump was introduced after RC1 was made, so RC2 will include the fix. |
What happened?
I started to use AppSec component 1 month ago and everything went well.
However, I found After starting AppSec, the /tmp folder will quickly increase with a large number of files, the file names will be in a format like
crzmp1015053877
.In less than an hour, there will be an increase of over 200 MB of temporary files.
What are these files? Is there any way to remove them?
Thanks
What did you expect to happen?
I expected the AppSec component to run without generating a large number of temporary files in the /tmp folder.
How can we reproduce it (as minimally and precisely as possible)?
crzmp[digits]
.Anything else we need to know?
No response
Crowdsec version
OS version
Enabled collections and parsers
Acquisition config
Config show
Prometheus metrics
Related custom configs versions (if applicable) : notification plugins, custom scenarios, parsers etc.
The text was updated successfully, but these errors were encountered: