unlink(…): No such file or directory

Hi @babelhalsupport,

What is the file throwing the error? It may point to a temporary or other wflogs file that is either having problems because of permissions that may require a switch to the MySQLi engine instead of physical files, but in some cases we ignore files that are no longer present intentionally.

Are you also using anything like Query Monitor or another tool/plugin to monitor PHP warnings, errors, etc.?

Many thanks,
Peter.

What is the file throwing the error?

Sorry but the error log was already rotated several times, and we do not have the file path anymore.
And the error did not happen since then.

Are you also using anything like Query Monitor or another tool/plugin to monitor PHP warnings, errors, etc.?

We have an own solution for logging some PHP errors in a different log file too.
This log file was also cleared since the error.

Hi @babelhalsupport,

Unlike the setcookie() deprecation message you saw, I can confirm this message is expected and can be ignored.

Errors such as this are often picked up in Query Monitor (or in this case your custom mu-plugin) for our intended silent failures. We sometimes utilize WordPress’?$wpdb->suppress_errors(true);?function or PHP’s?@?in situations we know an error may occur. These tools tend to ignore those whereas they’d normally not show to any customers or their site’s visitors.

There’s no fixed amount of resources we know Wordfence will use on each customer’s server. Therefore, some non-critical situations where it’s more expensive on resources to retry or check for the presence of a file/record first, we simply choose to fail silently and continue.

Many thanks,
Peter.