-
Notifications
You must be signed in to change notification settings - Fork 63
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
naemon reload does not release deleted objects.cache file #462
Comments
Indeed, i can reproduce that. Haven't noticed that so far, because we disable the object cache by setting: |
Perfect, thanks 👌 |
sni
added a commit
to sni/naemon-core
that referenced
this issue
Nov 10, 2024
using fopen opens the object.cache a second time and naemon closes just one afterwards. So with every write of the objects.cache file, one reference will be kept and prevents the file from beeing deleted which finally fills the disk with deleted files. Using fdopen solves the issue, since it just reuses the existing fd.
Took a bit, but should be fixed with #483 |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that naemon keeps previous instances of the
objects.cache
file open when it reloads its config. As a result these cannot be freed in the filesystem and in no time the disk fills up. (our objects.cache is around 450 MiB)When I restart naemon, everything is freed again.
Until recently we were running naemon 1.0.8, with that version this problem did not occur.
I've been running 1.4 for a few months now but until now I restarted naemon on each config change instead of reloading it (cfr. naemon/naemon-livestatus#117 (comment)). That's why I'm only noticing this now.
To reproduce:
The text was updated successfully, but these errors were encountered: