Title: wflogs/rules.php throwing errors
Last modified: May 21, 2023

---

# wflogs/rules.php throwing errors

 *  Resolved [fewturewebdesign](https://wordpress.org/support/users/fewturewebdesign/)
 * (@fewturewebdesign)
 * [3 years ago](https://wordpress.org/support/topic/wflogs-rules-php-throwing-errors/)
 * We are facing a strange issue, in which **the allowed memory size is exhausted**.
 * >  Allowed memory size of 134217728 bytes exhausted (tried to allocate 2161744
   > bytes) in /wp-content/wflogs/rules.php on line 4456
 * We have enough memory allocated and tried everything possible. 
   Reinstalled the
   plugin and deleted the folder. Tried to refresh the rules manually as well.Can
   anyone help???The line which throws the error is the following:
 * >  )))), new wfWAFRuleLogicalOperator(‘OR’), new wfWAFRuleComparison($this, ‘
   > equals’, ‘Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Firefox/
   > 45.0’, array(wfWAFRuleComparisonSubject::create($this, array(‘request.headers’,‘
   > User-Agent’), array (
    -  This topic was modified 3 years ago by [fewturewebdesign](https://wordpress.org/support/users/fewturewebdesign/).
    -  This topic was modified 3 years ago by [fewturewebdesign](https://wordpress.org/support/users/fewturewebdesign/).

Viewing 1 replies (of 1 total)

 *  Plugin Support [wfpeter](https://wordpress.org/support/users/wfpeter/)
 * (@wfpeter)
 * [3 years ago](https://wordpress.org/support/topic/wflogs-rules-php-throwing-errors/#post-16757384)
 * Hi [@fewturewebdesign](https://wordpress.org/support/users/fewturewebdesign/),
   thanks for getting in touch!
 * You _can_ safely delete the contents of wflogs entirely and Wordfence will try
   to repopulate it within 30 minutes or so, which could be a good first thing to
   attempt just in case they’ve become too large or corrupted in some way.
 * However, an `Allowed memory size of x bytes exhausted (tried to allocate x bytes)`
   error is almost always memory exhaustion occurring outside of PHP somewhere on
   the server. The operating system log files and web server log files will likely
   show if memory is being exhausted somewhere outside of PHP and why. This is usually
   a job for your hosting company’s support channels as they have access to those
   logs, diagnose the source and potentially resolve the problem.
 * Thanks,
   Peter.

Viewing 1 replies (of 1 total)

The topic ‘wflogs/rules.php throwing errors’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

## Tags

 * [wflogs](https://wordpress.org/support/topic-tag/wflogs/)

 * 1 reply
 * 2 participants
 * Last reply from: [wfpeter](https://wordpress.org/support/users/wfpeter/)
 * Last activity: [3 years ago](https://wordpress.org/support/topic/wflogs-rules-php-throwing-errors/#post-16757384)
 * Status: resolved