Closed Bryce-Souers closed 11 months ago
the precached objects file is one of the few files which will be written in place. Not in a tmp file and then moved on success like most other files. Maybe this could be changed... But until then, if you start a precaching job twice, it will potentially corrupt the file as 2 processes open the same file and write into it. Could this be the case here that for some reason you are starting the precaching multiple times?
I'd say this is fixed with #439
Hi,
There is a rare issue that I cannot seem to replicate.
I have automation that generates configurations and reload every 8 hours by calling "omd reload naemon". The call to this command returned OK, but when I checked the logs:
It starts up, and then fails when it tries to read the objects.precache file.
If it's important, I am running this with the docker image: https://hub.docker.com/r/consol/omd-labs-centos
Any ideas why the precache object would be invalid and how I can avoid this?