• Resolved vikp

    (@vikp)


    I’m getting below errors continuously

    PHP Fatal error: Uncaught InvalidArgumentException: wfWAFAttackDataStorageFileEngine::unpackMicrotime $binary expected to be string with length of 8, received string of length 0 in /code/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:964
    Stack trace:

    0 /code/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(262): wfWAFAttackDataStorageFileEngine::unpackMicrotime(”)

    1 /code/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(1233): wfWAFStorageFile->_getAttackDataRowsNewerThan(Resource id #10, 49261, 5463)

    2 /code/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(247): wfWAFAttackDataStorageFileEngine->scanRowsReverse(Array)

    3 /code/wp-content/plugins/wordfence/lib/wordfenceClass.php(8880): wfWAFStorageFile->getNewestAttackDataArray(‘1683744024.4803…’)

    4 /code/wp-includes/class-wp-hook.php(306): wordfence::syncAttackData()

    5 /code/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)

    6 /c in /code/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 964

    Please help on this

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support wfjanet

    (@wfjanet)

    Hi?@vikp,

    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, login via FTP or hosting file manager, navigate to your wp-content/wflogs folder. You should be able to delete 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,

    Janet

    Thread Starter vikp

    (@vikp)

    Thanks for your reply.

    When i gone through Diagnostics tab i could see that

    Checking if web server can write to?~/plugins/wordfence – NO

    Is it required to make this folder writable

    For security purpose we made these folders with less permission. but symlinks are configured properly

    Please advise

    Plugin Support wfjanet

    (@wfjanet)

    Hi @vikp,

    Thank you for getting back to us.

    That’s right. The folder needs to be writable. The permissions should be set to 755, and the process owner www-data?if appropriate for your setup.

    Thanks,
    Janet

    Thread Starter vikp

    (@vikp)

    Permission for the folder is 755 itself and owner is root

    Still we are getting this error

    Uncaught InvalidArgumentException: wfWAFAttackDataStorageFileEngine::unpackMicrotime $binary expected to be string with length of 8, received string of length 0 in /code/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:964 Stack trace: #0 /code/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(262): wfWAFAttackDataStorageFileEngine::unpackMicrotime(”) #1 /code/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(1233): wfWAFStorageFile->_getAttackDataRowsNewerThan(Resource id #10, 54267, 1565) #2 /code/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(247): wfWAFAttackDataStorageFileEngine->scanRowsReverse(Array) #3 /code/wp-content/plugins/wordfence/lib/wordfenceClass.php(8881): wfWAFStorageFile->getNewestAttackDataArray(‘1685370013.2555…’) #4 /code/wp-includes/class-wp-hook.php(306): wordfence::syncAttackData() #5 /code/wp-includes/class-wp-hook.php(332): WP_Hook->apply_fi

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘getting Uncaught InvalidArgumentException: wfWAFAttackDataStorageFileEngine erro’ is closed to new replies.