It is not clear by your message if the problem is happening on WordPress Admin area or something else.
You may want to disable open file cache while doing direct changes to files (what some WordPress plugins may do, although not common - the problem is more frequent when using "remote connection" IDEs like VSCode+SSH extension), depending on how you/the plugins are modifying files (the problem does not happen if your IDE save changes to a temporary file then rename it to the original name instead overwriting directly to the file itself).
- Open file
/etc/nginx/conf.d/tweaks.conf
- comment the 4 lines starting
open_file_cache
(add a #
to the left of them)
- save and close the file
- run
nginx -t && service nginx reload
to reload Nginx
The nginx -t
test will verify no modifications you did will break Nginx on reloading before proceeding.
To revert the changes, just remove the #
comment indicator from the same file and reload Nginx again. However, having open file cache disabled is not much of a concern with the access time of current industry standard SSDs (specially the NVMe) being very low.