Receiving Fatal Error Message After Last Update

  • Resolved Machine IT Services

    (@machineitsvcs)


    4 years, 10 months ago

    I’m getting these messages in my error log:

    Got error 'PHP message: Unable to save temporary file for atomic writing.PHP message: PHP Fatal error: Uncaught wfWAFStorageFileException: Unable to save temporary file for atomic writing. in /web/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:35\nStack trace:\n#0 /web/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(659): wfWAFStorageFile::atomicFilePutContents()\n#1 [internal function]: wfWAFStorageFile->saveConfig()\n#2 {main}\n thrown in /web/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 35'

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Machine IT Services

    (@machineitsvcs)

    4 years, 10 months ago

    Actually, looks like this was caused by file system lock due to max quota reached. Perhaps there’s a way to check if filesystem is writable first and provide a warning instead of a calling a function immediately that produces a Fatal error?

    Plugin Support wfpeter

    (@wfpeter)

    4 years, 9 months ago

    Hi @machineitsvcs, thanks for getting in touch.

    The reason why we allow this to happen silently in the background is because it takes more resources to check for the presence of a file rather than just attempt to perform an operation and silently ignore the error at the front-end if it’s not there.

    If you foresee persistent problems with filesystem locks due to your host’s max quota rules, this could be avoided entirely by setting Wordfence to write to the MySQLi storage engine instead of a file if you prefer: https://www.wordfence.com/help/firewall/mysqli-storage-engine/

    Thanks,

    Peter.

    Thread Starter Machine IT Services

    (@machineitsvcs)

    4 years, 9 months ago

    I think the confusion is that you said it fails silently, but it does not. It causes a fatal error that prevents the site from loading.

    I will look into the MySQLi storage engine you mentioned. Thanks for that.

    Plugin Support wfpeter

    (@wfpeter)

    4 years, 9 months ago

    Hi @machineitsvcs,

    Ah, yes after checking I noticed that Query Monitor (when installed) flags the silent failures even when WordPress’ $wpdb->suppress_errors(true); is set, however this particular issue is fatal due to the max quota on the server causing the write issue.

    If you or your host are unable to increase the quota, I’m hoping the MySQLi method of logging can assist you. Let me know how you get on with it!

    Peter.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Receiving Fatal Error Message After Last Update’ is closed to new replies.