• Resolved Stingraynut

    (@stingraynut)


    The error_log.txt in public_html is filling up very quickly with WF errors. I deleted it today and within an hour it had 480mb of data! very quickly it gets so full, around 43 GB that the site slows down and then stops working.
    this has been happening for many months and during that time I’ve kept everything up to date, yet the errors contimnue and are now happening faster.
    I have searched the forum and found suggestions to rename the file in wp_content/wf_logs, which I’ve just done,
    here is a typical error

    [28-Sep-2018 04:29:55 UTC] PHP Fatal error: Uncaught exception ‘InvalidArgumentException’ with message ‘wfWAFAttackDataStorageFileEngine::unpackMicrotime $binary expected to be string with length of 8, received string of length 0’ in /home/aawcomau/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:771
    Stack trace:
    #0 public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(226): wfWAFAttackDataStorageFileEngine::unpackMicrotime(”)
    #1 [internal function]: wfWAFStorageFile->_getAttackDataRowsNewerThan(Resource id #22, 75601, 491)
    #2 public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(1038): call_user_func(Array, Resource id #22, 75601, 491)
    #3 public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(211): wfWAFAttackDataStorageFileEngine->scanRowsReverse(Array)
    #4 public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php(7118): wfWAFStorageFile->g in /home/aawcomau/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 771
    [28-Sep-2018 04:31:21 UTC] PHP Fatal error: Uncaught exception ‘InvalidArgumentException’ with message ‘wfWAFAttackDataStorageFileEngine::unpackMicrotime $binary expected to be string with length of 8, received string of length 0’ in public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:771

    Please can anyone tell me what is causing this and how to fix it?
    thank you
    Rob

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hi @stingraynut!

    That sounds like a good guess. When you renamed the wflogs folder a new one should have been automatically created. Are you still getting these errors in logs after you did that? If you’re not getting them anymore, the cause would likely have been a corrupt config.php file in wflogs.

    Thread Starter Stingraynut

    (@stingraynut)

    Unfortunately renaming the wflogs folder hasn’t fixed the problem. In less than 24hrs the error log is now 993mb and too large to open.
    I’ll delete it and check after an hour and see what the error log shows

    Hi @stingraynut,
    Sorry I haven’t gotten back to you earlier. I’ve looked at the code to get a better grasp of what we’re doing right here and it doesn’t seem like you’re using the most recent version of Wordfence, or? If you can let me know the Wordfence version that would be great.

    What is happening is that the Firewall is trying to read data from your wflogs, I’m pretty sure it’s the attack-data.php file but the data it’s getting back is incorrect. Why it’s happening is harder to say. Knowing PHP version would be good as well. If you’d rather just activate Wordfence quickly and send me a diagnostics report, I should be able to get all that info via that. You can send a diagnostics report from Wordfence Tools > Diagnostics at the top of the page. If so, send it to [email protected].

    Spiceweb

    (@spiceweb)

    Was there a general solution to this issue?, I am getting this error currently on one website, so have deactivated WF, thanks

    wfasa

    (@wfasa)

    @spiceweb,
    are you using the most recent version of Wordfence?

    wfdave

    (@wfdave)

    Hi @stingraynut,

    We haven’t heard back from you in a while, so I’ve gone ahead and marked this thread as resolved.

    Please feel free to open another thread if you’re still having issues with Wordfence.

    Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Errorlog filling up with WF errors’ is closed to new replies.