-
-
Notifications
You must be signed in to change notification settings - Fork 231
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
/tmp "crzmp*" never deleted after a POST #922
Comments
Totally. Do you mind coming up with a PR fixing it? |
Hi, |
thnaks :o) |
@jcchavezs @jptosso What is the status of this one? Currently our servers are running out of space since these are never deleted. |
Hey! This was fixed long time ago in #924 Can you upgrade and try again ? |
Hm ok, im using https://docs.crowdsec.net/docs/next/appsec/intro which should be using Coraza as engine for processing SecLang rules. Maybe its a bug at their end. On another note, do you know if these files are also created by coraza "body999644643"? |
I might have missed something, but #924 is open so we probably have not yet a fix merged.
I think you are referring to these files, created when the in-memory buffered is full: coraza/internal/corazawaf/body_buffer.go Line 78 in ec0497a
|
Yes, that's correct. For some reason they are not deleted either. I have files from 23rd of April for example. So what is the actual difference between crzmp* and body*? |
|
Thanks a lot for explaining. I guess the only option for now is to schedule some cron that actively deletes these files twice a day or so. |
Hi,
file: /corazawaf/coraza/[email protected]/internal/bodyprocessors/multipart.go
line: 61
"/tmp/crzmp*" files are never deleted after a POST.
bye Fred
The text was updated successfully, but these errors were encountered: