Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hello Matt.

    I realize it’s been a couple months now but, I just wasn’t getting anywhere and spending way too much time chasing down this problem—since I’ve done everything to mitigate this issue, including spending hours and numerous phones calls to the host’s tech.

    My scans are still freezing with “Fatal error: Allowed memory size of 67108864 bytes exhausted.”

    However, I may have found another glitch in WordFence: The error occurs now in “wp-content/plugins/wordfence/lib/wordfenceHash.php” on line 337. When I set an exclusion to skip this file in Options, scans still jam up on the excluded file!

    Weird eh?

    Not only is WF failing on an excluded file, the file belongs to WF!

    Guess it’s time to give up on this endeavor and forget about scanning!

    Thanks for your reply, though.

    -Gurn

    P.S. No “suhosin” found anywhere.

    Hey Ciao,

    I did manage to get that ini_set command to save in wordfence.php but, I am still getting the Fatal Error on scan in the exact same place (line 1129)! I upped it to match the 256M specified everywhere else.

    I ‘spose I could try changing everything to 512 but, since everything has worked perfectly up to a few days ago and this suddenly appeared, I hesitate to continue to chase problems that don’t appear to be, well, me.

    As WF appears to be catching violators just fine, as always, I guess it’s time to give up on scanning and wait until an update is released, to see if that solves the issue.

    Thanks for your help. I will continue to read any follow-ups, in case anyone has another idea.

    -Gurn

    Thanks, WFBrian.

    GoDaddums confirms there is 256M available, which matches the phpinfo.php return.

    I’ve tried using php4, php5 and their “native” php5.4 (5.4.43). I’ve turned off all plugins individually and by temporarily renaming the plugins directory. Between each action, I killed off all php processes.

    I’ve also turned off all comments, just in case that interferes.

    Very frustrating!

    And I should mention I have removed WF, cleared all transient cache and reinstalled WF.

    I’ve set the maximum execution time of each script to 120 seconds, increased the amount of time each script may spend parsing request data to 60 seconds and upped the maximum allowed size for uploaded files to 32MB. With the exception of setting ‘memory_limit = 256M’ in /public_html/php.ini (which I learned here on another thread from some other bright folks), all of the above I did as a tech at GoDaddums held my hand. Unexpected from them, but very nice!

    Speaking of very nice, WF has done a yeoman job of protecting my site since its inception and has never failed me before.

    And maybe I shouldn’t mention this word here but, while I was concerned there was something malicious doing something unsavory, I did DL and install—to make a single scan—that Securi plugin. Once it said “all clear” it was out of there …and I hope WF can be returned to working properly.

    Oddly, this all began just a few days ago without any prodding. That is to say, no new plugins, no changes to other programs, and only one or two posts.

    Your thoughts? Much appreciated.

    -Gurn

    Man, this is kicking my butt, too. It’s been going on for a few days now. I’ve done everything that has been suggested to increase the memory limit and and phpinfo clearly shows I’ve got plenty of memory but…

    ‘ Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 4025073 bytes) in /home/andthatsthenews/public_html/wp-includes/wp-db.php on line 1129’

    …and WordFence is crashing, as you can do the math, at 16.67MB requested.

    So, what now??

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