Fatal errors

  • Resolved juanantonio

    (@juanantonio)


    1 year, 1 month ago

    I am having many fatal error reports in error.logs any info pls ¿?

    [19-Feb-2025 23:09:31 UTC] PHP Fatal error Uncaught InvalidArgumentException: wfWAFAttackDataStorageFileEngine::unpackMicrotime $binary expected to be string with length of 8, received string of length 0 in /var/webs/site/httpdocs/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:963
    Stack trace:
    • #0 /var/webs/site/httpdocs/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(261): wfWAFAttackDataStorageFileEngine::unpackMicrotime()
    • #1 /var/webs/site/httpdocs/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(1232): wfWAFStorageFile->_getAttackDataRowsNewerThan()
    • #2 /var/webs/site/httpdocs/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(246): wfWAFAttackDataStorageFileEngine->scanRowsReverse()
    • #3 /var/webs/site/httpdocs/wp-content/plugins/wordfence/lib/wordfenceClass.php(8972): wfWAFStorageFile->getNewestAttackDataArray()
    • #4 /var/webs/site/httpdocs/wp-includes/class-wp-hook.php(322): wordfence::syncAttackData()
    • #5 /var/webs/site/httpdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    • #6 /var/webs/site/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action()
    • #7 /var/webs/site/httpdocs/wp-settings.php(704): do_action()
    • #8 /var/webs/site/httpdocs/wp-config.php(177): require_once(‘…’)
    • #9 /var/webs/site/httpdocs/wp-load.php(50): require_once(‘…’)
    • #10 /var/webs/site/httpdocs/wp-blog-header.php(13): require_once(‘…’)
    • #11 /var/webs/site/httpdocs/index.php(17): require(‘…’)
    • #12 {main}

Viewing 1 replies (of 1 total)
  • Plugin Support wfmargaret

    (@wfmargaret)

    1 year, 1 month ago

    Hi @juanantonio,

    Thank you for reaching out!

    Based on previous cases of this error message, it appears to be an issue around writing data to our log files. In most cases, this is caused by corrupted file or the hosting environment running out of allowed space. There is also a possibility that the file is not available/permitted to be written to.

    To resolve this, log in via FTP or a hosting file manager, and navigate to your wp-content/wflogs folder. You should be able to delete or rename the wflogs folder or its contents entirely, and Wordfence should try to repopulate it within 30 minutes.

    It’s also worth checking that permissions on your WordPress site’s directories are 755, and that the process owner is www-data if appropriate for your setup.

    If you have persistent problems with this file/folder, you can bypass it 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/ 

    Let me know how it goes!

    Thanks,
    Margaret

Viewing 1 replies (of 1 total)

The topic ‘Fatal errors’ is closed to new replies.