You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Indeed, i can reproduce that. Haven't noticed that so far, because we disable the object cache by setting: object_cache_file=/dev/null
Which would be a workaround for you too. The object.cache is usually not required and just a
leftover from the time when guis need to parse that file to acutally display things instead of just using livestatus.
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: